Hi, I was hoping someone could help me!
I had a Titan which I successfully updated to WP7.8 earlier this year using the 78er tool. Unfortunately I dropped that phone and smashed the screen but my insurance company just sent me a new handset so, naturally, the first thing I did was attempt to update to 7.8 again.
I realise now that I should probably have let the default WP7.5 ROM fully update through Zune before running 78er but, alas, I did not. Now, since updating to WP7.8, some aspects of my phone's functionality are working fine but other aspects are not.
For instance I cannot access a variety of settings: the WiFi menu, the accounts menus (email, Facebook, etc), the lock + wallpaper menu, mobile network menu and others. Every time I select one of these nothing happens.
I don't know what to do to resolve this - I cannot re-run 78er as it tells me that it has already updated, so I can only assume that I need to flash an earlier (stable) ROM and then re-run 78er again. But, I must confess I don't know how to do this.
Something that puzzles me is that the OS is otherwise operating normally.
Any thoughts?
Many thanks.
[RESOLVED]
RESOLVED!
After some searching I discovered that this was due to my selecting the wrong language during the Seven-Eighter update (I selected US English instead of UK English). It seems this is quite a common problem and the solution was to use Cab Sender to send the relevant UK English files to my phone from this page: http://forum.xda-developers.com/showthread.php?t=1306415
I had to start from the first update and work my way through. It didn't start working until I had updated to "WP 7.8 OS UPDATES (7.10.8779.8 - 7.10.8779.8)"
Patience is necessary!
ROM's main highlight is that exchange server security restrictions that are enforced from your exchange server is bypassed ONLY for the lockscreen. So no more entering a password while unlocking your device! Also, you get to use lockscreen widgets, quick camera access, lockscreen targets etc. while you use your company's exchange server account!
Besides, the build has been compiled with the latest CM10.1 fixes (dozens of fixes that happen on a daily basis).
Version 2
- Latest CM10.1 sources (27th May 2013)
- Locktargets crash issues fixed
- Lockscreen with delayed locking - bug fixed (now works as expected!)
- Performance improvements/optimization
- Bluetooth stability fixes
Download Link: http://www.mediafire.com/?0whujps4hzbh4rp
Version 1
- Lockscreen exchange security disabled, always defaults to slide to unlock
- CM10.1 source as on May 14th 2013
Download Link: http://www.mediafire.com/?yyktiubn1lq4x80
-dt39
reserved.
Great !thank you
It would be great if any of you guys can let me know if this is something you find useful. I could try and embed this as a hack-switch somewhere in settings, clean it up from the root level (rather than just disable at lockscreen) and allow the other lock options in settings.
Also, please report if you find any other bugs!
i'd love just a flashable zip aosp or twiz.
Hi
Could you post just the MOD to disable Lockscreen Exchange Security, not the whole ROM, so that we can use it with any 10.1 ROM?
many Thanks
I recall sometime last year there was such a mod for the Exchange apk somewhere in the HTC forums, but I can't recall where exactly. Building a ROM just to enable this is overboard IMHO.
pasil.pt said:
Hi
Could you post just the MOD to disable Lockscreen Exchange Security, not the whole ROM, so that we can use it with any 10.1 ROM?
many Thanks
Click to expand...
Click to collapse
+1
Sent from my GT-N7100 using Tapatalk 2
I am using Revo HD 17.0, can I flash this? I need this badly!
Thanks.
Bert
Unfortunately all the hacks to fix exchange.apk and other email related apks don't completely kill exchange imposed security restrictions system-wide.
The only way to disable these restrictions for specific modules is by doing this -
1. DevicePolicyManager module in Android sources manages all the restrictions across the device. Fixing this directly would ensure perfect removal of these restrictions. The module should still exist to communicate with the exchange servers letting it know that "the device is all fine and secure". The disabling has to be done with all the interfaces exposed which other parts of Android (lockscreen, homescreen widgets, device wipe etc.) accesses. When other parts of the OS queries the DevicePolicyManager module if any restrictions exist - it should return "NO restrictions".
This would take a little longer to implement and test - and is something I will now work on and implement.
2. The second dirty approach is to fix individual modules (such as Lockscreen - like what i've currently patched right now). Only within LockScreen i'm currently overriding querying anything from the DevicePolicyManager.
Version 2 uploaded! Bug fixes, latest CM10.1 sources compiled, performance tweaks.
While working on an Android app for the company I work for, we have run into a very weird situation where the app doesn't work as expected. One of our paying subscribers reports seeing a black screen when opening our app on his Android, even though we have successfully tested our app on the same model of phone. We suspect the problem stems from other software running on his phone, what could it be?
Here are a couple things to consider:
1. To my best knowledge, the "black" screen is actually a dark gray color that is used within our app. This tells me that maybe a view is not rendering correctly, or possibly transparency is not working correctly.
2. We were informed that our latest version of the app in the Google Play Store was working momentarily, but then ceased to work (i.e. the dark gray screen). We don't have enough info to know how long it took for this behavior to start happening, but we cannot recreate this issue at all.
3. We have other customers using the same model of phone, but not calling up complaining about the issue. We don't think it's affecting others, but we do have evidence in our logs that suggests the users are using the app and making all the API calls that the app would normally make.
4. An older version of our app DOES work for them. There were a lot of changes to the build system that we made, including taking out hard references to the package name from the manifest and putting them in the gradle build system. I couldn't imagine anything I changed in code would affect this user except some of the manifest changes.
(example: com.company.app.activities was refactored to .activities in the manifest)
My questions to you are: Do you know of any apps that can interfere with another? Have you seen this or heard of this before? Are there any tricks for me, as a developer, to resolve this issue? (perhaps it's a problem with my AndroidManifest.xml or a dependency in my build.gradle file)
Thank you so much for your help! Even though this is affecting one customer, we're hoping that we can identify this problem and solve it so others facing this problem can learn from this post.
Root, ROMs, Android Pay, Tmobile WiFi Calling & Google Fi, and choosing a new phone
I wish I could see all of this info together, so I thought I'd ask the question and see what we can come up with.
1. In my experience, if you root a stock rom, sooner or later an update comes that un-roots it. Is this still usually true?
1.a. And sometimes the new stock rom will make the rooting process more difficult than previously, or even impossible. Right?
1.b. Thus, the most reliable way to get a root that doesn't go away, is to use a custom ROM. Right? Is there something I'm missing here?
With a custom ROM, one can typically disable/enable root at will.
2. Android pay.... will I ever get it working on a custom ROM? Easy or difficult? Does it work with only a few select phones / ROMs? Does one have to reboot the phone after disabling root, in order to get Android Pay to work? What does the space look like, and how practical is it to use on a daily basis?
3. How about T-Mobile Wi-Fi calling? There are a few things I've read on this topic...
3.a. I've read that some non-Tmobile phones have WiFi calling enabled, which will work on Tmobile's network. Is that pretty common or is it only a small number of select phones?
3.b. Does LineageOS or some other custom ROM support WiFi calling on ALL phones, which works on Tmobile's network?
3.c. One guide I read recommended getting some software off of stock before installing the custom ROM, and then installing that stock software onto the phone; is this a standard practice, and does it generally work?
3.d. one resource that is fueling some of these questions: http://www.spectrumgateway.com/compatible-phones
4. What about Google Fi? They officially only support a handful of phones. What's that about? Is the space similar to Tmobile WiFi calling, or is it completely different in practice?
5. Ok, you know what, maybe I could get by without root? But how would I find substitutes for these features I find indispensable?
5.a. view stored WiFi passwords; 5.b. emoji switcher; 5.c. properly removing bloatware; 5.d. Backing up app data that is stored in /data/ (wifi passwords, contacts, few other things)
I'm shopping for a new phone, and not knowing about the above makes it really difficult: do I need to go with a Tmobile branded phone? If I choose right is it possible I could be able to move the phone to Google Fi? Will I be able to use a custom rom, root + android pay without rebooting, and wifi calling, all in concert with minimal friction? Is there one magic phone or custom ROM that does it all, or are there a number of them? Or none of them?
Thanks y'all!
David
Info on T-Mobile VoLTE and WiFi calling here: http://www.spectrumgateway.com/compatible-phones
It appears that "SafetyNet" is the name and branding for android's system that monitors the system and reports root status and other modification to different apps, disabling Android Pay as well as netflix and others. Here is an article about using Magisk to fool SafetyNet:
https://android.gadgethacks.com/how-to/magisk-101-switch-from-supersu-magisk-pass-safetynet-0177578/
Magisk has modules, a few of which are described in the above article.
One that I didn't see there, but which I saw described elsewhere, was "Universal SafetyNet Fix / Univeral Hide" - a Magisk module.
Lots of information still not figured out -- it would be great to collect some more of this information here!
Hello,
Not sure if it's the right place, but I'm getting depressed with my Xiaomi 12 behaviour. Since last update, MIUI global 13.2.4, the phone keeps killing apps, even if I set those with :
- not battery restriction
- auto startup
I tried a factory reset, I unlocked it, rooted it. It keeps killing apps. It's annoying, because I use Vivid and removed the navigation buttons. I let you imagine how I can be stuck sometimes when Vivid is killed. Yet, Vivid is locked... So MIUI regurlaty kills it, and sometimes, it even loses the accessibility autorisation.
How can I know what's killing it ? Obviousily, I'm not in Eco mode, and this behaviour also occurs in performance mode. Everything worked very fine until last update.
Sirguda said:
Hello,
Not sure if it's the right place, but I'm getting depressed with my Xiaomi 12 behaviour. Since last update, MIUI global 13.2.4, the phone keeps killing apps, even if I set those with :
- not battery restriction
- auto startup
I tried a factory reset, I unlocked it, rooted it. It keeps killing apps. It's annoying, because I use Vivid and removed the navigation buttons. I let you imagine how I can be stuck sometimes when Vivid is killed. Yet, Vivid is locked... So MIUI regurlaty kills it, and sometimes, it even loses the accessibility autorisation.
How can I know what's killing it ? Obviousily, I'm not in Eco mode, and this behaviour also occurs in performance mode. Everything worked very fine until last update.
Click to expand...
Click to collapse
Maybe a bug in the rom which is a stable beta.
The ROM is official, it's been deployed in France last week.
Sirguda said:
The ROM is official, it's been deployed in France last week.
Click to expand...
Click to collapse
And so, Xiaomi has been deploying beta roms on stable channels for a long time.
Xiaomi 12 EEAStable BetaRecoveryV13.2.4.0.TLCEUXM13.04.8 GB2022-12-01
If it worked before this update, you have the answer.
NOSS8 said:
And so, Xiaomi has been deploying beta roms on stable channels for a long time.
Xiaomi 12 EEAStable BetaRecoveryV13.2.4.0.TLCEUXM13.04.8 GB2022-12-01
If it worked before this update, you have the answer.
Click to expand...
Click to collapse
OTA update for an entire country are with beta ? If so, this is a joke. How can I report this to Xiaomi ?
Sirguda said:
OTA update for an entire country are with beta ? If so, this is a joke. How can I report this to Xiaomi ?
Click to expand...
Click to collapse
You are not the only one to have had problems following updates, the solution if it worked before, is to flash the previous rom or to use a Xiaomi EU rom.
Sometimes Xiaomi renames a Stable Beta to stable without fixing anything.
NOSS8 said:
You are not the only one to have had problems following updates, the solution if it worked before, is to flash the previous rom or to use a Xiaomi EU rom.
Sometimes Xiaomi renames a Stable Beta to stable without fixing anything.
Click to expand...
Click to collapse
Previous ROM is in Android 12. Downgrading won't be a problem ? Keeps root ? EU Roms seem far behind.
Sirguda said:
Previous ROM is in Android 12. Downgrading won't be a problem ? Keeps root ?
Click to expand...
Click to collapse
Downgrading requires a clean flash and the root is lost along with your data.
Use this tool:
https://forum.xda-developers.com/t/flash-tool-guide-use-xiaomi-flash-tool.4262425/
And disable the update.
EDIT:
I use a Xiaomi EU rom on my 12 pro and I have several apps that must remain in the background, works very well.
With a Xiaomi EU rom you will have the certified play store without root and lots of extra options.
This is happening to me also and many other people. Fun times waking up to find that your alarm clock hasn't gone off because it was killed in the background.
There doesn't seem to be a workaround yet. There's several posts on the mi.com forums regarding it:
Xiaomi Community
new.c.mi.com
People there have discussed making a bug report via the feedback app (Settings->"Services & Feedback") might garner some support for Xiaomi to fix the issue... one can only hope.
All I can say is if you're thing of updating to V13.2.4.0.TLCEUXM OTA then DONT! Teach me to apply an update without checking on it first.
bunklebeard said:
This is happening to me also and many other people. Fun times waking up to find that your alarm clock hasn't gone off because it was killed in the background.
There doesn't seem to be a workaround yet. There's several posts on the mi.com forums regarding it:
Xiaomi Community
new.c.mi.com
People there have discussed making a bug report via the feedback app (Settings->"Services & Feedback") might garner some support for Xiaomi to fix the issue... one can only hope.
All I can say is if you're thing of updating to V13.2.4.0.TLCEUXM OTA then DONT! Teach me to apply an update without checking on it first.
Click to expand...
Click to collapse
Go to this site if you need anything, the updates with beta roms on the stable channel do not date from today, many threads on this subject have been created without change since today the problem persists.
Reporting bugs via Services & Feedback hasn't changed anything either.
Note that since the redesign of their site, important threads have disappeared and even some devices.
As a reminder, it is the moderators of this site who report information, well that's just theory because in practice, nothing happens.
If you want answers from Xiaomi, tell them you want to buy a new phone because that's what they're interested in, selling.
I tell you this because at a certain time, I was active on this site, but some of my posts were deleted because I explained how to solve or work around the problem.
Sometimes by checking the hash of a beta rom and the following stable, it was the same.
The solution is to unlock the bootloader and downgrade or install a Xiaomi EU rom.
bunklebeard said:
This is happening to me also and many other people. Fun times waking up to find that your alarm clock hasn't gone off because it was killed in the background.
There doesn't seem to be a workaround yet. There's several posts on the mi.com forums regarding it:
Xiaomi Community
new.c.mi.com
People there have discussed making a bug report via the feedback app (Settings->"Services & Feedback") might garner some support for Xiaomi to fix the issue... one can only hope.
All I can say is if you're thing of updating to V13.2.4.0.TLCEUXM OTA then DONT! Teach me to apply an update without checking on it first.
Click to expand...
Click to collapse
I'm kind of relieved that's I'm not the only one with this issue. For sure I dont take a xiaomi anymore. I had doubt about MIUI, and gesture unavailable with 3rd party launcher + this killing app bug, makes me regret not have taken a Samsung S22.
" I had doubt about MIUI, and gesture una aimable with 3rd party launcher"
Xiaomi blocks this function with third-party apps (not new).
NOSS8 said:
" I had doubt about MIUI, and gesture una aimable with 3rd party launcher"
Xiaomi blocks this function with third-party apps (not new).
Click to expand...
Click to collapse
Not new, but it's a detail you have trouble knowing before buying. With Vivid Gesture, I was plainly satisfied, but this new bug is really frustrating.
Regarding "Xiaomi EU rom", how well tested is it? Do they have an issue tracker and a list of known bugs?
I've rooted and flashed community ROMs in the past only to find out they are poorly tested / have horrible QA and although superficially they work fine other aspects didn't like Bluetooth, Android Auto or certain camera modes etc.
It has been a while though since I last attempted one, maybe things have moved on since then?
Xiaomi has removed so much of the Google framework that even push notifications isn't working. Take note that the Global ROM is based on the CN variant which is known for aggressive background killing of apps.
In Xiaomi's defense, they are "freeing up" up to 800mb of your internal storage by removing most of Google's API but in the expense of all the issues encountered by Global ROM users.
So if anyone is interested, I'm trying to see if disabling com.miui.powerkeeper works round this issue of background apps being killed in V13.2.4.0.TLCEUXM .
I followed this tutorial:
How to disable any pre-installed system app bloatware on Android without root
If you hate the bloatware or pre-installed apps on your Android smartphone, here's how to disable them even if Android doesn't normally let you.
www.xda-developers.com
Will report back if I notice any improvement.
Maybe someone more knowledgable might be able to tell me if there are any downside to disabling this package?
I am suffering the exact same problem with my device since the 13.2.4 update, what i nightmare to use the device since then ! As the other users already reported, it s even killing the alarm app which prevents it to ring ! But it also impacts all app notifications, like whatsapp, outlook, etc. After being killed I don't get the new notifications for those.
I can't believe that they are pushing such an update globally, they are gonna lose a lot of customers which such a poor strategy, as this is not just a "little" bug.
I am interested in the Xiaomi.EU rom, looks like they released one 2 days ago with version number 13.2.6, but I have to investigate if we can install that over our official version on an original EU device, and if it requires a full data wipe or not.
kalhimeo said:
I am suffering the exact same problem with my device since the 13.2.4 update, what i nightmare to use the device since then ! As the other users already reported, it s even killing the alarm app which prevents it to ring ! But it also impacts all app notifications, like whatsapp, outlook, etc. After being killed I don't get the new notifications for those.
I can't believe that they are pushing such an update globally, they are gonna lose a lot of customers which such a poor strategy, as this is not just a "little" bug.
I am interested in the Xiaomi.EU rom, looks like they released one 2 days ago with version number 13.2.6, but I have to investigate if we can install that over our official version on an original EU device, and if it requires a full data wipe or not.
Click to expand...
Click to collapse
Welcome to XIAOMI.
You can check below the version of the rom proposed for the update, before performing it.
https://xiaomifirmwareupdater.com/archive/miui/cupid/
EDIT:
You can either update the rom with the update.bat file included in the Fastboot.zip folder but since it is an A13 version, it is preferable to format the data with the first install.bat file .
Obviously the bootloader must be unlocked.
Also remove the security from the lock screen and restart the system.
Hello. I have exactly the same problem. I just bought the phone, after a week I got that update and it made me completely regret that I bought it. Is there any "clean" way to return to the version of MIUI I bought the phone with?
Would a reset return me to the old version? Since i got almost nothing important in the phone, it wouldnt be a big deal.
zazajin said:
Hello. I have exactly the same problem. I just bought the phone, after a week I got that update and it made me completely regret that I bought it. Is there any "clean" way to return to the version of MIUI I bought the phone with?
Would a reset return me to the old version? Since i got almost nothing important in the phone, it wouldnt be a big deal.
Click to expand...
Click to collapse
Bootloader must be Unlocked.
https://forum.xda-developers.com/t/miui-keeps-killing-apps.4529641/post-87852189