Develop Bugs

Wifi issue on AOSP Roms

Hi guys,
I have had the s2,s3,galaxy nexus,original note and i am used to flashing and modifying,but i have a serious issue with the note 2.
The problem is whenever i flash AOSP rom(cm,aokp,pa) my wifi would not connect.It shows the name of the network and when i click conenct nothing happens.Flashing back TW rom fixes it,wifi works like a charm. I've done full wipes but it doesn't seem to resolve the issue.I tried different kernels,but that doesn't help either.
So I am stuck at TW roms and i hate that.Anyone has any ideas?

You can try options 2 and 3 from this thread.

Thanks for your reply,but i tried this and it didn't solve my problem.

Anyone?

spookhc said:
Anyone?
Click to expand...
Click to collapse
I Have the same problem...

Not sure that it will help you but I read something yesterday about this issue.
The solution was to NOT restore your Google profile during first boot so you should full wipe and try again.

Primokorn said:
Not sure that it will help you but I read something yesterday about this issue.
The solution was to NOT restore your Google profile during first boot so you should full wipe and try again.
Click to expand...
Click to collapse
This actually has nothing to do with the problem.
After a few days I finally found the cause ,and therefore,a decision to the problem.
It is the bootloader from 4.3 sammy leaks.It seems that this new leaks(probably the reason being KNOX) cause malfunction of wifi in aosp roms.What i did was ODIN flash stock MG1 from sammobile .This brought back stock recovery so i had to flash TWRP again and it solved the issue for me.
Before that i had tried changing roms,kernels,recovery,modems and nothing worked so I am pretty sure it is the new 4.3 leaks bootloader.
Some people will say that it can\t be the issue because they are using 4.3 sammy and do not experience the same problem on aosp roms,but i think thats because they flash it through CMW ,which doesn't change bootloader,while flashing through ODIN does.

With my Note2 this is not the solution. I've tried everything. What you said, move file "pit" ..... but nothing. I can not connect wifi. The connection does not appear region Spain, and have opted to choose europe, but neither. I do not know to do. CM 10.1 also does not work WIFI. In Stock ROM or Custom ROM works fine fine, but in ROM CM 10.1, 10.2, AOKP don't work.
spookhc said:
This actually has nothing to do with the problem.
After a few days I finally found the cause ,and therefore,a decision to the problem.
It is the bootloader from 4.3 sammy leaks.It seems that this new leaks(probably the reason being KNOX) cause malfunction of wifi in aosp roms.What i did was ODIN flash stock MG1 from sammobile .This brought back stock recovery so i had to flash TWRP again and it solved the issue for me.
Before that i had tried changing roms,kernels,recovery,modems and nothing worked so I am pretty sure it is the new 4.3 leaks bootloader.
Some people will say that it can\t be the issue because they are using 4.3 sammy and do not experience the same problem on aosp roms,but i think thats because they flash it through CMW ,which doesn't change bootloader,while flashing through ODIN does.
Click to expand...
Click to collapse

[Q] cannot connect to the camera error problem

Am so sorry mods if i didn't post this in the right section, I have limited sections i can paste owing to the fact that am still a junior member and my posts aren't up to 10. I have an sgh-t999 samsung galaxy s3, that is the snapdragon chipset type. I would love to update the whole firmware to 4.3 boatloader, baseband and so on just dat i've only succeeded in updating the baseband to the latest but not the boatloader cos it will involve downloading the whole firmware and am scared of this knox security stuff imbeded in 4.3 and another thing is that i have a slow network which might cause broken and corrupt downloads. My main problem is that when ever i flash any kitkat custom rom, that is all this weekly, nightlies and so on roms, am always having this persistent cannot connect to the camera error which i have searched for a fix to no avail. Ok look at how I have tried to fix it, i copied the camera data of a touchwhiz rom to replace the kitkat own but no changes, have tried restarting and wiping but still same problem. I happened to come across this beautiful rom ie [D2LTE]
~~AICP~~4.4.4----{5.0}---(RELEASE)-JUN-25 rom which i so much love and discovered that it has same problem. Seriously if it were just the bluetooth, i wouldn't have any problems but the camera is ab essential somethhing i can't stay with. Is this problem because am flashing a kitkat custom rom without an updated boatloader or is it particular to the rom? I need some help plz. How do i have a long standing solution to it?

dikachik1 said:
Am so sorry mods if i didn't post this in the right section, I have limited sections i can paste owing to the fact that am still a junior member and my posts aren't up to 10. I have an sgh-t999 samsung galaxy s3, that is the snapdragon chipset type. I would love to update the whole firmware to 4.3 boatloader, baseband and so on just dat i've only succeeded in updating the baseband to the latest but not the boatloader cos it will involve downloading the whole firmware and am scared of this knox security stuff imbeded in 4.3 and another thing is that i have a slow network which might cause broken and corrupt downloads. My main problem is that when ever i flash any kitkat custom rom, that is all this weekly, nightlies and so on roms, am always having this persistent cannot connect to the camera error which i have searched for a fix to no avail. Ok look at how I have tried to fix it, i copied the camera data of a touchwhiz rom to replace the kitkat own but no changes, have tried restarting and wiping but still same problem. I happened to come across this beautiful rom ie [D2LTE]
~~AICP~~4.4.4----{5.0}---(RELEASE)-JUN-25 rom which i so much love and discovered that it has same problem. Seriously if it were just the bluetooth, i wouldn't have any problems but the camera is ab essential somethhing i can't stay with. Is this problem because am flashing a kitkat custom rom without an updated boatloader or is it particular to the rom? I need some help plz. How do i have a long standing solution to it?
Click to expand...
Click to collapse
Are you getting force close?
Sent from my GT-I9100G using XDA Premium 4 mobile app

dikachik1 said:
Am so sorry mods if i didn't post this in the right section, I have limited sections i can paste owing to the fact that am still a junior member and my posts aren't up to 10. I have an sgh-t999 samsung galaxy s3, that is the snapdragon chipset type. I would love to update the whole firmware to 4.3 boatloader, baseband and so on just dat i've only succeeded in updating the baseband to the latest but not the boatloader cos it will involve downloading the whole firmware and am scared of this knox security stuff imbeded in 4.3 and another thing is that i have a slow network which might cause broken and corrupt downloads. My main problem is that when ever i flash any kitkat custom rom, that is all this weekly, nightlies and so on roms, am always having this persistent cannot connect to the camera error which i have searched for a fix to no avail. Ok look at how I have tried to fix it, i copied the camera data of a touchwhiz rom to replace the kitkat own but no changes, have tried restarting and wiping but still same problem. I happened to come across this beautiful rom ie [D2LTE]
~~AICP~~4.4.4----{5.0}---(RELEASE)-JUN-25 rom which i so much love and discovered that it has same problem. Seriously if it were just the bluetooth, i wouldn't have any problems but the camera is ab essential somethhing i can't stay with. Is this problem because am flashing a kitkat custom rom without an updated boatloader or is it particular to the rom? I need some help plz. How do i have a long standing solution to it?
Click to expand...
Click to collapse
As you have installed custom recovery so I feel it might have increased your warranty count and as far flashing 4.3 rom, I don't think if you flash root66 of latest NC2 build is going to harm as only thing that you will not be /should not flash older firmware in Odin as it will brick your device but you will be able to flash older custom Rom in recovery without any issues
With this you will be enjoying latest bootloader and modem and use all 4.4 Rom without issues.
For camera issue, you download other camera from play store and try as I used Google camera without issues on this Rom but I am on latest bootloader and modem.

Something like a force close
captaindeep said:
Are you getting force close?
Sent from my GT-I9100G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Not exactly cos when i tap on the camera icon, the error message just appears ie cannot connect to the camera, restart camera or ok. When u click on restart, the camera just restarts but does same thing but if u click on ok, the camera just closes.

[Q] Need to downgrade, how?

Greetings, I wonder if somebody can solve the following problem. I'm from Venezuela and I bought this model GT-I9192 in December 2013 when the update came out this year it was updated from 4.2.2 (JellyBean) to 4.4.2 (KitKat). I almost never use the camera of this phone and then I noticed that every time I opened the camera app I would get "Warning: Camera Failed". Thinking it was the update I proceeded to install the Cyanogenmod rom 11 for this model, but continued with the same problem. The flash works every time I turn the flashlight application. I took it to a technician telling me that the problem was not hardware but software. This is where my troubles began. I do not remember which firmware was installed. I tried to install several firmwares 4.2.2. but without success all with flashing failures. However, I could install version 4.4.2 of Trinidad and Tobago but with the same camera error. Hopefully someone can help me with this problem. I would like to know exactly what firmware should download to install? Thank you very much.

nelson2006 said:
Greetings, I wonder if somebody can solve the following problem. I'm from Venezuela and I bought this model GT-I9192 in December 2013 when the update came out this year it was updated from 4.2.2 (JellyBean) to 4.4.2 (KitKat). I almost never use the camera of this phone and then I noticed that every time I opened the camera app I would get "Warning: Camera Failed". Thinking it was the update I proceeded to install the Cyanogenmod rom 11 for this model, but continued with the same problem. The flash works every time I turn the flashlight application. I took it to a technician telling me that the problem was not hardware but software. This is where my troubles began. I do not remember which firmware was installed. I tried to install several firmwares 4.2.2. but without success all with flashing failures. However, I could install version 4.4.2 of Trinidad and Tobago but with the same camera error. Hopefully someone can help me with this problem. I would like to know exactly what firmware should download to install? Thank you very much.
Click to expand...
Click to collapse
I registered here just to answer your question.
My Android expertise is very limited but I try to learn from past experience. If I understand correctly, your want:
1. the camera should work.
2. the phone should function properly.
If you do not remember your original firmware, do not worry as it does not matter. Once your upgraded to KK, Knox (google it) kicked in to prevent you from downgrading to JB. That's why all flashing efforts to downgrade failed. So, you can keep your phone with KK if the phone works except camera. In case you want to downgrade to JB, I am sure that able XDA members can help you with that. I am unaware if such methods exist.
Now, to see if the camera works there are several methods. I encountered the same problem with my wives i727 Skyrocket which has JB 4.1.2 installed. One day the camera suddenly failed with the error "Warning: Camera Failed". The flash-light worked flawlessly so I was a bit perplexed. I researched and found several remedies:
1. From application manager, clear cache/data of the camera app and restart phone - Tried this several times, did not work.
2. Perform factory reset- Thought I'd use it as a last resort as the phone had gigs of data in it.
3. Uninstall apps (last installed app uninstalled first and so on) - I uninstalled the last installed app and restarted the phone. Voila! The camera was back. I have no explanations why but it just worked.
Let us know how it goes, good luck!

On the i9195, it is possible and easy to downgrade to JB since there's a 4.2.2 firmware which is similar to the 4.4.2 firmwares, but I don't know about the i9192.
Be careful with this;
If you know what you are doing, get the CWM recovery, format system/data and flash a 4.4.2 firmware again. If that didn't fix it, I suspect that it's a hardware problem and it's having problems with the software, but there should be something wrong with the hardware, for sure.
Good Luck.

snipar said:
I registered here just to answer your question.
My Android expertise is very limited but I try to learn from past experience. If I understand correctly, your want:
1. the camera should work.
2. the phone should function properly.
If you do not remember your original firmware, do not worry as it does not matter. Once your upgraded to KK, Knox (google it) kicked in to prevent you from downgrading to JB. That's why all flashing efforts to downgrade failed. So, you can keep your phone with KK if the phone works except camera. In case you want to downgrade to JB, I am sure that able XDA members can help you with that. I am unaware if such methods exist.
Now, to see if the camera works there are several methods. I encountered the same problem with my wives i727 Skyrocket which has JB 4.1.2 installed. One day the camera suddenly failed with the error "Warning: Camera Failed". The flash-light worked flawlessly so I was a bit perplexed. I researched and found several remedies:
1. From application manager, clear cache/data of the camera app and restart phone - Tried this several times, did not work.
2. Perform factory reset- Thought I'd use it as a last resort as the phone had gigs of data in it.
3. Uninstall apps (last installed app uninstalled first and so on) - I uninstalled the last installed app and restarted the phone. Voila! The camera was back. I have no explanations why but it just worked.
Let us know how it goes, good luck!
Click to expand...
Click to collapse
I haved tried the first two steps and no luck at all. Maybe this weekend I'll try the third one. Thank you for the reply.

snipar said:
I registered here just to answer your question.
My Android expertise is very limited but I try to learn from past experience. If I understand correctly, your want:
1. the camera should work.
2. the phone should function properly.
If you do not remember your original firmware, do not worry as it does not matter. Once your upgraded to KK, Knox (google it) kicked in to prevent you from downgrading to JB. That's why all flashing efforts to downgrade failed. So, you can keep your phone with KK if the phone works except camera. In case you want to downgrade to JB, I am sure that able XDA members can help you with that. I am unaware if such methods exist.
Now, to see if the camera works there are several methods. I encountered the same problem with my wives i727 Skyrocket which has JB 4.1.2 installed. One day the camera suddenly failed with the error "Warning: Camera Failed". The flash-light worked flawlessly so I was a bit perplexed. I researched and found several remedies:
1. From application manager, clear cache/data of the camera app and restart phone - Tried this several times, did not work.
2. Perform factory reset- Thought I'd use it as a last resort as the phone had gigs of data in it.
3. Uninstall apps (last installed app uninstalled first and so on) - I uninstalled the last installed app and restarted the phone. Voila! The camera was back. I have no explanations why but it just worked.
Let us know how it goes, good luck!
Click to expand...
Click to collapse
RoyaLKurTx3 said:
On the i9195, it is possible and easy to downgrade to JB since there's a 4.2.2 firmware which is similar to the 4.4.2 firmwares, but I don't know about the i9192.
Be careful with this;
If you know what you are doing, get the CWM recovery, format system/data and flash a 4.4.2 firmware again. If that didn't fix it, I suspect that it's a hardware problem and it's having problems with the software, but there should be something wrong with the hardware, for sure.
Good Luck.
Click to expand...
Click to collapse
Tried that too and nothing. I also suspect that the problem is a hardware issue. Thank you for the reply.

nelson2006 said:
Tried that too and nothing. I also suspect that the problem is a hardware issue. Thank you for the reply.
Click to expand...
Click to collapse
The problem, in fact is a fault in the hardware problem. If it's still under warranty, request a new phone.

Weird Power Issue with all custom RoMs

So I took out my age old xperia M(single sim) a couple of days ago and installed cm 12.1 on it. The only issue I'm facing with it is that if I keep the phone on standby for a while the phone completely and silently shuts itself off. When this happens it doesn't turn on with the power key as well so the only way to turn it on after this happens is by removing and re inserting the battery and then pressing the power button. (phone boots normally then)
This problem only appears when the phone is in standby. I could use it 2hrs straight and the phone would keep functioning normally as long as I don't keep it on standby for a long period.
I've tried tons of different cm12.1 roms and factory reset the phone multiple times but the problem is there with every single rom. Haven't tried any rom that isn't based on 12.1 yet.
Strange thing is that this standby dead thing doesn't happen when there is a music app that's playing some song while in standby. Even if the phone is on silent and media volume is 0. So the temporary fix is to keep playing some song and keep media volume at 0. I would be really happy if someone comes up with a permanent solution though. Thanks. Any help would be greatly appreciated

Was the problem present on the stock ROM?

elmkzgirxp said:
Was the problem present on the stock ROM?
Click to expand...
Click to collapse
I have the same problem with CM based roms, went back to stock and it doesn't have this issue, could it be something to do with ambient display/doze?

kurtbvb said:
I have the same problem with CM based roms, went back to stock and it doesn't have this issue, could it be something to do with ambient display/doze?
Click to expand...
Click to collapse
No, I don't think so. Which version did you come from? I would suggest flashing 15.4.A.1.9 first because most custom ROMs use it as base and doesn't offer full compatibility with older versions.

elmkzgirxp said:
Was the problem present on the stock ROM?
Click to expand...
Click to collapse
Nope. My sister had been using this phone on 4.3 since 1yr now. I decided to use it as a secondary media device when she got a new phone. When I first unlocked my bootloader after rooting the device went into bootloop. So had to restore it to stock 4.1 Indian (couldnt find 4.3 indian ftf) using flashtool (took 2 days and tons of researching to get the drivers working). Then I rooted it again and flashed twrp and cm 12.1. Have been facing this problem ever since.
It's driving me crazy now. Might go back to stock if it doesn't get fixed
Edit - also just checked the sim slot isn't working either. Tried multiple 12.1roms but it won't get detected. Didn't realise this before as I'm using this as a media device and don't need sim card working anyway.

RagzyB said:
Nope. My sister had been using this phone on 4.3 since 1yr now. I decided to use it as a secondary media device when she got a new phone. When I first unlocked my bootloader after rooting the device went into bootloop. So had to restore it to stock 4.1 Indian (couldnt find 4.3 indian ftf) using flashtool (took 2 days and tons of researching to get the drivers working). Then I rooted it again and flashed twrp and cm 12.1. Have been facing this problem ever since.
It's driving me crazy now. Might go back to stock if it doesn't get fixed
Edit - also just checked the sim slot isn't working either. Tried multiple 12.1roms but it won't get detected. Didn't realise this before as I'm using this as a media device and don't need sim card working anyway.
Click to expand...
Click to collapse
Do what I said to @kurtbvb too, as it may just be base incompatibility. Flash everything except the TA partition (if present) and wipe /data and /cache.

elmkzgirxp said:
Do what I said to @kurtbvb too, as it may just be base incompatibility. Flash everything except the TA partition (if present) and wipe /data and /cache.
Click to expand...
Click to collapse
So do I flash stock 4.3 using twrp or do I need to flash the ftf file using flashtool ?

RagzyB said:
So do I flash stock 4.3 using twrp or do I need to flash the ftf file using flashtool ?
Click to expand...
Click to collapse
Flashtool. Some files are required which custom recoveries can't flash.

Just flashed the above mentioned ftf file and then rooted the phone, installed twrp and then cm 12.1 based rom. Everything runs perfect now. No random shut downs and Sim card works as well.
Thanks you so so much

Upgrade broke the GPS

Hi all, I have a note 2 shg-i317 that was originally on Bell in Canada. It was unlocked and the aws mod done to it, I use freedom mobile, aka T-mobile in the states.
I was running a Rom for the past 3 years Slimfast 4.4 and liked it. I had tried Nugat on another phone, thought I would try the [ROM][7.1.2][OFFICIAL] LineageOS for N7105
I did the upgrade, broke the root, could not get a few things working, so I decided to restore the Slimfast backup I had just made (complete including modem etc) and everything works except the GPS.
GPS for me is huge, I use it a lot. I cannot lock on to 1 satellite now. Before i was able to lock onto a minimum of 16 in about 30-45 seconds, if outside.
I really dont care if I can get to 7.1 at the moment. I need my GPS back - any troublshooting for getting GPS to work on this phone?
James

I would try to flash the original stock for your phone and country from sammobile. com
Gps should work normaly then. If not your hardware is broken. If it works you can always flash your data back from your Slimfast rom.
Verstuurd vanaf mijn SM-N910C met Tapatalk

Crap, I am posting here, because I did it again. Again not sure how. I tried to run Reserection, and I guess that messed up the GPS.
To put the original stock rom on.. I have to do that through ODIN? I dont remember how I fixed this last year.. Sorry.
Hope somone can help I need the GPS.
James
ps. Used odin 3.09 to flash the original rom... still no GPS

You flashed the latest 4.4.2 room?

audit13 said:
You flashed the latest 4.4.2 room?
Click to expand...
Click to collapse
The Rom that I flashed to try and restore the GPS was I317MVLUDNF1_I317MOYADNF1_BMC (mine was an originally BELL phone)
But that did not repair the GPS from me flashing resurection.. I THINK did it. I flashed an android 6 and an android 7 rom. (Mokee) but tried to go back to my Slimfast.. and the GPS was now broken.
Basically what I did a year ago.. somehow I fixed it then.. but cannot remember at all how I did it.
James

The note 2 sold by Rogers, Bell, and Telus are exactly the same model and stock roms from these carriers can be cross flashed.
Try flashing the stock ROM twice in Odin with a factory reset in between each flash.

audit13 said:
The note 2 sold by Rogers, Bell, and Telus are exactly the same model and stock roms from these carriers can be cross flashed.
Try flashing the stock ROM twice in Odin with a factory reset in between each flash.
Click to expand...
Click to collapse
Do you mean boot up the rom.. run the reset in the rom? or flash.. - load TWRP back in.. WIPE.. then FLASH again with odin?
Thanks for helping btw.
James

I have backups (complete all partitions) of my rom.. Slimfast 4.4 from 2-3 days ago.. when I tried this. SO.. if I can get the Factory rom to restore the GPS.. how can I restore the backup.. I saw somewhere that the EFS partition could be left out and that might help? dont restore the modem? how??
James

I meant flash with Odin, boot into stock recovery, factory reset, flash again with Odin, boot into stock recovery, factory reset, and boot into the stock ROM.

Nope, still no GPS lock.. I have the flashing circle (always had) and it will not lock.. I read about where people go into a service mode and rebuild the NV? .. I assume this is something that Mokee or Reserection did.. not sure how.
Any other ideas?
James

what about using Odin or TWRP to put different modems in? does the modem effect the GPS?
tried this.. does not seem to. grrrrr wish I knew how I fixed this.
James

I assume there are no loose wires. Does it get a lock when using wifi? Not sure what else to suggest.
Not sure about rebuilding NV.

No.. I broke it with playing with custom roms.. Liniage was last year.. I did not try that this year.. but tried both android 6 reserection and android 7 Mokee.. and I am pretty sure they messed it up.. I am also pretty sure there was something I did .. easy like load an old STOCK rom and it fixed it.. I was then able to put my slimfast 4.4 back over it and it was fine. Unfortunatly .. not enough people still using this device.. I will have to have patience I guess.
James

So I have tried differenct stock roms, but I think the issue is ODIN will not restore code from a rom image that is HARDWARE based. I wanted to use Samsung smartswitch but they disabled the part of it that allowed you to factory reset the phone, this seemed to work for several people. Many have also reported entering a code and going into a service mode.. there you can do to a menu that will rebuild hardware modules back to default. But I have not been able to get into that mode because it seems to be a touchwiz only option, and I cannot find a factory rom that is touchwiz based for this model.
What needs to be done is a true FACTORY ROM image.. that would revert all software and hardware back to original, but I cannot seem to find that anywhere.
James

The only factory roms that I know of come from places like sammobile.com and they are all based on TouchWiz which is Samsung's launcher.

So guess what? put Ressurection back on.. and the GPS is back.
I cannot get it to work in any KitKat based rom.. but now anything Marshmellow up.. works.. HMMMMMM
James