yashsingh1/xdaforums huggingface dataset:
[One (M7) Android Development] QuRdAdZze:
i have just installed latest vzw ROM and while i was trying to set pattern UI stopped and i had to reboot but when it turned on pattern was sat and when i draw it UI frozen again
[One (M7) Android Development] icxj1:
Yup, I think its been mentioned to use lock screen at your on risk. Just like proximity, it's working for some but not for other's. Probably a denial or something installed
[One (M7) Android Development] kamikazedc:
I've made a clean install to flash only gapps pico.

Proximity works perfectly!

Just one thing: this build has KA preinstalled, and cannot uninstall.
[One (M7) Android Development] icxj1:
Use system app remover in aicp extras. Sorry unofficial, it stays. Lol
[One (M7) Android Development] kamikazedc:
I'm sorry I can't find that option. I think need root for that (and don't want to root for now).
[One (M7) Android Development] icxj1:
Yup, root is needed before its available.
[One (M7) Android Development] gehess:
Correct me if I'm wrong (I may well be), but could most problems possibly be solved if everyone started out with the latest firmware (sense or gpe), root and s-off?

Look, I appreciate that icxj1 is trying to make a ROM that works for everyone whether they've got root/no-root, s-off/s-on, GPE/Sense, latest firmware/older firmware, etc. but frankly I always thought it's OK for a ROM this far out from official support to have a few prerequisites. For the M7 I'd think the minimum should be latest firmware, root and s-off. I'd also recommend GPE firmware, simply because it's newer and isn't that why people keep updating to the latest versions of stuff in the first place?

If you're willing to flash a ROM over and over again for testing purposes, then you should be OK with making your device as up-to-date and compatible as possible before flashing the latest, unofficial, experimental ROM.

Sorry for the rant but it may help some of ya'll. :)
[One (M7) Android Development] icxj1:
Very true.
[One (M7) Android Development] ysnakkblt:
Where can I download the google camera for htc one m7?
[One (M7) Android Development] kamikazedc:
Hi all,

After some calls I've seen the sensor problem:

On incoming calls works great, but on outgoing calls it still fails. The screen goes off and have to push power button twice to get back on.
[One (M7) Android Development] gehess:
apkmirror (I think the app filename is: com.google.android.GoogleCamera_4.1.006.135988111-41002253_minAPI24(armeabi-v7a)(nodpi)_apkmirror.apk)

I think I just experienced this in Nougat, so perhaps it's just one of those quirks the M7 has had forever.
[One (M7) Android Development] sudowtf:
I can't S-Off. It is reported that only one method works, which is sunshine for $25, but i can't justify cost for a device that is just re-purposed not as a phone. I tried to install the DEV version HTC RUU for my unlocked ATT phone, but it failed repeatedly. I have been through all the RUU extractors and failed to resolve. I did TRY to flash the dev hboot.img that was extracted, but can't recall if it succeeded.

This is what i got right now and is doing what i need it to do (Run DJI Go 4).

(bootloader) version: 0.5

(bootloader) version-bootloader: 1.61.0000

(bootloader) version-baseband: 4M.32.3218.06

(bootloader) version-cpld: None

(bootloader) version-microp: None

(bootloader) version-main:

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

(bootloader) serialno: xxxxxxxxxxxx

(bootloader) imei: xxxxxxxxxxxxxxx

(bootloader) meid: 00000000000000

(bootloader) product: m7_ul

(bootloader) platform: HBOOT-8064

(bootloader) modelid: PN0712000

(bootloader) cidnum: CWS__001

(bootloader) battery-status: good

(bootloader) battery-voltage: 4305mV

(bootloader) partition-layout: Generic

(bootloader) security: on

(bootloader) build-mode: SHIP

(bootloader) boot-mode: FASTBOOT

(bootloader) commitno-bootloader: dirty-0e2a13e5

(bootloader) hbootpreupdate: 11

(bootloader) gencheckpt: 0

aicp_m7_o-13.1-UNOFFICIAL-20180321.zip

I'm happy to report back anything requested, logs, etc. (just tell me how)

Off subject: Is there anyway to get AICP Extras onto my stock Moto X4? or is there any hardware key apps that i can make my back-key double-click to be "force close"?
[One (M7) Android Development] hedeon76:
[MENTION=7327102]icxj1[/MENTION]

I had to zip the file because of the forum rules.

I hope you can find something interesting there.
[One (M7) Android Development] icxj1:
Gr8! Thanks. Try the second test. I will probably have everyone do the same soon.
[One (M7) Android Development] hedeon76:
Ok. I did it. But there is always the same

Here the logs.

Log 1 is with mixer_paths.xml moved to system/vendor/etc and with media_profiles_V1_0.xml in system/etc.

Log2 is with mixer_paths.xml moved to system/vendor/etc and without media_profiles_V1_0.xml in system/etc.
[One (M7) Android Development] gehess:
Fair enough, although have you tried contacting and asking the devs of Sunshine to perhaps forgo the $25 since the M7 is now so old? I think you have a reasonable case and the worst they can say is no.

I don't mean any offence, but it seems developing Oreo for the M7 is hard enough as it is. I don't think it's unreasonable to expect that users will meet the developer half-way by having their device rooted and s-off with the latest firmware. icxj1 could then get the ROM working for that standard and figure out how to get it to work on non-root and s-on devices later.

Basically, if you're experiencing bugs that others aren't, ask not what icxj1 can do for your M7, but what can you do for your M7. :D
[One (M7) Android Development] eaglefreewings76:
...Hi guys, well I completly agree with the ones who say it's really hard to improve a developping project day by day when everybody here has got a different starting point for working with!!!...it begins to be really impossible to fix bugs if everyone has a different outcome just when the developer thinks to have fixed something! ..this is a project involving ONLY the M7s that are S-OFF!!!!...I think so...the way everybody has got the same firmware is the essential requirement to allow the developer fix everything quickly without wasting time flashing everyday twice for getting the same issue at the end!..so my phone is unfortunately S-ON and if I cannot turn it OFF (mine is still the everyday only main phone!) I have to come back to nougat (xenonhd in my case)...I feel like a stupid to flash my phone everyday without having improvement and getting the same issues. The develeper icxj1 is working really hard to fix issues with so many different cases and I understand it's also really hard to satisfy everybody personal situation!..that's only what I think...
[One (M7) Android Development] evilcoleslaw:
Just dirty flashed the 3/21 build. Everything besides the obvious bugs you know about is working as expected. Proximity works perfectly so far -- not even requiring a dt with dt2w on. No reboots so far, either.

KA still occasionally seems to cause some slight jankiness when enabling the dt2w settings, but it's irregular and nothing major. Settled down after a bit without a reboot.
[One (M7) Android Development] henning_h:
If we are thinking about a common standard as baseline for the M7 development, we shouldn't forget the verizon & sprint variants, which obviously can't be updated to latest GPE firmware. Also the request not to spend 25$ for an 4 or 5 year old device is absolutely reasonable. Therefore, S-on and latest Sense firmware might be a good starting point for further development.:confused:
[One (M7) Android Development] saentis:
For people who have older hboot (1.54 or 1.55 for example), it should still be possible to get S-OFF using rumrunner? Is this incorrect?

https://xdaforums.com/showthread.php?t=2488772
[One (M7) Android Development] samhhmobil:
Don't forget... the Sense-based 1.55/1.54 are MUCH older as 1.61, ...

... but the 1.54 GPE hboot is the newest/youngest, one can get.

1.54-Sense and 1.54-GPE are totally different!

And — yes — for the old sense-hboot-versions rumrunner may work (AFAIK there is a security hole in old hboot, which is "misused" by rumrunner to switch to S-OFF), but I never did that by myself.

samhhmobil
[One (M7) Android Development] Rajeel911:
Is hboot 1.57 Lao sense firmware?
[One (M7) Android Development] sudowtf:
okay, finally caved in and tried OpenGapps 8.1 Pico, but it continuously reports "Google Play services keeps stopping". Is this because i have sense hboot and not gpe hboot?

(Turns out i need gplay do get beta edition of a specific app i use.) otherwise i'd just manually install my apk's like i've been doing.
[One (M7) Android Development] abdrk00:
Did you flash the GApps with the ROM or you did it later separately? I had the same issue and flashing the GApps with ROM helped solve it.
[One (M7) Android Development] sudowtf:
So you're proposing install aicp*.zip and add open_gapps*.zip at same time, is that what i should understand?
[One (M7) Android Development] abdrk00:
Yeah, install AICP and then OpenGApps before you boot the ROM for the first time.

Never tried the add zip option but it should do the job too I guess. Basically, install the GApps before booting the ROM for the first time.
[One (M7) Android Development] evilcoleslaw:
Yes. I'm pretty sure that's always the recommended procedure when installing GApps.
[One (M7) Android Development] icxj1:
Yup, I think so. That's the only we to go through setup wizard.
[One (M7) Android Development] sudowtf:
[frown face] tried this method... still fails. i keep getting the "Google Play services keeps stopping" "open again / close app" ... tried gapps 8.1 pico and nano.

Would a full wipe help or not worth the effort?
[One (M7) Android Development] kamikazedc:
Yes, you should install aicp and opengaps without reboot.

You can use the "add zip" option in TWRP, or flash separately, but always at the same time (without reboot between the two).
[One (M7) Android Development] sudowtf:
WOOT, double WOOT, triple WOOT -- wiped "everything" then it worked! thanks for the posts otherwise i may not have persisted.
[One (M7) Android Development] Rajeel911:
In the ROM description it's written that it's not recommended to install titanium backup (with backup of systemapps and system data). So can I flash the ROM with titanium backup ofuser apps and data?
[One (M7) Android Development] samhhmobil:
I made it with all "user apps" (no system apps of course), using TB without any issue.

samhhmobil
[One (M7) Android Development] CanVeeD:
Installing latest build after factory reset and GApps Nano package. I will test proximity sensor after installation. No other bugs I've found.

One more thing. I've noticed some kind of lag. After phobe turning on/reboot, no wallpaper and battery indicator shows 0%. But after 5-8 seconds everything begin work stable.

Thanks.
[One (M7) Android Development] Rajeel911:
Can I clean flash this rom with the official [full] gapps(Along with titanium backup)?

Will it cause any issues?
[One (M7) Android Development] rickliu2000:
Hi I tried to build LOS15.1 from your kernel and device tree but it stuck and reboot at boot animation :(

I think I need some help
[One (M7) Android Development] hedeon76:
Hello [MENTION=7327102]icxj1[/MENTION],

I have the last build from 25.03. tested.

Unfortunately, it does not change the problem with the Bluetooth phone call.

My interlocutor only hears a loud noise and my voice is very distorted.

Otherwise, everything runs smoothly.

Thanks for your hard work.
[One (M7) Android Development] icxj1:
You need help for sure! Way more to it then device & kernel.
[One (M7) Android Development] samhhmobil:
I even did install 0325.

The dialer-issue with proximity handling is back again. Sigh..... :(

In the previous build 0321 it did work without any issue.

samhhmobil
[One (M7) Android Development] icxj1:
Well maybe it Will work for you next build. Since it works for you every other build even when I don't change anything.
[One (M7) Android Development] icxj1:
20180326 m7ul is up. On the road didn't have time to post link. No prebuilts other than camera.
[One (M7) Android Development] samhhmobil:
Yes, you're right! :)

In 0321 proximity handling did work!

In 0325 it did NOT work.

In 0326 it works again without any issue.

This is reproducable and not randomly.

Strange, eh?

samhhmobil
[One (M7) Android Development] icxj1:
Haha! Yup, not sure the deal. I think something to do with system server.
[One (M7) Android Development] thcthcm7:
https://www.youtube.com/watch?v=ewFg5wUvkGI
[One (M7) Android Development] icxj1:
Guys check camera & flashlight qs tile. Think I may have broke it.
[One (M7) Android Development] samhhmobil:
Excuse me, I'm not native english speaker, what do u mean with "qs tile"?

GCamera and flashlight work without issues, for photos and videos.

samhhmobil
[One (M7) Android Development] icxj1:
Quick setting tile
[One (M7) Android Development] hindydidou:
GPS problems

I have been using the latest AICP 12.1 during a few months and GPS was perfect.

On saturday, with the previous rom (Mach 21nd ), I noticed a lot of accuracy and no-fix problems.

And today, during a long walk in Fontainebleau forest (near Paris), with the latest build (march 25), it was even worse. The fix with the satellites was almost impossible, and when reception was OK, the point was far from the track on the map.

I understand that GPS is not a priority for a smartphone, but I use it a lot.

Could you have a look on it ?

Many thanks.

Alain.
[One (M7) Android Development] icxj1:
OK, mine gets a 3D fix quickly. Not sure how accurate. I will check it out more.
[One (M7) Android Development] samhhmobil:
OK.

When flashlight (qs tile) is switched on, then starting GCamera, flashlight switches off and flashlight control is going to GCamera.

When GCamera app is open, flashlight control in qstile is inactive.

So everything works as it should.

samhhmobil
[One (M7) Android Development] abdrk00:
Camera, flashlight both working as they should on Sense firmware. The running services button is a good addition. (I don’t know what build it was added on since the last build I used was from 21 March). Anyways, the ROM is almost perfect for my use. Thanks a lot!
[One (M7) Android Development] samhhmobil:
My one is even precise. Delta is less than 5 meters.

No problems with 3D fix.

samhhmobil
[One (M7) Android Development] abdrk00:
Same, mine is pretty accurate too.
[One (M7) Android Development] hindydidou:
OK. I will do a "factory reset" wipe, flash again everything and test it again.

Alain.
[One (M7) Android Development] abdrk00:
View attachment 4458485

I just noticed that it shows Charging at times and Slow charging too. It keeps changing between the both. I’m using a 1A 5V charger. It used to be slow charging always.

Don’t know if its just with me or anyone else too.
[One (M7) Android Development] vasya_Vasin:
Can we find a new ROM to Verizon phone?
[One (M7) Android Development] icxj1:
I will Try to upload it soon.
[One (M7) Android Development] vasya_Vasin:
:highfive:
[One (M7) Android Development] icxj1:
Yup, there is option somewhere to show specs. You will see only 4-4.3v most times. The system is looking for full 5v. I dropped it some, & will a little more on next build.
[One (M7) Android Development] chemm30:
[/COLOR]proximity sensor is not working properly. Is there a solution
[One (M7) Android Development] evilcoleslaw:
Just flashed 3/26. Flashlight toggle works fine, camera works fine including flash settings. Proximity sensor works but seems to be requiring me to do a dt2w, which it's done before, but in the last build I ran (3/21) it was working flawlessly. It's probably just due to KA and the dt2w settings I guess. Nbd.

Also still having KA seemingly cause a system UI crash and related flakiness at first boot but it still calms down after 15-30s.
[One (M7) Android Development] :
Running aicp_m7_o-13.1-UNOFFICIAL-20180325.zip with HBOOT 1.57 S-ON Sense firmware, so far only 1 reboot. The call bug when you hear no sound when making a phone call still exist since I Nougat ROMs. I can't update my firmware since I have S-ON so does updating the firmware to a GPE firmware fix the call bug? Does anyone else experience no audio when making a phone call?
[One (M7) Android Development] evilcoleslaw:
Is it no audio when making any call, or no audio in calls after using speakerphone for any call? The latter seems to be a common bug for the M7 LineageOS based ROMs since at least Nougat. At least in my experience.
[One (M7) Android Development] :
No audio when making any calls even when I put it on speakerphone. Sometimes the audio does work and sometimes it does not work.
[One (M7) Android Development] vasya_Vasin:
i have the same issue, but i thik that problem at my phone only)) when i`m calling(no matter incoming or outcoming) 50% chance to have only silence. Verizon with soff and 1.61
[One (M7) Android Development] icxj1:
If speaker bug, make call turn on speakerphone, then turn off speakerphone & end call. If you end call with speakerphone on then you have to do that or reboot device.
[One (M7) Android Development] vasya_Vasin:
it`s interesting bug, i don`t know when it appear)) sometimese i make a call it`s silence, and i call again and it`s good, sometimes first time is good, sometimes i need reboot:D it was at 7.1 6.0 and now 8.1, but at sense roms it was good

i was think that is my phone glitch)))
[One (M7) Android Development] saentis:
For me on the newest build (and latest GPE firmware) no option to wake the screen works during an active call (be it power button, dt2w, or connecting a power source). They all work after the call has been disconnected though. Is there any way to get dt2w to work during a call that I am missing?
[One (M7) Android Development] icxj1:
Seems to be that way for everyone on every other build. Try this as as test just to see if any different. Clear dialer app data & re-dirty flash ROM. Not sure it will change anything, but worth a try. And make sure sensor block is turned off in aicp extras, I had everyone turn it on when we had reboot issue. Other then that wait to see if works on next build.
[One (M7) Android Development] icxj1:
Anyone with with proximity problem. Try this go to aicp extras/ system behaviours, enable suspend action & bump screen off time up 2-5 minutes. Reboot & test proximity during phone call.

Never mind, it only worked once.
[One (M7) Android Development] icxj1:
Suspend actions

Never mind. Worked on first call but not the next.
[One (M7) Android Development] saentis:
They both don't work for me either.
[One (M7) Android Development] Rajeel911:
You have volte in M7?

Which variant?
[One (M7) Android Development] icxj1:
Vzw, not complete yet & depends on if available from your carrier.
[One (M7) Android Development] icxj1:
Funny! Ran m7 twice no changes. Proximity worked fine on first build & not on second build. Makes no sense at all.
[One (M7) Android Development] Rajeel911:
Even I have vzw M7. Will try that withy volte sim once I install this rom,not getting time to install these days..:crying:
[One (M7) Android Development] chemm30:
Proximity sensor not working latest build 180326 do you fix its

Thanks
[One (M7) Android Development] icxj1:
Isn't that in the post you quoted & 3-4 before that.

Works for some users & not for some every other build.
[One (M7) Android Development] chemm30:
Why its changing for users.can not be stabilized.is it difficult to set the proximity sensor ro work for each user.
[One (M7) Android Development] hindydidou:
GPS is working much better now. I edited europe.zip found here to modify my gps.conf :

https://xdaforums.com/showthread.php?t=953630

and I also set server to fr.pool.ntp.org .

I 'll do more testing when rain will stop ...

And I installed spiritf.apk to use HTC built-in FM tuner.

I'm now downloading build dated march 27 to flash it tonight. But I'll probably wait a week or 2 before moving the SIM card from my S3 to the HTC and use it as a telephone ...

Alain.
[One (M7) Android Development] icxj1:
Well if I knew that then it would not be an issue. [MENTION=5992697]chemm30[/MENTION]
[One (M7) Android Development] mrakobes0001:
kill/keep process 'system' after reboot

I see that it works much faster as for me, but not excellent.

while calling it won't show screen after range sensor is disable the screen until you block ant then unblock phone with button (even while calling)

after enabling sensor with

it works normally, however has delay in 2-3 seconds

and now it show 900MB free, was 500MB

still have sometimes message with "kill/keep process 'system' ", (and always just after reboot, i`m clicking 'wait' and it works)
[One (M7) Android Development] markg546:
Hey ... Can anyone test if their volume control on headphones work with this rom?
[One (M7) Android Development] mrakobes0001:
Yes it works good
[One (M7) Android Development] markg546:
May I ask what headphone you have?
[One (M7) Android Development] mrakobes0001:
https://hotline.ua/av-naushniki-garnitury/philips-shl4805dc-mic-dark-grey/

i just realised that i've wrong understand your question, it works with on-phone control,

Just now tested with wired I-phone headphones - start-stop is working, volume-control - no
[One (M7) Android Development] markg546:
[MENTION=7327102]icxj1[/MENTION] Can you please look into Headphone volume control?
[One (M7) Android Development] samhhmobil:
[MENTION=7327102]icxj1[/MENTION]

Thanks for the build 0327. Proximity handling is working as it should. I've tested carefully during phone calls. It works without any issue and without any delays.

You've thrown away GCamera yet, what's your new favor for a camera?

samhhmobil
[One (M7) Android Development] icxj1:
Camera is same , I just did not rename it. Shows up as Google Camera now.
[One (M7) Android Development] icxj1:
Will do, I bet it is related to the BT call problem with noise & low volume output. Give me some time.
[One (M7) Android Development] markg546:
Wait how is Bluetooth bug related to aux headphones :confused:

Well Good luck then ;)
[One (M7) Android Development] icxj1:
BT headset
[One (M7) Android Development] markg546:
Wait so Bluetooth audio isn't isolated from aux audion?
[One (M7) Android Development] icxj1:
I think all the audio or any media issues are mainly due to the fact that our audio (policy, mixer)is deprecated, media (profiles, codec) deprecated. Only so much I can change, I've been back & forth with all of these since day one. One change can break audio or media completely.
[One (M7) Android Development] vasya_Vasin:
:good: new rom is gr8 proximity sensor works good
[One (M7) Android Development] icxj1:
these are todays builds. updated apps & should have all adaptive icons now. you will have to go to home settings, change icon shape to enable them on dirty flash. removed prebuilt KA Mod, it is outdated so just use playstore version. These are last builds until i have some fixes or at least till next security patches are merged. Aicp uses the second patch update on the 5th of the month normaly. if you have build with working proximity sensor then make a backup, i cannot promise it will work on this build for you. Btw, this is the same m7ul that some of you already downloaded.

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

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

m7spr += https://www.androidfilehost.com/?fid=818070582850503893
[One (M7) Android Development] saentis:
dirty flashed newest version. Proximity sensor still buggy, screen doesn't wake up on its own. dt2w during call works now, but only on about every fifth try.
[One (M7) Android Development] mrakobes0001:
call history issue

0327 - last phone calls always empty :(

and what is with OTA updates, last time i had to download it manually, OTA didn't saw any update
[One (M7) Android Development] phan_tom:
OTA update should only working for official rom. This rom is unofficial one
[One (M7) Android Development] corum3:
Great rom, really snappy and fast, however, at boot I always get the message "process system isnt responding" close or wait, I can press close or wait and it just disappears, is this any kind problem or just a glitch?

Also Skype is unable to sign in, message is "unable to sign in in, please check your internet connection" which is fine.