yashsingh1/xdaforums huggingface dataset:
[One (M7) Original Android Development] Frazzy:
Wifi problem

I've searched the thread for a solution for the wifi problem but couldn't find one...

I have the problem that when i'm out of reach from the wifi network i was connected to my wifi stops completely. It only starts again when i do a full wipe.

Is there a way to manualy reset wifi as if it were a rom reinstall? Or better, a solution to the problem?

Thanks
[One (M7) Original Android Development] bbabiuk:
I wanted to say

1. Fantastic ROM. I find it smooth and quick. Most everything works. Very quick. Closed works great with it. Tried flashing teamseven kernel to get logo2menu but it distorted the video. Someone in that threat pointed out it likely was older vid drivers. I have no idea. I did a fresh wipe and install and stopped playing there.

Things that appear buggy for me: (perhaps there is a work around and someone can share a fix or I can provide more data)

A. Bluetooth calling: person on other end sounds clear. Sound quality from me to that caller is tinny and garbly sounding. Tripkat build appears to have worked around this. Sound quality on this build is considerably worse for bluetooth.

B. Exchange crashes fairly regularly requiring a reboot to fix sync. Anyone else see this? I find it frustrating.
[One (M7) Original Android Development] Chezbel:
This ROM already has the teamseven kernel by default. Logo2menu does work, but you may have to specifically enable it. See my earlier post that has an example userinit.sh file that you can put into /data/local to keeps those settings from getting changed on every reboot

http://xdaforums.com/showpost.php?p=47892241&postcount=392
[One (M7) Original Android Development] djbeck811:
Disappointed as well

I'm disappointed as well that you are thinking of stopping. I love your ROM but am also disappointed in your comment about my post. I'm a relative noob but I was trying to get an easy answer for all but since you think "(must be hard to read whats ´the diference between nightlies and this build... khmkhm.... changelog ??) If u doesnet know what the difference is then this is not the right place for u at all." I have to say that comment was not appreciated. I was even one of the people who actually used your "donate" button. It wasn't much but it was all I can give right now and I was thinking of adding more later.

Just disappointed in your comment and I'm sorry if I'm not smart enough to join in. :(

But I still love ur ROM and thank you for your efforts.
[One (M7) Original Android Development] noky76:
Are there any themes to flash?

Inviato dal mio One utilizzando Tapatalk
[One (M7) Original Android Development] Chezbel:
I don't think his comment was directed specifically at you. It's just that a development thread is supposed to be about development and not a general Q&A thread. But so many of people on xda don't respect that and it gets frustrating even for the people that follow the dev threads without participating.
[One (M7) Original Android Development] n3ocort3x:
[MENTION=3426685]djbeck811[/MENTION]

wasnt in ur direction :) as [MENTION=3507415]Chezbel[/MENTION] stated, it is a DEV forum. But i will refactor OP tonight anyway to sort out things that confuses people. I donnt see any reason that "I" as a contributer shouldnt be allowed to post customized builds that i use on my own on my phone.

I´m behind the philosophy of OMNI, but this i cant understand tbh. I like multiwindow, i like listview animations, and i like to test stuff out of gerrit and share it with community. I contribute and share. I dont see anything negative.(I remember that THIS IS OMNI all about, someone said)

I spent a lot of hours in this project (and I still do, not only on m7ul) Im no founder, thats right. I also respect every statement of the founders and appreciate working together with them, but why not posting customized testing builds without gerrit stuff.. I dont get it. What i get is that i should state exactly whats the difference between my builds and official nightlies and i understand that as its confusing, but most of the users here already know whats the difference.
[One (M7) Original Android Development] Donjuanal:
So i've been very excited to try this, I just wiped and clean flashed with the linked Gapps but im missing quite a few things. camera.apk is missing from the app drawer and my google account didnt start a restore, tried a clean wipe and flash again to no avail. has anyone else experienced this? Thanks in advance.

EDIT: I should add I flashed the latest nightly, vs the version linked in the OP. Not sure how much of a difference that makes.
[One (M7) Original Android Development] chas_43:
Omniswitch still seems to be missing from the nightlies, isn't it ?

I couldn't locate much about its status on Gerrit.

After a bit of tinkering to get the handle location etc sorted it works really well, so I've returned to N3o's latest build which he kindly included Omniswitch in.

Any updates/pointers on its inclusion status for the future ?
[One (M7) Original Android Development] bia9977:
Main difference between your builds and Omni nightlies is that yours work, where 2 out of 3 nightlies I've tried wouldn't even boot. It's that simple.
[One (M7) Original Android Development] v1r0x:
I'm glad you will still release your builds.

Maybe it would be better to add another tag (e.g. [DEV], [UNOFFICIAL]). I think most people think this is an official build.

Keep up the good work :)
[One (M7) Original Android Development] n3ocort3x:
because i fetch it from dev directly and no, it isnt included in nightlies as multiwindow or listviews are

thats still a mystery for me... but i will look into again

I will provide both here, OFFICIAL NIGHTLY and UNOFFICIAL PERSONAL BUILD
[One (M7) Original Android Development] kravguy:
Yes, please don't stop your builds.

Sent from my One
[One (M7) Original Android Development] DanOMac:
[MENTION=4635674]n3ocort3x[/MENTION] can u spread any light on when omnifile explorer will find its way into urs or official builds
[One (M7) Original Android Development] dseries60:
[MENTION=4635674]n3ocort3x[/MENTION]

Please continue building and sharing your homemade builds. They are great and much appreciated. There's no confusion for those that only use your builds! :)
[One (M7) Original Android Development] Sushibagel:
Hi guys if this has been asked already I apologize but did a quick search and couldn't find anything about it.

I just flashed the 12/04/13 nightly version of OMNI from the website yesterday. All was working great. Today, however I started getting SystemUI force closes every time I try to read an active display notification. They were working fine yesterday so I'm not sure what the cause would be. Anyone else experience anything like this?
[One (M7) Original Android Development] jawonder:
I flashed the 12/03 version but it's showing 12/02 in settings .
[One (M7) Original Android Development] mj084:
build.prop was not deleted before started the rebuild;)
[One (M7) Original Android Development] Chezbel:
Good point. If the build scripts are not doing a clean build then they should probably delete the following at the beginning of the build

out/target/product/m7ul/system/build.prop
[One (M7) Original Android Development] androidindian:
[MENTION=4635674]n3ocort3x[/MENTION] and [MENTION=2162789]XpLoDWilD[/MENTION] : instead of doing official and unofficial, its better to make the nightly merges etc. more stable.. its a kind of a mess right now. get that fixed and its all good mateys!
[One (M7) Original Android Development] XpLoDWilD:
[MENTION=4635674]n3ocort3x[/MENTION] still waiting for your updates patches list :)
[One (M7) Original Android Development] n3ocort3x:
[MENTION=2162789]XpLoDWilD[/MENTION]

Trust me.. I spent yesterday 4 hours and the day before yesterday also lot of hours in trying to figure out why that one commit in system core breaks our cam.. I compiled until late night and also talked to [MENTION=4683552]maxwen[/MENTION] but atm we are all a bit clueless what's causing it. I have the exact error message but no clue atm how to fix it :) maybe we can hook up in irc (Friday and Saturday are always days where I can work until late night). Maybe I don't have the knowledge to fix it or doesn't see the right things... :)

No one sees a mess.. Except those who are aren't able to read. This is a development forum. And not everything will be presented on the silver platter

noNeedForAsig
[One (M7) Original Android Development] Chezbel:
Do we want to do this?

[MENTION=4635674]n3ocort3x[/MENTION], [MENTION=2162789]XpLoDWilD[/MENTION] and [MENTION=4683552]maxwen[/MENTION]

Here is a screen shot of some changes I made to show Touch Settings, is it something we want to do?

Also, before anyone gets excited, this can't work the way the touch features are implemented because currently their values are in files in /sys/android_touch and as far as I know the java code that handles the settings can't write to the /sys directory. So on my phone everything "looks" like it works, but it can't actually change any settings.

If we want to do this, can synaptics_3200.c be modified to read the values from where the preferences are normally saved? Maybe it's not good for the kernel to do that, maybe it's not even possible?

Finally, my Java expertise is really really minimal. If we do want to do this and someone was willing to finish this I will gladly give you the 3 modified files :)
[One (M7) Original Android Development] Chezbel:
Just an idea, can you compile VectorImpl.cpp with --save-temps? That will produce VectorImpl.ii, which is the result of gcc's pre-processing pass. All the #define and #if items should be resolved and maybe that will provide a clue. Also, the full compile command line should be in the top of that file so you can verify if the symbol NEEDS_VECTORIMPL_SYMBOLS is really being defined on the command line.
[One (M7) Original Android Development] dseries60:
[MENTION=3507415]Chezbel[/MENTION]

The touch options would be awesome!
[One (M7) Original Android Development] Chezbel:
Damn, it doesn't seem to work for the Android version of gcc.

I tried a few variations in system/core/libutils/Android.mk including the following. I thought that either the "--" or the "-" option would give an error, but there was no error and no .i or .ii file

LOCAL_CFLAGS += --save-temps -save-temps
host_commonCflags += --save-temps -save-temps

I googled a bit and it seems other people have found that --save-temps does't work for Android gcc.

---------- Post added at 11:26 PM ---------- Previous post was at 11:01 PM ----------

OK a new test that shows that the following definition of NEEDS_VECTORIMPL_SYMBOLS in device/htc/m7-common/BoardConfigCommon.mk is not working as we expect

COMMON_GLOGAL_CFLAGS += -DNEEDS_VECTORIMPL_SYMBOLS

I added the following in the top of system/core/libutils/VectorImpl.cpp (sorry for the "creative" use of the English language :) )

#ifdef NEEDS_VECTORIMPL_SYMBOLS
#if (NEEDS_VECTORIMPL_SYMBOLS == 1)
#error "Hooray!"
#else
#error "Oh sh*t!"
#endif
#else
#error "Oh fu*k!"
#endif

The error message I got was

system/core/libutils/VectorImpl.cpp:36:4: error: #error "Oh fu*k!"

This means that COMMON_GLOGAL_CFLAGS is either not being used when VectorImpl.cpp is compiled or it's value is getting changed somewhere.

P.S. I never new this but XDA must have a "bad word" filter because it changed some words in my error message to '****'. So I had to edit them so you could tell the difference between the 2 bad cases... oops, lesson learned.

EDIT: So the comment in https://gerrit.omnirom.org/#/c/3005/ is either wrong or it's not detailed enough as to where to use COMMON_GLOGAL_CFLAGS += -DNEEDS_VECTORIMPL_SYMBOLS
[One (M7) Original Android Development] n3ocort3x:
That's what I think too. I grepped a log and vendor-camera.msm8960.so wants to access a vector symbol in libcameraface. So but don't get response.

I wanted to try the same as u but I'm still at work. Glad u did it and we are one step further. The next interesting thing is that if this vector symbol flag is used nearly every sensor refuses to work. If u revert that commit in system /core everything is working again.

So what do we learn? It compiles with the right vector symbol if they are not in the ifdef. When ifdef is defined the vector symbols aren't used and it breaks every sensor. We need to find out where and why it derps.

There is so much stuff we have to track down... Frameworks/av frameworks/native camera2 device tree. I tried to compile cm11 with Omni device tree and it's fully working. So maybe we miss something here or I dunno :) this is now the 3rd time that cam is broken... But now sensors are too.. Lol

However... I'm pretty sure the flag isn't used and through the ifdef the code is out of reach while compiling. That is why it's broken. Before it wasn't because it wasn't ifdefed.. But why the hell isn't the flag used.... I will play when back home
[One (M7) Original Android Development] Chezbel:
It's almost time for bed here. I'll check if there are any updates tomorrow and see if there is anything else I can do. I don't know enough about how the build works, but given the name "COMMON_GLOGAL_CFLAGS" it sounds like these flags are supposed to get used on the command line for all *.c/*.cpp files. Maybe that isn't true, but I was assuming it was true. Another possibility is that something is overwriting its value, for example some later place could be using "=" instead of "+=".

EDIT: there's a way to have makefiles display the value of make variables, but it's not very flexible. Maybe this will help

$(warning COMMON_GLOGAL_CFLAGS is $(COMMON_GLOGAL_CFLAGS))
[One (M7) Original Android Development] n3ocort3x:
Yeah... Let us see what I can do tonight... Still not at home but already have a few new ideas. Thanks for ur contributions and helping me :) if my days would have 36hours it still wouldn't be enough time lol
[One (M7) Original Android Development] Thomasfoolery:
Hot word detection in search or Google now

the hot word isn't working no matter what I do (I've replaced velvet.apk libgoogle_recognizer even the PrebuiltGmsCore)
[One (M7) Original Android Development] n3ocort3x:
[MENTION=3507415]Chezbel[/MENTION]

moving the flag to BoardConfig.mk in m7ul results also in nothing... still everything derped... why is this flag not applied goddamn
[One (M7) Original Android Development] n3ocort3x:
good news, things are fixed we are back on track.

[MENTION=3507415]Chezbel[/MENTION] i hit u a pm when i get up in the morning ;) Just merged necessary stuff in repos (worth a look) next nightly should work again as it should. Anyway, I will upload a build now to get some 4.4.1 flavor into HTC ONE. The ONLY thing i merged in from gerrit is Multiwindow, otherwise the build is EXACTLY as the nightlies are (to prevent confusing people).

Be advised: Upload should be done in 1 hour so hang in there, Iḿ off to bed.

DONWLOAD:

=================

BUILD FROM 06.12.2013 -> LINK

VERSION 6.DEC.

-pure as nightly, only merged feature from gerrit is multiwindow

I need reports:

- on Front Face camera please, if the tint is better or gone (I cant see any tint, but i might be wrong)

- on Rear Camera if everything is working as it should (for me it works)

- on Rear Camera if preview is still stretched (for me no more stretches)

Thanks :)
[One (M7) Original Android Development] dseries60:
Outstanding!

Thanks Omni Team and your HomeMade builds! No confusion here! :)
[One (M7) Original Android Development] Chezbel:
I saw your fix, can't believe I didn't see that LOL
[One (M7) Original Android Development] DaringDomino3s:
Cam's work w/o stretch/shape distortion, however there's a little glitch/hang in the image when going from portrait position to landscape position (in preview, not captured image). the color thint thing is hard, because its dark and my walls are green..so everything is tinted green. lol but I just came from the official nightlies off the omnirom site (12/6) and the camera didn't work AT ALL on it.

Thanks much for these!
[One (M7) Original Android Development] Yuma75:
I'm pretty sure the changes won't be until the next nightly. I guess your testing proves that. :)
[One (M7) Original Android Development] saj2001ind:
can I flash on international HTC One ? and will TWRP work or need CWM ?
[One (M7) Original Android Development] Chezbel:
I forget is international m7ul? That's what I have and I use twrp 2.6.3.3. I haven't tried cwm...
[One (M7) Original Android Development] saj2001ind:
.can we download the new build now or its still uploading ?
[One (M7) Original Android Development] Eddster3000:
Yes you can download..... I have and flashed already
[One (M7) Original Android Development] Chezbel:
Home build works now without any cherry picks or reverts. Camera works, but I'm not a good enough photographer to comment on quality, it's fine for my use.
[One (M7) Original Android Development] saj2001ind:
how to get multi window work ? cannot find the option anywhere
[One (M7) Original Android Development] Chezbel:
Try going to your recently used app list and long pressing the app you want. I can't test because my build doesn't include that cherry pick
[One (M7) Original Android Development] saj2001ind:
cannot see any option there, it just have app info and remove from list, just flashed 6/12 build
[One (M7) Original Android Development] eyosen:
I think n3o cherry picked that for his home build.
[One (M7) Original Android Development] saj2001ind:
so is it present in 6/12 build or not ?
[One (M7) Original Android Development] Chezbel:
It's not in any nightly build, it's only in the build by [MENTION=4635674]n3ocort3x[/MENTION], look 2 pages back at post 618
[One (M7) Original Android Development] eyosen:
As chezbel said. Was too lazy to point to the actual post
[One (M7) Original Android Development] saj2001ind:
I downloaded the ROM from that post itself

BUILD FROM 06.12.2013 -> LINK

VERSION 6.DEC.

-pure as nightly, only merged feature from gerrit is multiwindow

but still I dont see that option....very confusing...can someone pls point me to a ROM version with multiwindow
[One (M7) Original Android Development] Chezbel:
I just downloaded that ROM and tried it and I don't see the multi-window option either so it's probably just an oversight. You'll have to wait for the next version...
[One (M7) Original Android Development] saj2001ind:
Anyone experiencing stutter or few lag while opening or browsing apps ... Is there a way to overclock GPU
[One (M7) Original Android Development] Ste98B:
I think overclocking GPU isn't a way for make the device smoother, anyway, if you want doing this you can install a custom kernel, with the Omni stock one you can't.

Inviato dal mio HTC One utilizzando Tapatalk
[One (M7) Original Android Development] saj2001ind:
and how to get OK Google function at home screen
[One (M7) Original Android Development] Ste98B:
If you want that you have to install and use GEL.

Inviato dal mio HTC One utilizzando Tapatalk
[One (M7) Original Android Development] n3ocort3x:
some updates:

I havent done a clean build, thats why multiwindow is missing. Error from my side. Havent tested as it was too late yesterday. Just wait for next UNOFFICIAL build. Also, I will remove Votlage Control and Overclocking out of Kernel as it shouldnt be in a stock kernel that comes with a ROM. If u guys want an "featured" Kernel, u have to wait until I update teamSeven Kernel.
[One (M7) Original Android Development] saj2001ind:
IR blaster doesn't work .. too bad that's the imp feature for me
[One (M7) Original Android Development] n3ocort3x:
Are u finshed then with complaining ?? i think 2 full sites are enough. Thanks. This is still in Development and im constantly working on it. There were a few other major things that needs to be ironed out before IR. If its an important fetaure or not for u, i dont care tbh. Its done when its done. no one pays me for that, i can stop immediatley if u want

---> OP refactored ---> The difference between nigthlies and homebrews is stated there ---> I wont answer any question about that anymore. dont get me wrong guys, but reading OP takes less then 1 minute and everything is cleared out there
[One (M7) Original Android Development] saj2001ind:
I am not complaining just giving my review that something is not working as its not menyioned in release note....

My bad if I did not read full apologies
[One (M7) Original Android Development] dseries60:
I use the following steps to get "OK Google" working.

1.Using titanium I uninstall Google.search

2.Download & install from play store Google search

3."OK Google " now works

4. If still not working confirm in Google search settings you have English US downloaded for the offline voice engine

5. Enjoy.. It's a nice feature
[One (M7) Original Android Development] v1r0x:
there is a typo in the homebrew link (http// instead of http://)
[One (M7) Original Android Development] Chezbel:
[MENTION=4635674]n3ocort3x[/MENTION], [MENTION=2162789]XpLoDWilD[/MENTION] and [MENTION=4683552]maxwen[/MENTION]

Here's a follow up to my post #609 (http://xdaforums.com/showpost.php?p=48193449&postcount=609) about adding Touch Settings. A few ideas about how this might be done

1) It looks like the normal settings are stored in /data/data/com.android.settings/shared_prefs/com.android.settings_preferences.xml

The kernel (i.e. synaptics_3200.c) could look for and parse that file looking for the settings. I don't like this idea, making the kernel parse user files doesn't seem right.

2) The touch specific settings could each be written to a seprate file as 0 or 1 just like they are now except the files would live somewhere in /data,

possibly in /data/data/com.android.settings/android_touch/*

This is less work for the kernel, if can test for file existence and read only the first character (or it can optionally ignore a file if it's size is not 1). For files that don't exist we use a sensible default, either whatever the default is now or we just assume 0 for all items. The only thing "bad" about this is that we have some settings that are stored in an unusual way instead of in the normal .xml file.

3) Someone else has a better idea...
[One (M7) Original Android Development] XpLoDWilD:
4) Add a sysfs
[One (M7) Original Android Development] Chezbel:
I just did a repo sync and a clean build a few minutes ago and it hangs on the boot animation. My last build worked, it was made after Peter's m7-common changes, but I don't know which checkins after that were included. There were only a few today so it should be easy to track down. Hopefully, it's not me doing something stupid.

The point is it builds without error so it's possible that the next nightly could suffer the same problem.

Logcat is attached.
[One (M7) Original Android Development] n3ocort3x:
Will have a look then :) why not leaving everything as it is chezbel and simply integrate it as we had with sysfs in AICP? maybe I get u wrong but we have a complete device specific menu there where u can adjust all this things. :) btw great work so far :) really like that but have forgotten to comment on this yesterday.

Atm trying to change some things in kernel but can't upload to Gerrit Atm and I haven't found out yet why :P
[One (M7) Original Android Development] Donjuanal:
Did a quick search in this thread, didnt see anything. Google wallet doesnt seem to have the tap to pay option whereas bigxies 4.4 gpe did, is that something ROM specific or AOSP specific?