yashsingh1/xdaforums huggingface dataset:
[One (M7) Android Development] grishaiozhig:
My carrier is Vodafone UA (ex. MTS) but tge bug is still present i cant switch to 2G too, even via service menu (about>phone information), whatever i chose (wcdma, lte, gsm, even settings that are not supported neither by the phone nor by carrier) the phone still operates in HSDPA mode. So none of mobile network settings works really, this may be the reason for no LTE..

Also, one XDA member recently wrote me in PM, that Ukrainian phones come with radio modules with letter "D" on end and lack LTE support, though my module version ends on "L", and i perfectly know that this m7 is UACRF and had lte option on stock firmware (still, lte in Ukraine came 5 years later, but nevertheless)

What can I do to help you (and hope me too) find the reason?
[One (M7) Android Development] grishaiozhig:
Upd: here come 2 screenshots with 2G and LTE (recommended) options, and clearly seen in the top bar that M7 still operates only in HSDPA, and cares no much whatever i want from it.....
[One (M7) Android Development] crownvn:
what is your devise M7? U or UL

my device is U . the chip don't support LTE although ROM have LTE. u can check here

https://www.upsieutoc.com/image/info-m7.G8pGlC
[One (M7) Android Development] grishaiozhig:
My m7 is PN07100 which is not even on the list.

Also model on the phone is 801n, so my is UL with lte...
[One (M7) Android Development] cannonleo:
can this rom work on htc m7 wlv verizon 4glte, and is the last build the latest and most stable

finally am still yet to understand the concept of magisk, does it mean i cant flash the rom the way i know with su in built.

my device is s-off with twrp installed

help a noob please please
[One (M7) Android Development] icxj1:
Be sure to download latest m7vzw. No more built in su. Flash rom, gapps, & latest magisk 18.0 stable. Bug list is at beginning of thread.
[One (M7) Android Development] ggalaj:
M7+M7vzw+M7spr AICP-13.1-O 8.1 UNOFFICIAL BUILD

Happy New Year 2019!

HTC One M7 with AICP-13.1 ROM is the best.

Greetings for the creator.:laugh:

[
[One (M7) Android Development] TacoLoco:
Also a happy new Year from me, keep up the great work, if you want :D

Maybe you could try to build Pie as Oreo is running stable ;)
[One (M7) Android Development] cannonleo:
I downloaded the latest build for sprint, installed with gapps with no issues Got trouble at startup as

Rom spends 5 minutes installing then phone reboots

What do i do
[One (M7) Android Development] icxj1:
Are you sprint or verizon? And I see you do not mention flashing magisk.
[One (M7) Android Development] icxj1:
I have everything ready, & have compiled a few builds. Unfortunately I need to upgrade the processor in my PC. There are a few errors that I have bypassed in order to get a successful build, but it leaves me with just a boot animation. I have to figure out what processor I can use or maybe even have to upgrade to new PC. Bad thing is that that takes money.
[One (M7) Android Development] sudowtf:
Thank you OlivrD, solved this for me too
[One (M7) Android Development] TacoLoco:
Can you give me details on your Hardware? Then I can suggest you a reasonable upgrade.. Maybe we can also collect a few $ to help you with your PC..
[One (M7) Android Development] icxj1:
I will send model numbers tonight. It is a Toshiba satellite, there are so many different models, makes it hard to find what is available. Thanks!

Toshiba Satellite L655-S5146 model # PSK2CU-0Q001T

Processor Intel Pentium(R) CPU P6200 @2.13x2
[One (M7) Android Development] TacoLoco:
https://www.youtube.com/watch?v=8P9UWX87cYA

An i7-620M or 640M should work (socket 988).. Costs about 40-50 Euro.. But I don't know if the cooling system will handle it under heavy load.. Thougt you had a Desktop PC ;)
[One (M7) Android Development] samhhmobil:
[MENTION=7327102]icxj1[/MENTION]

Just going back several weeks to an old "issue" I told you about.

The "timing" issue... some games are running awfully slow. I tested it with "Frozen Bubble". You remember?

Yesterday, I installed LOS 15.1 (official nightly release, it's Oreo 8.1) on a Sony Xperia-Z (yuga). It's a totally different platform and system, Oreo is running absolutely stable and clean.

But — tada — Frozen Bubble is there even extremely slow!

So... FORGET about this issue, it's either very deep in the Oreo-sources, or it's a bug (incompatibility?) in the app(s).

JFYI, and many thanks for your work,

best regards,

samhhmobil
[One (M7) Android Development] Tornados911:
Please help

TWRP-3.2.1-0

Install aicp_m7_o-13.1-UNOFFICIAL-20181218 and open_gapps-arm-8.1-pico-20190104

Install OK

I turn on and bootloop!

Please help
[One (M7) Android Development] daywalk3r666:
flash magisk 18.0
[One (M7) Android Development] Tornados911:
Thanks. It works great :)
[One (M7) Android Development] Habte:
Guys is it OK if I dirty flash the latest build
[One (M7) Android Development] icxj1:
Yes. If any issues, uninstall magisk then reinstall.
[One (M7) Android Development] Habte:
hey my phone freezes while setting pattern lock i hard rebooted it and the when i try to unlock it freezes again is there a way to fix it
[One (M7) Android Development] icxj1:
Not sure, but I think reports say wait for it to unfreeze. Up to 5 minutes? Look through thread, there should be a few posts about it.

Grab a log when you get unlocked.
[One (M7) Android Development] cannonleo:
Dont really know much about magisk plus i can see a link to download the zip

I get a bootloop both on the sprint spr and verizon vzw versions
[One (M7) Android Development] icxj1:
You need to flash magisk, something in the last security update is causing bootloop with selinux enforcing unless rooted.

https://xdaforums.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445/page5
[One (M7) Android Development] icxj1:
January 2019 builds are uploaded. Same bugs as before, Test hands free bt call for sound bug. I need a log for lockscreen freeze bug if anyone can catch it. Remember clean flash needs magisk, & if bootloop on dirty flash force recovery uninstall magisk, reboot back to recovery then reinstall magisk. Make that backup first!

m7ul += https://www.androidfilehost.com/?fid=11410963190603897577

m7vzw += https://www.androidfilehost.com/?fid=11410963190603897663

m7spr += https://www.androidfilehost.com/?fid=11410963190603897693
[One (M7) Android Development] daywalk3r666:
thx for the update. no problem with dirty flash and magisk
[One (M7) Android Development] BeatB:
Thanks for the update. Clean install worked without any problem.

Unfortunately bluetooth microphone bug is still present.

Still the best Rom for this phone ;)

Gesendet von meinem One mit Tapatalk
[One (M7) Android Development] mily-manson:
TNX

TNX icxj1,

i do clean flash but loop in bootloader and after uninstall magisk then reinstall its seems to be OK.

but i cant see settings icon on notification popup ! it be in before update version and is very useful.

and after startup android i have error message like before update. ( my phone is M7)

ill check another things and post later.
[One (M7) Android Development] ADJQ:
Hey i know this probably being ask somewhere already, but i could not find it.

after flashing the ROM m7 version

and flash GApps

then i went ahead and restart the phone and the phone just keep booting for a long time and i could not find what the issues is

i clearer the cache

i reflash the ROM

i wipe everything and reflash the ROM

but still nothing is working
[One (M7) Android Development] BeatB:
Did you install magisk? If not that's the reason.

Gesendet von meinem One mit Tapatalk
[One (M7) Android Development] ADJQ:
hah yeah ! thank you for your help :D

but unfortunately there is another issues

when im using the phone after awhile after boot

the network connection seems to be all turned off

the sim is not detected

and the WIFI is still scanning , the option is there but i cant connect it

it worked right after all the initial setup is done and after that nothing

sorry for the trouble , and thank you for the help. it worked
[One (M7) Android Development] icxj1:
Every once in awhile after a reboot if sim is not detected, turn airplane mode on for a few seconds then off. Or eject sim & reinsert.
[One (M7) Android Development] daywalk3r666:
[MENTION=7327102]icxj1[/MENTION]

i had a lookscreen freeze.i grab a logcat over adb.hope this was the right one

https://drive.google.com/open?id=183-_CNqMEcJoagyHUA8Wl18EGNv5vAvP
[One (M7) Android Development] ADJQ:
no mobile network despite the logo showing 3g but there is a cross in the signal strength sprite

sorry if i just sounded annoying , would be glad if someone help me :D

thank you all for all the help
[One (M7) Android Development] deC9r:
The first boot after an os / gapps install takes up to 10-20mins. Try it again and be patient. I think it's because the cache gets written.
[One (M7) Android Development] samhhmobil:
Please excuse me, but... NO!! This is not correct!

All the times a new install of THIS Rom (either new install or dirty flash) on an international M7UL after erasing cache/dalvik did not waste more time as 2 or 3 minutes! And I made that very often (at least with each update of these builds here).

Never before I had to wait 10minutes (or more).

That sounds in my ears that there are hardware issues, and that cannot be fixed by any kind of software.

Just my 2¢,

samhhmobil

PS

My third M7 got a new battery now two days ago, now all three devices are running without any trouble from the hardware-point-of-view. :)

And this is sent to you from my Xperia-Z running official LOS 15.1 without any issues.
[One (M7) Android Development] gehess:
Magisk modules can slow things down on boot.
[One (M7) Android Development] samhhmobil:
[MENTION=7327102]icxj1[/MENTION]

Hi,

just another question...:

Do you know, why faceunlock is missing in "smart lock" in the settings (in Oreo 8.1)?

"facedetect" and "faceunlock" are installed with OpenGapps nano, but it's not available in "smart lock" (with Nougat 7.1.2 it did work flawlessly).

It's not a bug of your work here, it's missing too in other Oreo-Roms, such as LOS 15.1.

But maybe, you know why??

Thanks again for your work,

samhhmobil
[One (M7) Android Development] icxj1:
Thanks for the info. No I do not know. I just assumed it was because of our camera. I will ask a couple Devs & see if I can come up with an answer.
[One (M7) Android Development] daywalk3r666:
i don't know if this a bug or rom rated.

swipe don't worked with the aosp keyboard.

thx in advance
[One (M7) Android Development] Pat603xx:
Hi Guys. How is average battery consumption with this ROM's version? Greeting
[One (M7) Android Development] samhhmobil:
A few days ago I wrote:

I have to apologize, I was wrong with this.

My experiences were with earlier builds.

And even with dirty flashes of new builds on a running system. Even with Cache/Dalvik erased, it took only a very few minutes.

But... ... ...

I tried for testing purposes now a complete clean new install of the latest build:

All partitions in TWRP are newly formatted.

Even data partition (internal storage) was newly formatted.

The Rom-Zip (and Magisk, and Gapps-nano) was copied into the clean new data partition.

Rom, Magisk and Gapps are installed with TWRP.

And..... in this scenario it took awfully long to boot.

10 minutes, 20 minutes, 30 minutes,...

now I did leave my desk.

I came back another half an hour later... and tadaaa, the system was up and running again.

So... for a clean freshly newinstall it took 30 to 60 minutes for the first boot, with the latest build.

But... why? Earlier builds did install much faster.

So long,

samhhmobil
[One (M7) Android Development] Earnie0815:
After your post i tried it again and after 1h20min it's still in booting process! I did an clean install with Rom, Gapps and Magisk v18!

Edit: after 1h30min i turned the Phone off and on again and now it boots without any problems!
[One (M7) Android Development] samhhmobil:
That sounds strange...

samhhmobil
[One (M7) Android Development] cannonleo:
i want to thank you immensely for the work youve done on the M7 and giving me proper guidance on the processes of installing this rom, after your response on magisk installion, i had to reflash back to my old rom viper 9.0.0 and oh yes i use a verizon htc htc m7 wlv

i installed the build of 18/12/2018 finally with magisk this morning after my viper messed up last night and got me pissed.

clean install.

rom

gapps nano

magisk

after reboot, system took 6 minutes to boot, then it restarted and finally boot up to home screen with the first bug system.process not responding

i waited and rom came alive, no issues and a joy to you.

i tried to use my bluetooth headset and i can report it is flawless when i make calls.

however, proximity sensor issue is there for outgoing calls alone, this is my only request to you please just fix this.

as for lockscreen , we all know its a normal issue so i can do without it.

so out of anger i flashed V4A + DOLBY ATMOS + SONY AUDIO + BEATS AUDIO Audio Mod (Update 2018) to see if i could get beataudio and dobly back, well i ended up bootlooping my device

am just pissed i have to go back to viper 9.0 cos this is the only device i have now. please do try, thank you anyway
[One (M7) Android Development] BeatB:
Bluetooth headset is flawless for you? Sure? The microphone sound is very bad when I talk to anyone. They can not hear me at all because there is background noise which is annoying. Tried it with my car and with my Bluetooth headphone on my voice mail.

Gesendet von meinem One mit Tapatalk
[One (M7) Android Development] cannonleo:
yep made a few calls , they all heard me properly though i noticed my sound was a bit to high for my ears else nobody complained about not hearing me properly even on a low tone.

meanwhile icxj1 have you considered writing the manifest.xml file for proximity sensor directly into the next build
[One (M7) Android Development] Groby:
Didn't get my M7_ul running. Original was a International Version, but set Super CID and S-Off. I've updated fw_7.19.401.2-NoRed_NoWipe via ADB and TWRP to actual 3.2.1.0. As the last Image was Lineage 14.0 I've wiped Cache and Davlik (and after some tries which didn't worked, wiped the whole phone and also tried formated the partitions). Then I flashed aicp_m7_o-13.1-UNOFFICIAL-20190112 (also tried some previos Versions as this one does not worked) and tried with Option to wipe Cache/Dalvik, install TWRP, does not Install TWRP App, with and without open_gapps-arm-8.1-mini-20190131, but in all cases the same: after reboot it stucks in the Animation and get warm to 40°C. I've waited several hours (longest 11 hours over night). Reset with Powerbutton and just restarted, and tried Reset and choosed "Reset to Factory" in TWRP. But all the same.

What can I try next to get the Image running?
[One (M7) Android Development] Gumka1977:
Install Magisk !!!

Wysłane z mojego One przy użyciu Tapatalka
[One (M7) Android Development] Groby:
Downloaded it, but if I try to install via TWRP I get "Invalid .zip format" ^^
[One (M7) Android Development] Gumka1977:
Download another zip.

You will do best if you flash the latest GPE firmware first if you have s-off. Then you will start playing roms.
[One (M7) Android Development] Groby:
Thank you very much! I'd installed as suggested latest GPE first, installed there Magisk (downloaded it new -now without errors), reinstalled TWRP and then the AICP & Magisk. Working fine now!
[One (M7) Android Development] icxj1:
Sorry guys, I've been working on a few things.

If ROM does not boot in 5 minutes, force reboot. You will know when it is booting because the button backlights will light up & most times an audible beep.

Now I am working on a O ROM that is pure source. We will see how that turns out. Also I will try to compile us a updated twrp. Most important is that I am cooking some PIE now & it is getting very close!

Let you know when things are moving.
[One (M7) Android Development] kamikazedc:
Great news!!! Thank you for your awesome work!
[One (M7) Android Development] Gumka1977:
Respect mate !! :)
[One (M7) Android Development] samhhmobil:
[MENTION=7327102]icxj1[/MENTION]

Just a new info...

Since two days it's there:

in LOS15.1 in "smart lock" now the topics "faceunlock" and "voice match" are present. That means, something important must have been changed in the O-sources.

Maybe it's possible to include that for our M7's too?

Thanks, you're great,

samhhmobil
[One (M7) Android Development] daywalk3r666:
is this not a part of gapps?
[One (M7) Android Development] samhhmobil:
Yes, of course... but it must be reachable in "Settings", and it was not in earlier releases of O-Rom, and it is not even yet in the latest build of this great M7-O-Rom.

samhhmobil
[One (M7) Android Development] cannonleo:
Big respect,bro very big respect
[One (M7) Android Development] icxj1:
TWRP 3.2.3-0 images are uploaded & ready for use. These are NOT device unified recovery images, so be sure to flash the correct variant.

link to all TWRP += https://www.androidfilehost.com/?w=files&flid=289786

m7 += https://www.androidfilehost.com/?fid=1395089523397887916

m7vzw += https://www.androidfilehost.com/?fid=1395089523397887921

m7spr += https://www.androidfilehost.com/?fid=1395089523397887919
[One (M7) Android Development] daywalk3r666:
thx for the twrp build.can you explain whats the different between your twrp and https://dl.twrp.me/m7univ/
[One (M7) Android Development] icxj1:
The kernel, sepolicy, & mine is built in an up to date android 9.0 environment. That official twrp is still stuck with a cm12 device tree.
[One (M7) Android Development] daywalk3r666:
ah ok.thx for the info
[One (M7) Android Development] cannonleo:
Bro how about the proximity sensor issue, is there a permanent fix within a build avaliable?
[One (M7) Android Development] icxj1:
The fix is in the kernel, until I get the code right we have to use the pocket mode work around or just do not enable dt2w.

I could also ship a kernel without dt2w. But I need some time. P has my hands full now.
[One (M7) Android Development] crownvn:
woh !!! goods new, :good::good::good:
[One (M7) Android Development] Benjaes123:
Thanks for the update but I just can't boot into TWRP, idk if anyone else can confirm this. I made sure to flash the correct image trough fastboot, but when I try to reboot into TWRP it just reboots to android.

btw I'm using the international model
[One (M7) Android Development] icxj1:
What command did you run?

fastboot boot recovery.img and then run fastboot flash recovery recovery.img
[One (M7) Android Development] samhhmobil:
I'm sorry, it doesn't work.

When doing both steps in one fastboot session, the second step is hanging during "sending 'recovery'", only breakable by longpress power/voldown.

When doing a reboot to bootloader inbetween, flashing works, but recovery does not work (it's rebooting back to the splash screen).

It's tested on three M7ul devices, all the same.

What's wrong there?

Thanks,

samhhmobil

Edit:

Re-flashing to 3.2.1 brings it back to normal recovery operation mode...
[One (M7) Android Development] icxj1:
You did rename the image to recovery.img , correct?

I think you need to reboot back to fastboot. Then run flash command.

https://xdaforums.com/showthread.php?t=2265618
[One (M7) Android Development] samhhmobil:
correct!

But I expect, it doesn't belong to the file name...
[One (M7) Android Development] icxj1:
Hmm, flash old recovery then just flash new recovery in recovery. Or keep old recovery. Not sure what issue is, All seems to work for me.
[One (M7) Android Development] samhhmobil:
Flashing works correctly (even inside of TWRP 3.2.1). But after that it doesn't boot into recovery. Maybe??? Maybe... there's something wrong with the IMG-file?

So it seems the problem does not belong to a particular flash procedure...

I'm yet back on 3.2.1, as long as it does everything I need to. :)

Thanks again,

samhhmobil
[One (M7) Android Development] wasserprojekt:
Hi. Nice job on the ROM.

I was having those problems when flashing, bit wiping everything and installing, by this order, the ROM, the latest Magisk and gapps solved it. Boot was around five minutes.

As of bugs, don't know if that's because of me, but when recording video, the resulting file is kinda weird. There's an alternating video between green screen and the picture, although the sound seems ok. Everything else seems to be working well.

But the biggest challenge I deal with now is about battery life. I installed kernel adiutor and chose the interactive mode (powersaving is unusable and conservative is sluggish), and the speed is ok. However, battery life is less than half of the 7.1 xenonhd ROM. When I first installed this ROM, the phone overheated too, however with interactive installed I didn't notice it happening again. Though battery life didn't improve. Any ideas on this?

Thanks for your time and dedication!
[One (M7) Android Development] Benjaes123:
Hi. I'm running into the same problem as [MENTION=8300892]samhhmobil[/MENTION], maybe as he pointed out it is a naming problem of the uploads.

I've tried flashing it in every way possible but I just cant boot into TWRP.

Re-flashing to 3.2.1 brings it back to normal.
[One (M7) Android Development] icxj1:
Probably just a few denials. We will test more in some time.
[One (M7) Android Development] Benjaes123:
Thanks man, It's incredible that ppl still care for this phone.

Really appreciate the work for this aging device :good::good:
[One (M7) Android Development] cannonleo:
Is proximity sensor working for you

---------- Post added at 09:58 PM ---------- Previous post was at 09:38 PM ----------

Can i get a link to the latest build please

---------- Post added at 10:00 PM ---------- Previous post was at 09:58 PM ----------

Forgive me for asking, which pocket mode work around, i simply want to know if your latest build has the proximity sensor at least working for out going calls .

Forgive me persistence and please can you give me a link to your latest build
[One (M7) Android Development] wasserprojekt:
Oh, I forgot to mention. Proximity sensor is also not working.
[One (M7) Android Development] kamikazedc:
I've seen the same problem. You have to select a lower resolution.
[One (M7) Android Development] wasserprojekt:
Thank you! That solved the problem.

So, as long as I know, if the issues with the battery life and proximity sensor are solved, I believe the ROM is ready for daily use (although I am already doing that haha).

Many thanks to the developer!
[One (M7) Android Development] kamikazedc:
I'm using it daily since the first unstable builds... :silly:
[One (M7) Android Development] wasserprojekt:
Any hints to ⬆️??
[One (M7) Android Development] kamikazedc:
I replaced my battery with a new one. Now it lasts almost all day (14-16 hours) with a moderate use. But I usually charge it at noon.
[One (M7) Android Development] grishaiozhig:
Juat flashed twrp3.2.3.0 for UL, runs flawlessly for me. Flashed it from under TWRP (of the same version, actually, but hence icxj1 says his is better, flashed it and relaxing waiting for a great new P rom.
[One (M7) Android Development] icxj1:
Working fine for me also. :good: only one problem is no adb on P, so development is a pain in the ass right now. :crying:
[One (M7) Android Development] u.b.e.r:
One problem I encountered with TWRP 3.2.3.0 is that I couldn't format the data partition to F2FS as it didn't show up on the list.

Also I do hope this new Oreo ROM will be a pure source like Lineage OS.

I don't know, I just find LOS to be lag-free and it's less bloated than some other ROM's out there.
[One (M7) Android Development] QuRdAdZze:
Hello Guys what are the BUGs so far?
[One (M7) Android Development] gehess:
I'd be really interested to see if people that are having reboots with gapps are still having reboots if they use NanoDroid (https://xdaforums.com/apps/magisk/module-nanomod-5-0-20170405-microg-t3584928) instead. I would try myself, but I need my phone for work.

I've been installing microG and patcher on Nougat and never needed gapps again.