[Q] 'Add To Split View' Not Working on Nexus 7 2013 - Omni Q&A

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.)

Related

[Q] CM 10.1 - 20121227 Nightly - Home Screen Bar

Good evening. Lastnight I updated my system to the latest CM - CM10.1-20121227 Nightly. Everything went smooth except an odd occurance is happening now. I noticed after the reboot, that all my 'favoriates' that I put on the home page bar (sorry new to N7 and not sure the proper name) disappeared, so I remade them and went about my business. Today after logging in, I noticed that they are gone again, so remade them and they seemed to stay put this time. But I just logged in again (after not using the tablet for about 4hrs) and yup you guessed it, they are gone! The only thing that stays on the bar is of course the 'button' that brings up the apps/widgets screen. So, what am I missing here? After the last 3 updates, I've never ran into this problem. Sorry for the noobish question, just new to the scene. Thanks in advance...
Are you talking about the 5ish icons at the bottom of the launcher? If you are, I think this is caused by a bug in the default launcher (see the comments at the bottom of this page http://review.cyanogenmod.org/#/c/28994/ ). There are quite a bit of changes getting committed to trebuchet, and when using nightly builds, you are the beta tester. You can install a different launcher that has been tested by more people and is considered stable.
gianptune said:
Are you talking about the 5ish icons at the bottom of the launcher? If you are, I think this is caused by a bug in the default launcher (see the comments at the bottom of this page . There are quite a bit of changes getting committed to trebuchet, and when using nightly builds, you are the beta tester. You can install a different launcher that has been tested by more people and is considered stable.
Click to expand...
Click to collapse
@Gianptune - Yes, the '5ish icons' at the bottom of the page. I knew after researching CM, that any nightly builds would be ' as is ' because they are considered work in progress, but I have CM selected to only notify me of when a 'stable' build is avail. Thanks for the link and can you tell me, or recommend a popular launcher to use? Did not know that you could replace that one. (BTW that link was broken on this puters IE). Thaks again
Nova launcher
https://play.google.com/store/apps/...sMSwyLDEsImNvbS50ZXNsYWNvaWxzdy5sYXVuY2hlciJd
Awsome thanks much ...
Hi all,
Not to hijack the thread, its almost the same topic i would guess...
I was running 12.22.12 nightly, i think, and all was well until i updated to the 27th. that when i noticed problems with the shortcuts at the bottom as well. Tried to flash back to previous version and noticed that I lost the quick settings pull down (upper right, opposite of the notification pull down)
I have tried to flash every single CM10.1 i can find and not a single one would bring it back.
Has anyone ran in to that?
thanks
I had this issue going to 12/27 too. I did not have it happen on today's nightly however.
Sent from my Nexus 7 using Tapatalk HD
dottat said:
I had this issue going to 12/27 too. I did not have it happen on today's nightly however.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
That's strange, on CM10.1 thread someone just reported it with latest build.
I dont know why, but when i install 12/15 unofficial CM10.1 build, the pull down is not available as well, yet i had that build for several days two weeks ago and everything worked fine.
basically any CM build i install does not have the pull down. only if i restore my backup of the stock rom it comes back.

Reasons not to update your N7 to Kitkat 4.4 (yet)

Here are some reasons that you should not update your Android OS to 4.4 for the time being (as of Nov 15):
1. Flash is broken. The sideloaded Adobe flash no longer works (at least with Firefox)
2. Stock email app is not fully functional. Issues are reported with Exchange sync. In my case, I use imap mail. Stock email app even had problem syncing with my imap server. Emails deleted on my computer still showed on my N7.
3. XBMC (nightly built) is only working after you disable hardware decoding.
4. Most of the improvements in UI (launcher) featured in Nexus 5 DO NOT appear on Nexus 7. Your launcher looks nearly the same as 4.3.
Anyone else encountered issues with KitKat? Feel free to add to the list above.
[Update]
In case you updated to 4.4, and want to revert back, this is one way to return to 4.3:
http://www.androidpolice.com/2013/0...stock-using-a-full-factory-image-and-root-it/
Warning!!! You will lose your data. So backup anything important.
After you put 4.3 back, here is how you remove notification to automatic update to 4.4:
1. Go to Settings - Apps - ALL - Google Services Framework (Uncheck "Show notifications")
2. This doesn't stop Android from download the update. If your N7 is rooted, you can delete the update file. It is in /cache. (If your N7 is not rooted, you are out of luck)
3. In the future, if you want the update again:
Go to Settings - Apps - ALL - Google Services Framework (clear cache and data, restart)
For the reason 4, you can download and install Google Home launcher. It work perfectly ☺
Sent from my Nexus 7 using Tapatalk
ikeny said:
4. Most of the improvements in UI (launcher) featured in Nexus 5 DO NOT appear on Nexus 7. Your launcher looks nearly the same as 4.3.
Anyone else encountered issues with KitKat? Feel free to add to the list above.
Click to expand...
Click to collapse
I don't count this as an issue. If it looks just the same, but has the software improvements, then why not? Just saying....
_______________________________________
Phone: HTC EVO 4G LTE
Rooted, Custom Rom & Kernel
Tablet: ASUS Nexus 7.2
Rooted, Stock Rom & Kernel
Your on XDA, and your telling them not to flash the new update...? Irony?
Lol yeah not sure if they are trolling or joking
Sent from my HTC One XL using XDA Premium 4 mobile app
I came from CM10.2 and glitch kernel to stock Kitkat then kitkat with glitch.
Things I miss from that transition:
- In the close programs area I miss the close all the programs at once ability.
- I miss being able to swipe down and hold on the WiFi toggle to switch networks
- I miss my USB DAC working (this is no big deal to me but it is cool when it works)
I am beginning to come to the understanding though that regardless whether you are on a Custom ROM, Stock 4.3, Stock 4.4, whatever......
it really all looks the same, and acts the same. I think you just pick what you like and go with it and that's what is wonderful about the Android platform......the ability to pick and choose.
If I want my USB DAC back I'm quite literally a ROM flash away from doing it.
For now I'm going with kitkat and glitch kernel which nets me a 3G wireless dongle. If it weren't for the dongle stock 4.4 would be just fine for me.
ikeny said:
Here are some reasons that you should not update your Android OS to 4.4 for the time being (as of Nov 15):
2. Stock email app is not fully functional. Issues are reported with Exchange sync. In my case, I use imap mail. Stock email app even had problem syncing with my imap server. Emails deleted on my computer still showed on my N7.
Click to expand...
Click to collapse
For this, IMAP server works that way, you can download mails on multiple devices, you delete mail on one device, it will stay on the other...
teddy0209 said:
For this, IMAP server works that way, you can download mails on multiple devices, you delete mail on one device, it will stay on the other...
Click to expand...
Click to collapse
Not true for all of my Android (4.3 or older) and iOS devices. When you move an email to trash box on one device, all other devices sync to remove that email to trash automatically.
ikeny said:
Not true for all of my Android (4.3 or older) and iOS devices. When you move an email to trash box on one device, all other devices sync to remove that email to trash automatically.
Click to expand...
Click to collapse
that is if you move a mail (that hasn't been downloaded) to trash on the server itself...
Edit:
by the way, what the other guy said above is right...
this is xda, there is no reason not flash kitkat... =)
The_Zodiac said:
Lol yeah not sure if they are trolling or joking
Sent from my HTC One XL using XDA Premium 4 mobile app
Click to expand...
Click to collapse
:laugh: agree no more
truongnguyen1912 said:
For the reason 4, you can download and install Google Home launcher. It work perfectly ☺
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
It works for me, as well. Nice new feature, especially once Google Search is updated to v3.1. Thanks for the tip!
I don't see very many reasons NOT to upgrade to 4.4 on a Nexus 7 2013.....I've lost two apps: wifi manager and Xposed framework to activate the "experimental features" of Greenify. Greenify still works, of course, and Xposed will soon be updated.
ConradTDI said:
It works for me, as well. Nice new feature, especially once Google Search is updated to v3.1. Thanks for the tip!
I don't see very many reasons NOT to upgrade to 4.4 on a Nexus 7 2013.....I've lost two apps: wifi manager and Xposed framework to activate the "experimental features" of Greenify. Greenify still works, of course, and Xposed will soon be updated.
Click to expand...
Click to collapse
The two things I miss are Xposed (and the Gravity add on). I also didn't want to give up Multiboot. So, I left 4.3 as my "internal" OS and loaded 4.4 as a secondary in Multiboot. I then set 4.4 as the default. Elemental kernel works fine with the WiFi fix posted. Now I need to go back and trim a lot of fat off my 4.3 "base" install.
When I can get Multiboot and Xposed I will probably flash 4.4 as the base OS.
Xstop said:
Your on XDA, and your telling them not to flash the new update...? Irony?
Click to expand...
Click to collapse
Hey, I waited.. about 10 seconds!
Flash is dying. I don't think adobe is developing it any longer for android. They only have older version without support on their website.
Good, then we shall fight in the shade!
The biggest 4.4 issue for me is that text reflow is broken in lots of apps including Yahoo Mail and browsers (Next, Opera, etc). (Text reflow reformats the column of text partially visible on the screen to fit the screen. ie. zoom in until it's big enough and the the text is reformatted either automatically or by a double tap.
It's a huge issue for me as I find mobile web sites a poor substitute for their full featured desktop siblings. Without text reflow, I'm stuck scrolling horizontally to read each line.
I don't use flash a lot but find it pretty essential when I need it.
Web browsing also seems significantly slower with multiple browsers than 4.3.1,
I'm restoring my backup and going back to 4.3.1. Kit Kat didn't bring anything I've found significant in my use but has broken stuff that's important to me.
Kitkat doesn't bring anything significant, but brings problems (which will be ironed out over time, but now they are there).
It's definitely best to stay on 4.3 until it really pays to upgrade.
Sometimes the Android community appears to me like a religious cult where people dance around a golden calf and don't want to see reality anymore. "Holy update! Save my soul!"
Anybody else got problems with flash? Tested Dolphin?
TheGoD said:
Anybody else got problems with flash? Tested Dolphin?
Click to expand...
Click to collapse
Tested. It doesn't work. There are many apps not working like VLC, MX Player, Titanium ...
I go back to my previous backup
TheGoD said:
Anybody else got problems with flash? Tested Dolphin?
Click to expand...
Click to collapse
flash still works..
I don't feel like downgrading since I got sick battery life with 4.4 but what I miss the most is app ops. The best feature from 4.3 and almost no-one is talking about the removal of it.
I'm not going to upgrade my 2012 N7 though, it has great battery life already.
Sent from my Nexus 7 using Tapatalk 4

[Q] Does Verizon Galaxy Nexus (toro) have multiwindow ?

Hey guys, so I would just like to start off by saying I am new to this rom (coming from CM11) and one feature I heard about and was looking forward to trying was the multiwindow feature. However, when I go to recent application and try long pressing to get the option it's no where to be found? I have the latest omnirom update for the Verizon galaxy nexus and I'm not sure if there is something extra I missed or might have to do somewhere in the settings to enable multi window ? If anyone knows the answer to this problem it would really help. Thanks to anyone who replies.
Multiwindow is still a WIP, so it doesn't come by default. You'd either have to add it and compile yourself, or find an unofficial build with it already in. That, or wait.
PonsAsinorem said:
Multiwindow is still a WIP, so it doesn't come by default. You'd either have to add it and compile yourself, or find an unofficial build with it already in. That, or wait.
Click to expand...
Click to collapse
https://gerrit.omnirom.org/#/c/1510/ - Progress is here. When you see this change to "merged", you'll see multiwindow on all devices with nightlies.

[Q] No "Add to Split View" in i9300?

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.

T-Mobile Wi-Fi Calling.

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.

Categories

Resources