yashsingh1/xdaforums huggingface dataset:
[One (M7) Original Android Development] sabret00the:
Would it be possible to simply reduce the volume of the second mic by 50% rather than shut it off completely?

---------- Post added at 09:08 AM ---------- Previous post was at 09:05 AM ----------

What kinda freeze? It's stopped crashing while plugged in to auxiliary now.

I'm having a few problems with the phone locking itself when it runs out of memory. Sometimes it simply kills the status bar other times it refuses to wake up. But none are auxiliary cord specific.
[One (M7) Original Android Development] tiny4579:
It's not shut off, it's just not used in speakerphone. Are you in a loud environment? Is that why you need the second mic?

Can you check whether the memory actually gets low? While the status bar dying could be a memory issue (systemui) being killed by Android, it seems odd that that would be the case since I haven't heard a lot of cases of apps closing.

The other issue is a black screen of death and I believe completely unrelated. Some of the cm team have confirmed it. I'll ask them if they know the cause or have any idea on a fix.
[One (M7) Original Android Development] sabret00the:
Yeah, that's what I meant, shut off when using speakerphone.

And nope, sitting at my desk, phone before me and the remote party can hear themselves.

I've been playing Clash of Clans on my phone a lot. And it seem that when that's sitting in memory, I have the biggest problems.

Thank you.
[One (M7) Original Android Development] tiny4579:
For the speakerphone issue, the remote party had no problems hearing me in my test call and didn't mention their voice was echoing. I will have to test it when the phone on the desk. Maybe it's how I hold it (in hand with the phone screen facing me. According to the gerrit commit that's under review, the audio pickup was improved. I'm not sure what would cause the echo. Maybe their voice is getting picked up by your speakerphone since the mic is stronger.

Maybe Clash of Clans is a buggy game and doesn't clean itself up from memory properly. I can try launching the game, playing a few minutes and back out without closing normally and see if there's a dip in RAM available after while. Android logs when apps are killed in I believe the kernel logs, so if you pull a kernel log (/proc/kmsg) after the phone gets funky, you should see lowmemorykiller messages or pid killed messages in the kernel logs if apps are being killed due to low memory.

EDIT: I started playing it and didn't notice any odd dips in memory available after suspending or exiting it.

Why don't you try going to IRC and discussing your issue there as intervigil mentioned in an earlier post if you need to communicate with them?

I'm not sure how to reproduce either issue. I'll try with the phone further away, but last time I've seen the echo issue with my phone was early in CM development. I think you stated before that your firmware was up to date.
[One (M7) Original Android Development] Spoofy:
com.android.phone stopped working after upgrade to M5 Snapshot

Hey Guys,

OTA update to M5 has fried my phone, it wont do anything vwithout promting com.android.phone has stopped, my radio is also unusable.

Any ideas?

I have re-installed, flashed boot.img via fastboot, wiped cache & dalvik, fixed permissions....

Thanks
[One (M7) Original Android Development] tiny4579:
The error that I received is similar to the error I reported in this pastebin:

http://pastebin.com/fCcpX2JQ
[One (M7) Original Android Development] strickyy:
Not just on the latest, but on every nightly so far, especially if you try setting a lower Max frequency.
[One (M7) Original Android Development] KaZo58:
someone found out what occurs random reboots?

sometimes i have double locks. i use the pin method. before pin, slidelock appears to unlock and then pin :D
[One (M7) Original Android Development] cschmitt:
Yup, I'm working on a fix. Hopefully will commit in the next couple days.
[One (M7) Original Android Development] xiaNLJ:
where can i report bugs?

i found that after a phonecall is made , the loudspeaker is not stereo anymore , it become single sound track！！！！
[One (M7) Original Android Development] tiny4579:
Jira is the official bug reporting place but it's not accepted for nightlies. So either go back to a stable or try to fix it and submit it to Gerrit. That's been the cm rule for a while.
[One (M7) Original Android Development] knudsen81:
Does otg works on cm11

Sendt fra min HTC One med Tapatalk
[One (M7) Original Android Development] david279:
Yes
[One (M7) Original Android Development] knudsen81:
It dont show up in file manager or in storage like gpe and sense roms

Sendt fra min HTC One med Tapatalk
[One (M7) Original Android Development] strickyy:
Please also inform us here when it's implemented into nightlies so we'll know and jump right on it. :)
[One (M7) Original Android Development] :
Go to:

root ( Directory )

storage

usb
[One (M7) Original Android Development] cschmitt:
Working on the cpu min frequency pegged to max issue.

There's definitely a kernel issue with attempting to set the max frequency to anything other than 1728000, as doing so immediately forces the min frequency to 1728000 as well. This happens even by editing /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq directly. We can set /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq all day long without issue. At first I thought it might be an issue with the Processor settings code and how it's updating the cpu values. Added a bunch of debug logging and did some more testing, but no matter what as soon as max frequency is changed the min value gets pegged to 1728000. Digging a little deeper...

Can someone confirm that changing max frequency on 10.2 actually worked?
[One (M7) Original Android Development] strickyy:
I'm pretty sure it did, used mostly every CM before and always used lower than stock max freq.

And it really is a huge bug, since battery life is awful for me, and right now i'm searching for another ROM to go to.
[One (M7) Original Android Development] cschmitt:
I've seen that error occur on attempting to set max freq after the min freq gets pegged because the kernel checks for min > max and throws an exception.
[One (M7) Original Android Development] tiny4579:
I updated my post with a theory of it being related to the CM powerHAL. I'm going to test that by disabling it.

I renamed the powerHAL libs and the same issue exists. So CPU frequency is fine as long as you don't change the max though this puzzles me so I'm trying to figure it out.
[One (M7) Original Android Development] cschmitt:
It works for a bit to echo a new value to scaling_max_freq, but then check it in a minute or two, especially after coming out of sleep and min / max will be pegged again.

Also, another thing to try: open an adb shell and repeatedly issue: cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq

then lock the device and wait a minute for it to sleep, then repeatedly press up arrow enter to re-run the cat command while pressing the power button to wake the device, you'll see something like this:

root@m7ul:/ # cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
384000
root@m7ul:/ # cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
384000
root@m7ul:/ # cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
384000
root@m7ul:/ # cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
1728000
root@m7ul:/ # cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
384000

the scaling_min_freq will briefly jump to 1728000 and then back to 384000. It shouldn't be doing that I'm guessing.

Exactly, stuff like this bugs me until it gets figured out.
[One (M7) Original Android Development] strickyy:
Can't talk from the developing side of things, but locking the screen also changes the max freq to 1728 even if it stood right for a few minutes when set.
[One (M7) Original Android Development] Thismines:
is anyone having problems connecting via adb?
[One (M7) Original Android Development] tiny4579:
No, I'm not. If you are it could be a driver issue on Windows or a udev issue in Linux.
[One (M7) Original Android Development] adyscorpius:
Flash back to older version.
[One (M7) Original Android Development] Spoofy:
I flashed back to the M4 OTA and to no avail, I get android.core crashes aswell when I do that :(

Back to M5 and back to just phone crashes..
[One (M7) Original Android Development] tiny4579:
You might need to wipe data.
[One (M7) Original Android Development] :
How can I disable at the Standard-SMS the contact Images :confused:

with contacts without photo does not look good.
[One (M7) Original Android Development] EaglesGPC:
HI!

I've flashed CM11 on girlfriend S2. It has given new life for that old phone

I thought, because I did not try on my "new" HTC ONE?

My HTC today FLIES

Really fast ROM
[One (M7) Original Android Development] tiny4579:
There doesn't appear to be a way to do that.
[One (M7) Original Android Development] marvin_666:
cm 11 s

Hi, smb know anything about cm11s lockscreen?
[One (M7) Original Android Development] tiny4579:
So far I'm hearing mostly positive feedback from the few that reported it. I'm not sure why there is an issue for some where the other party will hear an echo. It's as if the mic is picking up the audio from the speaker and transmitting it back.

If others have tried it please report how well the speakerphone works.

The following use cases should be tested:

speaker phone

voice input

voice recognition

camcorder input

For those who are curious, here is the change:

http://review.cyanogenmod.org/#/c/62605/
[One (M7) Original Android Development] YouLaxy:
Is there a way to make sounds louder? I'm talking about ringtone sounds, notification sounds, in-call voice sound... Some sort of a patch, a different kernel, anything? Thanks!
[One (M7) Original Android Development] pavik62:
DSPManager

This program can still be
[One (M7) Original Android Development] thebeardedchild:
Has anyone experienced a problem where SMS notifications don't disappear automatically after reading/replying? I get a new SMS, the notification appears like normal, and no matter how I open the message (click on the notification, go into the app myself, or reply with the pop up, etc.) the bubble won't disappear on it's own unless I click the "read" button in the notification.

Anyone else getting this?
[One (M7) Original Android Development] Ke11ett:
Yeah, that keeps happening to me.
[One (M7) Original Android Development] Mashkawizii:
Nah it only does the speakerphone thing about a sixteenth of the time since the last nightly. Just be patient instead of expecting it to work perfect.
[One (M7) Original Android Development] afiqq:
so in the testing menu under phone info, we can change the preferred network type. Its always on LTE/GSM auto prl.

Is there a way to permanently change that? i want it to set to LTE/WCDMA. Ive tried changing ro.telephony.default_network=9 to 12 (because LTE/WCDMA is 12th in the menu) in build.prop but it doesn't stick after i do a reboot. Somewhere in this forum they say you have to do a factory reset to make it stick. is that really necessary? And should i include ro.ril.def.preferred.network=12 also? since its not in the build.prop.

Thanks in advance
[One (M7) Original Android Development] tiny4579:
You can change the preferred network in settings-wireless and networks-mobile networks. Tap the menu item not the on-off switch to mobile networks.

No need to do fancy build.prop or phone edits.
[One (M7) Original Android Development] PureLife90:
Do we know a work around for this? It's super annoying
[One (M7) Original Android Development] Rix70:
kernel flash question

I would try cm rom! the teamseven kernel i have flashing after cm11 first boot and configuration or flashing ron+gapp+kernel and after reboot first time ?
[One (M7) Original Android Development] pottyvick:
not sure what you're asking but rule of thumb is to flash rom, gapps then do a first boot. after it boots then go back and flash kernel...
[One (M7) Original Android Development] razorloves:
There's no workaround that I know of or have seen people post about. Except to use a different text messaging app. This bug has been going on for 5 or 6 weeks now, and not just on this device. Wonder why it hasn't been fixed. Seems odd.
[One (M7) Original Android Development] :
Does it mean the New Style from the CM11S ( OnePlus Phone ) see first Photo-Series
[One (M7) Original Android Development] YouLaxy:
Thanks for your effort but DSP Manager makes almost no difference at all. And in-call volume is still very low, I can barely hear what the other person is saying if I'm not in a quiet enviroment :(

Any other ideas? How do you make ringtones, notifications and in-call volume louder in CM11 (volume sliders are set to the max, of course)?
[One (M7) Original Android Development] elherr:
It appears that wifi died again on me this morning. The only thing I could see in log was a whole bunch of --

04-22 05:44:48.660 W/wpa_supplicant( 759): wlan0: Failed to initiate AP scan

dmesg had this:

[15154.393950] CFG80211-ERROR) wl_run_escan : Escan set error (-16)
[15154.399047] CFG80211-ERROR) wl_run_escan : error (-16)
[15154.405425] CFG80211-ERROR) __wl_cfg80211_scan : Scan err = (-16), busy?-16
[15154.412200] CFG80211-ERROR) __wl_cfg80211_scan : Unusual continuous EBUSY error, 1 0 0 0 0 0 0 0 0
[15154.424895] CFG80211-ERROR) __wl_cfg80211_scan : GET BSSID failed with -17
[15154.431914] CFG80211-ERROR) wl_cfg80211_scan : scan error (-16)

And this:

[15250.712523] mmc0: mmc_start_bkops: raw_bkops_status=0x1, from_exception=0
[15250.718596] mmc0: mmc_start_bkops: Starting bkops
[15251.066527] mmc0: mmc_start_bkops: raw_bkops_status=0x1, from_exception=0
[15251.072295] mmc0: mmc_start_bkops: Starting bkops
[15251.632445] mmc0: mmc_start_bkops: raw_bkops_status=0x1, from_exception=0
[15251.638366] mmc0: mmc_start_bkops: Starting bkops

Disabling/re-enabling wifi seemed to do nothing, but toggling airplane mode restored connectivity. Does airplane mode use RFKILL? Hmmm.

Nightly 0421. WLAN info:

root@m7:/sys/module/bcmdhd/parameters # cat info_string
Driver: 1.88.45 (r)
Firmware: wl0: Oct 29 2013 19:25:28 version 6.30.171.430.b0
Chip: 4335 Rev 1 Pkg 2
[One (M7) Original Android Development] abrakadabra_srb:
Building CM11

I'm trying to self build CM11. Now, i've managed to have it working until 27.03 nightly (or few days after). I noticed that there was a change from m7ul device name to m7 so I reupdated my repo to match the new naming and structure. I have no problems building the rom, this is the roomservice.xml im using:

<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="CyanogenMod/android_device_htc_m7" path="device/htc/m7" remote="github" revision="stable/cm-11.0"/>
<project name="CyanogenMod/android_device_htc_m7-common" path="device/htc/m7-common" remote="github" revision="stable/cm-11.0" />
<project name="CyanogenMod/android_device_htc_msm8960-common" path="device/htc/msm8960-common" remote="github" revision="stable/cm-11.0" />
<project name="CyanogenMod/android_kernel_htc_msm8960" path="kernel/htc/msm8960" remote="github" revision="stable/cm-11.0"/>
<project name="CyanogenMod/android_device_qcom_common" path="device/qcom/common" remote="github" revision="stable/cm-11.0"/>
</manifest>

Now, the problem is that when I flash the newly built ROM it boots but it is giving me a Force close loop on systemui process. I tried different branches in roomservice.xml but still the same problem. If I do a clean install (wiping everything and flashing from scratch), first boot works normally, I setup my account and everything, but as soon as I reboot the device, I get systemui has crashed loop. I checked the logs and it throws NullPointerException on DevicePolicyManager or something (had to flash back my backup since I needed the phone)...

Im guessing that my roomservice.xml is not pointing to correct branches, so can someone please tell me is my roomservice.xml correct?
[One (M7) Original Android Development] dseries60:
You could try "unlinking" the ringtone and notification volume so they are independent. This is done under Settings /sound
[One (M7) Original Android Development] cschmitt:
Are you trying to build the nightlies (cm-11.0) or stable (stable/cm-11.0) branch? It appears you're pointing to the stable branch.

What's the default revision in your manifests/default.xml: refs/heads/cm-11.0 or refs/heads/stable/cm-11.0 ?

<default revision="refs/heads/cm-11.0"
remote="github"
sync-c="true"
sync-j="4" />
[One (M7) Original Android Development] abrakadabra_srb:
Hm it is exactly how you wrote it, default revision is refs/heads/cm-11.0. So that means I totally missunderstood the stable/cm-11 naming convention... So if I switch my roomservice to point to cm-11.0 instead of stable/cm-11.0 it will infact build the current nightly?
[One (M7) Original Android Development] cschmitt:
You shouldn't have to edit roomservice.xml directly, but if you did, just remove the revision attribute.

<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="CyanogenMod/android_device_htc_msm8960-common" path="device/htc/msm8960-common" remote="github" />
<project name="CyanogenMod/android_device_htc_m7-common" path="device/htc/m7-common" remote="github" />
<project name="CyanogenMod/android_kernel_htc_m7" path="kernel/htc/m7" remote="github" />
<project name="CyanogenMod/android_device_htc_m7" path="device/htc/m7" remote="github" />
<project name="CyanogenMod/android_kernel_htc_msm8960" path="kernel/htc/msm8960" remote="github" />
</manifest>
[One (M7) Original Android Development] dseries60:
Also try setting

persist.audio.handset.mic = analog
[One (M7) Original Android Development] sharonbw:
My phone is so loud it scares me if I accidentally set the volume up all the way. I have to wonder if your speakers are gone bad. Are you under warranty?

Sent from my GT-p511x
[One (M7) Original Android Development] razorloves:
shouldn't his manifest look like this? this is untouched, except for me adding the needed muppets repo.

<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="CyanogenMod/android_device_htc_m7" path="device/htc/m7" remote="github" />
<project name="CyanogenMod/android_device_htc_msm8960-common" path="device/htc/msm8960-common" remote="github" />
<project name="CyanogenMod/android_device_htc_m7-common" path="device/htc/m7-common" remote="github" />
<project name="CyanogenMod/android_kernel_htc_msm8960" path="kernel/htc/msm8960" remote="github" />
<project name="TheMuppets/proprietary_vendor_htc" path="vendor/htc" remote="github" />
</manifest>
[One (M7) Original Android Development] abrakadabra_srb:
Here is what I have tried so far:

Building rom with stable/cm-11.0 branches in roomservice, not working

Switched between using m7 and msm8960 kernels, not working

Today I built the rom from scratch, using roomservice cschmitt suggested, and installed it on full wiped device, it worked for first boot,

second boot brought back the systemui process crashing.

Not sure what am I doing wrong, im at work now, so will try later to flash again and get the logcat from the error im getting (its still regarding DevicePolicyManager and Keyguard).
[One (M7) Original Android Development] cschmitt:
You need to extract proprietary blobs from a recent nightly build. There where a couple libs added recently related to keystore encryption and without those libs DPM will crash on boot.

Here's the commit: Revert "Revert "m7-common: use QCOM hardware keystore"
[One (M7) Original Android Development] razorloves:
Extracting props from another ROM might work but it is the wrong way of doing it. Themuppets repo I mentioned is up to date and maintained by the official cm maintainers and is used to build all official cm roms. He just needs to add that to his manifest so that he always has the correct props.
[One (M7) Original Android Development] abrakadabra_srb:
Thank you for your help, I cloned Themuppets repo (cant flash nightly on phone, need it for work) so im building the ROM right now, will let you know how it works.

Btw, is there any significant difference in using m7 kernel vs msm8960?
[One (M7) Original Android Development] cschmitt:
The CM build guides outline extracting the libs from a ROM build , but TheMuppets repo is best as it will be in sync with current nightlies.

Msm8960 is the current, common kernel so build with that. I still use m7 kernel for TWRP builds because of a couple issues with msm8960 in recovery builds.
[One (M7) Original Android Development] tiny4579:
What issues do you see with the msm8960 kernel in TWRP builds? I'm using PhilZ recovery and I am not having any issues that I am aware of using the msm8960 kernel.

On a more related note to CM11 directly,

Cyanogen recently merged a number of Bluetooth related patches from CAF from a more stable branch. I'm curious how it's working for you. I couldn't notice a huge difference.

AVRCP is still somewhat broken for me in that metadata won't update and sometimes not even show if I have my car audio system on and set to bluetooth prior to it connecting. If I turn on the car unit after letting it connect to the phone first, it works fine. I can also re-create the issue by disconnecting bluetooth and reconnect it while audio is playing. Music won't stop in this scenario and switch over to the phone speakers.

I was having issues with that earlier until I was able to narrow down just recently what was triggering it. AVRCP has been a WIP since CM11 started due to a really early merge (October 31) of a lot of patches.
[One (M7) Original Android Development] cschmitt:
An issue with ext4 and format/wipe operation taking a very long time. It's somewhat random, not every user experiences it, but the implementation used in the m7 kernel doesn't exhibit the issue.

Bluetooth has been working well for me overall.
[One (M7) Original Android Development] gorgo80:
I have a question. Is CM a good option against GE? I allways liked CM before, but heard that there was alot of issues on CM on this device. But I'm interesting to test again to see how well its working.

So just wundering how good this is as a daily driver. I'm using music, phone,sms and some gaming, but not alot of gaming.
[One (M7) Original Android Development] :
CM11 is 100% working 4 daily driving :good: chck it out

Take a look here
[One (M7) Original Android Development] gorgo80:
It was a long list of known issues.

I will install CM11 tonight, hope it work as good as I want, I have miss the CM very mutch

send from the one
[One (M7) Original Android Development] gorgo80:
I got cm installed. Everything seems to work great, no problem at all. So will run this a while and see how's is going ?

Skickat från min One via Tapatalk
[One (M7) Original Android Development] xc8118:
Back to SIM card nonsense...

recently received an insurance phone back from Asurion that is what once was m7ul, even though it is on verizon. When I attempt to flash m7vzw, i can't because it says that the phone is m7. When I flash m7, it doesn't recognize my SIM card so I can't connect to any networks. Any advice?
[One (M7) Original Android Development] tiny4579:
Have you thought that maybe they made a mistake and sent you the wrong phone? What does HBOOT identify your phone as?
[One (M7) Original Android Development] xc8118:
I think that is a possibility - but the stock rom that they sent works perfectly, so it just doesn't make sense to me.

M7_WLV PTV SHIP S-OFF RH

HBOOT-1.54.0000
[One (M7) Original Android Development] tiny4579:
Do you have the right recovery for your device? Based on above, you need the m7vzw recovery. By the way this is the thread for the international unlocked GSM model.
[One (M7) Original Android Development] xc8118:
wow... well... that was embarassing. thanks for your help.