yashsingh1/xdaforums huggingface dataset:
[One (M7) Original Android Development] DroidManIc:
How is the test build?
[One (M7) Original Android Development] andybfmv96:
Is there no option to turn off the low battery/charging indication for the notification light? This is an option on my nexus:/
[One (M7) Original Android Development] menos08642:
Stay away unless you like playing with very rough software. Give it a little time till they can iron out the bugs.
[One (M7) Original Android Development] pavik62:
You can take out Nexus system / priv-app Settings.apk and paste into ONE
[One (M7) Original Android Development] sensationfan623:
I see why my install wasn't working. Thought about flashing different recovery's and such, glad I came here to read what was up first :P
[One (M7) Original Android Development] twped:
Has boot loop been fixed?
[One (M7) Original Android Development] question.com:
Don't know. About to flash today's build and see if it boots
[One (M7) Original Android Development] InterFace86:
Yep. Fixed and working.

Why to ask. Try urself.
[One (M7) Original Android Development] vauge:
Only issue for me, so far on 2/2 m7, is that I cannot send pic via messages it crashes messaging.
[One (M7) Original Android Development] strickyy:
Is there a delay when pressing the power button? Or you didn't even notice it?!
[One (M7) Original Android Development] tiny4579:
I'd be curious if the cmpower module related changes like set_interactive_ext had any effect. There's been a delay since 1/26 with the new kernel. For me it was noticeable. I'm hoping the recent changes have helped.
[One (M7) Original Android Development] vauge:
The delay is

much

less than 1/30. It feels much more natural now.
[One (M7) Original Android Development] tiny4579:
Good to hear.

Can anyone comment on Bluetooth streaming? I use that in my car a lot and don't like skipping or choppy playback.
[One (M7) Original Android Development] crucky:
checked it with todays nightlie and it works like in sense roms :) used a sony sbh-52 smartbluetooth headset.i heard 20 minutes music when getting some dope xD
[One (M7) Original Android Development] Sinistersky:
Still present though. Hopefully they can speed it up in the next version...btw, which governors do you use for best performance? Cpu and ram
[One (M7) Original Android Development] question.com:
Used bluetooth streaming in my car and at the gym today. No issues
[One (M7) Original Android Development] tiny4579:
This device has been tuned for interactive for cpu so it's best to use that governor. Ondemand may be faster but it's not specifically tuned. Ram governor you mean gpu? Ondemand for that one as it's the only option. Performance might exist but it locks gpu to max. If you want max performance and don't care about battery, actually performance wherever available is what you want.
[One (M7) Original Android Development] tiny4579:
Good to hear. I should be able to come back soon.
[One (M7) Original Android Development] cschmitt:
Logcat still shows unblank display running 800 to 900mS on the new kernel.
[One (M7) Original Android Development] tiny4579:
This shows in sense as about 200ms.

02-02 16:20:08.601 D/SurfaceControl(716): Excessive delay in unblankDisplay() while turning screen on: 192ms

So this message is normal. I guess the extra delay there contributes to the cm wakeup lag.
[One (M7) Original Android Development] Spoofy:
Log file shows it crashes on tegra driver?

Really would love a fix!
[One (M7) Original Android Development] tiny4579:
M7 doesn't use tegra. That's weird if you get a terra error. Maybe the app is detecting device as tegra on cm. Posting the full logcat would help or at least the related segment.
[One (M7) Original Android Development] Spoofy:
Thanks the logcat was from a transformer, so I assumed CM was incorrectly reporting our CPU/GPU ect.

This user has found a fix, I don't fully understand the fix myself.

http://xdaforums.com/showpost.php?p=49990763&postcount=22

Thanks
[One (M7) Original Android Development] tiny4579:
Makes sense to me. If you swap /system/lib/libc.so from M2 or a build prior to Jan 17, it should work. That might be the cause of my benchmark crash.

This is the commit I believe

https://github.com/CyanogenMod/android_bionic/commit/53f15d0325feeaf7e58dc79fce4ddf55e0a64b7a
[One (M7) Original Android Development] andybfmv96:
Would that really work?

Wouldn't that cause compatibility errors?

And why wouldn't it just already be like that?
[One (M7) Original Android Development] sabret00the:
I've done some testing on the loudspeaker problems. The bottom microphone isn't being used for noise cancellation at all and also the DSP Manager presets affect audio on the other end. Audio sounds terrible by default as though all bass is being removed while the treble is turned up to max.
[One (M7) Original Android Development] Spoofy:
Thanks for that, would it have any adverse affects?

Also, I have never seen the M2 release for the M7 would it be better I use the file from that than say the 16/01 build?
[One (M7) Original Android Development] tiny4579:
Nope. Its just bionic. No changes before that day since before the m2 build.
[One (M7) Original Android Development] Spoofy:
I don't seem to have that issue running viper4droid and the Neon cortex A8 driver.

Thanks again for your help.
[One (M7) Original Android Development] kopeko:
Official

:confused: I love cyanogen but I'm wondering, will there be an official rom? or at least a milestone :confused:
[One (M7) Original Android Development] sabret00the:
The problem is acknowledged by CyanogenMod

https://jira.cyanogenmod.org/browse/CYAN-2801

So just to confirm, the mods you've installed have fixed the microphone issues on the rear microphone and have also enabled the bottom microphone?
[One (M7) Original Android Development] Sinistersky:
Thank You very much for the information, m8 :D
[One (M7) Original Android Development] Spoofy:
I don't know what changed but I can tell you since using viper4android instead of DSP my speaker problems were resolved, it even sounds better than the beats audio manager.

As for the loudspeaker issues, the only one I faced was the caller would hear a lot of white noise in the background. This seems to have fixed itself either on the 30th nightly or since using teamseven kernel.

Thanks
[One (M7) Original Android Development] fireforhire:
So the speaker phone issue has been fixed after over a year?
[One (M7) Original Android Development] sabret00the:
Nope, [MENTION=1957942]Spoofy[/MENTION] is using a third party kernel, with third party drivers and a third party sound mod.
[One (M7) Original Android Development] cschmitt:
Yes, V4A leaves Beats in the dust.
[One (M7) Original Android Development] trjlive:
There was a milestone M2 build back on January 4th, and M1 build prior to that. Most likely will be another milestone build at some point, when the developers feel the codebase is stable enough to warrant a milestone build.
[One (M7) Original Android Development] tbalden:
they were snapshot builds tagged M1/M2, you can find them here: http://download.cyanogenmod.org/?device=m7ul&type=snapshot
[One (M7) Original Android Development] twped:
So can I simply flash v4a and then it's done or must I disable DSP first?
[One (M7) Original Android Development] cschmitt:
Follow the instructions here: http://xdaforums.com/showthread.php?p=39156718

No need to disable DSP manager, just switch to V4A in sound - music effects. Don't forget to set lpa.decode=false in build.prop.
[One (M7) Original Android Development] cschmitt:
I've done some testing with speakerphone between CM11 20140202 nightly and GPE 3.62.1700.1 by switching between nandroid backups and making test calls. I find no noticeable difference of the microphone behavior between the two roms. In both roms, almost all (if not all) audio is picked up by the rear microphone when on speakerphone and if the rear mic is covered the remote party hears nothing or a very faint voice-- even when speaking directly into the uncovered lower microphone.

The rear mic is mainly used for speakerphone calls and GPE is no better than CM in terms of speakerphone performance. I have not tested with a Sense rom.
[One (M7) Original Android Development] sabret00the:
The fact the rear microphone is used isn't new information. The mystery is the sound that's in the bug linked and why there's no noise cancellation using the bottom microphone.
[One (M7) Original Android Development] cschmitt:
The point is simply that GPE and CM behave the same with respect to mic usage and noise cancellation on speakerphone. On either rom, if the rear microphone is covered the sound is attenuated. On either rom, the lower microphone provides very little input on speakerphone (which should be expected giving it's proximity to the lower speaker) , and doesn't appear to do any noise cancellation.

I find that speakerphone work well on CM.
[One (M7) Original Android Development] sabret00the:
Are you using any third party mods or kernels?
[One (M7) Original Android Development] cschmitt:
Using Viper4Android at the moment. Tested speakerphone with V4A enabled vs. uninstalled; it makes no difference on speakerphone function in my opinion.

stock kernel.
[One (M7) Original Android Development] xetrev:
its works fine for you on the m7 when hearing someone on the other line.

the person on the other end hears things differently.

call yourself or your wife/boyfriend/girlfriends phone and leave a couple voicemails. you will end up hearing a voicemail with a ton of static in it.
[One (M7) Original Android Development] cschmitt:
It appears to be an issue between radio/firmware and radio interface libraries in the rom, which is why IMEI appears blank and phone doesn't detect SIM card-- the RIL isn't communicating with the radio hardware.

CM switched from m7 kernel to msm8960 kernel on 0127 and following builds. There may be something there.

You've tried a few 4.4.2 roms, but did you flash firmware with them or only system and kernel?

You mention being on 4.19.401.8 firmware, possibly try the 3.62.1700.1 GPE firmware/radio to see it that helps.

If it was me, I would flash the GPE RUU from here, boot into GPE and see if the radio works. If it does, then flash TWRP and the latest CM build and see if using the 3.62.1700.1 firmware takes care of it.

I'm using the 3.62.1700.1 firmware with the 4A.22.3263.14 radio from the Dev Edition 4.06.1540.2 build.
[One (M7) Original Android Development] trjlive:
Thanks for the reply! I'll give the 3.62.1700.1 RUU a go tonight and then try CM11 latest nightly again, and see how that works. I remember reading about the new CM kernel, but it just didn't click in my mind that maybe there's a firmware incompatibility. I've usually tried to run the latest firmware, but I'll revert back to the GPE firmware and see how that works. Thanks again! I'll share my results after I've done all these steps. :)
[One (M7) Original Android Development] jasalta387:
This is my firmware config too, although I'm not 01/26 nightly still, running smoothly. I upgraded the firmware last weekend. I didn't update CM yet because of the issues with new kernel. Moreover, I like to update one thing at a time and use it for a couple of days to test in isolation.

Please report if downgrading to 3.62.x firmware is solving the issue you have.
[One (M7) Original Android Development] trjlive:
Well, I've not had any luck with post-2014-01-24 builds. I first tried the 3.62.1700.1 RUU as [MENTION=4513061]cschmitt[/MENTION] mentioned to do, still got the same SIM card error message with CM11 2014-02-04. I then wiped and reflashed 2014-01-24 build and it works just fine.

So I tried a few of the other previous firmwares (and their corresponding matched radios) I have used in the past (and that worked just fine with CM11 prior to 2014-01-24), including 4.06.1540.2, 3.62.401.1, 3.58.1700.5. With all these firmwares, the result is the same: CM11 builds 2014-01-24 and prior properly detect my SIM card connect to the mobile network. All builds released after 2014-01-24 give me the Insert SIM Card error (attached screenshot).

I tried both 2014-01-24 and 2014-02-04 builds on each of the firmwares to make sure the results were valid. On each firmware, I flashed both builds, with full wipe (data, system, caches, sdcard) between each flash. I even tried flashing the teaMSeven-cm11-v2.3.6c3 kernel after installing 2014-02-04 build, and it doesn't make any difference, it still doesn't detect my SIM card.

I'm pretty frustrated at this point. I've enjoyed using CM11 on my One, but it seems like my device just doesn't like the new builds, it's like I've hit a brick wall and can't utilize the new builds anymore. Are there logs somewhere that would show the system trying to read the SIM card or connect to the network? There's definitely something different between the pre-01-24 builds and the later builds.
[One (M7) Original Android Development] cschmitt:
Might try this build: cm-11-20140203-UNOFFICIAL-m7.zip. It's 20140203 compiled with the pre-0127 m7 kernel. It will allow you to rule out the kernel change as possibly the cause, although I would expect many others reporting the issue if it was.
[One (M7) Original Android Development] jasalta387:
Well, this actually depends on whether the users jumped to the new firmware.

It'd nice that [MENTION=5362940]trjlive[/MENTION] tries the unofficial build you shared, and any other user reports if the newest firmware (4.19.401.8) and recent CM nightlies work nicely.
[One (M7) Original Android Development] psychomaniac189:
Anybody still have the extra long time to get the screen to turn on?
[One (M7) Original Android Development] trjlive:
I will do this later on today and report back. Lots of meetings this morning, but should have some time this afternoon. Thanks guys, I appreciate the suggestions and help to figure this out! :)

(I'm out of thanks for the day, but I will come back and get you both when I get more)
[One (M7) Original Android Development] Gunman84:
i do:rolleyes:. And i don't get it why this game GTA San Andreas isn't working on the latest builds, it did work before :confused::confused:
[One (M7) Original Android Development] question.com:
Can anyone reboot into recovery via the power menu? I always have to manually boot into the bootloader and select recovery
[One (M7) Original Android Development] cschmitt:
That's another side effect of the switch to the msm8960 kernel, along with sluggish screen wake, and funky screen brightness on wake.
[One (M7) Original Android Development] question.com:
Thanks for the update. Been going on for some time. Didnt know if I did something here.
[One (M7) Original Android Development] menos08642:
I've still not seen a reason for the switch to the msm kernel. What should it give us in the long term?
[One (M7) Original Android Development] trjlive:
So I just flashed this build on my device, running firmware 4.19.401.8, and to my surprise, it's working! It detects my SIM card and I have fully functioning LTE.

Just to double-check, I re-flashed the 20140203 official build, and got the "Insert SIM card error". Reflashed this unofficial build again, and it works. So it's definitely kernel related.

So it seems that for some reason, the new kernel doesn't like my combination of firmware and SIM card. Thanks for this custom build, at least now I know what was causing my SIM card errors. Though I'm not sure what the long-term solution is.
[One (M7) Original Android Development] cschmitt:
Hey, that's great! So that does tend to point to msm8960 kernel, since I mainly reverted the 4 commits in m7-common that switched the build away from the m7 kernel. (there are also some local audio service and exchange mods that I keep, but those won't affect radio function.)
[One (M7) Original Android Development] Spoofy:
Hi cschmitt,

I love using CM and prefer Neo's Smartmax CPUQUIET Kernel, unfortunately it is not based for the new CM. I am assuming your copy will work with it, will I be missing anything major by going to your version of the ROM?

Thanks
[One (M7) Original Android Development] broduderson:
I'm aware that this is a nightly kernel but how stable is this ROM besides the sim card issue with the new kernel? I've been wanting to go back to CM11 and give it another shot since there's a single maintainer for the ROM now. I was also wondering about the battery life fully stock. If anyone can comment on this I'd appreciate it!
[One (M7) Original Android Development] Spoofy:
Fully stock - The battery life is not the best, the last Milestone (snapshot) release along with TeamSeven's CPUQUIET Kernel does result in some great performance and battery life.

The new nightlies are great but do have some minor issues with the new Kernel and it's compatibility with all Kernels bar the TeamSeven Stable for CM11.

Thanks
[One (M7) Original Android Development] jasalta387:
Well, I guess I will be suffering the same issues that you reported, once I upgrade to a newer nightly (currently on 01/26).

The strange thing is that you could not get rid of the SIM card errors even when downgrading your firmware!

To all: anyone running lastest CM official nightlies and firmware 4.19.401.8??

We should try to get some logs and see if the msm kernel can be patched :eek:
[One (M7) Original Android Development] adyscorpius:
I have found a major difference in loudspeaker performance ever since I moved to GPE firmware. The CM ROMs happen to not have the loudspeaker issue, unlike earlier, when I had the Indian stock 4.3 firmware, which caused the mic not to work properly.

Basically, CM + GPE firmware = GPE mic performance on loudspeaker calls.

CM + Sense firmware = Different problems

I haven't gone back to Sense and tried, but after moving to full GPE firmware, I haven't had loudspeaker issues on CM or other AOSP ROMs.
[One (M7) Original Android Development] sabret00the:
That's actually a really helpful post. I'll look into switching over to the GPE firmware.
[One (M7) Original Android Development] tjsooley:
It works fine for me

Newest nightly newest GPE firmware
[One (M7) Original Android Development] qixiixiq:
Quick menu User Switcher

latest build is looking good. I am just having one issue with the quick menu user switcher. At some point the default user in the quick menu switched from one account to another (i have five accounts on this device) and i cant seem to switch it back.

When i click on the user avatar in the quick menu i am taken to the user profile but there is no way to switch to another user as default. Can this be done via adb if not through the android UI?:confused:
[One (M7) Original Android Development] cschmitt:
You incorrectly assume I'm somehow against you on this.

I was looking into the bug report to try and understand the issue and see what could be done and noticed a comment 'The only working speakerphone is in Google Play edition and Sense based roms'. Decided to look into the audio setup between GPE and CM11 and do some testing on how they both behave on speakerphone, then objectively report the results both in response to CYAN-2801 and in this forum, which is that GPE and CM11 speakerphones perform similarly.

It's important to point this out because the first step in addressing an issue is truly understanding it's cause and the conditions under which it occurs. I've found what Ethan reported in CYAN-2801, that CM11 is using the GPE setup, to be correct and that the GPE setup does work on CM11 at least as well as it does on GPE.

So the notion that GPE's speakerphone works and CM11's is broken is false-- therefore any attempt to 'fix' CM11's to work like GPE is probably a waste of time, because it's already there.

Is there room to enhance the performance of the speakerphone in general, certainly. Anyone is welcome to submit patches to that effect.

On the subject of firmware: I had mentioned that GPE DSP firmware works well with speakerphone back in mid-December: here. Guess you didn't jump on it then.

...mod edit
[One (M7) Original Android Development] qixiixiq:
Boot into recovery

What recovery are you running? i am using the latest twrp and havent had this issue at all. i have been on daily nightlies since cm11 development started.
[One (M7) Original Android Development] krook6023:
Quick thread cleanup with the hopes we can get back on topic and not let this get any further out of hand. It is fine to disagree with someone but there is no reason to make it personal. I suggest that we all frame our posts with the intent to further development and not to prove someone wrong.

krook6023 (mod team)
[One (M7) Original Android Development] flojho01:
Same issue (Boot to recovery) with CWM 6.0.4.4
[One (M7) Original Android Development] qixiixiq:
reboot into recovery

try upgrading to the latest recovery. I had a similar issue when i first made the jump to cm11 from cm10 and i read somewhere that cm11 required a recovery upgrade for compatibility reasons.

Personally i use twrp but upgrading your recovery to a later version should fix that.
[One (M7) Original Android Development] broduderson:
So the TeamSeven kernel is incompatible with the latest nightlies? Also, if I wanted to go back to the milestone 2 snapshot (I'm assuming you're talking about cm-11-20140104-SNAPSHOT-M2-m7ul.zip), is It okay to do a dirty flash? Thanks again :laugh:
[One (M7) Original Android Development] question.com:
Gpe firmware? So you're not running cm11? I see everyone that's running the latest nightly can't reboot into recovery Due to the kernel

---------- Post added at 12:08 PM ---------- Previous post was at 12:06 PM ----------

Latest twrp this issue started a few nightlies back. I've even flashed the latest recovery a few times just to make sure
[One (M7) Original Android Development] tjsooley:
I am running cm 11 with the gpe firmware

gpe firmware is all the other stuff in the gpe ruu other then the android os and data partitions
[One (M7) Original Android Development] broduderson:
I'm running the latest firmware (non-GPE) and I dont have any of the sim card issues or problems booting into recovery.
[One (M7) Original Android Development] Spoofy:
How do I flash the GPE firmware?

---------- Post added at 07:56 AM ---------- Previous post was at 07:54 AM ----------

The CPUQUIET version is incompatible with the new nightlies, there is another team seven cm11 kernel that works but it does not have the smartmax governor.

I have not done a dirty flash going backwards, I'd assume clearing dalvik and cache should suffice but I'm no expert.

Thanks
[One (M7) Original Android Development] tjsooley:
Search is your friend
[One (M7) Original Android Development] psychomaniac189:
I'll prolly stay on 01262014 nightly forever till the screen turning in problem is fixed. I just keep checking this thread.
[One (M7) Original Android Development] Fuzzydamnit:
So where do i find . . .

Anyone know where i can find 20140126??
[One (M7) Original Android Development] cschmitt:
Here : http://d-h.st/lTe

MD5:

f8762454978b5eca48e1062fa138245b
[One (M7) Original Android Development] gorgo80:
4.4.2 Firmware from OTA: http://d-h.st/htu

Is the link for latest gpe Firmware 3.62.1700.1? Do I also get the stock recovery so I then need to flash latest Cwm again?

The reason why I wunder this is couse in the cm11 three some says that it's better to use the gpe firmware than the sense firmware
[One (M7) Original Android Development] Spoofy:
Do you know what the difference is? How does it make it better?

Thanks

Edit: for those waiting, neo's kernel has been rebased and is now compatible.
[One (M7) Original Android Development] gorgo80:
Doesn't really know the difference, but just heard it was better. I will do some testing to se if there any difference :)
[One (M7) Original Android Development] Atrax_:
No nightlys from february for m7ul?

Gesendet von meinem HTC One mit Tapatalk
[One (M7) Original Android Development] minty1978:
They all come under M7 now..
[One (M7) Original Android Development] KeepingItCuttingEdge:
The build.prop is locked and I can't save it after modifying. This is a simple chmod correction I believe...
[One (M7) Original Android Development] Hedi86:
You need a root explorer

Gesendet von meinem One mit Tapatalk
[One (M7) Original Android Development] tiny4579:
Stock as in stock sense. A stock ROM will do.
[One (M7) Original Android Development] Upstreammiami:
No sh*t lol