Related
Hi,
Since i can't post in the thread, so I just highlight in here.
I've been using this rom for about a month. This rom is really nice but since the new update, it gets even better. Only one small thing, the LED flashlight widget in the quickpanel didn't show up although you have tick it in the settings.
That's all. I hope someone could tell this to Spizzy01 so that he can fix this.
Thanks...
matfai said:
Hi,
Since i can't post in the thread, so I just highlight in here.
I've been using this rom for about a month. This rom is really nice but since the new update, it gets even better. Only one small thing, the LED flashlight widget in the quickpanel didn't show up although you have tick it in the settings.
That's all. I hope someone could tell this to Spizzy01 so that he can fix this.
Thanks...
Click to expand...
Click to collapse
Most probably Spizzy01 has removed the flashlight because there is a bug with camera !!
Really?? Well, I didn't know that....
Thanks for a fast reply...
Swipe to move switch icons? No, havent listened...
Aurora Play Problems
Hello,
I just installed Aurora Play 1.1.0 and I am having problems which I think might be related to superuser.
The Rom works fine, but anything that requires root access gets frozen in place. My phone is rooted, I am pretty sure of it - not only the bootloader is unlocked but also, I did manage to initially change the clock speed to 1.4 ghz, and that change has remained so far.
However, if, for example, I try enabling root access on the ES File Explorer, it simply freezes the app (sort of like it is waiting for the confirmation from Superuser, but it never comes). I only ever saw the superuser authorization screen once when I changed the clock at first.
I am pretty sure the OC is not the problem, since I reinstalled the rom and did no OC on the 1st time at all, but the same problem persisted.
I would try uninstalling SU and installing that other superuser app on the market to see if that would solve the problem, but I couldn't manage to uninstall it.
Any thoughts on this? I would love to solve this problem since this room is outstanding on all other accounts.
PS.: I followed all instructions to the letter, and like I said I tried reinstalling the rom already. I am using Lupus v10 (tried Lupus v11 before on the 1st installation).
Fenrir007 said:
Hello,
I just installed Aurora Play 1.1.0 and I am having problems which I think might be related to superuser.
The Rom works fine, but anything that requires root access gets frozen in place. My phone is rooted, I am pretty sure of it - not only the bootloader is unlocked but also, I did manage to initially change the clock speed to 1.4 ghz, and that change has remained so far.
However, if, for example, I try enabling root access on the ES File Explorer, it simply freezes the app (sort of like it is waiting for the confirmation from Superuser, but it never comes). I only ever saw the superuser authorization screen once when I changed the clock at first.
I am pretty sure the OC is not the problem, since I reinstalled the rom and did no OC on the 1st time at all, but the same problem persisted.
I would try uninstalling SU and installing that other superuser app on the market to see if that would solve the problem, but I couldn't manage to uninstall it.
Any thoughts on this? I would love to solve this problem since this room is outstanding on all other accounts.
PS.: I followed all instructions to the letter, and like I said I tried reinstalling the rom already. I am using Lupus v10 (tried Lupus v11 before on the 1st installation).
Click to expand...
Click to collapse
Please try downloading the following ZIP and flashing it VIA clockwork mod.
Let me know the results.
http://forum.xda-developers.com/attachment.php?attachmentid=1890140&d=1366191665
Spizzy01 said:
Please try downloading the following ZIP and flashing it VIA clockwork mod.
Let me know the results.
http://forum.xda-developers.com/attachment.php?attachmentid=1890140&d=1366191665
Click to expand...
Click to collapse
Can CWM coexist with TWRP? I think I only have TWRP installed. Or can I just use TWRP instead?
missing pixels in landscape app drawer
Spizzy, first and foremost congratulations on this great rom, it is fantastic! The only gripe I'm having is that when the app drawer is in Landscape mode it is cutting some pixels on the bottom (can't see the lower end of the blue highlight when using the ps controls). Other than that, all is perfect so far.
It worked!
Thanks a lot, Spizzy! Whatever that package was, it worked great and now superuser is not giving me any headaches anymore. Everything works great and the rom is blazing fast!
Just one thing - when I checked the info that comes up on the pachage before installing it, it said it was for locked bootloaders, but I assume that was a typo (since the zip file is for unlocked, and mine is unlocked as well). Just mentioning since it could maybe cause a little confusion on people downloading it in the future.
Oh and I did use TWRP in the end - I guess it's the same thing.
AR Effect not working after .101 update. Only circles show up and the effect just rotates then vanishes.
Does anyone have the same issues.
What is DID! cleared data, uninstall, reinstalled no solution. same problem.
session20 said:
AR Effect not working after .101 update. Only circles show up and the effect just rotates then vanishes.
Does anyone have the same issues.
What is DID! cleared data, uninstall, reinstalled no solution. same problem.
Click to expand...
Click to collapse
Same here. But I never saw it working so I just thought it was too hard to use or it was buggy.
DoubleYouPee said:
Same here. But I never saw it working so I just thought it was too hard to use or it was buggy.
Click to expand...
Click to collapse
It working good before the new update
DoubleYouPee said:
Same here. But I never saw it working so I just thought it was too hard to use or it was buggy.
Click to expand...
Click to collapse
session20 said:
AR Effect not working after .101 update. Only circles show up and the effect just rotates then vanishes.
Does anyone have the same issues.
What is DID! cleared data, uninstall, reinstalled no solution. same problem.
Click to expand...
Click to collapse
clear data ...reboot and try again .. that worked for me .. if still not then try to re-calibrate gyro settings from service menu .
Edit: Spoke too soon. After rebooting my phone hours later the camera no longer starts. May or may not be related to what I did below.
Edi2: Well I tried clearing data, removing this new AR Effect, restoring the old one, rebooting dozens of times, did a factory reset. Camera just refused to work. I just spend my morning doing a complete firmware restore and re rooting again. Now this issue could have been unrelated to the steps below, reader beware. In case it matters, I was running a D5503 with 14.2.A.1.144 firmware, rooted, locked bootloader.
------------------------------------------------
I had this issue, where AR effect would only show the light flashes but nothing ever appeared. I resolved this on my device by following these steps.
Skej13 said:
Everything works perfectly. However, there is one BUT
Follow the instructions
1. Delete (your) old AR Effect in system\app - or save in sdcard.
2. Use CleanMaster https://play.google.com/store/apps/details?id=com.cleanmaster.mguard&hl=ru from delete [email protected] (remnants of applications)
3. Maybe not to do, but I advise you to do. Use SD Maid https://play.google.com/store/apps/details?id=eu.thedarken.sdm&hl=ru
Delete lost lib AR effect. Section system or debris.
Click to expand...
Click to collapse
Basically I uninstalled AR Effect then used a root file browser to delete AR effect from the /system/app folder.
I then got AR Effect from here.
Ben Ling said:
Inside The Zip Includes AR Effect 3.0.27, Celebration, Comic, Butterfly, Funky Disco, Horror & Spider-Man Effects
AR Effect Camera Apps For JB 4.3 (79.24 MB)
AR Effect Camera Apps For JB 4.1.2 & 4.2.2 (78.92 MB)
Click to expand...
Click to collapse
Unzipped it, moved to device, installed the apks. Then used Titanium Backup to move AR Effect to system folder. Rebooted and AR effect is working great.
Hi, new to the forum, I tired to figure out this problem on youtube to no avail. So I have a rooted g3 with twrp. After the botting process, it takes me to the setup screen. But after getting to the point where I pick the look of the onscreen home buttons etc, the wizard crashes, I press 'OK" and it starts over. So then I found a link here about going into twrp and deleting the setupwizard.apk file which is supposed to 'fix" the problem(http://forum.xda-developers.com/showthread.php?t=2668851). Did that then I rebooted but still same issue remains. What else can be done about this?
Can't you just skip it and do it manually
Dez730 said:
Hi, new to the forum, I tired to figure out this problem on youtube to no avail. So I have a rooted g3 with twrp. After the botting process, it takes me to the setup screen. But after getting to the point where I pick the look of the onscreen home buttons etc, the wizard crashes, I press 'OK" and it starts over. So then I found a link here about going into twrp and deleting the setupwizard.apk file which is supposed to 'fix" the problem(http://forum.xda-developers.com/showthread.php?t=2668851). Did that then I rebooted but still same issue remains. What else can be done about this?
Click to expand...
Click to collapse
I had the same issue when flashing "Lonely Rom" and "Zone Rom" (come to find out my original out of the box rom crashed also if I went back into it and tried to do the set up again). 2 apks need to be deleted (4 if still odexed) LgStartUpWizard in system app folder and LgSetupWizard in priv-app folder. I edited my zip before flashing with all the updated Google equivalents plus some other stuff I normally do. The Google set up process worked like a charm and everything is running better than stock (better battery life and no noticeable lags) even though it's a "stock rom", I also run Xposed with several modules for my needs with no adverse effects here.
zoman7663 said:
I had the same issue when flashing "Lonely Rom" and "Zone Rom" (come to find out my original out of the box rom crashed also if I went back into it and tried to do the set up again). 2 apks need to be deleted (4 if still odexed) LgStartUpWizard in system app folder and LgSetupWizard in priv-app folder. I edited my zip before flashing with all the updated Google equivalents plus some other stuff I normally do. The Google set up process worked like a charm and everything is running better than stock (better battery life and no noticeable lags) even though it's a "stock rom", I also run Xposed with several modules for my needs with no adverse effects here.
Click to expand...
Click to collapse
Thanks man, lol but I unrooted back to stock an hour ago. But now I'll know what to do when I root again & have the same issue pop up
BACARDILIMON said:
Can't you just skip it and do it manually
Click to expand...
Click to collapse
Nah, the step I got to there was a 'next' or 'back'.
Similar Issue
Dez730 said:
Hi, new to the forum, I tired to figure out this problem on youtube to no avail. So I have a rooted g3 with twrp. After the botting process, it takes me to the setup screen. But after getting to the point where I pick the look of the onscreen home buttons etc, the wizard crashes, I press 'OK" and it starts over. So then I found a link here about going into twrp and deleting the setupwizard.apk file which is supposed to 'fix" the problem(http://forum.xda-developers.com/showthread.php?t=2668851). Did that then I rebooted but still same issue remains. What else can be done about this?
Click to expand...
Click to collapse
Hello,
I am new to the site, and fairly inexperienced with rooting. I used KingRoot to root my LG G3 and then did a factory reset so that I could re update to the current android version before rooting. Now I get stuck at the same point in the setup process. However, I do not have TWRP or CWM installed. What are my options?
Thanks
I'm having an issue on my SPH-L710 where the back camera works in all cases, but the front camera is laggy and stutters, and has a skewed / stretched aspect ratio in all applications except the camera app itself. That is, the front camera works as expected, fast and looks normal in the stock camera app or the google camera app, but when it is embedded in another such as facebook, snapchat, etc., it exhibits the problems above.
This is not a problem on ND8 (4.4) stock, but has happened on all the custom roms I have tried in the list below :
Slim-d2lte-4.4.4.build.7.0-OFFICIAL-5979
Slim-d2lte-4.4.4.build.7.2.1-WEEKLY-6080
cm-11-20140814-NIGHTLY-d2lte
cm-11-20140805-SNAPSHOT-M9-d2lte
BeanStalk-4.4.4010-20140722-d2lte
Quantum.4
I do a factory wipe and erase the cache every time. I have tried force closing the camera and gallery apps and clearing their data. None of these solutions have worked. What roms are other people using that don't have this issue? If the issue is this widespread, I would think there would be more posts regarding it.
I just tested the front camera on Facebook and another app. I was not able to replicate the problem and experienced no issues with the front camera preview.
Tested and working on CM11 20140812 Nightly w/ stock kernel and just finished testing with DKP kernel.
It could be hardware related if you are not seeing this as a common issue in forums.
Higgs_Boson said:
I just tested the front camera on Facebook and another app. I was not able to replicate the problem and experienced no issues with the front camera preview.
Tested and working on CM11 20140812 Nightly w/ stock kernel and just finished testing with DKP kernel.
It could be hardware related if you are not seeing this as a common issue in forums.
Click to expand...
Click to collapse
Can't see it being hardware related if the camera works just fine in the stock camera. I'll install that nightly and see how it works.
tulient said:
Can't see it being hardware related if the camera works just fine in the stock camera. I'll install that nightly and see how it works.
Click to expand...
Click to collapse
Right. You did mention that detail. Hope another nightly works for you.
Just tested cm-11-20140812-NIGHTLY-d2lte and I am having the same issue. No idea what could be wrong. Are you sure its not skewed in any way on the front camera?
I wiped and installed the nightly and gapps-kk-20140606-signed, went straight to google play, installed messenger, and tested the camera. No funny business, and it doesn't display correctly.
tulient said:
Just tested cm-11-20140812-NIGHTLY-d2lte and I am having the same issue. No idea what could be wrong. Are you sure its not skewed in any way on the front camera?
I wiped and installed the nightly and gapps-kk-20140606-signed, went straight to google play, installed messenger, and tested the camera. No funny business, and it doesn't display correctly.
Click to expand...
Click to collapse
I am 100% sure there is no skewing, distortion, stretching etc. on apps accessing the front camera outside of the stock camera app.
The only difference between our setup is that I use this GAPPs package:
pa_gapps-stock-4.4.4-20140629-signed
I also use the DKP kernel, as I mentioned before. But, as I also reported, stock kernel worked fine for me, too.
No luck even with GAPPS pa_gapps-stock-4.4.4-20140629-signed with and without the DKP kernel dkp-aosp44-d2-20140726.
tulient said:
No luck even with GAPPS pa_gapps-stock-4.4.4-20140629-signed with and without the DKP kernel dkp-aosp44-d2-20140726.
Click to expand...
Click to collapse
I was reading around a bit more on the Internet. Have you tried going into the Google Camera app settings when you launch the camera from one of the apps in questions and changing the resolution? I read on a few sites that this might fix the stretch issue. I'll keep digging around.
I don't suspect that it's a code issue, since mine is working normally. Do you have more than one camera app installed that is possibly tweaking the resolution? Just a thought.
I have tried to change the picture size from 1:1 to 4:3 of the front facing camera in the camera app, as well as change the resolution from 1.9 to 1.3, but neither change is reflected in the facebook messenger camera. I also tried using no GAPPS and installing the facebook messenger APK only after a fresh install, and still have the problem, so it's not a separate app causing the issue. Are you sure you're using a SPH-L710?
I'm assuming the problem is in whatever base all these custom roms are built on, but since it's working for you, I have no idea.
For the record, I am installing CM11 with recovery CWM-6045_touch_d2spr_naddict and the other roms philz_touch_6.48.4-d2lte only because CM11 wont install with philz due to assert failures.
tulient said:
I have tried to change the picture size from 1:1 to 4:3 of the front facing camera in the camera app, as well as change the resolution from 1.9 to 1.3, but neither change is reflected in the facebook messenger camera. I also tried using no GAPPS and installing the facebook messenger APK only after a fresh install, and still have the problem, so it's not a separate app causing the issue. Are you sure you're using a SPH-L710?
I'm assuming the problem is in whatever base all these custom roms are built on, but since it's working for you, I have no idea.
For the record, I am installing CM11 with recovery CWM-6045_touch_d2spr_naddict and the other roms philz_touch_6.48.4-d2lte only because CM11 wont install with philz due to assert failures.
Click to expand...
Click to collapse
Yes. I have a SPH-L710. I encourage you to ensure that you are using the correct and most current version of Philz recovery for our device, as I am able to successfully install CM11 using Philz.
Please download and try the latest Philz recovery here, and try wiping and reflashing the ROM and GAPPs.
PhilZ Download Link:
https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/
(Came from this thread: http://forum.xda-developers.com/showthread.php?t=2446393&page=56)
The following procedure fixed the front facing camera 3rd party apps for me, but in turn now the camera app itself is broken. Still trying to figure this out.
Flash philz_touch_6.48.4-d2lte.tar.md5 with Odin 3.09
Flash ROM Slim-d2lte-4.4.4.build.7.2.1-WEEKLY-6080
Flash GAPPS pa_gapps-stock-4.4.4-20140629-signed
Ensure root (apps) is enabled on ROM (slimkat defaults to disabled)
1. Enable Developer Options - Click Settings / About Phone / Build number 5 times
2. Enable root (Apps only) - Developer Options / Debugging / Root Access
Install root browser (jrummy)
Install facebook messenger
Verify camera does NOT display correctly in facebook messenger
Using root browser, delete system/lib/hw/camera.MSM8960.so (Give root browser permission to superuser when prompted)
Using root browser, rename system/lib/hw/camera.vendor.MSM8960.so to system/lib/hw/camera.MSM8960.so
Verify camera still does NOT display correctly in facebook messenger
Reboot (Reboot necessary? Camera saved in memory?)
Verify camera does display correctly in facebook messenger
tulient said:
The following procedure fixed the front facing camera 3rd party apps for me, but in turn now the camera app itself is broken. Still trying to figure this out.
Flash philz_touch_6.48.4-d2lte.tar.md5 with Odin 3.09
Flash ROM Slim-d2lte-4.4.4.build.7.2.1-WEEKLY-6080
Flash GAPPS pa_gapps-stock-4.4.4-20140629-signed
Ensure root (apps) is enabled on ROM (slimkat defaults to disabled)
1. Enable Developer Options - Click Settings / About Phone / Build number 5 times
2. Enable root (Apps only) - Developer Options / Debugging / Root Access
Install root browser (jrummy)
Install facebook messenger
Verify camera does NOT display correctly in facebook messenger
Using root browser, delete system/lib/hw/camera.MSM8960.so (Give root browser permission to superuser when prompted)
Using root browser, rename system/lib/hw/camera.vendor.MSM8960.so to system/lib/hw/camera.MSM8960.so
Verify camera still does NOT display correctly in facebook messenger
Reboot (Reboot necessary? Camera saved in memory?)
Verify camera does display correctly in facebook messenger
Click to expand...
Click to collapse
All you did there was delete and rename a camera library, which are stored in the kernel, and that I perceive to be the reason the camera broke.
Are you savvy on ADB?
I think at this point the best thing for your to do would be to:
Flash ROM Slim-d2lte-4.4.4.build.7.2.1-WEEKLY-6080
Flash GAPPS pa_gapps-stock-4.4.4-20140629-signed
Get everything back up to a freshly flashed ROM with GAPPs, then:
1. Enable Developer Options
2. In Developer Options, enable USB debugging
3. Connect phone to USB port on PC
4. Launch ADB
5. Input command: adb devices (to ensure the device has been detected by adb)
6. Input command: adb logcat
7. Launch and switch to front camera in 3rd-party app
8. Disconnect USB cable
9. Copy and paste text from ADB terminal into a Notepad document. Save document (e.g. logcat.txt).
10. Upload Notepad document as attachment (.txt file) to this thread on XDA.
Yes, well by deleting the one camera library and replacing it with the camera.vendor, everything works exactly as it should in the 3rd party application. Its just when using the stock camera app where it doesnt work now - essentially making the opposite situation I started with. FYI with the fix the stock camera looks fine and can take a picture but usually closes and forces a reboot right away.
Here is the logcat for opening messenger, opening the camera option and snapping a (stretched) picture.
It seems I've been summoned.
I didn't see a whole lot in the logcat (or rather, the camera spews so much debug info that nothing stood out). So far, I'm able to reproduce the stretched preview thing but not the lag. I think the lag probably depends on the app, so I'll try a few more.
I think I know what's causing the stretching, but I won't know for sure until I get a ROM built.
EDIT: My changes didn't help any.
decimalman said:
It seems I've been summoned.
I didn't see a whole lot in the logcat (or rather, the camera spews so much debug info that nothing stood out). So far, I'm able to reproduce the stretched preview thing but not the lag. I think the lag probably depends on the app, so I'll try a few more.
I think I know what's causing the stretching, but I won't know for sure until I get a ROM built.
Click to expand...
Click to collapse
Sir, your presence here is most appreciated. Thank you.
decimalman said:
It seems I've been summoned.
I didn't see a whole lot in the logcat (or rather, the camera spews so much debug info that nothing stood out). So far, I'm able to reproduce the stretched preview thing but not the lag. I think the lag probably depends on the app, so I'll try a few more.
I think I know what's causing the stretching, but I won't know for sure until I get a ROM built.
EDIT: My changes didn't help any.
Click to expand...
Click to collapse
Thank you tremendously for trying!
Any idea why it would only be affecting his phone in other apps?
Guessing there's no solution to this until someone in the CM main trunk figures it out.
Hi there,
First off I would like to thank AngSanley for his work on the 4.4.4 CM 11 ROM, absolutely excellent development and keep up the good work. Hopefully I thought I would make a bug report here since i still can't post in the X development section:
1. Phone.apk problems:
a. Operator and Caller names coincide with each other (Issue was mentioned before in the thread however still looking forward to hearing from @AngSanley for a reply)
b. Repeated Missing Calls crash the com.android.phone process and the only solution is to call the missing call to get the phone app running again. To emulate that leave the call until it ends twice and see what happens
2. System Processes
In Jelly Bean and Ice Cream Sandwich you were able to disable system stock apps such as Browser, email, messages and it was possible to install the playstore apps as a replacement. I was wondering if it's still possible to enable that in the current ROM or it's not a bug as of the new releases.
Note: This also includes Trebuchet since I'm not currently using it.
3. Reboots in some cases disables the home button action in UDNB and prevents the lockscreen process from running properly which requires me to reinstall the ROM and Gapps while clearing cache and Delvik or by force stop and enabling lockscreen (which gets me to problem 2 sometimes).
Thank you again for the ROM and looking forward to hearing about upcoming updates with the ROM.
For the first issue, the problem is known. I mentioned it but it's difficult to fix.
For the third issue though, I found a solution. I disabled UDNB and installed Soft Buttons app. If the buttons crash, I disable them from the app and immediately enable them again. I reboot and... that's all!
(as for the second, I use some stock apps, so I can't tell you for sure)
Sent from Tapatalk via Nokia X
For the first issue, the problem is known. I mentioned it but it's difficult to fix.
Click to expand...
Click to collapse
Hopefully it gets addressed because it makes the phone literally unusable. The current list by AngSanley doesn't show it so I hope it's addressed to him.
For the third issue though, I found a solution. I disabled UDNB and installed Soft Buttons app. If the buttons crash, I disable them from the app and immediately enable them again. I reboot and... that's all!
Click to expand...
Click to collapse
Any specific app on the playstore because there are many apps for it
(as for the second, I use some stock apps, so I can't tell you for sure)
Click to expand...
Click to collapse
No problem it's fine. The imitation of it can be made if you even disable messages for example. It shows immediately that the phone loses functionality especially in the lockscreen process.
I'm really looking forward to hearing from @AngSanley on these. Especially on the phone process issue .
ElementalXY said:
Any specific app on the playstore because there are many apps for it
Click to expand...
Click to collapse
Couldn't attach it from Tapatalk. Here you are!
(Note that you MUST disable UDNB from Settings > Apps first, because the phone will show you 2 navbars!)
plankton69 said:
Couldn't attach it from Tapatalk. Here you are!
(Note that you MUST disable UDNB from Settings > Apps first, because the phone will show you 2 navbars!)
Click to expand...
Click to collapse
Thank you very much . It's working well and even better than UNDB!
PS: I can now post in the development section so is it possible to repost it over there instead or wait for AngSanley?
Yea bro....ur all mentioned bugs are also happend with the me... and there is also a big problem.... this bug happed with me two times and i need to wipe dalvik cacke two times....
so that problem is when i install xpossed app n when i restart than the statusbar gone.. it says com.androd.systemui.apk stopped... plz find way to fix it without wipe dalcik cacke
n second problem is whn i install any new theme n appy n restart my phone than same happens.... please do something brohers... love this rom ... really awsm..
Yea bro....ur all mentioned bugs are also happend with the me...
Click to expand...
Click to collapse
Does the phone crash happen with you too in missed calls? If not then I honestly think I should wipe the phone haha.
yes... i also get that error phone procced stopped.... but i pressed ok button 4 5 times and its stopped... but if i donwload any cm theme and after appy it when i restart mob the process of sytemui stopped than i need to to wipe data that time tht ok button not working.. please find any trick repair it without formating data..
ElementalXY said:
Does the phone crash happen with you too in missed calls? If not then I honestly think I should wipe the phone haha.
Click to expand...
Click to collapse
You should. Do a full wipe before flashing CM11.
Dom3616 said:
You should. Do a full wipe before flashing CM11.
Click to expand...
Click to collapse
Unfortunately I won't be able to do that since I just bricked my phone while formatting to the original stock version lol. I'm currently stuck on Nokia Emergency Connectivity and will be sending it to the Nokia care center next month haha. I'll be doing a fresh install when I get it back.
PS: I'm guessing no solutions for this problem outside the warranty am I right?
ElementalXY said:
Unfortunately I won't be able to do that since I just bricked my phone while formatting to the original stock version lol. I'm currently stuck on Nokia Emergency Connectivity and will be sending it to the Nokia care center next month haha. I'll be doing a fresh install when I get it back.
PS: I'm guessing no solutions for this problem outside the warranty am I right?
Click to expand...
Click to collapse
Yes you are right.