yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] MWisBest:
Sorry for the delay with getting a new build up and replying to posts, been a little busy lately. I'm working on a new build now and when I get it uploaded I'll go over and reply to what I've missed in the past week.
[Samsung Galaxy Nexus] MWisBest:
If this is the case, then whatever changes occurred in OmniROM between 12/29/2013 and 01/02/2014 or so are what introduced it. I'll have a look at what they changed in there.
[Samsung Galaxy Nexus] MWisBest:
Alright, new build is up. It's very late here so I'll have to reply to posts tomorrow, I gotta get some sleep before I drop dead!
[Samsung Galaxy Nexus] fk.gregor:
whats new in this build?
[Samsung Galaxy Nexus] Enter The Nexus:
look at the changelog...
[Samsung Galaxy Nexus] fk.gregor:
I can't read!!
[Samsung Galaxy Nexus] MWisBest:
I don't believe they persist on reboot, however you could get Terminal Emulator on your phone, then do something like...

logcat > /sdcard/logcat.txt

...as root of course. That will send the output of logcat to that logcat.txt file, and it should still be there if the phone needs a battery pull/reboot/etc.

ActiveDisplay is really... messy. There's a lot of glitches and stuff with it.

I don't think that's in OmniROM yet. I'll look into it.

I can't reproduce this, please check again with the latest build.

The pink flash thing is akin to what was happening when I was working on updating the GPU drivers, so I assume there's something tripping up the GPU drivers. Try and get a logcat of this if you can, see above for a way to do this without being hooked up to a computer or sitting there waiting for the problem to happen etc.

I'll change the default setting for the vibration length. In the mean time, go to the AOSP Keyboard Settings, scroll down to Advanced Settings, and change the Keypress Vibration Duration to something like 10ms or so.

I'm not a big user of alarms, can you check with the latest build to see if it was fixed? If it is still giving you problems I'll look into it more.

I'm not having this issue, if you could get me a logcat of it or at least try with the latest build that'd be great, thanks.

Thanks for the heads up on that, I'll definitely take a look at it.

1. Thanks, but no need to be so harsh!

2. No, I'm still here. :P

To all who addressed the screen freezing stuff, let me know if the newest build is any better. Thank you!

Oh BTW, for those who have gotten logcats before you may have noticed some spam from "Tuna PowerHAL" or something like that about not finding a file, I shut that up recently so it won't be flooding your log.
[Samsung Galaxy Nexus] fk.gregor:
Thanks for the respond on the hepatic feedback. Strange enough that option is available for me to edit from the keyboard setting. I'll look more at it, maybe I don't have something selected. ROMs awesome so far though man.
[Samsung Galaxy Nexus] DevVorteX:
Too big a post to quote, so I'll make a comment about the radio stability. The latest commits in my development branch are proving pretty solid. The last ones I sent you have an issue going from 3g back to 4g. If you want more details, feel free to pm me.
[Samsung Galaxy Nexus] Enter The Nexus:
Reminds me of this...

[YOUTUBE]watch?v=6eWz-wdSj7I[/YOUTUBE]
[Samsung Galaxy Nexus] namelesske:
Can i flash it to maguro? Its supports dirty flash from CM11?
[Samsung Galaxy Nexus] metalspring:
No, toro only...
[Samsung Galaxy Nexus] MBQ_:
Dude, Tyler+BBNG is DOPE.
[Samsung Galaxy Nexus] fk.gregor:
I figured out the vibration settings. That was my bad.
[Samsung Galaxy Nexus] MWisBest:
Thank you for the heads-up.

At the moment it is indeed toro only. Once I get a few things done on my FML to-do list, I'll be looking at the feasibility of getting FML going on maguro and toroplus. There has definitely been enough interest in it lately for me to consider it.

Glad you got things sorted out! :)

Can you guys that were having freezing problems check if the new build has made any improvements? I've been dumping logcats 24/7 like I described above and haven't been able to come up with anything yet, since the 2014/01/01 build I've only had one freeze, and since I wasn't expecting that to reappear I wasn't running logcat or anything. I'm going bonkers trying to track this thing down! I really do think it's a kernel issue, and not something with OmniROM.

Since I think it's a kernel issue, that would mean using a different kernel could resolve the issue. One kernel I remember as being extremely stable is LeanKernel, and was wondering if you guys have tried it (or could try it) and see if it resolves the screen freezing problems.
[Samsung Galaxy Nexus] joeygutz:
kernel

Metal do you have a recent link for the latest lean kernel i will give it a shot....i was thinking the same thing maybe a kernel issue i have had about 3 reboots since last night.....
[Samsung Galaxy Nexus] Rushead:
http://xdaforums.com/showthread.php?t=2028549

Or from the horse's mouth:

http://rootzwiki.com/topic/13092-kerneljb43-v83-102413-leankernel-minimalistic-kernel/

Sent from a flashead cracker.
[Samsung Galaxy Nexus] namelesske:
Thanks for your answare. So i need tap the F5 button for some weeks :)
[Samsung Galaxy Nexus] neilwashere:
For me the random reboots only happen when I am about to call someone and I open up my phone app. It always freezes right when I click it then reboots. Even with the latest build.
[Samsung Galaxy Nexus] MWisBest:
Is this with a different kernel, or the stock one?
[Samsung Galaxy Nexus] hsypsufan:
I have the same problem when I open the phone application. My phone hangs and I have to pull the battery. This does not happen every time. Usually after I use it once after boot. As a preventative measure, I have been clearing out the phone app from memory. This seems to help. I am using the stock kernel.

Thanks for your great ROM!
[Samsung Galaxy Nexus] fk.gregor:
I'm using golden kernel and its pretty solid.
[Samsung Galaxy Nexus] rbrenart:
Clean flashed 1/1 then dirty upgrade to 1/9.

Black screen this morning and couldn't wake the phone. Was not on the charger, but after battery pull reboot I still had 40% battery.

No kernel swaps so far. On 1/1 I had similar freezes twice.

Just a report, still living the ROM... Just using a backup alarm clock on test days!
[Samsung Galaxy Nexus] terminal13:
Had a serious hot reboot issue with the messaging app. Got into a pattern of either attempting to use voice typing g or standard replies would cause an instant hot reboot.... seemed to clear up after a bit... just some fyi....
[Samsung Galaxy Nexus] neilwashere:
On stock kernel
[Samsung Galaxy Nexus] rstokc:
Okay, I figured out my issue with the dots on the widgets stopping half way through. Apparently there is a maximum number of page dots that will display even if you have more widget pages than that. When you get to the page with the middle dot, the dots won't change again until you get to the point that the number of pages remaining matches the number of remaining dots. For me, that meant the dots didn't change until I had flipped through six more pages, then they started changing again. I just usually never went that far.
[Samsung Galaxy Nexus] MWisBest:
I didn't know you could have so many widgets! :eek:
[Samsung Galaxy Nexus] rjs987:
I am still getting the random lockup which needs a battery pull. Others still having this issue?
[Samsung Galaxy Nexus] MWisBest:
I'm working my ass off on fixing this. All the work that I did on adding the bells and whistles to the kernel is being completely redone, and it's not easy. I'm hoping to have a new build up today that fixes this stuff.
[Samsung Galaxy Nexus] metalspring:
Are you using the latest changes omni made to frameworks/native? They discarded like 70 commits and switched to cms opengl version, which along with the other newer commits should fix the graphics reboot issue with omni (which was the main cause of reboots before shown by logs I had in older builds)

If you still have reboots after that then it probably is a kernel issue
[Samsung Galaxy Nexus] MWisBest:
I am. It was more than just frameworks/native that had stuff discarded too if I remember correctly. They had stashed the "discarded" stuff into a different branch (old-4.4), and I did the same (putting it into omni-4.4-old). It's definitely the kernel, and I stashed the changes I had made to the kernel into a different branch and started from scratch again.
[Samsung Galaxy Nexus] MWisBest:
New build up. This should fix the screen freezing problems. If it doesn't, I still have a few things I can try.

EDIT: I ended up getting a lockup, but different from the usual ones: the phone rebooted itself at least. Had the slight pink flash thing before rebooting, and it happened after playing a pretty intensive game for at least an hour. I was able to get a last_kmsg to help in debugging this. In particular, this is certainly helpful (followed by another 1500 lines or so):

[ 5803.794769] PVR_K:(Error): SGXOSTimer() detected SGX lockup (0x113e0 tasks) [1386, /home/kyle/OmniROM/kernel/samsung/tuna/drivers/gpu/pvr/sgx/sgxinit.c]
[ 5803.794982] PVR_K: HWRecoveryResetSGX: SGX Hardware Recovery triggered

(For those unfamiliar, the Galaxy Nexus uses an SGX540 for the GPU, so it's the GPU going bonkers here).
[Samsung Galaxy Nexus] jpildave:
don't judge me, but...

I just upgraded to the latest for 1/15 build, so I'll let you know if I experience any more lockups, but... I did notice that Candy Crush still doesn't work. :eek:

Anywho, like I said, don't judge me, but I noticed it hasn't been working, so I thought I'd drop you a line!

As always, thanks for the hard work! :good:
[Samsung Galaxy Nexus] MWisBest:
I'll try Candy Crush and see what's going on. I've never played it before to be honest.

EDIT: BTW, for the next build I'll be trying to get Link-Time Optimization going again, along with trying a few things to fix the rebooting problem. At the very least the rebooting problem now actually has the phone reboot itself rather than requiring the battery pull it did before, and by the looks of it I don't think it's actually kernel related anymore and the commits [MENTION=4328678]metalspring[/MENTION] posted on page 106 might just be exactly what's needed to fix this.
[Samsung Galaxy Nexus] jpildave:
Okay, cool... BTW - What happens for me is that when you try to open it, all you see is the orange "King" splash screen like it's getting ready to load, but then it craps out and you go back to your home screen.

So important, I know...
[Samsung Galaxy Nexus] domenci:
In post 1105 metalspring asked if you were using the latest commits and in post 1106 you said you were... trying to figure out if I should flash this latest build or stick with 1/9 which has only crashed twice, until your next build

either way thanks for your work on this ROM, works pretty well most of the time and has the options I want
[Samsung Galaxy Nexus] MWisBest:
That was concerning a different matter. OmniROM had a "reset" of sorts on a few things, metalspring was making sure I had picked up on that.
[Samsung Galaxy Nexus] devator22:
Bluetooth works near flawlessly for me since you switched to omnirom. I use bluetooth constantly, so thanks for that.
[Samsung Galaxy Nexus] MWisBest:
I'm glad to hear that. CM was definitely really finicky with Bluetooth, which was another thing that pushed me to switch. I think that was related to all the Qualcomm stuff.

I haven't had the issue of the phone rebooting for some time now, I think the phone just needed to stabilize a little bit, might've been SmartReflex calibrating things. I'll adjust the voltages for the next build. I've had some internet issues since last night so I haven't been able to do much dev stuff, and I got some school things to get done as well as some work on my car, so it'll be a day or two before I get a new build out.

EDIT: AOSP has done quite a bit of work on ART in the master branch, looks feasible to port some of the stuff to the kitkat branch... are there any apps you guys use that don't work on ART which has prevented you guys from making the switch to ART (besides Xposed of course)? I know there's that list of apps that don't work with ART, but I'd rather just focus on stuff that I know is really being used...
[Samsung Galaxy Nexus] rice923:
Just switched to the 1/15 build yesterday (wiped cache, Dalvik, system, and data). Things are pretty smooth except for a few things so far:

1) Launching Yelp will occasionally cause the phone to reboot itself. However, this has been the case since the first build of FML for me.

2) When receiving a call, the display takes significantly longer to show the caller than when I was using CM based FML.

3) When plugging in the phone, the phone does not give me any sort of indication (vibration, display turns on, sound etc.) that it has started charging. I'm assuming this is an option that I missed somewhere in the settings.

4) The quick settings tiles seem to be missing a few options that I would consider relatively common: LTE toggle and tethering.

I've only used this build for less than 24 hours so I might just not know where to look for certain things. Please correct me if that's the case.
[Samsung Galaxy Nexus] cd95yj:
As far as charging the phone there is an option under display that wakes the phone when plugged in or unplugged.
[Samsung Galaxy Nexus] huizingajm:
Switched over to Vanir just to try it out. No problems with Vibrate and Sound cutting out.
[Samsung Galaxy Nexus] RoxRedEye:
Running the 1/15 build and so far it's great! Smooth and quick.

An honest and sincere opinion -- Navigation Bar customization (i.e AOKP-like) and Nav Bar cursor keys would be an amazing addition to this rom.
[Samsung Galaxy Nexus] MWisBest:
I'm hoping to get a new build up today sometime.
[Samsung Galaxy Nexus] MWisBest:
Sorry I didn't get a new build up, testing of it wasn't going very well. Hopefully I'll have the issues resolved today.
[Samsung Galaxy Nexus] rjs987:
Does anyone happen to know the Clock widget that is included with this rom? I was wondering if it could be used with other roms?

Thanks
[Samsung Galaxy Nexus] kdmhong:
Is Voice+ implemented with the OmniROM? I'm curious because Voice+ does wonders with Hangouts SMS and Google Voice.

Thank you!
[Samsung Galaxy Nexus] ricola1989:
What does Voice+ do anyways?
[Samsung Galaxy Nexus] MWisBest:
FML. After an update to my laptop I use for dev work (I like to call it my "development slave" lol), it's segfaulting on boot. Spent a while trying to fix it without any luck, so I decided to do a fresh Linux install. Unfortunately, the folder containing all the FML/OmniROM source code was too large to be able to back it up to any storage devices I had, so I'm having to redownload all the code which takes hours at best.

The month of January has been absolute hell for me. It's really been Murphy's Law at its finest. I keep hoping that I'll wake up and it turns out January was just a big nightmare. Let's hope February turns out better.
[Samsung Galaxy Nexus] rice923:
Hey don't sweat it over this ROM. We still appreciate everything you're doing for us, especially when the quality of your ROM justifies the waiting.

Thanks for keeping us up to date even when you don't have to. Hope your laptop Is back to normal. Keep up the good work!
[Samsung Galaxy Nexus] metalspring:
Voice+ is a cm specific thing
[Samsung Galaxy Nexus] rice923:
How do we use the "cast screen" function? Does it simply recognize miracast devices on the same network and give you a list of those available devices to cast to?
[Samsung Galaxy Nexus] buhohitr:
Yes, you're correct!!
[Samsung Galaxy Nexus] rice923:
Oh nice, so I can just buy some generic miracast dongle and cast?! I've wanted to do that for so long
[Samsung Galaxy Nexus] buhohitr:
If you want android on TV and turn your TV into a Super Media Center, then buy an Android TV box instead. It plug right into your TV hdmi and now you have FULL android on your TV with XBMC, real browser, all the apps from playstore, youtube, hulu+ etc...you get the picture! Finally use your phone as wifi remote control. XBMC is a super media app, you can stream/download latest movies and such in HD/720/1080 quality..the possibility is endless. In summary, your TV is exactly same as your phone but with a much bigger screen, connect directly to the internet, never run out of power....Also if you go over to friend house or family, just bring this little box and you all can enjoy movies/music/photoes etc,, on big screen.
[Samsung Galaxy Nexus] Sheetzie03:
Wouldn't this be the same thing as using the Samsung HDMI dock for the gnex?

If not, whats r difference? Thank you
[Samsung Galaxy Nexus] buhohitr:
The results of watching movies/TV etc..are the same, but what you give up is convenience:

1) Everyone in your family need your phone to watch movies, without your phone (if you out of the house), no one can watch, unless everyone in your family each has SAME smart phone or you will need to get the adaptor for each phone.

2) You need to get off the couch to make changes, like change channels, volume, switching movie etc...(This is a big deal to me).

3) While watching movies, you can not use your phone like texting/receiving/making phone calls.(This is a big deal to me)

I brought 3 of these for each TV in my house and all my kids can enjoy their own Android on TV while they browser/chat/talk/text on their phone.

It's a matter of luxury and convenience...your choice!!
[Samsung Galaxy Nexus] Sheetzie03:
Awesome explanation, thank you and much appreciated! Good day to you sir
[Samsung Galaxy Nexus] MWisBest:
New build up. Check the changelog.

*passes out*
[Samsung Galaxy Nexus] newellj79:
Is the multi window function cherry-picked in these builds? I hope to be coming into a gnex soon and am really looking forward to rocking omni on it!
[Samsung Galaxy Nexus] metalspring:
I don't think so...?

And multi window is going through a few changes to improve the multi tasking so it wouldn't be the best time to cherry pick it

Also, it still has a few bugs that need ironing out (which is why it hasn't been merged officially)

But [MENTION=3390093]MWisBest[/MENTION] if you wanted to include it since it's one thing omni is known for, as of patch set 18 in the gerrit commit it works well enough (only a few little occasional issues but I'd say it's 99% fully working)
[Samsung Galaxy Nexus] newellj79:
Thanks for the reply. Patch set 18 works awesome for me on nexus 10. Very rarely any issues. I've tried patch set 21 and it still has a ways to go. In either case the possibilities are awesome. I was hoping for a toro build with it though. ?
[Samsung Galaxy Nexus] MWisBest:
Gah, still busy. The next day I should have free is Tuesday, hopefully then I'll be able to help [MENTION=4328678]metalspring[/MENTION] with getting the vendor repos setup for toro and toroplus to get official OmniROM builds going for them. Then if I still have time left over I'll look at the multi-window stuff.

I'm starting to think I run on Valve Time.
[Samsung Galaxy Nexus] MWisBest:
New build up.

EDIT: Oh wow, I didn't even realize it has OmniSwitch added. Thanks XDA news for the heads up, xD!
[Samsung Galaxy Nexus] joeygutz:
Rom

Metalspring this Build is got to be the best yet!.....Thanks, Im loving the Omniswitch as well....Running smooth as can be.:good:
[Samsung Galaxy Nexus] metalspring:
You mean [MENTION=3390093]MWisBest[/MENTION] lol

Actually most of the linaro fixes I use for my builds came from his github and he has helped out with quite a few errors I had as well.

So if anyone here ever ran my builds, please give MWisbest here some thanks
[Samsung Galaxy Nexus] joeygutz:
Correction

Thanks for the correction , MWisBest thanks for such a great build!.......Really enjoying it!
[Samsung Galaxy Nexus] Sheetzie03:
?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] domenci:
the new Omniswitch does seem neat. I would like to try replacing the standard recents functionality with this rather than having a blue dot on the side of my screen or even having to reach over there. I don't see how to do this, perhaps I'm missing something. I was thinking just replace the action on the recents button but I can only get the settings to show up when I press it. Any ideas?
[Samsung Galaxy Nexus] neilwashere:
New build is flawless for me. Omniswitch is awesome but when I enable it the settings only stick for about 10 minutes. Anyone know a workaround?
[Samsung Galaxy Nexus] rstokc:
I have the same issue.
[Samsung Galaxy Nexus] neilwashere:
weird....I also have the same issue when I try to overclock in performance
[Samsung Galaxy Nexus] metalspring:
I think they fixed it in source since then
[Samsung Galaxy Nexus] neilwashere:
oh ok I figured they would eventually
[Samsung Galaxy Nexus] rice923:
Latest build dropped my LTE signal (doesn't even revert to 3g, just no data at all). Restored to previous build and it's working again
[Samsung Galaxy Nexus] pattyboi:):
did you reboot twice? like after flash boot,then reboot,normally that fixes it for me.
[Samsung Galaxy Nexus] rice923:
I used it flawlessly for at least 4 days until it happened
[Samsung Galaxy Nexus] drxikh:
edit: wrong topic.
[Samsung Galaxy Nexus] digitallure:
One of the best KK roms. I've been running for almost 3 weeks with no problem with Dirty-VR kernel
[Samsung Galaxy Nexus] Shadow Death:
Flashed this using the stock kernel. It ran great until my phone powered off due to low battery. When I charged it and tried to power it back on it boot looped indefinitely.
[Samsung Galaxy Nexus] MWisBest:
Hey guys, sorry bout the inactivity. Since about the 4th or 5th of the month, my ISP was bought by another company and they've been transitioning stuff to their new system, and unfortunately while they've been working on this my connection hasn't been stable enough to do much of anything really. I've also been spending some more time with my mom and dad, as they recently had their birthdays.

It seems that my ISP has sorted out the issues, so I'm planning on a new build tonight or tomorrow. They are going to be bumping everybody's internet speed free-of-charge, and are throwing in some more TV channels as well, so for me it's been worth it I guess.
[Samsung Galaxy Nexus] Moody66:
Awesome!
[Samsung Galaxy Nexus] jayandare:
Can't wait
[Samsung Galaxy Nexus] MWisBest:
Gah, didn't get a build up yesterday like I had planned, sorry. I got busy with homework and then somehow fell asleep at 8:30PM... usually I'm up til like 2:00AM! On the flip side, usually I don't wake up until a little before noon, and today I woke up at 7:30AM. I'll get working on a new build shortly, just gotta get my morning soda! :D
[Samsung Galaxy Nexus] metalspring:
I believe this commit, along with your other ones on cm fix building with LTO ;)

https://github.com/metalspring/android_art/commit/2c42e7932dde67ac43bf6097410ca115f36064eb
[Samsung Galaxy Nexus] MWisBest:
Thank you, that'll be nice to have up and running again! :)
[Samsung Galaxy Nexus] MWisBest:
New build up, not tested much yet since I've just been waiting for ART to compile the 156 APKs on my phone...
[Samsung Galaxy Nexus] jayandare:
Great. I'll test this monster and get back to you
[Samsung Galaxy Nexus] MWisBest:
Everything seems to be OK. Among the new changes are:

OmniSwitch:

- New, better looking icon.

- Option to replace the built-in Recents with OmniSwitch.

UI:

- Options for the clock in the status bar (e.x. center alignment, AM/PM after the time, date before the time).

- More configuration for the option to show data speed in the status bar.

Misc Settings:

- Some new stuff in the Sound menu.

- Option to force apps into thinking you have a hardware menu key in order to hide the overflow button (mostly useful if you put a full-size menu button in the nav bar, which I do, so I reeealllly like this feature).

Other:

- New boot animation.

- Probably lots of bug fixes and whatnot.
[Samsung Galaxy Nexus] rice923:
I'm still having the LTE issue, where I simply lose all data on LTE. It's fine when I switch to 3g though. This happened for me (as well as another user) for this build and the last build. Clean flash with system wipe every time. Currently running the latest January build still