yashsingh1/xdaforums huggingface dataset:
[One (M7) Original Android Development] scutworker:
Until recently I was using the homebrew version and it all worked well.

Since changing to the official nightlies after a clean install the phone frequently goes slow for a while under general use and soft reboots when using Google maps to navigate.

Here is my last ksmg

http://s000.tinyupload.com/?file_id=43952201219435915581

Can anybody help? I have the smartmax governor on with the settings in the n3ocort3xs kernel thread. I'm using Dalvik.

For now it's back to the homebrew version, but any help would be great. This happens with a nightly from about a week ago and last nights too.

Thanks.
[One (M7) Original Android Development] Xyleme:
I'm running nightlies (did an scary full wipe recently). Switched to Art runtime.

I'm also experiencing soft reboot...

For me seems to happen after activating and then deactivating bluetooth... But also someone avec getting disconnected from Wifi/3G...

Can't clearly put words on a bug, but sound settings are buggy for me... Sometimes too loud, sometimes stuck...

Patiently waiting for fixes has n3o seems to be working on it !

(Can someone give me a link on how to get logcat, ksmg... or whatever is helpfull for developpers ?)
[One (M7) Original Android Development] dB Zac:
I was able the to get the "Ok Google" command to work but u installing Google search using titanium backup and then reinstalling it from the play store
[One (M7) Original Android Development] Sushibagel:
I've been getting hot reboots with Bluetooth active too
[One (M7) Original Android Development] Chezbel:
You can get the kmsg using using this adb command from your PC (DOS Box or Linux terminal)

adb pull /proc/last_kmsg

That will create a file named last_kmsg in whatever directory you are in when your run the command.

For logcat you can do something like this if you want all the output to go to a file named foo.txt

adb logcat > foo.txt

If you just run adb logcat, all the output will be displayed on your PC's screen.
[One (M7) Original Android Development] scutworker:
As I mentioned above in this post:

http://xdaforums.com/showthread.php?p=50631750

I have problems when using any nightly and so am stuck on the last homebrew version.

I am now wondering if I should change my governor settings as I am using those from the Teamseven kernel thread that gives details for the smartmax governor:

Freq Range General: 270MHz - 1728MHz

awake_ideal_freq 594000

boost_freq 1242000

suspend_ideal_freq 384000

touch_poke_freq 1242000

What settings are recommended or standard for people using the nightlies? Could somebody let me know so I can give them a go. I'm hoping that changing them will sorry our my problems.

Cheers.
[One (M7) Original Android Development] samyong76:
not sure if its an app problem or what, facebook messenger doesn't work well with the facebook app. everytime i try to login to one app, the other one would say 'session expired'. this prob only started when i switched to this ROM. could it be a problem with the account syncing or sth?
[One (M7) Original Android Development] Chezbel:
[MENTION=4635674]n3ocort3x[/MENTION], does this help even more? I looked your 2 AICP commits related to the compass and ported only the compass related changes into my source code (I didn't take all the new GPE drivers and I didn't mess with flick2wake, etc).

Those changes are in the attached .7z file. I'm posting them because I can't ssh to github and I don't want to debug that again (I think this new problem occurred after my ISP changed it's routing policies related to github).

Anyway, with these changes in my homebuild the compass is working. I tested a compass APP, GPS Status and Google maps.
[One (M7) Original Android Development] n3ocort3x:
Yep it does chez. I'm still busy with other stuff and now onto a new second job so things will slow down here a bit. I merge ASAP
[One (M7) Original Android Development] Chezbel:
I got my git issues fixed, so I submitted the compass fix, here is the link

https://gerrit.omnirom.org/#/c/6005/

See, if you wait long enough someone else will do it so you don't have to ;)
[One (M7) Original Android Development] samyong76:
thanks chez. that means the latest nightly will have your compass fixes merged in as well?
[One (M7) Original Android Development] mj084:
Nope you have to pick manually..

Not merged yet...read the link;)
[One (M7) Original Android Development] n3ocort3x:
Many thanks, that saves time. :) Good guy u are :D

merging now -> merged :D
[One (M7) Original Android Development] Chezbel:
Awesome, thanks!
[One (M7) Original Android Development] scutworker:
Whenever I get an incoming call and the phone has been off for ages (so in deep sleep, I guess), I hear the ringing and vibrating but the screen doesn't wake up, nor can I wake it up.

I see the CPU minimum speed is set to 162000. Should this be higher? If not any other suggestions would be welcomed.

Cheers.
[One (M7) Original Android Development] n3ocort3x:
Don't use ondemand governor... I have to remove it
[One (M7) Original Android Development] scutworker:
I'm not, I'm using smartmax. What should the minimum speed be? Cheers.
[One (M7) Original Android Development] mj084:
Stock is 384...

With smartmax i got reboots too...
[One (M7) Original Android Development] Chezbel:
I guess everyone's hardware is a little different. I've been using smartmax for weeks without any reboots. I have I/O schedule set to "row", max speed at 1566 Mhz, min speed at 162 Mhz and apply automatically at boot.
[One (M7) Original Android Development] scutworker:
Well, I've set the minimum speed to 270 and that seems to be OK. Strangely I had it set to the same on the homebrew version and never had this problem. I'll see how it goes. Thanks for any help given.
[One (M7) Original Android Development] n3ocort3x:
next reboots: please provide a last_kmsg, thanks. then i can see if its a kernel bug or something else
[One (M7) Original Android Development] scutworker:
Thanks.

Here's one I made earlier. I was using the navigation function on Google maps and it rebooted.

http://s000.tinyupload.com/?file_id=43952201219435915581

Thanks.
[One (M7) Original Android Development] n3ocort3x:
as i thought, kernel log is klear. Good for me :D has nothing to do with kernel
[One (M7) Original Android Development] Mk.Xal:
Hi,

I am still having a strange issue with cellular network and wifi crash.

- When I loose cellular network (or maybe at anytime, I can't confirm exactly), the pincode is asked again.

- Very often, when I go from home to work and from work to home, once arrived, I can't reconnect to wifi.

Enabling and disabling wifi doesn't fix anything. it seems that wifi completly crashed (wifi still shows me network from the place I was) and enabling/disabling wifi is very fast so I think it does nothing. The only fix is to reboot the phone.

I have encountered the same issue when testing CM.

And clean install of omni doesn't fix this.

I don't know if it change something but I never updated my firmware, my baseband is 4a.17.3250.14

Thanks for your help.
[One (M7) Original Android Development] Xyleme:
Got the same pb here (regularly asking pincode, and pb connecting to known wifi). Did a totaly clean install 2 weeks ago, and I update the rom every day using delta....
[One (M7) Original Android Development] Mk.Xal:
I was finally able to reproduce the issue.

First, how to fix this without rebooting ?

- Switch On Airplane mode

- Switch Off Airplane mode

Did you use the bluetooth between your two wifi places ?

Me yes, here is how to reproduce the issue :

- Go out of range or your wifi to lost the connection

- Enable Bluetooth

- (Disable Bluetooth) edit : not necessary, bug occurs if bluetooth if still on

- Go back to Wifi Range

=> You will never be reconnected.

I was able to reproduce the issue by this way (but not every time) :

- Switch off Wifi

- Wait on cellular data to be connected

- Enable Bluetooth

- (Disable Bluetooth) edit : not necessary, bug occurs if bluetooth if still on

- Enable Wifi

On the same way, by using the second method, If I go to the wifi signal lists, The phone crash and reboot.

In attachment, I have done a logcat while testing method 2. I'am not a rom dev, so if someone can take this log and check it, maybe he can find a fix.

Edit : In attachment, wifissue2.zip :

(- Switch Off Wifi)

- Enable logcat

- Enable bluetooth

- Enable Wifi

- Wait 2 -3 secondes

- Stop logcat.
[One (M7) Original Android Development] TiesB:
Hey all,

First and foremost, I love this ROM.

There's just one thing bothering me: I can't mount any of my USB drives (OTG). :(

The adapter works on my old phone (Sony Xperia S).

Is this just me or are more people having this problem?
[One (M7) Original Android Development] Headless96:
With AOSP rom's you need a third-party app to mount, for example Stickmount
[One (M7) Original Android Development] samyong76:
hey I realised that the teamseven v54 omni kernel breaks the compass fix. heh.
[One (M7) Original Android Development] Chezbel:
Whatever code base that is built from probably needs this set of changes then

https://gerrit.omnirom.org/#/c/6005/

EDIT: Hmmm, I guess that is the same kernel that is used here, so maybe a new version just needs to be built, [MENTION=4635674]n3ocort3x[/MENTION] should know though.
[One (M7) Original Android Development] samyong76:
sure thing! keep the awesomeness coming (: I love the efficiency of the ROM.
[One (M7) Original Android Development] Mikey:
Is this project (ROM) discontinued? I hope not
[One (M7) Original Android Development] dseries60:
Not hardly..

This forum is quiet because the ROM is rock solid.

Check out Omni on G+ for the latest news. :)
[One (M7) Original Android Development] Pons:
The device has been pretty quiet, as far as commits go, but the actual ROM itself has been getting quite a few updates.

https://gerrit.omnirom.org/#/q/status:merged,n,z

https://changelog.omnirom.org/#/m7ul/next
[One (M7) Original Android Development] h4waii:
Latest nightly have been missing transparency/opacity on behind-focus windows.

Using OmniSwitch, if I enable "Dim background", no overlay is applied to the entire screen. Disabling "dim background" shows the correct darkened background on the slide-out switcher.

This also occurs with applications; using reddit sync, selecting an image preview, no overlay is set on the background window to indicate lost focus.

Didn't happen on nightly before the 15th.
[One (M7) Original Android Development] ilamaan:
[MENTION=4635674]n3ocort3x[/MENTION] development on this stopped? And does this use CM kernel?

Thanks.
[One (M7) Original Android Development] iggdawg:
Looks like there were commits on Friday per the changelog. none over the weekend, but even developers sleep =P
[One (M7) Original Android Development] Pons:
https://github.com/omnirom/android_device_htc_m7-common/blob/android-4.4/BoardConfigCommon.mk#L37

and

https://github.com/omnirom/android_kernel_htc_m7
[One (M7) Original Android Development] ilamaan:
Does it mean we have to use CM-based kernels?
[One (M7) Original Android Development] n3ocort3x:
Im still with u guys... just busy with a second job and aicp rom, i always keep an eye on this thread... no worries my friends :) im glad that its so silent here because that means that most of things are working. Also another device will hopefully arrive late april and hit omnirom... I^m just hope that [MENTION=4683552]maxwen[/MENTION] my mentor, and the other omnirom vrew can help me bringin it up *teaser teaser* and no.. its not M8 :p

no this is not cm based kernel :)
[One (M7) Original Android Development] shin06:
Waiting you for m7 ;)
[One (M7) Original Android Development] dictionary:
I want a OnePlus too, lol
[One (M7) Original Android Development] n3ocort3x:
It's find 7.

U saw my g+ post? If price is true for Austria (below 350) I sideload OnePlus to find 7.lol. Of course not because of software but if it looks cool it might be worth a try lol.. No vacation for me this year anyway... So yeah...What to do else lol
[One (M7) Original Android Development] dictionary:
No, just figured that's the only device I know releasing around the time you mentioned lol. I'm really excited. I hear Oppo makes really quality stuff, and I know the community will support it. Find 7 looks great too, but the OnePlus sounds like it's everything the Find has, for less.
[One (M7) Original Android Development] Mountainjew:
Still no progress on the music stuttering bug which has plagued this rom since December. I've tried everything under the sun to fix this and gotten nowhere. I believe it's a kernel issue. And there don't seem to be any other kernels suited for AOSP roms.
[One (M7) Original Android Development] h4waii:
I've had to switch to CM because of this. Unfortunate.
[One (M7) Original Android Development] samyong76:
the stuttering bug is random and far between. I actually got used to it after a while but it's always good to have a fix for this heh.
[One (M7) Original Android Development] Homonkuli:
How to enable multi window ? Didn't find it anywhere y.y
[One (M7) Original Android Development] v1r0x:
Multi window is not part of the nightlies afaik
[One (M7) Original Android Development] Homonkuli:
Wehre can i find the official Rom then mate?
[One (M7) Original Android Development] v1r0x:
The nightlies are the official roms.

You have to wait until the omni team merges this feature.
[One (M7) Original Android Development] thelastwilson:
This is exactly what I've been experiencing, I hoped it would go away once I finally got around to updating the rom (was running 20140320, updated to 20130421) but it's still happening :(
[One (M7) Original Android Development] Froschfinger:
Something I am not sure about... I get update notices each day, let it boot into recovery, only it does not visibly install any update. Is the ROM still being updated at any time in the process?
[One (M7) Original Android Development] manups4e:
i'm not really accostumed to this rom, i got random reboots, default camera app crashes any time i try to get 2 pics one following the other, music stutters sometimes with any application and battery life it's awful. i'm really sorry to disappoint someone ^^ but i think that with some work everything it's fixable :)

thank you for this good rom :) but i think i will revert to another :)
[One (M7) Original Android Development] Mountainjew:
Check here for updates. There haven't been any commits in ages :rolleyes:
[One (M7) Original Android Development] dseries60:
I guess devs are moving onto the M8. Thanks Omni team for all your efforts for our device!
[One (M7) Original Android Development] Pons:
Negative. That site hasn't been updated in a bit, and it's been put on the back burner. You should see no updates for any devices, not just the m7. To see all the merged commit, check out https://gerrit.omnirom.org/#/q/status:merged,n,z
[One (M7) Original Android Development] papei:
firewater on Omni

Does anyone have any experience running firewater on Omni to gain s-off?
[One (M7) Original Android Development] merrittj1989:
Sorry if this has been asked already, but will OMNI be incorporating the theme engine or remain without it?

Sent from my One using the Tapatalk app that I...paid for?!
[One (M7) Original Android Development] Mountainjew:
I've been able to reduce my music stuttering issue drastically using the xposed module 'performance profile' and setting Spotify to a higher min. Frequency and higher NICE priority. It's still not perfect, but much better than it has ever been :)
[One (M7) Original Android Development] MrAndroid-HD:
Anyone having bootloops after the 22-5-2014 nightly ?
[One (M7) Original Android Development] neptune_:
I'm on the latest nightly and getting FC when trying to open call history.

Anyone else run into this problem?

Thanks
[One (M7) Original Android Development] thegh0sts:
yes, i am getting this problem and just a few minutes ago i got an incoming call as the phone app FC'd and i don't know who called.
[One (M7) Original Android Development] dictionary:
Need more information for those with bootloops and fc. Full wipes? Different kernels? Gapps installed? Any mods flashed?
[One (M7) Original Android Development] neptune_:
OTA update to latest nightly...no mods... running aosp teamseven kernel from http://xdaforums.com/showthread.php?t=2236121

gapps installed from here http://xdaforums.com/showthread.php?t=2397942
[One (M7) Original Android Development] Pons:
A logcat would probably be useful. Hard to troubleshoot without one of those.
[One (M7) Original Android Development] hiimimtayaz:
Hi there!!!...

This rom is exceptionally great due to its wake functionality and battery performance. I'm using this since yesterday and pretty much happy with everything except I'm not able to connect my device with laptop/computer!!!!!...

What I did was, I enabled USB FAST CHARGE...now I'm completely exhausted and it really giving my a hard time....

NEED HELP????
[One (M7) Original Android Development] neptune_:
Disable Fast Charge. That will fix it.
[One (M7) Original Android Development] hiimimtayaz:
This is the very first thing which I did but nothing happened . By the way I'm using ESFILE explorer . And I'm on windows7 on pc.
[One (M7) Original Android Development] Bastaerd:
Try disabling adb debugging ;)
[One (M7) Original Android Development] hiimimtayaz:
It worked this time................... Thanks again....
[One (M7) Original Android Development] thegh0sts:
After flashing several nighties the dialer keeps force closing... Will have to do a full backup and wipe to see what the heck the problem is.
[One (M7) Original Android Development] hiimimtayaz:
I got myself updated with 4.4.3 nightly and so far works fine with xposed with not a single FC..

Try full wipe and let us know...
[One (M7) Original Android Development] Sheetzie03:
For sure the nighties are 4.4.3??
[One (M7) Original Android Development] thegh0sts:
Yes it is now in 4.4.3.

Also, I fixed the dialer FCing by wiping the contacts and contact storage in the apps manager in settings. Though restoring backup call logs will also cause it to FC.
[One (M7) Original Android Development] zelendel:
Thats why its never advised to restore any system data like call logs and such. Mainly when the base code has huge changes like the new dialer.
[One (M7) Original Android Development] thegh0sts:
I was getting dialer FCs a few nighties before the new dialer came out.
[One (M7) Original Android Development] neptune_:
Same here. Has been fixed in previous night's release.
[One (M7) Original Android Development] jedi-knight-:
How do you use multi window?
[One (M7) Original Android Development] mcduffie2010:
Must say I'm very impressed by this 4.4.3 Rom. It's working nice and smooth. No issues at all. Thanks

Verstuurd van mijn One met Tapatalk
[One (M7) Original Android Development] Bastaerd:
Has been asked before and you can google it but watch this: http://youtu.be/DNcf8K3EkXA
[One (M7) Original Android Development] v1r0x:
Afaik this feature is not enabled. They are working on a better solution:

http://omnirom.org/features/dev-diary-making-android-multi-window/
[One (M7) Original Android Development] SchmilK:
I've had no stuttering with close to 20 hours of playback using Google play music.
[One (M7) Original Android Development] mcduffie2010:
Not bad for the first battery cycle. Like I said : I'm impressed

Verstuurd van mijn One met Tapatalk
[One (M7) Original Android Development] mcduffie2010:
I've a question.

The first day after I installed the Rom I received a OTA notification witch I installed. The days after I didn't receive a notification for any new nightly. Can someone explain how I can enable this again.

Thx

Verstuurd van mijn One met Tapatalk
[One (M7) Original Android Development] MrAndroid-HD:
4.4.3 Nightlies working like a charm! Only have one little problem, since 4.4.3 my notification bar auto hides all the time, I find this slightly annoying.. And I can't figure out where to fix it?

I run Lucid Launcher - And i have unchecked full screen.

I don't find any way to foce it on in Gravity Box (Xposed)

I am by no means sure it's Omni's fault, but the problem came some days ago with the first 4.4.3 nightly..
[One (M7) Original Android Development] iossux:
how can i change launcher grip from 6*4 to 5*4
[One (M7) Original Android Development] mcduffie2010:
You can use xposed module from xgel or gravity box. Works both

Verstuurd van mijn One met Tapatalk
[One (M7) Original Android Development] mcduffie2010:
Server down?

Verstuurd van mijn One met Tapatalk
[One (M7) Original Android Development] akkufix:
I'm on omni-4.4.3-20140612 (so, 6 days till now) and this beast is running fantastic smooth. No issues found yet.

Good job, thx! :good:

---------- Post added at 12:12 AM ---------- Previous post was at 12:07 AM ----------

It is in launcher's options (long press on screen and choose options there) - change lines and columns.
[One (M7) Original Android Development] thegh0sts:
what? no new updates?
[One (M7) Original Android Development] hiimimtayaz:
I believe this rom doesn't contain theme engine???????????
[One (M7) Original Android Development] Pons:
Check the merged changes log.

Correct.
[One (M7) Original Android Development] v1r0x:
No new nightly in the last 10 days?
[One (M7) Original Android Development] Pons:
Build bot is broken for the m7s due to this not being merged. I'm working on getting this changed.

msm: vidc: Initialize kernel space stack variables

Edit: I went ahead and merged the commit. Nightlys should be backup next go round.
[One (M7) Original Android Development] papei:
Any word on the next update?
[One (M7) Original Android Development] Pons:
No word yet. I need to look into it, but don't have the time till this weekend. Also, I have a m7vzw, not m7, so there's only so much I can do.
[One (M7) Original Android Development] hiimimtayaz:
Is there any chance of adding new CM theme manager to be added in future builds???????

Desperately in need of it...
[One (M7) Original Android Development] Pons:
Test build: http://www.androidfilehost.com/?fid=23501681358556423

Have a nandroid ready. I don't have a m7ul to test this on, all I did was compile as-is (basically what the build bot would do). But the m7vzw had issues with Setup Wizard FCing, so this build may or may not work. Please let me know if there are any issues, and if so, please post a logcat and (since the last change was a kernel change) a dmesg.
[One (M7) Original Android Development] akkufix:
Ok, i gave it a shot.

Came from omni-4.4.3-20140617-m7ul-NIGHTLY and did a dirty flash in Philz 6.47.7 (because of less time atm. and only wiped cache) - booted :victory: into.

Updated supersu from market, to get latest binary.

Some quick checks with apps and settings - works fine so far. No issues found till now.

Only thing is adb shell comes up with user shell ($), not as root shell (#) and /system isn't mounted rw.

So, typed su and did "mount -o rw,remount /system" to got full access.

I will keep it and report, if i will find some probs.

Good job, thx. :good:

Edit:

Regarded some battery drain after flashed pa-gapps 4.4.4 over the night and saw cpu most time jumped between 20-40%.

Found out that google-keyboard caused this drain. After deleted kb-data, cpu only uses app.3-6% while screen on.

So, as a hint, if someone also make a dirty flash, look for it.

Rom is really good till now.
[One (M7) Original Android Development] Pons:
Nightlys are backup as of 20140703.
[One (M7) Original Android Development] v1r0x:
Anyone else with battery problems on the latest nightly? (see attachment)

And my google music doesn't play my songs (no problem with other players, e.g. vlc) and the album covers are wrong. Is there a way to reload all files or anyone else with this problem?
[One (M7) Original Android Development] akkufix:
Battery seems ok for me (i'm on this rom only since 3h), like as it was on the homemade rom.

Cpu-monitor shows me 1 to 6% while idle on homescreen and deepsleep works too.

Just installed google music to test it and it plays my songs, but i don't get any covers. Maybe google don't like metal? :D

Think you have to check your gapps (version), because i had also lot of drain, after i came from 4.4.3 omni to this 4.4.4 - see above.