I can't seem to get the camera light to work at all with AllianceROM build 1. It won't flash in the camera app, and I've tried 3 different flashlight/torch apps and it none of them will light it. Any ideas?
Update
GuitarAudiologist said:
I can't seem to get the camera light to work at all with AllianceROM build 1. It won't flash in the camera app, and I've tried 3 different flashlight/torch apps and it none of them will light it. Any ideas?
Click to expand...
Click to collapse
It suddenly works again. I'm not sure what happened, but I restarted the phone a few times, booted to the stock ROM, and then booted AllianceROM again and now it works (for now). Possible bug?
GuitarAudiologist said:
It suddenly works again. I'm not sure what happened, but I restarted the phone a few times, booted to the stock ROM, and then booted AllianceROM again and now it works (for now). Possible bug?
Click to expand...
Click to collapse
There are many reported issues with rom slots in Safestrap. It is always recommended to flash on the stock slot. If you insist on running multiple roms I'd advice keeping your daily rom on the stock slot for the battery performance alone.
kinstre11 said:
There are many reported issues with rom slots in Safestrap. It is always recommended to flash on the stock slot. If you insist on running multiple roms I'd advice keeping your daily rom on the stock slot for the battery performance alone.
Click to expand...
Click to collapse
Thanks for the advice. I'm still scratching my head on this one though, as AllianceROM is currently in the stock slot.
I'm going to try out Jasmine ROM v1.8. Flashing it to the stock slot now (did a nandroid backup of AllianceROM and moved it to a ROM slot.) Maybe Jasmine ROM will be less quirky.
GuitarAudiologist said:
I'm going to try out Jasmine ROM v1.8. Flashing it to the stock slot now (did a nandroid backup of AllianceROM and moved it to a ROM slot.) Maybe Jasmine ROM will be less quirky.
Click to expand...
Click to collapse
There are some quirks to every rom but multiple flashing can leave residual things behind that screw with what is currently running.
I do this everytime I flash a new rom. If you don't know about this already you'll be surprised just how much is left behind after wiping the slot the normal way. You should still do both wipes. However be aware that even doing both of these multiple times there will still be some residuals left over.
The other thing I can recommend (but not all the time, warnings are in the OP) is a Odin restore. This will completely wipe and reset everything, there should be no residuals.
Good luck on Jasmine.
Not sure on your particular problem, since you said you were in fact on stock slot. But a few comments just in case it helps. I had problems with every single rom that I did NOT put on a freshly wiped stock slot. Any other slot always created problems. I also ran into many various issues when reinstalling my titanium backups. So the last install of Alliance that I made (the current rom that I'm using now, for the last couple of months), I kept it to a very minimum. I used titanium to reload my texts and maybe a few game apps (data only), that was all. I always use google to restore my contacts, emails, etc. And my pictures, ringtones, etc are always stored on my sd card. I know allot of people rely heavily on backups, but I usually have more problems than what its worth. Hell, up until the last couple of roms, I never even made backups. If I bricked a phone, I just wiped and started all over. And the same every time I switched roms. The only thing I lost was old texts and my progress on solitaire scores, lol.
As far as your specific problem. The only thing I would suggest is try thinking of any sort of settings or apps that might link the flashlight or torch feature with the camera. I don't use any other apps, but I know there are allot of alternative torch apps, and also ones that use the camera, like instagram, etc. The only experience I have with any related error is if I try to open the camera while the torch is on, it force closes the camera. Turn off the torch, reopen the camera, all is back to normal. I'm using the stock camera, and stock torch app...
Related
Hi!
I put my MAGLDR on my HD2 and tried tytungs ICS ROM, was not happy with the performance, went back to Boxmax GB Sense build, but after restoring data+apps the phone will start rebooting every few minutes.
I boot andorid from the SD card, so I tried a few versions of the ROM, v8.5 and v7 ([BoxmaX.S3.5.v8.5][Runny HTC Sensation XL][Kmarc2.1 + KTytung r14]).
Same result, sooner or later it'll start rebooting.
The weird thing is that I got another HD2 which is set up identically (magldr+BoxmaX.S3.5.v7) and is working perfectly for months.
I'd appreciate if someone could give me a few ideas on how to debug this?
kosmarnik said:
Hi!
I put my MAGLDR on my HD2 and tried tytungs ICS ROM, was not happy with the performance, went back to Boxmax GB Sense build, but after restoring data+apps the phone will start rebooting every few minutes.
I boot andorid from the SD card, so I tried a few versions of the ROM, v8.5 and v7 ([BoxmaX.S3.5.v8.5][Runny HTC Sensation XL][Kmarc2.1 + KTytung r14]).
Same result, sooner or later it'll start rebooting.
The weird thing is that I got another HD2 which is set up identically (magldr+BoxmaX.S3.5.v7) and is working perfectly for months.
I'd appreciate if someone could give me a few ideas on how to debug this?
Click to expand...
Click to collapse
When it reboots, is it when you're heavily using the phone? Do you feel the back of the phone getting warm before it reboots? Do other SD ROMs work perfectly? Logically since another HD2 with the exact same setup works fine, I would assume that it's something to do with hardware but I don't really know why something like this would happen so suddenly (assuming it worked fine before you changed the ROM)
Nigeldg said:
When it reboots, is it when you're heavily using the phone? Do you feel the back of the phone getting warm before it reboots? Do other SD ROMs work perfectly? Logically since another HD2 with the exact same setup works fine, I would assume that it's something to do with hardware but I don't really know why something like this would happen so suddenly (assuming it worked fine before you changed the ROM)
Click to expand...
Click to collapse
Ah, some more info: Phone was working perfectly with wm6.5+haret, and with magldr+ICS (albeit with ICS bugs) but no reboots ever though it was always overclocked.
As to reboots, they happen for no reason, even when on stock frequency. I don't even have to use the phone, it'll be sitting there sleeping and I just hear the boot up sound.
And here we go: swapped the sd and sim cards, and it is rebooting even in the other HD2, so it's a software OR SD card problem.
I'll move my data to another SD card to exclude it from the equation, but I doubt it's the card.
Ok, so my procedure to setting up a rom is:
after the 1st boot, either log in in to google or not
install TB, restore apps+data
use MyBackup to get SMSes back
Only after or in the middle of that does the rebooting start happening, once it starts it's game over as I only get a minute or two before reboot.
My idea is that something I'm restoring is causing it, but have no clue what it could be.
My last backup was in ICS, but I have no clue how could that be a problem, apps are apps :|
I'm only backing up/restoring regularapps+data not any system stuff.
How could get to the logs from the data.img? Maybe they'll give me a clue about this?
kosmarnik said:
My idea is that something I'm restoring is causing it, but have no clue what it could be.
My last backup was in ICS, but I have no clue how could that be a problem, apps are apps :|
I'm only backing up apps+data not any system stuff.
Click to expand...
Click to collapse
Hmm, so if it reboots after you restore then perhaps you're right, it may be a problem with something you're restoring. Apps may be apps, but some apps are different for ICS and GB (e.g. YouTube, Launchers, Google Chrome etc.) so it's quite possible it may be causing a problem. Try doing the following:
Fresh install the SD build
Restore apps which you KNOW are the same on ICS and GB. This includes all games and many other apps.
For apps which you aren't sure about, download them for the play store.
Manually restore specific app data for the apps you downloaded
Hopefully, if the problem's to do with an app being restored, this will sort it out.
Nigeldg said:
Hmm, so if it reboots after you restore then perhaps you're right, it may be a problem with something you're restoring. Apps may be apps, but some apps are different for ICS and GB (e.g. YouTube, Launchers, Google Chrome etc.) so it's quite possible it may be causing a problem. Try doing the following:
Click to expand...
Click to collapse
Could be, but I only had ICS running for 10 day and did not install any new apps. I don't have any games
Fresh install the SD build
Click to expand...
Click to collapse
Done that ~10 times.
With different approaches. (Restoring more/less)
Tried both newest v8.5 and v7 (gf's [email protected] is running the v7).
Restore apps which you KNOW are the same on ICS and GB. This includes all games and many other apps.
For apps which you aren't sure about, download them for the play store.
Manually restore specific app data for the apps you downloaded
Hopefully, if the problem's to do with an app being restored, this will sort it out.
Click to expand...
Click to collapse
Yeah, I'll have to do that. I'll see if have the backups before ICS and just put the latest data.
What a chore
Tried another SD card, same happens, so at least I know it's 100% software fault.
How could I check the logs?
System Specs: Galaxy S4 Canadian i337m OTA 4.3 (jfltecan), carrier is Bell, stock Samsung firmware, stock kernel (use wicked rom 9.1 sometimes too)
WARNING:
lot's of reading so go grab a coffee and have a cigarette before you sit down to read this, you'll probly be here for awhile
The rom/fix in question: MDOB rom/i337m fix - here's a link to both.
http://forum.xda-developers.com/showthread.php?t=2280556
first off i'd like to mention this phone was 100% perfect on stock Samsung rom 4.2.2 using Ktoonsez KT-SGS4 kernel for many months, until the day I installed this dreaded MDOB 4.2.2 rom and the "fix" that came with it
everything went bad on me back while I was running 4.2.2 stock unlocked boot loader and could never get it back to normal so this isn't a issue caused by 4.3 knox or 4.3 itself that i'm currently using. (i'm stuck on 4.3 roms but had this issue way before 4.3 existed)
i'm having an extreme amount of issues AFTER installing the MDOB rom, even after changing rom back to stock (flashed back to stock rom with ktoonsez kernel which is what I was using before I installed MDOB rom and phone has been royaly screwed ever since that day) more specifically I think it happened from the "i337M fix" that's included with the rom, either way after installing this rom I've never been able to get my phone back to normal.
everything runs fine except until I install a custom kernel (Ktoonsez KT-SGS4 kernel) then all hell breaks loose.
I don't blame the kernels or my current rom since I've ran this before for many months until the day i installed MDOB rom on my phone my phone was a dream machine.
issues since this rom has been installed include:
Issues:
A. RANDOM SLEEPS OF DEATH (phone shuts off or freezes)
B. random freezing while trying to turn on phone or enter recovery
C. some kernels won't work proper (specifically ktoonsez KT-SGS4 kernel) example gpu stuck at max while idle and downclocking when screen is touched with this kernel
D. wifi won't work with custom kernel on stock 4.3 rom without build prop edit to ro.securestorage.support, although it should
E. weak wifi and mobile signals
F. bad battery life
G. bad call quality
H. More that I can't remember off the top of my head
here's my flashing process, in attempts to remove as much as possible:
I know a few of these steps are probly pointless but hey can't blame me for trying.
step 1. enable usb debugging & unknown sources
step 2. install root & recovery
step 3. fresh boot phone let files settle so they can save (5mins or more) then plug into computer while turned on and delete everything
step 4. reboot into TWRP recovery (version 2.6.3.1) and clear everything, full advanced wipe, factory reset, format data than clear cache/dalvik afterwards just to be sure
step 5. remove SD card plug into computer and format to make sure there's nothing
step 6. install rom
step 7. (sometimes) clear cache/dalvik/permissions after rom install, although fix permissions seems to break my permissions rather than fix them or maby my permissions just break during flashing and I just can't fix them (haven't tested enough to be 100% sure)
i'm SOOO temped to try a full nand erase since i noticed there ARE still lot's files on my phone directory even after wiping, but i know that isn't a good idea;(
once stock kernel is back on my phone these issues are all gone.
Ktoonsez says it's not his kernel (used to work before, so i have no reason not to believe him), he says it's the rom well i'm on 100% stock Samsung rom (exception of kernel) and the rom was built to act the way it does so you can't really blame the rom so who do i blame??
until i went to go try wicked rom and flash back to stock I didn't realize these things were still on here, but now they emerge! wicked rom was giving me some (unrealated?) issue so i decided ima go back to stock so i flashed stock rom via odin (pc) and right away i noticed the 4G symbol, Samsung wallet, desktop not setup proper (no shortcuts) this ONLY happens when switching from wicked rom to stock rom on the first flash, i flash again everything looks how it should, and in order to get it to do this again i have to flash back to wicked rom and flash stock rom again and BAM it happens.
i knew my issue started on the same day that i installed this MDOB rom but after doing a full wipe and MANY "fresh" stock rom installs later i stopped questioning the rom and just lived with a crap phone that reboots itself all the time and has bad battery life, AS SOON AS I SEEN THE SAMSUNG WALLET bam it hit me like a truck, IT WAS THE MDOB ROM INSTALL.
UNLESS stock Samsung rom comes with wallet preinstalled and hidden on stock/wicked roms than the ONLY other way it coulda got on my phone is from the MDOB rom.
I can wipe/delete/factory reset/flash with twrp & odin on pc all I want, my roms are still messed up after FRESH installs. I believe there is still left over files from this rom/fix, I didn't think there would be anything until I noticed when i'm flashing from wicked rom back to complete stock rom using odin on pc I experience things from MDOB rom (while It should be 100% stock after odin (pc) flash, but it's not)
after the first flash from going from wicked rom back to stock I always experience the following "bug" i'll call it a bug since these things ALL HAPPEN AT THE SAME TIME: once I flash AGAIN all these symptoms go away until I go back to wicked rom and flash back to stock rom than right there after this first flash going from wicked rom BACK TO stock ALL these symptoms come back until I flash stock firmware AGAIN, a second time (even though I just flashed it)
Symptoms:
1. Samsung wallet appears in my apps (this was only EVER on my phone once, when I had the MDOB rom on my phone), this thing shoulda never somehow appeared back on my phone in any way shape or form after ditching the MDOB rom, but again is comes back after the first flash going from wicked rom to stock rom.
2. I get the 4G icon from MDOB rom (not the LTE icon I SHOULD have while on stock, when on wicked rom I have a little LTE icon with a tiny 4G above it, the only time I've ever had just a 4G icon (without LTE) like this is when I had MDOB rom on my phone (which is the only other rom I've run other than wicked rom and stock rom).
3. this icon ONLY shows up after the FIRST flash from wicked rom back to stock, once I install stock AGAIN than it returns to it's normal LTE icon.
4. now i'm not just *****in about an icon here, this is just a part of my problem (indicator if you will), when my rom is "bugged" after first install from wicked rom to stock rom my wifi works normal how It used too. but once corrected (flashing again) AND using custom kernel on STOCK firmware it breaks my wifi 100% broken until I use this little build prop edit fix, set ro.securestorage.support = true to false, bam wifi now working but the rest of my problems are still there (wifi used to work 100% on custom kernels and everything until MDOB rom touched my phone and left this "bug" behind)
5. when this 4G icon appears after this "first" flash back from wicked rom to stock rom I also experience something else, my wifi button works during first boot setup and auto enables itself and I have no issues with my wifi connecting (as soon as I see this toggle on I already know once my phone locks onto the network it's gonna give me a 4G icon and not an LTE icon like it should and sure as shiznit it does, as soon as I get my icon back to how it's supposed to be (LTE icon) all of a sudden wifi won't auto connect on a first boot anymore, never, 100% never. (back before installing MDOB rom I used to auto connect 100% of the time on first boot) like it does now only when it's "bugged" out.
6. apps are missing, when this "bug" appears there's no app shortcuts on the desktop of my phone by default after fresh flash like there should be, sometimes they appear on first flash once in awhile (some apps might not even be installed? or just shortcuts missing, have yet to verify)
7. it feels like the phone flashes way too fast (second flash takes longer, I think?) and more/all? apps get installed on second flash, and Samsung wallet get's REMOVED (how'd it even get there? other than bein left behind from MDOB rom, same with the 4G icon, that icon isn't in either of the two roms I use so how does it get there? and ONLY at the same time the wallet magically appears and the rest of this stuff)
8. when this 4G icon appears my phone seems to be great except for the fact that I know my rom didn't install properly since i'm still missing apps ect, once I flash again, apps appear, Samsung wallet DISappears, 4G icon gets replaced with LTE icon and everything is A-OK until custom kernel is installed, remember this is NOT the kernels fault as it ran 100% perfect for many months ON THIS PHONE until the day this MDOB rom was installed, and it's had these issues ever since.
some of the things I've tried:
- Countless wipes, including full advanced wipe, restore to factory, data wipes
- Ton's of fresh installs of BOTH versions of 4.2.2 - now doing same with 4.3 and wicked rom 9.1
- Tried wiping using TWRP and odin mobile (flashed mobile odin via TWRP, it works incase anyone didn't know)
- Tried flashing roms using odin (pc) v1.85, v3.07, v3.09
- Downloaded new copys of roms from new sources to make sure my roms weren't corrupted in anyway
i'll hopefully edit this post and get some pics up soon and simplify my text to help you guys better understand my situation and i'll also add a list of things I've tried to fix this problem when i have time.
any thought would really be welcome, there's sooo many of us s4 users with random sleeps of death, i'm sure if we could fix this it would help out a lot of S4 users.
thanks, dustin
Amb669 said:
System Specs: Galaxy S4 Canadian i337m OTA 4.3 (jfltecan), carrier is Bell, stock Samsung firmware, stock kernel (use wicked rom 9.1 sometimes too)
WARNING:
lot's of reading so go grab a coffee and have a cigarette before you sit down to read this, you'll probly be here for awhile
The rom/fix in question: MDOB rom/i337m fix - here's a link to both.
http://forum.xda-developers.com/showthread.php?t=2280556
i'll hopefully edit this post and get some pics up soon and simplify my text to help you guys better understand my situation and i'll also add a list of things I've tried to fix this problem when i have time.
any thought would really be welcome, there's sooo many of us s4 users with random sleeps of death, i'm sure if we could fix this it would help out a lot of S4 users.
thanks, dustin
Click to expand...
Click to collapse
Have you tried to flash the stock firmware in Odin. You can get it off the Samsung Updates site.
The guy who puts MDOB together generally makes great rom's. If everyone had the same issues then no one would use it... you really could have gotten a bad download, user error somewhere or one of many other problems.
With apps' just "appearing" are you certain once you log into your google account that it not set up to automatically start downloading apps ?
hednik said:
Have you tried to flash the stock firmware in Odin. You can get it off the Samsung Updates site.
The guy who puts MDOB together generally makes great rom's. If everyone had the same issues then no one would use it... you really could have gotten a bad download, user error somewhere or one of many other problems.
With apps' just "appearing" are you certain once you log into your google account that it not set up to automatically start downloading apps ?
Click to expand...
Click to collapse
don't get me wrong, i'm sure it's a great rom but my battery drain was worse than stock so I went back to stock, I REALLY appreciate his hard work towards our community. I just dislike what it possibly did to my phone is all.
and I don't have issues with the MDOB rom itself, it's AFTER that rom has been on my phone EVERY other rom ever since then now has issues in some way shape or form, no matter what I do.
if it's user error I put down the steps on how I flash in OP, I dunno what's going wrong
i'm gathering screenshot's to better show my situation.
I am 100% positive GAPPS is NOT installing anything after rom installs (I don't connect to wifi until after setup is done spacificlly to prevent this from happening, my rom just flashes this way (only on first flash from wicked rom going to stock rom) once I flash again a second time my symptoms part goes away and I get the issues part of my OP
if i'm on wicked rom and flash to stock = symptoms listed above
if i'm on stock rom and flash to stock = issues listed above
I can replicate this problem all day long.
I've flashed his rom on and off. Never had the issue. The rom doesn't invade anything a full wipe wouldn't cure. If it doesn't full wipe then it's the recovery. It helps once in awhile if you Odin back to stock or even copy your sdcard contents and format your sdcard to make it fresh. read up on it first.
Sent from my SGH-I337 using Tapatalk
---------- Post added at 01:45 PM ---------- Previous post was at 01:44 PM ----------
Also I recommend doing 9 wipes when swapping roms. It sound ridiculous I know but I do it and have never had issues.
Sent from my SGH-I337 using Tapatalk
Amb669 said:
don't get me wrong, i'm sure it's a great rom but my battery drain was worse than stock so I went back to stock, I REALLY appreciate his hard work towards our community. I just dislike what it possibly did to my phone is all.
and I don't have issues with the MDOB rom itself, it's AFTER that rom has been on my phone EVERY other rom ever since then now has issues in some way shape or form, no matter what I do.
if it's user error I put down the steps on how I flash in OP, I dunno what's going wrong
i'm gathering screenshot's to better show my situation.
I am 100% positive GAPPS is NOT installing anything after rom installs (I don't connect to wifi until after setup is done spacificlly to prevent this from happening, my rom just flashes this way (only on first flash from wicked rom going to stock rom) once I flash again a second time my symptoms part goes away and I get the issues part of my OP
if i'm on wicked rom and flash to stock = symptoms listed above
if i'm on stock rom and flash to stock = issues listed above
I can replicate this problem all day long.
Click to expand...
Click to collapse
Just odin back to stock and set if that clears things up. It should solve any odd problems. The thing with flashing rom's is that someone's issues cannot always be replicated.
Going back to Odined stock will take it back to factory stock then do a factory reset in stock 3e recovery and you should be fine
I never had to use my GPS til now and found out it cant lock on to any GPS sat. Ive had no other issuses with this phone
This is all the things ive done. I've enable TMO AWS since day one. I'm a TMO user that was a given.
My phone had the old orginal baseband, i think its MDC, then i upgraded to MDL and now i'm on the new NB1.
Ive bounced around all KK roms and even some older roms i still had saved. Nothing can get a GPS lock. I'm leaning now towards something physical, but Google now works and they can trianglulate via cell towers.
Ive 99% sure ive enable all GPS items. Location settings are on high accuracy.
Ive been using GPS status apps to help get a better location and nothing seems to be working.
Does playing around with Kernals help? I never installed one before or played with any of those. I need GPS to be working now so if i cant figure it out soon, i might just jump ship to the nexus/s5/iphone
bump up. Anyone have suggestions?
ive tried many different roms, Touchwiz and not touch. All diffrent basebands. I dont know what kernal work with what roms so ive been avoiding that
A kernel is not going to help. Have you gone back to stock rom and still have the issue? It sounds more like it's a hardware issue. Like the gps antenna is not working.
sadly i'm thinking the same thing. It looks like a cheap part but no idea on taking it apart just yet.
I always thought a kernal acted like a driver for computers,
turtle* said:
sadly i'm thinking the same thing. It looks like a cheap part but no idea on taking it apart just yet.
I always thought a kernal acted like a driver for computers,
Click to expand...
Click to collapse
The kernel is the boot image and in essence it interprets between the software and hardware. If you've flashed other roms you've flashed a kernel each time.
jd1639 said:
The kernel is the boot image and in essence it interprets between the software and hardware. If you've flashed other roms you've flashed a kernel each time.
Click to expand...
Click to collapse
ah, understood. I thought it was like the baseband where i had to manual change it.
Does anyone know where the GPS antenna is located at? Is it a part i can swap out or attached the main board. I just pulled apart the phone looking for obvious parts not being connected and everything looked good.
Ebay listings GPS antenna as the 3g blue cable that runs down the side of the battery. I dont think thats the GPS antenna but it does cost a small amount but i dont think that will help.
before you tear it apart try what jd suggested and odin back to stock. you may want to backup and format your internal and ext sdcards also. they can harbor old junk that may effect new roms.
also, are you wiping all including system before flashing and on your phone and some roms i believe you have to odin a modem.bin file as part of flashing. am not familiar with that stuff as i am i337 and never used odin. "yet"
not sure if any of it will help--but--
good luck
Might need more info on what our suggesting.
I'm wiping data and the option under data in clockworksmod.
I don't have anything important, everything is cloud.
Sent from my GT-I9505G using Tapatalk
I think he is suggesting that first you get the STOCK MDL Odin package and flash it. Then wipe all data, dalvich cache, and internal sdcard (remove your external sdcard before hand). Then power it up and IMMEDIATELY turn OFF WiFi, you do NOT want it to try to update on its own. Now check GPS and see if it works.
If it does work now (the FIRST LOCK can take a bit of time) Then again use casual+motochopper to root and install twrp. Then flash a good ROM. Once that is done you can check GPS again and make sure it works, it may take a bit since it will be the first lock again (I always had trouble with MK2 modem for some reason. All the rest worked perfectly).
Or just make sure you have the ROM you want to run on a external sdcard. Then remove it for safe keeping. Now go into twrp/clockworkmod and wipe data factory reset/ cache/ dalvich cache/ and sdcard. Power off the phone after it is done and reinsert your external sdcard. Do not boot up but go directly to where you have the ROM at on your external sdcard CIA twrp/clockworkmod and flash the ROM. This will give you a perfectly clean slate. Now once it is done and booted up let it sit without touching it for at least 5 minutes. Then check GPS. If it works you are good to go. Then download any of your apps from the play store (not from titanium backup in case some system setting are being reinstalled with something). Once you have your apps back check GPS again to make sure one of them hasn't caused an issue with your GPS. If all is still good use titanium backup to recover your DATA ONLY for the installed apps.
Sent From My Spiderman,Ironman,Red,Dark Blue,Green, GreyedOut BadAss Themed I337
I have no idea why
I had the same problem, and I just fixed it too.. I don't know if this will cause the problem but here it goes.
I found this solution from the forum, but forgot where..
1) I installed the rom (AOSP) I wanted and checked if gps worked (but didnt work, checked with GPS Status)
2) Went to recovery, nandroid the Rom
3) Clean install to Rom that GPS worked (TW Rom) and again checked if gps worked (and worked, also checked with GPS Status)
4) While leaving the GPS toggle on, went into recovery, and without wiping anything, restored the AOSP rom
5) booted checked GPS Status and I was able to see the satellites..
I have no idea right now if this will cause any trouble.. but at least gps works in aosp..
I'll update again if I face any problems
Good luck
Its working now. Not 100% sure what the problem was but that's for everyone with the suggestions.
I flashed about 15-20 different Roms from touchwiz to aosp and miui thing.
Opened the phone up and looked for basic things not connected.
Removed my case and wireless charger insert.
Did the MDB Odin flash. With stock ROM. It didn't still didn't work.
Finally gave up and flashed back old GE ROM. And all of a sudden it works.
I think the Odin wipe and SD card wipe had a big role but not sure. Either way it works now. Might not be the fastest connection to GPS as it takes a few moments now but it works. I'm normally locked on to 13/21 SATs out there in a matter of 2-3 mins.
Now that it works I'm a little weary of trying MDL
Sent from my GT-I9505G using Tapatalk
Hi,
I use BasicPlus 2 rom by t-shock (http://forum.xda-developers.com/s7-edge/development/rom-basicplus-1-t3402601).
When I reboot my device, specific apps are complety missing and I have to restore them with TB to go on.
This is reproducible with these certain apps, for example Swiftkey, Es Explorer and Google Calendar.
I had this issue before and I fixed it by deleting the 'Android' folder on my external microsd (128GB Samsung Evo Plus), since the missing apps always create an empty folder there. Now this seems not to be working anymore, therefore I'm asking for a permanent solution in this thread.
Unfortunatelly I'm not able to post in the rom's thread since my account is locked for the development section, but I hope I will get some help here.
Thanks!
Did you dirty flash?
If you did, I highly recommend clean wiping after every update to a custom ROM.
iSaitama said:
Did you dirty flash?
If you did, I highly recommend clean wiping after every update to a custom ROM.
Click to expand...
Click to collapse
Yes I dirty flashed from 1.1.1 to 2.0, since this was supported by the developer and he provided a fix to have a stable rom.
I also tried a clean install, but for any reason battery life wasn't that good compared to the dirty flash from 1.1.1.
It seems that no one else has such an issue, that would mean no one else did a dirty flash from 1.1.1, otherwise there would be more reports!?
In the meanwhile I made a clean install in each case of 2.0 and 2.1, but the issue still exists. I also wiped all caches after rom install, but there is no change. All apps survive several restarts but all of a sudden some apps disappeared after restart. I will try now with 3.1 and Prometheus kernel, too bad I cannot post to the main thread of the rom, since the developer doesn't see this thread I think
I am currently on the f model and after the N910FXXU1DPH2_N910FOXA1DPH2_DBT my phone has come to an almost unusable state. Fc, random reboots, freezes during calls, black screens etc. Full factory reset and reinstalling didn't helped. I have root and tried some custom roms but i need some opinions. I want a MM based rom with full Spen and snote usage. I dont care nor use fingerprint, shealth, svoice, knox, android pay, note 7 or edge gimmics or ports. I just want a stable light and reliable rom to fully use the spen, make and receive calls, send texts, use social media and have full data and wifi connectivity and as less bloat as possible. A theme feature will be nice but not mandatory. Cheers and ty in advance!
The feeling I get from reading the various threads on these fora is that stock ROM remains to be the most stable of the lot. If you are having these problems with clean stock then could it be your setup or a hardware fault that is causing these issues?
If it is not a hw issue, then it could be that TWRP has been corrupted. Try downloading and reinstalling your recovery.
I am using nameless now and it looks pretty sweet. About the recovery when I first updated it reverted to stock recovery. I reseted to factory settings which caused me to loss root. And today when I tried to get to nameless I could not get twrp to install via flash via odin. It succeeded but it always booted to stock recovery. I had to root first and then install twrp through it's app from the play store. Anyway all seems pretty solid in nameless I will try it out for a few days.