I am looking for the notofication pull down widgets.
A cherry pick or a link to a github page is also ok. I can work my way from there.
Can someone help ? I looked into CM9/AOKP/Paranoid Android, but there is so much to search.
I'm guessing apps like Power controls or widgetsoid are out of the question? Also, are you planning on making this into something to add to stock roms or a whole new rom? Just curious.
CrackerTeg said:
I'm guessing apps like Power controls or widgetsoid are out of the question? Also, are you planning on making this into something to add to stock roms or a whole new rom? Just curious.
Click to expand...
Click to collapse
I want to add this into a AOSP ROM. Which I hope to release sooner or later. If I can integrate that, less RAM will be used in the process than having another app running in the background.
Makes sense. If you get it figured out, I'd love to know how to add it to something of my own.
Found it finally
https://github.com/CyanogenMod/android_packages_apps_Settings/commits/ics
it should be somewhere there. That will give you good place to start looking I found the cleanup code so the original must be there as well.
Hey everyone,
I tried both the alpha and nighly builds of Omnirom for the Nexus 7 2013 flo. I am using the flow build. When I flashed it, I opened two apps, went to the Recent Apps, long pressed the app I wanted to add. Lo and behold 'Add to Split View' wasn't there. I have tried it with one of the apps open on the screen, I have tried it on the home screen and the add to split view will not appear. Anyone know what's going on here? I have seen other people on the Omnirom Nexus 7 2013 thread saying it works for them.
ezio2altair said:
Anyone know what's going on here?
Click to expand...
Click to collapse
Yeah, we know.
Multi Window feature has not yet been merged into Omnirom repo.
chasmodo said:
Yeah, we know.
Multi Window feature has not yet been merged into Omnirom repo.
Click to expand...
Click to collapse
Yup, which means you won't see it in any autobuild. (Unless the guys working on autobuild add the ability to do "experimental" builds that cherry-pick items from gerrit)
As to why it's not merged - still work to be done. It mostly works, but there are remaining issues. For example we need to either figure out how to fix G+ layout, blacklist G+ and any other apps known to misbehave, or implement a whitelist similar to Samsung's only allowing apps known to work. (If we do a whitelist, there needs to be a good way to add overrides/add to the whitelist as more people report compatible apps.)
Hi, OmniROM recently introduced a new UI for the way one answers (or rejects) a call. On the nightly I am running, there is no option to go back the old UI. Will it be possible to pick and choose or are we stuck with it?
XxPixX said:
Hi, OmniROM recently introduced a new UI for the way one answers (or rejects) a call. On the nightly I am running, there is no option to go back the old UI. Will it be possible to pick and choose or are we stuck with it?
Click to expand...
Click to collapse
The option to disable it was recently merged, should be in next nightly.
Hi,
I flashed Omnirom 4.4.2 nightly 2014-03-17 yesterday and then updated it to the 21st nightly using the built in update.
I can't figure out how to enable/use the multi-window / split screen feature.
I don't have the "Add to Split View" option in "Recent Apps" manager like shown in so many blogs and how to videos, no matter on which app I tap and hold.
The only options I have are "remove from list" and "App info".
I also tried enabling OmniSwitch but that didn't seem to help.
I flashed superuser from TWRP so I do have root.
Am I missing something?
I'm on i9300.
Baseband I9300JKEMC1
Boeffla kernel 2.1 (although I also tested with Omni stock kernel)
Thanks,
Pyrocks
Same here on my n7105
Pyrocks said:
Am I missing something
Click to expand...
Click to collapse
Yeah, you're missing add to split view.
chasmodo said:
Yeah, you're missing add to split view.
Click to expand...
Click to collapse
You're sharp
Now really, I did some more reading, do I have to install Xposed framework and XMultiWindow?
I thought this was supposed to be integrated into OmniRom.
Does it work for others?
What may be the reason?
After digging around I found out its not implemented by default in the final/nightly builds yet. I think you can patch it in.
Chris_c81 said:
After digging around I found out its not implemented by default in the final/nightly builds yet. I think you can patch it in.
Click to expand...
Click to collapse
Thanks for replying.
Do you know how can I patch it in? is there a flashable zip I can download (and maybe place in the FlashAfterUpdate folder) ?
I couldn't find more information about this (except for Xposed framework and XMultiWindow) - and found it strange that so many reviews and blogs show this feature with OmniRom and it's not there.
Thanks again.
Pyrocks
OK - found it:
http://forum.xda-developers.com/showthread.php?t=2567667
I think that the fact it's not yet integrated in the nightlies should be mentioned in a more visible place. It's not so obvious as some might think.
To be honest I gave up on it after reading about stability issues. Probably why it doesn't get included in the night lies.
Aside from that, I have a Note II which had split view on Touchwiz and I never used the feature!
Chris_c81 said:
To be honest I gave up on it after reading about stability issues. Probably why it doesn't get included in the night lies.
Aside from that, I have a Note II which had split view on Touchwiz and I never used the feature!
Click to expand...
Click to collapse
Indeed stability issues, i gave it a try and ended up with a bootloop. Luckily the post also contains instructions for reverting the change so no harm done eventually, but yes, very unstable.
In all the forums and blogs this is like THE feature when peopele discuss about this rom. It has gotten too much publicity and too little discussion or work.
I also had toucbwiz and never used it, the reason was it was only for a limited list of apps. If it would be limitless and any app can be split - i'm pretty sure it'll end up being useful. That's kind of one of the reasons I wanted to try this rom in the first place (i'm not regretting though, it's mor:laugh:e stable than cm 11 nightlies).
Hope it gets fixed. Until then maybe I'll give xMultiWindow a try.
So does anyone have an idea on how to get this to work on AOSP ROMS? I'm making new vebdor blobs and the only real new APK I see is CNEService. There's other files here and there but nothing I can tell that will help with this.
xanaxdroid said:
So does anyone have an idea on how to get this to work on AOSP ROMS? I'm making new vebdor blobs and the only real new APK I see is CNEService. There's other files here and there but nothing I can tell that will help with this.
Click to expand...
Click to collapse
I haven't been able to look into it yet and I don't have tmobile so it's going to be tough for me... I plan on checking into it tomorrow while I'm off work though...
Im very interested in helping with this as I would love wifi calling on my gpe htc one m8, anything you guys need to test ill do it. I even have an old m7 with aosp firmware on it I'm willing to brick for the cause if needed.
I'm on 5.1.1, and I'm on T-Mobile with my Nexus 6. Anything you need? My Bootloader is unlocked, but I'm stock and not rooted
swimdude1120 said:
I'm on 5.1.1, and I'm on T-Mobile with my Nexus 6. Anything you need? My Bootloader is unlocked, but I'm stock and not rooted
Click to expand...
Click to collapse
I already have a system dump which is here, and I've made some test blobs here. Now comes the hard part.
xanaxdroid said:
I already have a system dump which is here, and I've made some test blobs here. Now comes the hard part.
Click to expand...
Click to collapse
I am running the stock ROM (don't worry, bro, be back later today :victory: ) and I just got an update on an app I had never seen before: Google Connectivity Services. The tag line is "Improved Networking for Android", and the description talks about automatic wifi connections and Google VPN. Obviously this is a precursor to Fi, but I am wondering if the delay for T-Mobile WiFi calling was to wait for it to be built on the Fi platform for WiFi calling, which we know will be part of the deal.
Not sure what to make of it, other than it's looking very proprietary right now.
brizey said:
I am running the stock ROM (don't worry, bro, be back later today :victory: ) and I just got an update on an app I had never seen before: Google Connectivity Services. The tag line is "Improved Networking for Android", and the description talks about automatic wifi connections and Google VPN. Obviously this is a precursor to Fi, but I am wondering if the delay for T-Mobile WiFi calling was to wait for it to be built on the Fi platform for WiFi calling, which we know will be part of the deal.
Not sure what to make of it, other than it's looking very proprietary right now.
Click to expand...
Click to collapse
Yeah the Google Connection Service app has been on the Play Store for awhile. I already added it to my blobs. Yeah it is looking proprietary, but I'm sure we can get it to work. It's been done on other phones before.
i have faith is will be a short time before you guys get it to work
justcallmeTHEKID said:
Im very interested in helping with this as I would love wifi calling on my gpe htc one m8, anything you guys need to test ill do it. I even have an old m7 with aosp firmware on it I'm willing to brick for the cause if needed.
Click to expand...
Click to collapse
You won't brick, the WiFi calling feature requires framework changes that (I can pretty guarantee) are not open source.
Second: This is in the DEVELOPERS ONLY section, so if you guys want to discuss WiFi calling and aren't actually working on it then you need to move general discussion of it to a different thread. This area is strictly for development and discussion of such development (technical things, not "oh nice can't wait" or "I'll test for you" )
i think we should look at the file systems for the stock nexus 6 and t mobile nexus 6 and check for differences i know its a long shot but ill check it out tonight and see what i can find.
Second: see development were not just chatting anymore
Third: If anyones already done that please tell me so I don't have to its gonna take forever.
justcallmeTHEKID said:
i think we should look at the file systems for the stock nexus 6 and t mobile nexus 6 and check for differences i know its a long shot but ill check it out tonight and see what i can find.
Second: see development were not just chatting anymore
Third: If anyones already done that please tell me so I don't have to its gonna take forever.
Click to expand...
Click to collapse
you need tmobiles blobs. besides that, all n6 roms will be identical.
So I decompiled LYZ28E and took a look around in the Settings app. It has a class called WifiCallingSettings. Inside there it makes calls to ImsManager.isWfcEnabledByUser. It seems like Wfc is WiFi Calling. I took a look at frameworks/opt/net/ims/src/java/com/android/ims/ImsManager.java and it doesn't have a function called isWfcEnabledByUser. I looked at android-5.1.1_r4 and android-m-preview tags. I think we need to wait for Google to push androiid-5.1.1_r5. According to https://android.googlesource.com/pl...om/+/ecfa803f8e7ca0cb65e74fb4dda90c16156655f3 that's the tag for LYZ28E.
From what I've been told by a guy I know at Tmo, you can only use WiFi Calling on phones that have been authorized by Tmo. (Example) Nexus 5 with Android M preview shouldn't be able to do WiFi calling. Even though Google is now baking in WiFi calling into Lollipop and M.
Check out the latest revision (5.1.1_r5) on AOSP. It includes WiFi calling support. Check it!
https://android.googlesource.com/
Gandalf said:
You won't brick, the WiFi calling feature requires framework changes that (I can pretty guarantee) are not open source.
Second: This is in the DEVELOPERS ONLY section, so if you guys want to discuss WiFi calling and aren't actually working on it then you need to move general discussion of it to a different thread. This area is strictly for development and discussion of such development (technical things, not "oh nice can't wait" or "I'll test for you" )
Click to expand...
Click to collapse
I'll just leave this here since guarantees were made and all
https://github.com/codeaurora-unoff...mmit/2cc69a62cb1bc4989f0421e0006290e3985aa506
https://github.com/codeaurora-unoff...mmit/1a2e9e4a1dffe211bb503962bc42f476072dd216
https://github.com/codeaurora-unoff...mmit/98f974e95d880d76d653e2f4a36a057c667ce1b3
I will add that you don't just need the frameworks part but also kernel commits to support this WPC feature
I'll submit the specific changes made to bcmdhd driver (rather than just merge the entire m-preview kernel) to Omni Github once it is tested further and verified functional and stable for merge.
Gandalf said:
I'll submit the specific changes made to bcmdhd driver (rather than just merge the entire m-preview kernel) to Omni Github once it is tested further and verified functional and stable for merge.
Click to expand...
Click to collapse
Interesting. Todays nightly came closer than ever!
Stock CM Kernel allowed me to get the IWLAN status in SIM Status, but the Data Quick Toggle Shows TMOBILE (Not WiFi Calling), and I am unable to call out. Also, WiFi Calling Settings don't show up in the "More" Tab (Under Wireless & Mobile Network Settings), and no WiFi Calling toggle in the Dialer (Does CM use the Google Dialer? Or its own?).
Interesting. It seems like the hard part is done at least.
npjohnson said:
Interesting. Todays nightly came closer than ever!
Stock CM Kernel allowed me to get the IWLAN status in SIM Status, but the Data Quick Toggle Shows TMOBILE (Not WiFi Calling), and I am unable to call out. Also, WiFi Calling Settings don't show up in the "More" Tab (Under Wireless & Mobile Network Settings), and no WiFi Calling toggle in the Dialer (Does CM use the Google Dialer? Or its own?).
Interesting. It seems like the hard part is done at least.
Click to expand...
Click to collapse
To my knowledge, all wfc builds so far have merged the m-preview kernel into the lollipop-mr1 kernel. I believe I have the specific commits needed and it will be up on Omni's github once ready.
Gandalf said:
To my knowledge, all wfc builds so far have merged the m-preview kernel into the lollipop-mr1 kernel. I believe I have the specific commits needed and it will be up on Omni's github once ready.
Click to expand...
Click to collapse
Outstanding. Thank you for your work.