[Q] multi window does not respond to back key - AT&T Samsung Galaxy Note II

Would much appreciate help/advise/pointers with respect to the following:
The problem: multi windows does not work. Long press on the “back” key just does not have any effect whatsoever.
Yes, multi-window toggle is on. Yes, cleared data, cache, restarted, used garlic and holy water, etc, to no avail. Yes, I’ve read through the forums extensively, and did not find any info related to my problem.
Tried to install multi-window manager from the play store, same nothing. Checked apk, permissions, etc. – all seems to be in fine order. The only thing that seems suspicious is that /data/data/com.sec.android.app.FlashBarService is empty – which kind of suggests to my amateurish mind that something somewhere does not get started. Checked that services framework is up, but that’s about the limit of my diagnostic skills on Android.
Oh yeah, running latest OTA version of AT&T 4.2.1 Note 2 stock, rooted.
Any ideas?
Thanks.

Related

[Q] various problems. Car Mode and Force Closing everything.

Love my epic, but I've been having problems for a month or more now. Not sure which section this belongs in, but I'm posting it here because I'm looking for answers.
Problem 1-
Phone randomly enters "car mode", doesn't always give me the option to disable it and even when it does, if I click disable it often stays in car mode (all calls go to speakerphone, phone won't rotate). The problem has followed me through 3 ROMs and now to 100% stock, nonrooted gingerbread pushed from sprint. Is there anyway to uninstall this "feature"? I've done some searching but haven't found a solid answer. Its gotten bad enough that now, during a phone call, it will enter and leave car mode multiple times. Enabling and disabling speakerphone during the call.
Problem 2-
For awhile my phone was force closing Everything. Things like "Android Core System Process" and "Google Framework Services" along with any app I attempted to launch. It started while I was running ViperRom(most recent release) and kinda came and went. Would be ok for awhile after I restored from my initial backup. Finally became unlivable so I tried the SyndicateRom(with genocid kernel) and the problem continued to come and go. Finally got to the point that a brand new install of syndicate, after full system wipe wouldn't fix it so I returned to 100% stock and it hasn't come back yet. I imagine it could be corrupt system ram? But I couldn't find a ram tester. Id really like to go back to Syndicate, so any help would be nice.
Thank you
Sent from my SPH-D700 using XDA App
x2 with problem #2 here. wiped and reflashed srf 1.2 3 times now in the past 2 months and eventually the "Google Services Framework (process com.google.process.gapps)" force close message comes back.
WTF?
#1 iis baffling , for #2 you've probably already tried this but "fixing" permissions.usually does the trick with FC's. Good Luck

[Q] Maps/Navigation force closing on custom ROM/Kernel - HELP Please!

Hi all,
Hopefully someone can shed some light on this and help a tortured soul. By no means am I an Android expert, but I definitely am not a noob. I had an S2 in the past and done plenty of flashing there, and now own a Bell SGH-I747M S3... my precious...
First off I tried a whole bunch of different ROMs, of all flavors (AOSP, AOKP, CM10, PARANOID, and some TW), and a lot of them are awesome. However, I found that after having done so much flashing and customizing using other people's work, it was now time for me and attempt to make my own ROM. I feel I now have the knowledge to do so. Don't get me wrong, I am far from a Dev, and I don't do much coding at all. I found this great suite called Android Kitchen, which pretty much guides you through the steps for making your own ROM, and it's great for learning.
In the end, I was able to come up with a final working version of my own ROM, built from scratch using the original official Bell JB 4.1.1 update file. and I have to say I am quite proud of it, as it has all the apps, features and theming that I want, and works quite well I might add. I get great results performance and battery wise (for my taste and needs) when using my ROM with KToonsez kernel.
BUT!!... as good as I think the ROM is, it is unfortunately not flawless. I do have an issue (the only one I could find so far after 2 weeks using it), and for me it is a BIG issue. Maps/Navigation does not seem to like the ROM/kernel combo on MY phone. I say MY phone because I have setup a friend with pretty much the same thing, and he is not experiencing the same issue.
Here is a description of the problem I get. Let's say I go to my contacts and select one with an address. I will touch the address, then Maps opens no problem, and finds the place, and I also get fast GPS lock, no issues there either. Then I will select Navigate to get a voice turn by turn description while driving. The Nav app starts OK as well and seems to work fine. Then after a few minutes (sometimes 2 sometimes 10), Navigation will shutdown, and I get a pop-up saying "Unfortunately Maps has stopped working...". When I OK that, after a few seconds, Navigation starts talking to me again, although not on screen. Also a Navigation icon will appear in the notification area, and if I hit that it resumes Nav, as if nothing had happened. Another few minutes like that, and then I get the same message again, but this time it crashes for good. ALWAYS!!
Troubleshooting:
- Flashed the ROM/Kernel 3 times now. Always wiping and formatting ALL!
- Cleared cache and data from Android Settings/Applications
- Cleared cache from Maps settings.
- Re-installed Maps
- Wiped phone cache, dalvik cache and fixed permissions from recovery.
- Changed kernel back to stock (that seems to work fine btw,, but I do not want stock kernel, plus the setup I want works well on my friend's S3, same as mine, which I setup myself for him (he's a total noob)).
- Changed kernel again from stock to KToonsez (that also works fine after that, however I get other things that start not working well... too many).
- I always wipe cache, dalvik cache and fix permissions after changing kernels.
I have been poking at this for about a week now, and I am tired! I was hoping someone would have a suggestion, maybe from past experience. The only thing I can think of that is different on his phone and mine is the apps that we restore after installing the ROM and kernel (Titanium Backup, user apps and data only, nothing related to system is touched). I am guessing one of my apps could cause a conflict, but pardon my laziness, but I really do not feel like testing / installing my apps one by one to hopefully without guarantee find a culprit... way too many apps for that So I am testing my luck here on XDA... there are a lot of smart people here
I appologize for the lenghty post, but this way, there is less chance I left anything out... PLEASE HELP!!!
Raz...
Sorry for the bump guys... I was really hoping someone can give some input here. Desperate for a solution here!!
Thanks

note 3 voice recognition not functioning

I recently used the cleaner to remove the bloat ware from my note 3. Like a nub I didn't think to check the file list and accidentally picked the one that removed all the cool features from the phone.. Most importantly the voice recognition was gone.
So I downloaded a complete app file and put it in the appropriate folder and did a factory reset. Almost everything went back to stock except one thing. My voice activation of the camera, music, and alarm clock no longer works. I am also not getting the notification at the top telling me that I can use said voice functions. Additionally the voice setting is missing in the settings screen. I can still get to it by searching for the settings and it says it's on.. and I can even change it ect.. but still nothing. The only thing I can do is say "hi Galaxy" to wake the phone. S voice still works And I Can Search And Text And All that.
So what am I missing? Is it just a simple ask that I may have overlooked? Any help would be awesome.. or directions to a download of a 100% complete stock app folder would be awesome
nevermind.. found the stock rom
http://forum.xda-developers.com/showthread.php?t=2465764

[Q] Settings menu all fubard

As my title states, no idea what happened to my settings menu.
I'm "stock" rooted. (Did it back in December with odin flash - 4.3)
Firewalled, Greenified, and TitaniumBackup to Freeze useless apps.
Everything has been great, then all of a sudden I was getting 3 errrors.
Google Text to Speech, Maps and Settings all quit working. (The whole, unfortunately *blank* has stopped working)
I removed Text to Speech, but Settings still crashes and refuses to work and now Maps took it's place (T2S).
Removed Maps and still Settings does not work and will randomly crash in the background.
I have done nothing new from what I described I have already done above.
Nothing was newly frozen. I have never uninstall any stock apps, just freeze them.
Last thing I uninstalled was a GoSMS theme I no longer use. Uninstalled it through ROM Toolbox Pro as I saw it was running in the background.
Everything else appears to be working fine. Camera, Chrome, Texting, Calling and my various daily apps.
Just something with the settings "app" has gone all wrong.
It also appears it's not the entire settings. Like if I go to about phone, it's all good. If I go to display part of the settings, *crash*
Two other odd issues pertaining to this as well:
My assistive light widget no longer works. So I know this happened within a 24 hour period as I use that light nearly every day.
And when you get into the settings part of the phone, all the text / font is screwed up. (Pic attached to see what I'm talking about)
Assistive light widget shows the same messed up text as well.
Data corruption. It will spread. The easiest and most successful solution is to wipe data, system, cache, and Dalvik cache, then re-flash the stock firmware, then re-root.
If you don't want it that successful you can do the wipes and restore a backup, but there is always a chance that there was corruption saved in the last backup and in a few days it will be as it is now.
What caused the corruption? It could be anything from a bad USB cable to a nearby flash of lightening, but more likely it's whatever you do that you need root for.
Frank
I would believe that was the issue if it was more wide spread.
Or I was having stability issues in daily usage.
The phone only gets charged via usb, I have not hooked it up to a computer for some time.
No storms or surges recently either.
As far as root usings, nothing has changed or updated recently. And none of what I do hard changes anything.
Reflash. Much faster and easier than wracking your brain trying to track down what exactly little thing went wrong.

Rebuilding Pure Android v6.0.1 (Please help!!!)

Greetings,
I'm trying to rebuild an Android v6.0.1 from a old/leaked rom I stumbled upon for an older Samsung phone not widely supported.
I'm running into a few problems and was hoping someone could point me in the right direction regarding what I am missing.
Stuck in "Factory Mode"
I've been battling this issue by doing various compare directory / compare files to try to track down the issue.
From what I've found so far, supposedly if I jump into /efs/FactoryApp/factorymode and change the value from OFF to ON, it will fix the problem; but it's proven to not be that simple.
I've found some settings floating around /system/csc/ that look like good places to stab at, but every attempt playing there has caused the phone to bootloop.
Additionally, there are two directories in /system/ that don't appear on the retail rom; /system/factory/ and /system/data/. Deleting these seem to do nothing, but don't result in boot loops, so I at least consider it a win killing these.
Google Contacts won't sync
This one is driving me almost mad. I can't figure out how to get this one working.
I feel like there are services I am missing. Android properly lets me see that I can sync the contacts using the latest version of Google Contacts, but it can't seem to actually do it.
- GoogleContactSynAdapter is installed in /system/app/ with the correct permissions (I've tried several different versions of v6.0.1)
- mcRegistry is using a known working file set with other roms; but neither the original mcRegistry nor ones from different roms work.
- Android Download Manager is installed in /system/priv-app/ and seems to be working with just about everything else.
Gmail, Google Calendar and Google Voice all sync correctly, though they won't, for any reason, hit contacts without producing an error.
Power Button powers off immediately
This is another one that's boggling my head.
/system/usr/keylayout/Generic.kl properly defines the power button (button 116) as "Power", but it doesn't produce the power menu. HOWEVER, I can map to the Power Button with any of the various button remapper apps --- I just can't map it to the power button. I'm really confused where this menu is being pulled from or where the "Power" function is being defined at.
Lock Screen won't start
I haven't really started tackling this problem as I've been trying to track down the other issues for the better part of the last two weeks.
I feel like something massive is missing and wanted to see if anyone had any immediate thoughts why the lock screen won't work. Any kneejerk thoughts welcomed on this one.
---
Any help for tackling any of these problems would be very much appreciated. Thanks in advance.

Categories

Resources