yashsingh1/xdaforums huggingface dataset:
[One (M7) Original Android Development] miki4:
Sorry mate, I cannot help you because I have no clue about the bugs and specifics of the Galaxy S4 builds. This here is the HTC One M7 thread. You would be better helped if you wrote in the according thread for your phone. ;)
[One (M7) Original Android Development] icxj1:
Haha! He should go buy m7 on eBay and then try. :cyclops:
[One (M7) Original Android Development] scartsjer:
BueTooth headset Volume

Each time i connect my Bluetooth headset the volume is set to maximum. is this a common problem with lineage?:confused:
[One (M7) Original Android Development] kruc Ire:
I bought 5 m7s last year. I kept 2. He really should. It beats the samsung I used before it hands down.
[One (M7) Original Android Development] sabrinaf:
Hey guys, have you been able to make progress on joining the lineage os official maintainer program to see your builds one days as official builds? Thumbs up for our work until now!
[One (M7) Original Android Development] miki4:
Do you guys still have the calling bug on the 20170515 build where you cannot hear your participant and vice versa after hanging up your last call with the loudspeaker on? This is the first LOS build I flashed to my M7 (clean flash) and I had that bug occur maybe two or three times. I am not 100 percent sure if it was always after having my last call in speaker mode but it's likely. I must admit that I flashed the latest DT2W kernel which unfortunately is based on the rather old 20170308 build ( https://xdaforums.com/htc-one/development/kernel-current-kernel-s2w-dt2w-l2m-l2w-t3568353 ) and did not test the ROM untouched. Can someone please verify if the bug is gone or still there on the untouched 20170515 build? Thanks!

They seem to still wait for an official answer.
[One (M7) Original Android Development] camambeou:
Alial04 is working to fix this. Be patient....
[One (M7) Original Android Development] mchowdhury:
[MENTION=5944557]alial04[/MENTION] and I are working on this. If you can provide a logcat for us that would greatly help us.

Also we must fix this bug and do some security patches before they will accept us a maintainers.

---------- Post added at 05:24 AM ---------- Previous post was at 05:20 AM ----------

New builds are up!

M7 - https://www.androidfilehost.com/?fid=673368273298957051

M7vzw - https://www.androidfilehost.com/?fid=889764386195901506

Please report any issues that you are having.

Changelog:

- Latest LOS source

- A number of CVE Kernel patches
[One (M7) Original Android Development] sabrinaf:
Not tested, but thank you for your effort until now. [MENTION=7694084]mchowdhury[/MENTION], please add your PayPal donation link, so I can send you a donation like I actually did to [MENTION=5944557]alial04[/MENTION].

Thank you again guys! Keep up the work!
[One (M7) Original Android Development] miki4:
I have created a logcat.txt while reproducing the call bug, exactly doing the following:

starting logcat after reboot

calling number, no pickup, hang up

calling number, pick up, hang up

calling number, [pick up, speaker on (maybe the other way round)], speaker off, hang up

calling number, speaker on, pick up, hang up

calling number, speaker on, NO SOUND, pick up, STILL NO SOUND, hang up

calling number, speaker on, STILL NO SOUND, pick up, STILL NO SOUND, hang up on the paricipants phone.

stopping logcat

info: always speaking for some seconds after pickup.

The logcat.txt is about 1 MB in size. Do you have some preferred hoster where to upload it? Otherwise I would put it on http://www.share-online.biz/ and send you a private message with the link to it.

Thanks!
[One (M7) Original Android Development] saturday_night:
Just pack it in .zip and upload it here to your post. Btw you can solve the bug if you disable speaker before ending the call, next call has sound.
[One (M7) Original Android Development] miki4:
Alright, I'll do that but will encrypt the *.zip as I don't know if there is any personal information in my logcat which should better not be open to the public. I will post the decryption key to alial04 and mchowdhury via PM.

Thanks for the workaround for the call bug. I already know that but it's not always applicable, e.g. if the connection interrupts. I also reproduced this workaround in my logcat ("calling number, pick up, speaker on, speaker off, hang up") for the sake of completeness and to make it easier for the devs to trace the bug by comparing the different behaviour when ending the call once with speaker turned off and once with the speaker left on.

EDIT: PM to alial04 and mchowdhury has been sent.
[One (M7) Original Android Development] coolerprog:
NFC Payments

Why there is no support for hce (host card emulation)? I tried to write a file android.hardware.nfc.hce.xml with permissions in /system/etc/permissions folder, but nfc service began to crash right after reboot.

I just want Android Pay start to work. This ROM is really great, but NFC payments matter for me.

Maybe you guys know how to fix it or Nougat ROM where it already have been fixed?

Thanks.
[One (M7) Original Android Development] v42:
I did a clean install (full wipe including, cache, dalvik, data, system, and internal storage) of lineage-14.1-20170302-nightly-m7-signed.zip on my HTC One M7 via TWRP. Boot and sign-in etc proceeds successfully, but I can't click pictures with the camera. I get a "Insert SD card" error.

Has anyone seen something like this before? What am I missing?
[One (M7) Original Android Development] camambeou:
Use the unofficial build on this thread
[One (M7) Original Android Development] icxj1:
https://www.androidfilehost.com/?fid=673368273298957051
[One (M7) Original Android Development] mchowdhury:
New builds for this week are up!! Once again, thanks to [MENTION=5944557]alial04[/MENTION] for use of build server, and helping me maintain this device.

M7 - https://www.androidfilehost.com/?fid=817550096634773869

M7vzw - https://www.androidfilehost.com/?fid=961840155545569637

These builds include the latest LOS source and kernel security patches.
[One (M7) Original Android Development] haykweb:
Hey bro, please changelog about fixes.
[One (M7) Original Android Development] alial04:
check gerrit here --> https://review.lineageos.org/#/q/owner:mikhail.chowdhury%40gmail.com+status:
[One (M7) Original Android Development] saturday_night:
Thats an interesting thing "add maintainers for m7 & m7vzw" sad that its not visible in the wiki or on their webpage by now.
[One (M7) Original Android Development] Mr.Kiko:
Hello guys.

I just flashed the newest version of this ROM (lineage-14.1-20170601) but my GPS doesn't work. It can't localize my position. I've tried to reflash it, wiping dalvik/cache, performing a full-wipe but without success.

My M7 comes from a Sense ROM and before flashing this ROM I've made a full wipe

Hope you can help me, thank you!

Oh, one more thing: I've read this just now: Enable all location services: Settings > Location > (all location services) = On

Actually I didn't check this step before wiping my Sense ROM. May it be the issue?
[One (M7) Original Android Development] boris59:
I still run that build and it works just fine. I had one instance where the camera did not work properly, a reboot fixed it. Works fine ever since (weeks now).
[One (M7) Original Android Development] mchowdhury:
Yeah, that's probably the issue. Is GPS working for everyone else?
[One (M7) Original Android Development] stephendt0:
Just a heads up on an issue. I couldn't get VOIP via Zoiper to work properly on this ROM - I'd always get complaints that I was very quiet. This goes for all versions of CM13 and LOS14.1 that I tried. I am now using a Google Play Edition ROM and this problem appears to have disappeared. Not sure what the issue what the Microphone was but it seems to be gone now.
[One (M7) Original Android Development] Mr.Kiko:
Hey, first of all thanks for your message!

My issue is gone. Now GPS works perfectly and funny thing I don't know how! It simply works again after three days. A bit of luck sometimes :)
[One (M7) Original Android Development] sabrinaf:
Hi to all,

a few of you were using this build for a bunch of days/weeks. How stable is the build at the moment? Are there severe problems (except the speakerphone bug that has already been mentioned) or is the build working well for you?
[One (M7) Original Android Development] camambeou:
The latest build is stable, only a few bugs, but not big deal
[One (M7) Original Android Development] vario3:
Hello everybody,

Re: M7 GPS running TWRP 3.1.0.0

I've successfully been running lineage-14.1-20170302-nightly-m7-signed but i decided to upgrade to lineage-14.1-20170601-UNOFFICIAL-m7.

Constantly receiving Error 7 message and i've wiped everything including factory reset, no system is presently installed.

Latest Gapps loaded before rom doesn't help.

Does anybody have any ideas ?

Regards, Mark
[One (M7) Original Android Development] alial04:
u need to do a clean flash and then u need to flash the rom and gapps
[One (M7) Original Android Development] vario3:
Hello Alial04,

Thanks for your quick reply.

Using TWRP 3.1.0.0 i have wiped the following partitions: Dalvik / ART cache, Cache, Data, Internal Storage and system. The only partition i didn't wipe

is USB OTG.

"Updater process ended with ERROR 7"

I can't see where i am going wrong but maybe you have another suggestion ?

Regards, Mark
[One (M7) Original Android Development] alial04:
after wiping everything download the latest build and then flash it with gapps
[One (M7) Original Android Development] vario3:
[MENTION=5944557]alial04[/MENTION]

I have wiped everything and tried to install the latest build with the latest Gapps file.

Can't install this package on top of incompatible data. Please try another package or run a factory reset.

Updater process ended with error 7.

I have already wiped everything as said in my previous post and i wouldn't have thought there is any incompatible data still available.

Should i be doing anything else ?

Thanks, Mark
[One (M7) Original Android Development] saturday_night:
Additional to the usual wipe/factory reset, you can go to wipe -> advanced and there you can wipe the system partition. Sometimes that helps. If not, error 7 also can mean that your device is not compatible with the Rom. What kind of m7 do you have? You can see this in the bootloader (turn device complete off) and press and hold power and vol- at the same time for about 5-10 seconds. There is something like "m7_ul or m7_u or m7vzw"
[One (M7) Original Android Development] vario3:
[MENTION=7715118]saturday_night[/MENTION]

My version is "M7_UL PVT SHIP s-on RH" and the build i am trying to use is "lineage-14.1-20170601-UNOFFICIAL-m7"

I have wiped all partitions.

Does this tell you anything ?.

Thanks for your help.

Mark
[One (M7) Original Android Development] icxj1:
Fastboot getvar all & verify the MID is correct.

Are you able to flash the build you was one before?

If not, download team venom viper one fix zip from AFH & flash. Make backup them try los.

Also make sure you are trying m7 & not m7vzw, haha! :silly:
[One (M7) Original Android Development] vario3:
Thanks everybody for your help. Much appreciated.

I'll get back as soon as i have time to have another go.

Thanks,

Mark
[One (M7) Original Android Development] icxj1:
Make sure you have good internet speed when downloading zips. Drop outs and slow speeds can corrupt the files.
[One (M7) Original Android Development] vario3:
Hello alial04, Saturday_night and icxj1.

I have tried to follow your advice but i'm encountering problems with ADB & Fastboot. I can't transfer files using the push command. I have tried to solve the

problem myself by checking previous threads but i have hit a brick wall.

I have the following:-

HTC one M7_ul

installed TWRP 3.1.0-0

ADB version 1.4.2

I can't get any files onto the phone to attempt a new install. Old or new.

USB shows an "MTP device" but when i try to transfer files in windows explorer it starts to transfer and then freezes and bombs out.

ADB reboot bootloader is successfull.

Fastboot devices shows device.

adb push "filename" /sdcard/ produces "adb: error: connect failed: no devices/emulators found"

[MENTION=7327102]icxj1[/MENTION] using getvar command gives me some info but "MID" & "CID" present errors

U:\Phone\Minimal ADB and Fastboot>fastboot getvar all

(bootloader) version: 0.5

(bootloader) version-bootloader: 1.61.0000

(bootloader) version-baseband: 4T.35.3218.16

(bootloader) version-cpld: None

(bootloader) version-microp: None

(bootloader) version-main:

(bootloader) version-misc: PVT SHIP S-ON

(bootloader) serialno: FA34KW905454

(bootloader) imei: 354436050999976

(bootloader) meid: 00000000000000

(bootloader) product: m7_ul

(bootloader) platform: HBOOT-8064

(bootloader) modelid: PN0710000

(bootloader) cidnum: O2___102

(bootloader) battery-status: good

(bootloader) battery-voltage: 4329mV

(bootloader) partition-layout: Generic

(bootloader) security: on

(bootloader) build-mode: SHIP

(bootloader) boot-mode: FASTBOOT

(bootloader) commitno-bootloader: dirty-868a9c98

(bootloader) hbootpreupdate: 11

(bootloader) gencheckpt: 0

all: Done!

finished. total time: 0.078s

U:\Phone\Minimal ADB and Fastboot>fastboot devices

FA34KW905454 fastboot

U:\Phone\Minimal ADB and Fastboot>fastboot oem readcid

...

FAILED (command write failed (Unknown error))

finished. total time: 5.009s

U:\Phone\Minimal ADB and Fastboot>fastboot getvar mid

getvar:mid FAILED (command write failed (Unknown error))

finished. total time: 5.008s

Until i can get the files onto the phone i am unable to attempt any installs.

Hope somebody can point me in the right direction.

Regards, Mark
[One (M7) Original Android Development] icxj1:
Mid is good, I believe you have to b s-off to write cid or mid. Looks like you've wiped it out. [MENTION=5944557]alial04[/MENTION] has a solution probably.
[One (M7) Original Android Development] kAzGuRu:
Thx for the link,

which Gapps Version do we need for the HTC M7? ARM 7.1 ?
[One (M7) Original Android Development] ★Michaelo★:
Yes. I recommend Beans Mini Gapps
[One (M7) Original Android Development] kAzGuRu:
Thx ! Never heard of AICP 12.1 before, but it seems to be a nice Nougat Rom.. :cool:
[One (M7) Original Android Development] camambeou:
Yeah, ARM
[One (M7) Original Android Development] Awesome Wisdom:
Does it work for tecno kitkat
[One (M7) Original Android Development] camambeou:
What works???
[One (M7) Original Android Development] icxj1:
Its the only ROM there is! Los is just plain Los. Hahahaha! :silly:

Besides that Los abandoned m7 & then don't answer the call for [MENTION=5944557]alial04[/MENTION] & [MENTION=7694084]mchowdhury[/MENTION] to maintain.
[One (M7) Original Android Development] The Lich:
Seems to work well so far. Thank you so much!

Installed SuperSU and pico Open Gapps.

Anybody know if USB OTG works?
[One (M7) Original Android Development] camambeou:
Yes, it worked as expected
[One (M7) Original Android Development] icxj1:
Error 7 could mean not enough storage. Are you full of pixs & videos? Extract zip on PC and install boot IMG. On device. If successful, then flash zip. If error 7 again maybe we can get u system IMG. System image is big so when you flash it and its not successful it will say "not enough storage on device" instead of error 7.
[One (M7) Original Android Development] haykweb:
Some times not working bluetooth,it not turning on,only help restart. This bug is not fixed yet.
[One (M7) Original Android Development] gatetrans:
m7

Hi there,

I have some problem this ROM. I installed "lineage-14.1-20170601-UNOFFICIAL-m7" but not good for me. Why?

1. When I was call someone other side hear my sound too low. Also When I was use whatsapp I have same problem. This is propably mic. problem. Can u fix mic problem or if u fix this please let me know, sorry Im new member this forum.

2. When I was use whatspp video call my friends video turn green and turn normal and turn again green. I can't see other side.

3. I can't record 720p 60FPS video. This phone is support 720p 60fps.

I wanna test this rom if u tell me.

How did I install this rom? Here..

I used TWRP select Advanced Wipe and delete all data and then connect my phone everythink is delete, SD Card include! After that, upload lineage-14.1-20170601-UNOFFICIAL-m7 and gaps full. Disconnect my phone start new software. Everythink is working. If I do somethink wrong please let me know.

My Phone Htc One M7 801e Turkey
[One (M7) Original Android Development] vario3:
Update:

Using TWRP 3.1.0.0 i have wiped the following partitions: Dalvik / ART cache, Cache, Data, Internal Storage and system. The only partition i didn't wipe

is USB OTG.

"Updater process ended with ERROR 7"

I made the stupid mistake of removing my "OS". This caused massive problems transfering a new rom from the PC to my device. ADB connection was very flakey and TWRP wouldn't allow me to mount USB OTG. I was stumped and have been going around in circles for days.

I don't know why but today i tried USB OTG again and it worked. I transferred a few files and then installed them.

Lineage OS experimental: install successfull.

Lineage-14.1-20170302-nightly-m7-signed: install successfull.

Lineage-14.1-20170601-UNOFFICIAL-m7: install successfull.

Gapps

addonsu

Now running Lineage-14.1-20170601-UNOFFICIAL-m7 and i've restored my apps using Titanium.

I would like to thank everybody who took the time to offer advice, support very much appreciated.

Mark
[One (M7) Original Android Development] icxj1:
Not yet, best to leave it on once you have it linked up, even on when powering off & updating.

---------- Post added at 04:16 PM ---------- Previous post was at 04:12 PM ----------

Clean install?
[One (M7) Original Android Development] gatetrans:
Nop, Just I do my first msg. How can I install clean? Can u explane for me or can u share link. Also I didnt chance my Kernel. Which kernel is the best for LOS 14.1 ? How can I check my Kernel details?
[One (M7) Original Android Development] haykweb:
Yes it was clean install.
[One (M7) Original Android Development] icxj1:
Just swipe to wipe, no advanced options needed.

Kernel if fine unless you want dt2w then use this https://xdaforums.com/htc-one/development/kernel-current-kernel-s2w-dt2w-l2m-l2w-t3568353 . install kernel auditor from play store to enable features.
[One (M7) Original Android Development] gatetrans:
First of all,

1. upload kernel sd card

2.upload LOS 14.1

3. Gapps

Open the phone recovery mode

1. just swipe to wipe

2. install kernel

3. istal los 14.1

4.istall gapps

If I do this will fix my problem ?
[One (M7) Original Android Development] icxj1:
Install Los before kernel & you should be good.
[One (M7) Original Android Development] gatetrans:
Ok bro. I will try and I will tell u result

:good::)
[One (M7) Original Android Development] gatetrans:
Hi again,

I istalled soft and everytnik is working.

1. Talking someone hear my sound very good. This problem fixed. (Im testing);)

2.whatsapp video calling green screen problem fixed. (Im testing);)

Another problem.:(

1. I cant 720p 60fps video record. (Very important for me, do u know good video recorder?):(

2. FM radio cant work (Doesnt matter, I dont care radio) :cool:
[One (M7) Original Android Development] camambeou:
Be patiant... The developers are working on it. They need much time and a ton of codes to work well
[One (M7) Original Android Development] FeelThePoveR:
1. That issue basically exists since forever in AOSP based roms and it probably won't be solved unless someone picks up custom HAL development after iriijo.

(Links if someone is interested https://github.com/irii/android_kernel_htc_msm8960/tree/cm-14.1 https://github.com/irii/android_device_htc_m7-common)
[One (M7) Original Android Development] gatetrans:
Hi there,

I hope they can fix this problem. If they cant I will return back 5.0.2. :(
[One (M7) Original Android Development] tonde4jc:
Installed the rom and i loved it but it did not read any sim network. The one for m7 had errors when i tried to go into network settings but the one for m7vzw fixed that error but again did not register any network. Mine is the Verizon one. What could be the problem? Anyone facing the same errors?
[One (M7) Original Android Development] samhhmobil:
Battery problem (again and again)!!

Since months there are some topics with the battery-draining with LineageOS.

Here are my 2 cents:

Even with the old CyanogenMod 12.1 the battery drained very fast and the M7 tried to cook eggs (it became very hot).

Now I tried LineageOS 14.1 and... -- the problem is the same! :(

And just for people who like to say M7 is 4 years old, I want to explain: I changed the battery to a brand new one 10 days ago (it's original HTC, manufactured by Sony in 2017). With the HTC Stock ROM 5.0.2 everything runs clean down to 1% without trouble, but CM12.1/Lineage14.1 crashes the M7 at 60%, when using the camera (charging offline starts then at approx 3% or 4%). The handling of the voltage seems to be completely broken, but I'm not the person, who would be able to fix that issue. It's present since years!! And due to this strange battery behaviour in 12.1/14.1 the M7 becomes VERY hot, when in frequently use (50°C or more). Yes, that drains the battery too!!!

It's impossible to use the M7 when battery shows 50% or a bit lower, and in idle state it crashes down to zero with >30%, just when unlocking the screen.

Is anybody working on this issue? I like the 14.1, but for DAILY use it's useless!! Will it be possible for anybody to examine the HTC voltage handling?

Thanks very much.

samhhmobil
[One (M7) Original Android Development] saturday_night:
As there are very few people with this problem, it cant be caused by the rom or software. Think about it, there are several hundred people using it and there are just 3 or 4 with problems... maybe its the user or some hardware damage?!?
[One (M7) Original Android Development] samhhmobil:
Maybe, there are only three or four who did REPORT it? Even me, I tried 12.1 for many many months (with "old" batteries, and now with new ones), without writing about. But it's time now!

I have two of these M7's (both with "new" battery) with really different history, but: The behaviour is on both exactly the same... it's more or less unusable.

And... switching back to HTC Stock ROM... and ... tada... the power consumption is completely OK, the phones (both) are running very clean. It's just then ONLY 5.0.2. sigh...

And... I even have a Sony Xperia Z (C6603/yuga), the power consumption there is even much higher as with the stock rom, but the battery draining is controllable there correctly until 1%, so there it runs much better (ok, even with higher battery consumption and much more heat as the stock rom, but it works much better as the M7).

Even I tried to mod the/system/build.prop with "Ultimate Performance Blazing", as suggested by several other people.

https://xdaforums.com/android/software-hacking/mod-ultimate-performence-blazing-fast-t3482317

This even didn't help in any way... sigh!
[One (M7) Original Android Development] saturday_night:
Well i use the m7 for 3,5 years now with original 3,5 year old battery. And i dont have any problems to make it trough the day, and with nougat its much better. With MM i only had about 10% left after the day, with N its about 25% left with same usage. If you have two devices and its the same on both i would say the problem is sitting in front of the screen ;)

And i had an Z4 and a Z5 last year sony devices are so crappy and getting hot without doing anything with the device. You cant compare devices of different manufactors just because both are running same rom, there are so many differences in the kernel and other stuff in the rom itself whats device related, otherwise you would be able to flash every los 14.1 rom to any device just flashing correct kernel after it. But it doesnt work that way.
[One (M7) Original Android Development] samhhmobil:
Thank you.

But I expect (no, I'm sure), here you're wrong. :fingers-crossed: