yashsingh1/xdaforums huggingface dataset:
[One (M9) Android Development] Claymore1297:
I uploaded another build. can someone with himawl test this one and report.

A log is welcome as always ;)
[One (M9) Android Development] lithophone:
Claymore, I know the info is out there already, but for the sake of expediency, it would be nice if you could quickly tell me how to grab a log so that I can test this for you right now. Downloading the file now.
[One (M9) Android Development] Claymore1297:
adb logcat > logfile.log
[One (M9) Android Development] lithophone:
Thanks for helping me out with that info. Still doesn't work. I attached a log for you. Hopefully it's of some use. Thanks again for everything.
[One (M9) Android Development] tiratored:
Guys, I checked. On version 2019.12.23, the SIM card does not see. Version 2019.11.09 works fine on HIMA_WHL. Afterwards, I installed version 2019.12.23 on 2019.11.09 - the sim card works. I installed version 20200115 on it - the sim card does not work. That is, since version 2019.12.23 there was a problem.

Version 2019.11.09 is fully operational.
[One (M9) Android Development] tiratored:
And how is it for you: after I installed the latest firmware, I can’t format partitions via TVRP. I can’t upload the log, because the recovery does not see the file system.

And I can neither reflash, nor erase, nor format. And the firmware does not see the sim ....

The firmware itself works, it sees the flash drive, everything except the SIM card works!

As a result of attempts to do something - the firmware stopped loading, TVRP stopped seeing everything.

I had to format through RUU. It helped.
[One (M9) Android Development] Biggie_still:
Please guys I need to make a full backup of my ROM and data so I can test out the lineage 17.1..how can I do it successfully???

Last time I did this I was unable to restore both system,data, vendor.
[One (M9) Android Development] tiratored:
I have never been able to with the transition to 10.0
[One (M9) Android Development] k4y0z:
This is likely caused due to the quota feature enabled in the newest release and an incompatibility with TWRP.

CaptainThrowback is aware and will release an updated TWRP soon.

Backup/Restore works fine here, select "System Image" and "Vendor Image" instead of "System" and "Vendor"

EDIT:

CaptainThrowback has just released the new TWRP: https://github.com/CaptainThrowback/android_device_htc_hima/releases/tag/3.3.1-0_CPTB-20200116-02
[One (M9) Android Development] Biggie_still:
Thank you so much
[One (M9) Android Development] lithophone:
I'm confused as to what the new TWRP fixes. Is it the SIM card issue, or partition issues that tiratored was experiencing?
[One (M9) Android Development] k4y0z:
No, it doesn't fix the SIM card issue. It fixes the partition issues.

Check CaptainThrowbacks release notes on the github page.
[One (M9) Android Development] tiratored:
It never worked! Film a video? It backs up and restores without problems. But the firmware does not work after that. It definitely started recently. I think at the same time when the problem with the SIM card started. 99% that the way it is.
[One (M9) Android Development] k4y0z:
That is what happens when you backup "System" and "Vendor" instead of "System Image" and "Vendor Image"

It's related to selinux, so it probably started after selinux was switched to enforcing.
[One (M9) Android Development] Biggie_still:
Okay I got the new TWRP VERSION flashed it but was unable to back up system image, I only backed up data..
[One (M9) Android Development] k4y0z:
Make sure your SD-card is exFAT formatted not FAT32 if you are backing up to external storage.

FAT32 doesn't support files larger than 4GiB
[One (M9) Android Development] Stosan:
Com.Android.Phone has stopped

Hi claymore,

Thanks for all you do.

the AICP build from 20190105 does not load mobile network on htc one m9 verizon, it shows com.android.phone keeps stopping
[One (M9) Android Development] tiratored:
I tried to do "System Image" and "Vendor Image" - the result is the same. Even when I restore the "data" to a clean firmware.
[One (M9) Android Development] k4y0z:
This is a kown issue, we are looking into it.

Also please don't quote the entire OP.

Please provide logs for backup and for restore.

---------- Post added at 05:33 PM ---------- Previous post was at 05:10 PM ----------

So you are saying dirty-flashing 2019.12.23 over 2019.11.09 the SIM card still works.

Could you try flashing a current build over 2019.11.09 (after verifying that works) and see if that still works?

Also, have you tried clean flashing a current build?
[One (M9) Android Development] lithophone:
I had tried clean flashing the 20200115 build, but it did not work.
[One (M9) Android Development] k4y0z:
Can you try flashing 2019.11.09, make sure that it works.

Then dirty-flash 2020.01.15 over it and report?
[One (M9) Android Development] lithophone:
I get what you're looking for. I saw tiratored's analysis. Not sure I'll be able to today or the next couple days because of work. But if I happen to get a chance, I will give it a whirl. Unless tiratored is able to.
[One (M9) Android Development] tiratored:
I tried everything.

1. Clean flashing 2019.11.09 the SIM card works

2. Clean flashing 2019.12.23 the SIM card dint works

3. Dirty-flashing 2019.12.23 over 2019.11.09 the SIM card works

4. Clean flashing current build the SIM card dont works

5. Dirty-flashing current build over 2019.11.09 the SIM card dont works and TWRP stopped seeing the file system.

Since I already had the trouble of reinstalling everything! Due to non-working recovery and any errors - I will not test anything for the next few days. There is no inspiration.
[One (M9) Android Development] k4y0z:
For the TWRP issue you mentioned you need to update TWRP, as I have announced here.

For your recovery-issues, you'll need to provide logs, as it works without issues here.

We won't be able to fix the issue without testers, since neither of us has a CDMA-variant to test ourselves.
[One (M9) Android Development] tiratored:
There are no errors there. The error is coming out of the system. She does not start. Everything is clean and error-free in the TWRP log - recovery is complete.

I am currently on LOS 17.1 current build. Everything works and so far suits me. If there is time, then maybe.
[One (M9) Android Development] k4y0z:
[MENTION=9537743]tiratored[/MENTION] [MENTION=7997936]lithophone[/MENTION] (or anyone else with a CDMA-variant).

I have uploaded two debug builds here

If you could please test these and provide logs.
[One (M9) Android Development] lithophone:
I can give it a try, but it probably won't be for another couple days.
[One (M9) Android Development] tiratored:
Okay. I'll try and write about the results. I will also do logs with backup and recovery.
[One (M9) Android Development] tiratored:
https://drive.google.com/drive/folders/17MYls0k-2t_jz9Sn83XLpxAMEBxpIx9g?usp=sharing

On both firmwares, I had to manually configure the network type and create an APN with the wrong address - everything works. SIMINFO_USING_SUBID has more choices in network types.
[One (M9) Android Development] k4y0z:
#### New build is up!! ####

the build is containing mainly the following:

- Quota feature enabled (read note below)

- Fix NFC-HCE (Google Pay etc)

- Fix himawhl/himawl SIM issue (hopefully)

- FlipFlap display threema notification

- minor fixes

AICP features added:

- Global system fonts

- WPS

- Settings Avatar

- Custom lockscreen clocks

- Launcher doubletap actions

Enjoy!

Important notes about this build:

Update TWRP, otherwise data and internal sdcard cannot be mounted in TWRP.

If you upgraded from the previous release and get constant "com.android.phone" crashes:

Boot into TWRP (make sure you have updated) and run:

Via PC with adb:

adb shell rm /data/user_de/0/com.android.providers.telephony/databases/*

Via TWRP terminal

rm /data/user_de/0/com.android.providers.telephony/databases/*

You can also delete the files manually within TWRP Filemanager
[One (M9) Android Development] ayoobelmasry:
My device is himaul, TWRP is at the same build as is in the url in page 1 of the thread. Now I get the com.android.phone crashes. I tried to run the script that you mentioned from within TWRP terminal but it returns " sh:adb not found".

The previous build of the ROM was working on my device with no single occurrence of this problem. Should I go back to that build?

I removed files using the file manager in TWRP and is OK afterwards. Thank you.
[One (M9) Android Development] Biggie_still:
My phone was just working perfectly until I flashed this last build. Now I'm getting simcard not dictated..
[One (M9) Android Development] Claymore1297:
have you installed the latest 2 testbuilds I uploaded - if yes, please follow the installation instruction of this build.
[One (M9) Android Development] tiratored:
With hima_whl, you must manually configure the network type.

Отправлено с моего 0PJA2 через Tapatalk
[One (M9) Android Development] Claymore1297:
so you can confirm, that this build is working too on verizon variant?
[One (M9) Android Development] Biggie_still:
The 20200111 build is the one I was on before I flashed this last build.. however I've reverted back.

My device is himaul

---------- Post added at 12:52 PM ---------- Previous post was at 12:28 PM ----------

In the AICP download site there's a new folder called debug, can I flash it?
[One (M9) Android Development] Claymore1297:
I think the 20200111 is one of the affected one, so you have to follow the instructions or you have to stay on this build.

A clean flash will also fix this.

No the debug-builds will fail too.
[One (M9) Android Development] Biggie_still:
I clean flash this last build on my himaul still simcard not dictated..
[One (M9) Android Development] Claymore1297:
logs please

EDIT: anyone else?
[One (M9) Android Development] Biggie_still:
I can't get log for you now as I've flashed lineage 17.1
[One (M9) Android Development] tiratored:
No.

logcat
[One (M9) Android Development] Claymore1297:
we've uploaded you to more test-builds (20200120) can you test both and report with logs. thanx :)
[One (M9) Android Development] tiratored:
I'll check it tomorrow. It's time to sleep.

Надіслано від мого 0PJA2, використовуючи Tapatalk
[One (M9) Android Development] Biggie_still:
Okay Julian I've get logs for you one of which Android dialer was installed and one of which Android dialer was removed..

I believe the problem is with the Android dialer, immediately I removed it and reboot simcard was not installed, as I reinstalled it I was back on line.
[One (M9) Android Development] Claymore1297:
we just had with [MENTION=9507104]MirrorMan3D[/MENTION] same issue here and the provided fix by [MENTION=7104332]k4y0z[/MENTION] (adb-command) solved it.
[One (M9) Android Development] Biggie_still:
For me no need I just disabled it and installed Google dialer, however I updated Google camera from playstore now I'm having FC issues. What can I do please.
[One (M9) Android Development] Claymore1297:
nothing - gcam don't work with this device
[One (M9) Android Development] Claymore1297:
[MENTION=9350973]All[/MENTION] verizon-users:

please test and report those 2 builds - otherwise we're not able to fix the issue!
[One (M9) Android Development] cyned:
WiFi issue

WiFi stopped working after dirty-flash latest build !!! Any Advise.

Also is there any way to get IR working ???
[One (M9) Android Development] Claymore1297:
wifi works here.

IR works as expected - answer has been given here https://xdaforums.com/one-m9/orig-d...oject-14-0-t3860594/post81270115#post81270115
[One (M9) Android Development] k4y0z:
"SURE" remote also works well.
[One (M9) Android Development] Biggie_still:
Im guessing this new build is for only Verizon user's
[One (M9) Android Development] tiratored:
Sorry, there was no time before.

Another remark is that the time in flip-flap is not updated.

LOGCAT
[One (M9) Android Development] Claymore1297:
did one on the build had a simcard found?

and about FlipFlap - this is correct, on LOS the same btw.

EDIT: I'm asking, because I see in both logs not the crash anymore
[One (M9) Android Development] tiratored:
In both build everything is fine.

It is necessary to eliminate the hang of time in a flip-flap. And the applications of my account from the cloud are not synchronized.
[One (M9) Android Development] Claymore1297:
will provide you soon another one to test... just let me know.

Yes it is ... I found the bug some month before... but seems noone use flipflap ... but I do since some days now ;)
[One (M9) Android Development] DaveedDB:
Is that the app for the flipcase ?
[One (M9) Android Development] Claymore1297:
I uploaded another debug build ... please test - himaul-users can install this too.

Enjoy!

EDIT: yes FlipFlap is DotCase
[One (M9) Android Development] ayoobelmasry:
The size of this Debug build is 2GB, while the size of the current unofficial build is nearly 0.5 GB, are they very different in a way that the Debug build is much better?
[One (M9) Android Development] Claymore1297:
no, please recheck - all the builds have the same size.
[One (M9) Android Development] ayoobelmasry:
Sorry, I miss the fact that the debug folder size is 2gb not the zip file itself
[One (M9) Android Development] tiratored:
Everything works.
[One (M9) Android Development] Claymore1297:
I moved the build into the regular hima-directory, so everybody can use it.
[One (M9) Android Development] MB242:
Hey, can you please tell me how is the sound compared to orignal ROM with BoomSound?

Thank you.
[One (M9) Android Development] Claymore1297:
never run the orginal rom, but due we have JamesDSP included you can modify to your needs.
[One (M9) Android Development] Claymore1297:
GAPPS Official

OpenGapps just released an official version.

I flashed the nano on my daily driver and all seems to work.

Will update OP.

Enjoy!
[One (M9) Android Development] ayoobelmasry:
I just found out that NFC does not work on this ROM although you can enable it, also you can enable Android Beam, however the communication is not established.
[One (M9) Android Development] MB242:
Just tried connection with OnePlus 7 with no issue.
[One (M9) Android Development] ayoobelmasry:
This is a bug report that has been generated automatically without my input. I believe that was meant by the developers to happen to improve their work. Here is the link:

https://drive.google.com/file/d/1-fBkxUhUE8uhchkLKRShII-C6hLjOdLU/view?usp=drivesdk
[One (M9) Android Development] Bu'dge:
Is there anyone having their microphone being constantly used by the Google application?

And then whenever make calls the receiver constantly saying I can't hear you I can't hear you because the sound is low.....my microphones are working well
[One (M9) Android Development] Claymore1297:
#### New build is up!! ####

the build is containing mainly the following:

-February ASB's

-latest AICP sources

Enjoy!
[One (M9) Android Development] Bu'dge:
Having WhatsApp audio playback issues on himaul.

It's like WhatsApp can't access the external speakers so the sound does not play but works fine when you put the phone to your ear
[One (M9) Android Development] Claymore1297:
thanks for reporting.

Uploaded a build with this issue fixed.
[One (M9) Android Development] lithophone:
Hey Claymore,

United States Verizon himawl user. Finally got around to checking out your new builds. Unfortunately I didn't have the same luck as tiratored. I wasn't able to get my mobile network settings to work properly. Had to go back to AICP 14.

I did a clean flash and booted into the system for the first time. On the first screen of the setup section, I got one of the "bad SIM" messages I had in the past, but it went away after a few seconds--"SIM card isn't supported. This phone is currently locked to another carrier. You'll need to use a valid SIM card. Once you insert your SIM card, it may take a few seconds to activate."

When I finished the setup and got to my homescreen, I noticed that I didn't have a mobile connection. I went to my mobile network settings and found some incorrect things. I fixed them to be--Preferred network type - Global; and CDMA subscription - RUIM/SIM. I attempted to change APN to Verizon, but instead of Verizon, I only saw 4 Sprint APNs listed. I couldn't add Verizon manually, but I don't think the Verizon SIM card allows that. I tried toggling the settings and rebooting a few times, and eventually I was able to see Verizon listed as an APN. I then had an LTE connection, but it reverted to a roaming connection on a Sprint APN after a few minutes. I could not get my settings to stick and work.

I also have to say that ever since you merged the himaul/himawl builds, I also encounter this same problem, although only briefly, when I update to the new weeklies. I am simply able to toggle the mobile network settings and they work fine. Verizon is always listed in the APNs--I never see Sprint. Not the case with the new AICP 15.

I've attached logs from after 2 reboots in AICP 15 where I was trying to get my mobile settings to hold. I think in logcat_1 I was connected properly to the Verizon network for a brief time. Hopefully these are of some use to you.

Sorry I don't have a lot of free time to check these more frequently, but thank you for everything that you do!
[One (M9) Android Development] Claymore1297:
I wonder, if LOS 17.1 builds work for you.

But this all don't sounds to me, like the issue we had before.
[One (M9) Android Development] WizzTech:
Hello,

On first login AICP shows an unlock patern of 3x3 but my unlock is on a 6x6 grid, unsure if I'm missing something (is there a way to swap to 6x6? on LOS 16 there are grid options underneath on the boot screen), but otherwise warning people to swap to a 3x3 before flashing.

I'm gonna try flashing my backup, swaping pattern and then flashing this again.

PS: [MENTION=8276284]Claymore1297[/MENTION] and team, thank you for your hard work and helping keep an old phone not obsolete. :)

Edit: Well my plan didn't work. Formatted everything so no unlock pattern is now required.
[One (M9) Android Development] lithophone:
I think I'll get some time to try LOS later on today. It looks like I can use the same TWRP, GApps, and Magisk as AICP, so I'm in good shape. Will report back.
[One (M9) Android Development] Claymore1297:
uploaded another build. [MENTION=7997936]lithophone[/MENTION] please test this one and report.

for all others:

this also includes:

-partial screenshot

-game mode

-new screen record feature

Enjoy!
[One (M9) Android Development] Claymore1297:
uploaded another build.
[MENTION=7997936]lithophone[/MENTION] please test this one and report.

for all others:

this also includes:

-partial screenshot

-game mode

-new screen record feature

Enjoy!
[One (M9) Android Development] MB242:
Very useful, thanks.
[One (M9) Android Development] lithophone:
Will test later on today and report back.

Checked Lineage yesterday. Worse luck with that. Install in TWRP was fine, got to first page of LOS setup, but I couldn't get any farther than that. Twice I got a "Shutting Down" message within a few seconds, and then it would reboot into TWRP. Once I was able to press Start on the first page of setup, but I got the "Shutting Down" right after that. Never able to get to homescreen, and therefore not able to capture any logs. Unless there is another way I don't know about. I included a TWRP log from after the last "Shutting Down," but doubt it's of any use.

Then tried AICP one more time. I found I was able to access the Verizon network briefly if I did these steps--Preferred network type - LTE; System select - Automatic; CDMA subscription - RUIM/SIM; then reboot phone. After reboot I had a Verizon LTE connection, but within a minute, it lost these settings, showed I was roaming, and only had Sprint APNs listed. I grabbed a log after this happened.

Then tried LOS a second time. After install, I actually avoided "Shutting Down" for a few minutes and was able able to complete setup and get to my homescreen. Wasn't able to get any farther than that in my attempt to get logs. Phone rebooted into TWRP. I restarted the system twice, got to my homescreen each time, but immediately got "Shutting Down." Unfortunately no LOS logs.

Attached is the one TWRP log from after LOS shutdown, and one AICP log after Verizon LTE connection reverted back to roaming with Sprint APNs.
[One (M9) Android Development] Claymore1297:
well LOS-issue is known and fixed now, and should not relevant here ;)
[One (M9) Android Development] lithophone:
I keep trying out all these builds just as new bugs are being introduced. Jeez. But cheers to you for being on top of all the reporting and your prompt fixes.
[One (M9) Android Development] WizzTech:
Got the latest build working. My google drive backup is now a goner since my pattern was on a 6x6 by and google only prompts u on a 3x3... live and learn live and learn!

On the home page there's a clock and calendar, I can't seem to get rid of it (added and removed other widgets with success).

What am I missing?

Cheers.
[One (M9) Android Development] Claymore1297:
you can customize this in launcher configuration.
[One (M9) Android Development] WizzTech:
Disabling "At a glance" seemed to work. Cheers.
[One (M9) Android Development] lithophone:
Any idea why I can't connect to my WiFi networks, even though they are showing up and I am entering the password correctly?

Figured you might have a quick answer before I go through reboot processes and tests and grab logs.

But Verizon LTE is working correrctly!
[One (M9) Android Development] Claymore1297:
so your issue is fixed? nice!

About wifi: no, works here fine. mybe a log could help.
[One (M9) Android Development] lithophone:
Tried forgetting WiFi network, re-adding, updating password, toggle WiFi on/off, restart phone, reset network settings under Settings > System. Wiped everything, re-flashed, and tried all the above again. Nothing.

***EDIT***Also restarted router.

But Verizon LTE network connection settings all stay and work fine. Didn't have to touch anything there.
[One (M9) Android Development] Claymore1297:
can you please try in selinux permissive mode
[One (M9) Android Development] lithophone:
How do I do that?
[One (M9) Android Development] Claymore1297:
adb root

adb shell setenforce 0
[One (M9) Android Development] lithophone:
setenforce: Couldn't set enforcing status to '0': Permission denied
[One (M9) Android Development] Claymore1297:
yes you need root - thats the first command, which is doing this ;)
[One (M9) Android Development] lithophone:
I have Settings > System > Developer options > Root Android debugging on.

I have Magisk Settings > Superuser > Superuser Access to Apps and ADB

I never got a Magisk prompt to allow Superuser for ADB, nor do I see ADB listed under Superuser apps as not having Superuser access.

Running out of time before I have to leave for work...
[One (M9) Android Development] Claymore1297:
I can upload you a test-build in 10 mins if you want
[One (M9) Android Development] lithophone:
That works for me if you want, but I still won't get to test it for a few hours. If you want to talk me through the permissive thing, I can do it that way. Sorry to be asking you how, but it saves me a lot of time (of the little time I have) in trying to help you out. And I want to do what I can to help. Thank you so much for everything.
[One (M9) Android Development] Claymore1297:
you only need to flash the build - maybe it is fixed ... we will see. WIll just replace the current build.

EDIT: build replaced.
[One (M9) Android Development] lithophone:
OK, got around to testing the new build. Everything appears to work properly. I did it at work on a different WiFi network, but I had no problem connecting. Verizon LTE still working. I wasn't quite prepared to do a full migration, so I'm currently back on AICP 14. I will move over completely tomorrow morning. Hopefully I won't have any problems then.

I can't thank you enough for all your help with everything.
[One (M9) Android Development] Claymore1297:
Thanks for helping fixing the verizon-issues :)
[MENTION=9537743]tiratored[/MENTION] can you also check and report, if this fits for you?

If there are any sprint-users - please test and report.