Database Develop

[Q] Good for Enterprise on custom Android ROMs

Has anyone had a problem with the intial setup for Good for Enterprise on custom Android ROMs? I installed it (using an issued PIN) on stock eclair on my Captivate and it worked fine. I then rooted, backed it up via TIBU and restored on Froyo and it still worked fine. The same process worked recently on Gingerbread. However, I have tried multiple custom Froyo ROMs and 1 GB recently and if I try the initial setup (with a new PIN) on anything other than stock eclair (even rooted), it will stop at "retrieving policies" and never complete. I then have to ask for a new PIN from my IT support and revert to eclair and finish the setup, backup, and restore on the later custom ROMs. Has anyone seen this and have any idea why? My IT support has no idea. I am not in a policy checking for root access and it does continue to work with root.
EDIT: I wonder if it is that the device name used in build properties is referenced during that step and it fails due to an unknown device...
Also, I have found that after I have it working after a certain PIN used, if I ever restore to an ealier point (due to a theme gone wrong, etc) then it stops syncing even if the restore point is AFTER I had it working with that PIN. It seems like the local software either is exchanging a dynamic password with the server or there is a message index, etc that has to be in sync. Any thoughts?

When in the Good setup screen, go to Menu>Device Info. Does the Phone number appear? I've been using CM7 just fine with Good but after the last few nightlies, Good no longer works. The phone number doesn't appear in the device info. Good thinks there is no phone network present.

I am a heavy Good user, unfortunately also addicted to changing ROMs on a frequent basis. I have never had an issue with Good running on any ROM, just on restoring from TiBu. I can flash new kernels, themes, etc, and Good works just fine. If I re-flash the same ROM, it resides and works just fine. It is only when flashing a new ROM I have problems. Good appears to restore OK, but won't pull new emails to the inbox. I ave to get a new PIN and re-install.

Same here.. i am addicted to flashing as well.
I tried Titanium backup to backup and restore to new ROM, but somehow Good just keep crashing after i put in my password.
I am sure I can ask for new pin, reinstall and what not.. but how often can we ask IT people (for my company at least) for new pins, until one day they may say, bugger off you ROM addict!

Finally figured it out, I think. The trick is to NOT have Good running in persistent mode when you do the backup with TiBu. IOW, reboot and backup with TiBu before you start Good and log in. I did that the last couple of new ROMs and it restored and worked just fine.
Sent from my SGH-I897 using XDA App

GOOD for Enterprise on Imito AM801 Tablet
I am also getting the Phone network is off. This is a tablet and does not have any phone piece or sim card installed. No hardware is even inside the tablet. Has anyone ran accross this issue on tablets?

This works for me.
http://forum.xda-developers.com/showthread.php?p=35263313#post35263313

Good with custom roms
Just to share a recent experience on that topic:
I wanted to have a custom rom but need GFE for my work which of course has a policy of no root with GFE.
So after a little research and useful info from this forum I figured a very simple way to do it, as long as you don't consider root as critical for your day-to-day stuff
1. Install your custom rom which most likely requires rooting
2. Install SuperSU from the Play Store and use it to remove root completely
3. Install and activate GFE
That's it!
Hoope this helps someone else how got a little scared to have to go through scripts and stuff to do this
Using a Galaxy S4 with Carbon Rom

Anteus20 said:
Just to share a recent experience on that topic:
I wanted to have a custom rom but need GFE for my work which of course has a policy of no root with GFE.
So after a little research and useful info from this forum I figured a very simple way to do it, as long as you don't consider root as critical for your day-to-day stuff
1. Install your custom rom which most likely requires rooting
2. Install SuperSU from the Play Store and use it to remove root completely
3. Install and activate GFE
That's it!
Hoope this helps someone else how got a little scared to have to go through scripts and stuff to do this
Using a Galaxy S4 with Carbon Rom
Click to expand...
Click to collapse
Does this still work?
I too need GFE on my Galaxy S4 but am sick of the poor battery life. I tried SlimKat and Google Play Edition roms, and removed root using Super SU in both cases. But GFE gives a message "Not supported for this type of Handheld". . Not sure if GFE is looking for a TW based ROM.
I will give it another go using Carbon ROM. Still, any other advice / experience on getting GFE working on a custom ROM would be much appreciated.
Thanks.

joshic75 said:
Does this still work?
I too need GFE on my Galaxy S4 but am sick of the poor battery life. I tried SlimKat and Google Play Edition roms, and removed root using Super SU in both cases. But GFE gives a message "Not supported for this type of Handheld". . Not sure if GFE is looking for a TW based ROM.
I will give it another go using Carbon ROM. Still, any other advice / experience on getting GFE working on a custom ROM would be much appreciated.
Thanks.
Click to expand...
Click to collapse
You quoted a 1 year old post, might be hard to get a reply. Also this is for the S1, while the app (GFE) might be the same, the ROMs definitely aren't.
That being said, chances are that the app was updated to prevent that workaround. You could flash a TW based ROM and test it though.

Thanks for the reply. I will try posting a fresh question in the Q&A thread in case anyone has more recent experience with GFE. Cheers.

joshic75 said:
Thanks for the reply. I will try posting a fresh question in the Q&A thread in case anyone has more recent experience with GFE. Cheers.
Click to expand...
Click to collapse
There is an xposed module for this.

Hi, are you referring to Wanam Xposed which has a "fake official system status" functionality?
As I understand, Xposed needs root, but Good for enterprise doesn't work on a rooted handset. Can Xposed work without root?
Also Wanam Xposed is meant to work with TW based ROMs whereas I don't want to go back to TW based ROM unless it is extremely light.

joshic75 said:
Hi, are you referring to Wanam Xposed which has a "fake official system status" functionality?
As I understand, Xposed needs root, but Good for enterprise doesn't work on a rooted handset. Can Xposed work without root?
Also Wanam Xposed is meant to work with TW based ROMs whereas I don't want to go back to TW based ROM unless it is extremely light.
Click to expand...
Click to collapse
I'm a bit confused here, Custom ROMs are pre-rooted. Therefor, if you're not on TW, you're rooted.
And yes, Xposed does require root. As for Wanam, I duno if it works on AOSP but best way to know is you try

Thanks for replying.
Supersu has a Full Unroot functionality which removes root.
Yes I will try, but every failed attempt sends an email to office admin so I have to be prudent.
http://www.gogadgetx.com/xposed-framework-install-use-best-modules-list/
The link above mentions that root is required while installing XPosed, but later it can perform without root. Is this correct or not?

joshic75 said:
Thanks for replying.
Supersu has a Full Unroot functionality which removes root.
Yes I will try, but every failed attempt sends an email to office admin so I have to be prudent.
http://www.gogadgetx.com/xposed-framework-install-use-best-modules-list/
The link above mentions that root is required while installing XPosed, but later it can perform without root. Is this correct or not?
Click to expand...
Click to collapse
I have never personally tried it without root but you can test that fairly easily. I expect it would depend on the module you're using, some require more permissions than others.

I tried it out but it didn't work.
I have to go back to stock ROM

Very strange problem - missing apps

yesterday, I pluged in my charger and started browsing.
at one moment phone freezed, purple led flashed and phone rebooted
after that a lot of apps I had installed are missing. among them are gmail, google search widget, play store, titanium backup, some office from market (can't remember which) ...
and one widget I use can't be loaded on startup but if I remove it and add again it works.
I tried all I can think off except factory reset.
I tried deleting cache, dalvik cache, switched app2sd off (which were on, although I remember leaving it off), fixed permissions from recovery ...
I even reinstalled kernel and ROM and gapps, but no change at all which is really strange.
I use MiniCM7-2.2.0 ROM and 2.6.29.6-nAa-11 kernel
SD card is working, I can browse files and swap is working.
It also seems that rebooting doesn't work well. Sometimes, I choose reboot but it doesn't boot up until I pull out battery and press power button.
I'm not sure if this is connected because I didn't reboot much phone with this kernel and ROM
Any ideas before I wipe data?

Overclocked ?
Sent from my E15i using XDA

Apps2sd that's why ur apps r gone. Full wipe and reflash rom. Reboot issue can be fixed with latest flashtool reflash kernel with that. Worked for me no reboot problems no more
Hit thanx if I helped
Sent from my E15i using XDA

thank you for fast replies
phone is not overclocked.
I also guess it has something to do with app2SD
but I do not use it.
when I installed ROM I wanted to use Link2SD but it couldn't work because of build in App2SD.
I tried that App2SD but I couldn't control which apps to move, I even didn't exactly understood how it works, so I gave up of it.
Everything worked until yesterday.
and I only browsed internet when this happened. what could go wrong?
Is there a way to fix this before I wipe the whole thing?
I would like to make some backups and for that I need missing apps.
thank you

Oh,
and the strangest thing to me is that even after I reflash gapps, I don't have any google apps (at least which I use) except google talk

Try this:
Root again your phone with SuperOneClick.
Go to Settings >CM Settings >Performance >a2sd, and deactivate it. Then, activate it again.
Reboot.
Hopefully... it will fix your problem (worked for me ).

any particular version of superoneclick I should use? I tried one I have (which I used to root my phone a long time ago) and it fails to root it.
but why do you think I should root again? This is custom room and it is already rooted.
I tried turning on and off app2sd but there's no change, except some files are in one case in sd-ext directory and in other arent. but that are not missing apps :-(

Use the newest version, it will work. If not... use any method to root your phone again and follow the above guide (YES, I know that your ROM is rooted, just do it).
Why you should root again? Well, I already had that problem and all root apps were having problems (I dunno if you are having problems too, try it), so I rooted again my phone and all the problems were solved.

I repeated this with superoneclick 2.3.3 but no difference.
I had to full wipe the phone.
thanks all for suggestions.
EDIT: just to be clear, it did root this time, but no difference about this apps.

[Q] Rooted Nook HD+ boot problem

A question for any intellectual Android/Nook-addicts out there...
Basically, I've rooted my Nook HD+ (Numberous times now) and have experience rooting android devices in the past and have had no problems. I used the CWM method - installed universal root on factory stock (And afterwards, 2.1.0 stock just to see if it fixed the problem... it didn't) and extras (Tried not installing extras twice also, didn't make a difference)
Basically, I've learnt the hard way that eight resets on boot and the device hard-resets to factory stock. The first Root Bootup is fine (The bootup after removing the CWM sdc) and, after turning it off and on again, so is the second bootup... But the third one is where the problem occurs. I power on as normal, and the standard 'Nook' screen appears as it begins to boot...
It then proceeds to resetting itself eight times - never getting past the 'Nook' screen that appears at the start of every bootup, therefore causing a hard factory reset.
I've tried using the CWM recover method to the OS I used before rooting the nook originally, and there doesn't seem to be any problems if the device isn't rooted. I've also just let it update itself from factory version to current version - and it works fine with that also.
Perhaps this is common and I'm just a plain idiot. I honestly can't find any answers - so if it is common, sorry for wasting your time!
Thanks for your time!
- P

Do you have some apps being automatically installed by Play Store? Sometime people have their settings set so that happens. Then a root app gets installed and makes some changes to /system and causes a reset. Go to Play Store and tell it not to automatically install or upgrade apps.`
Sent from my Nook HD+ running CM10.1 on emmc.

leapinlar said:
Do you have some apps being automatically installed by Play Store? Sometime people have their settings set so that happens. Then a root app gets installed and makes some changes to /system and causes a reset. Go to Play Store and tell it not to automatically install or upgrade apps.`
Sent from my Nook HD+ running CM10.1 on emmc.
Click to expand...
Click to collapse
No apps that automatically download that i can see. But you're likely onto something - I do install all the apps manually (No matter how menial) (Going through the list, hitting install for each of them) before manually logging into each one afterwards. I do use a few root apps - no ad-versions to avoid those annoying popups, Ultrabox, Superuser, Pimp my Android and Root Browser to name most, if not all of them.
I'm going to have to do things the awkward way now, installing each app, setting them to the setting I want for them, and seeing what happens. I have a mild suspicion it's a setting on Pimp my Android...
I'll let you know if I sort it. Thanks for the suggestion :cyclops:

P Complex said:
No apps that automatically download that i can see. But you're likely onto something - I do install all the apps manually (No matter how menial) (Going through the list, hitting install for each of them) before manually logging into each one afterwards. I do use a few root apps - no ad-versions to avoid those annoying popups, Ultrabox, Superuser, Pimp my Android and Root Browser to name most, if not all of them.
I'm going to have to do things the awkward way now, installing each app, setting them to the setting I want for them, and seeing what happens. I have a mild suspicion it's a setting on Pimp my Android...
I'll let you know if I sort it. Thanks for the suggestion :cyclops:
Click to expand...
Click to collapse
Why are you installing superuser? It is already installed with the universal root. That may be it too.
Edit: And some of the apps I put on there are old on purpose. Like Root Browser. I have it set so that the free version is ad free. If you update it, the ad free goes away.
Sent from my Nook HD+ running CM10.1 on emmc.

I am VERY sorry it's taken me so long to reply! Even though I've only just joined, I should have done it long before now.
I found the problem - it was 'Pimp my Android' app. I was experiencing something called 'boot loop' - so much for my research skills for such a common problem. I fiddled about with my usual settings - and found some that cause it to get stuck like that, even when they're set not to activate on startup!
Tis' all working now. Everything else seems to be just peachy! You were right, thanks for your help

[Q] Note 4 Lag and Fingerprint not working - tried everything

Hi everyone, OK I've tried everything in other threads, here's the situation:
Note 4 Sprint
cf-auto-root worked fine, everything working well for a week (stock recovery, stock ROM, just root). Then installed xposed (accidentally used the experimental 2.7 version) and RootCloak module. This threw me into a boot loop.
I recovered from it by redoing cf-auto-root/odin. That got me out of the loop, but-
Ever since then:
- Phone lags for a few seconds every few seconds - making it hard to even type in a phone number, let alone watch a video,
- Fingerprint doesn't work - when launching the menu from settings I get an error that it's unavailable.
I've tried everything in the other threads:
- build.prop change (disabling securestorage)
- successfully installed 2.6 xposed and tried:
- wanam xposed to disable securestorage
- and the xsecurestorage module
- flashed stock rom from sammobile with odin
- even tried disabling selinux with wanam
No matter what, these same issues. I haven't tried anything other than the stock rom. Any ideas at all? Is there a different ROM out there I should try? Does that even have a chance of working?
I'm not sure I understand why flashing stock didn't fix it - even though it caused me to lose root...
Right now I have TWRP with root and stock ROM.
Any ideas or suggestions really appreciated.. I'm out of ideas. Thanks

I have the Same Problem

I had the same problem, haven't bothered installing it again since, don't suppose anyone has heard from the developers?

Hope maybe the devs can shed some light here. Is there anything else I can do? Flashing stock didn't even help. What's left?

So after not touching anything for about a week - things started running smoothly. Very odd - didn't change anything. Xposed was uninstalled for that time.
But, after SuperSU updated (and updated the binary/rebooted), the lag came back. So, this is telling me this may be related to root/SuperSU instead.

Unable to unlock my lock screen after installing xpoosed.

Hi guys..
I have recently rooted (supersu) my j7 prime g610f (7.0) after installing dm-veriry pypass and twrp and then flashed xpoosed framework and tried aome moudles out and everything seemed to be fine .
Untill i rebooted to activate a moudle and i found that the lock screen doesnt want to unlock although the pin is right( just stands still for 2 seconds and then screen turns off and i repeated the process and same thing ) ..
I managed to unlock my phone through the website and tried other lock methods and i found that every method isn't responding aswell !
I then disabled all the models and denies all root access apps and rebooted and same thing happens.
I really need some help as i cant leave my phone unlocked.
Thx.

Bassem AbdullMonem said:
Hi guys..
I have recently rooted (supersu) my j7 prime g610f (7.0) after installing dm-veriry pypass and twrp and then flashed xpoosed framework and tried aome moudles out and everything seemed to be fine .
Untill i rebooted to activate a moudle and i found that the lock screen doesnt want to unlock although the pin is right( just stands still for 2 seconds and then screen turns off and i repeated the process and same thing ) ..
I managed to unlock my phone through the website and tried other lock methods and i found that every method isn't responding aswell !
I then disabled all the models and denies all root access apps and rebooted and same thing happens.
I really need some help as i cant leave my phone unlocked.
Thx.
Click to expand...
Click to collapse
1) Easiest way is to wipe and restore a backup in TWRP from when your device was working properly if you've hopefully already made one.
2) Another option is to boot into TWRP and go into file manager and delete the folders of the Xposed Modules you installed that you think might be causing the problem(in "/data/app/", "/data/data/, etc)". Then reboot and see if that fixed the problem. You have to be very careful when installing Xposed mods, especially when they're meant to tweak the system in some way, that they are actually meant for your device, particularly with Samsung Touchwiz devices that have heavily modded software.
3) Make sure that you're using the correct Xposed version for Samsung too, as this can cause problems with properly booting up the device.
4) Last case scenario you might want to consider wiping and reflashing your rom. Then at least you can make sure your touchscreen digitizer still works and can redo everything one at a time to see what's causing the problem.
I hope one of these suggestions helps.
Sent from my SM-N920T using Tapatalk

bogarty said:
1) Easiest way is to wipe and restore a backup in TWRP from when your device was working properly if you've hopefully already made one.
2) Another option is to boot into TWRP and go into file manager and delete the folders of the Xposed Modules you installed that you think might be causing the problem(in "/data/app/", "/data/data/, etc)". Then reboot and see if that fixed the problem. You have to be very careful when installing Xposed mods, especially when they're meant to tweak the system in some way, that they are actually meant for your device, particularly with Samsung Touchwiz devices that have heavily modded software.
3) Make sure that you're using the correct Xposed version for Samsung too, as this can cause problems with properly booting up the device.
4) Last case scenario you might want to consider wiping and reflashing your rom. Then at least you can make sure your touchscreen digitizer still works and can redo everything one at a time to see what's causing the problem.
I hope one of these suggestions helps.
Sent from my SM-N920T using Tapatalk
Click to expand...
Click to collapse
Unfortunately i dont hace a backup but i noticed something that the problem is a delay in responding to my pin , and i notice that the cpu usage goes 3% to 35% when i unlock my phone usinv the pin ... i managed to unlock it by entering the pin and tapping in the screen few times to keep it lit and prevent it from sleeping .. any ideas foe that delay or cpu usage ?

Bassem AbdullMonem said:
Unfortunately i dont hace a backup but i noticed something that the problem is a delay in responding to my pin , and i notice that the cpu usage goes 3% to 35% when i unlock my phone usinv the pin ... i managed to unlock it by entering the pin and tapping in the screen few times to keep it lit and prevent it from sleeping .. any ideas foe that delay or cpu usage ?
Click to expand...
Click to collapse
Truthfully, your best bet while you have your device up and running is to backup all your apps and data with something like Titanium Backup or even sync them with the Samsung Cloud. The cloud reinstalls everything and sets your device configuration back to the way it was. Then, if you have a custom rom installed, wipe it in TWRP and reinstall it. If you're running stock, then don't wipe. Just go to the Sammobile website, download the latest firmware for your specific device and reflash it to the device with Odin. This generally fixes all system problems with a device, while preserving your app data.
Alternately, you can also try searching XDA for kernels that are made for your device that have a higher performance and try installing one of those to see if anything improves. As far as the screen going off early too, you can always check in "Settings/Display/Screen Timeout" to see what it's set for and change it to the max screen on time. It really sounds like you may have broke something system wise with Xposed or an Xposed module though, which is very easy to do, so I would really recommend starting over fresh. If you're on stock especially, as you really have nothing(data wise) to lose.
Sent from my SM-N920T using Tapatalk