I have been working on a ROM based on the 1.61 ROM that was recently released on the site. However, I have been experiencing a strange glitch with the way the Fn keys are mapped. I have tried running the HTC Keyboard fix but to no avail. To give you an idea of a few of the incorrect mappings, ! and @ are switched, ? / and _ are right, and the rest are all basically wrong. Has anyone else ever experienced this error, or have any idea where it might have came from?
I have a feeling it might be from a missing file or something that I mistakenly added, but I have no idea what it could be.
EDIT: I released a fix for my problem http://forum.xda-developers.com/showthread.php?t=359143
download tilt keyboard fix
Like I said, I tried that. And theoretically, I shouldn't need it, because I based my ROM off an AT&T ROM.
EDIT: Nevermind, that was the problem. I just forgot to reset my Tilt. Strange that the fix is needed though, I used an AT&T ROM base.
On another topic, does anyone know why Pictures and Videos keeps showing up in Programs? I deleted the shortcut to it from OEM apps, but something seems to be recreating it. Any idea what? Also, and I am sure this question has been answered before (but I can't find the answer), but anyone know why I cannot make a OEM package of the Keyboard fix? The option to extract it is greyed out when I try to make it an OEM package.
FINAL EDIT: I released a fix for my problem http://forum.xda-developers.com/showthread.php?t=359143
hey guys i havent had any problems with this phone until today, and it seems like these have both started happening at the same time..
but when i turn wifi on, it connects and then a few seconds later disconnects. and when i try to go to the marketplace it says server unavailable, please try again.
also i sometimes i cannot find webpages on the browser. any ideas whats up with this?
hey guys, do any of you have a copy of the original setup.db file?
I'm pretty sure that is what is wrong with my phone..
when i was messing with mine, i messed up and changed the wrong thing with out noticing it before replacing it and now i can not access the marketplace or use wifi..
so if anyone has that file i can use i would really appreciate it.
Do you have an application named Navizon?
If so delete it.
I don't think i have the original setup.db?
Explain? I have no idea what you're talking about I'm pretty noobie about android.
accinfo said:
Do you have an application named Navizon?
If so delete it.
I don't think i have the original setup.db?
Explain? I have no idea what you're talking about I'm pretty noobie about android.
Click to expand...
Click to collapse
thanks for replying, but i got it to work.. i just went in to recovery mode and cleared the cache and its working great again..
First the details:
Sensation XE
OrDroid 8.6.
S-on
HTCdev unlocked
4ext recovery
Smartflash enabled
and formatted all partitions except SD Card before flashing
_____
The problem is that none of the MMS messages will go through if containing a photo that was taken with the flashed ROM. However, if I try to send a photo that was taken prior to OrDroid ROM, it goes through without a problem.
Doesn't matter if I send it directly out of the message app or going first to Gallery and share it. After about a minute I get the error in the notifications saying "Unable to send message after multiple attempts" and "Generic network failure" or "Service denied" written below.
The MMS settings and Mobile Data are all fine, considering it works with old images. Plus I can't notice any difference in the images' details between the new ones and the ones taken prior to flashing OrDroid.
One more thing, I also cannot receive MMS messages. I get a message with a download button and nothing happens if I click it.
Any help would be greatly appreciated. Oh, and I'm not looking for a ROM changing solution.
Edit: Ok, after about 30 new attempts of sending out photos, I see the problem isn't with newly taken images, but it's completely random. Now, about 1 in 10 attempts goes through. By the way, the signal bar is full. I really don't get it...
No one has any ideas? That's rather sad.
Hi I'm running Ordroid 8.6.5 and I'm able to take pictures and send them immediately, new pictures. I just tested it. It works perfectly for me. Perhaps do a full wipe and re flash the newest rom. I can say it's NOT ordroid because its working perfectly for me.maybe the download got corrupted somehow. I would definitely do a full wipe, download a NEW download to the computer then place NEW download to root of SD card and flash. Don't use old download as it is likely corrupted in some way. See if this solves the issue. Please do full wipe before flashing NEW download. This should do the trick. I'm hopeful this will fix the issue. Let me know. Because we know its NOT a issue with ORDROID, so give that a try . Good luck! Hope this helps out!
Also check and make sure settings are correct, if so do the new download of ordroid, see if it fixes the issue.
Sent from my Sensation 4G using xda premium
Thanks for replying, realsis.
I did a full wipe again and reflashed. I didn't bother downloading the file again, because the md5 matches and the file's fine. The MMS still doesn't work though.
So sorry, I can't think of another possible fix. Perhaps someone else has one ? Very strange because I'm using the same rom as you are and I can use mine without issues. I really hope you find a fix soon. Take care.
Sent from my Sensation 4G using xda premium
Thanks realsis.
Anyway, apparently ROM really isn't the issue. I've just flashed InsertCoin Evolution v1.91 and the MMS still won't go through.
I truly am baffled.
Check the apn settingd for your carrier...sometimes they get goofy ...ive had this happen before and I had the wrong settings..even though I never touched them...i googled for the settings and fixed it instantly
I've also tried that. Manually typed in proxy and port, and sadly it did not do the trick. Almost none of the MMS will go through.
I would call your carrier and see if it's goofed at their end, maybe they can help.one time I had to call for something and even though I'm using custom rom (they don't know this) they were able to fix my issue. Cannot hurt to try?
Sent from my HTC Sensation 4G using xda premium
I called them just now, and we went over the APN settings again, and she told me to change the authentication type to PAP (was 'none' before). Of course that didn't do the trick, and we parted without resolving the issue. She told me it should work and that was basically it.
It's getting really annoying because I know it really SHOULD work! Poop.
I've been having same problem. I'm using sensation running energy ics ROM. The work around i use is i have to use quickpics (app) and crop the image before sending... Almost as if Android isn't resizing the image correctly when "converting" to mms. This almost always works.
Thanks billybag, but that didn't do the trick.
The thing is, the problem is the same with the incoming MMS. It says download and after I click it, it says downloading for a minute or two and just pops back to download.
I tried really cropping the image with Quickpic (to about a pixle or two ) and it still didn't send it.
I feel a bit odd admitting to this, but i am stumped - i bought a shield portable, am running through the setup and the keyboard will not appear when i need to type in my wifi password. I've tried skipping that stage, and the keyboard won't pop up for anything else either.
The system was rooted and had supersu(?) on it when i bought it, i unrooted it through that or thought i did, but no difference except supers is no longer present. I've factory reset, nothing.
Is there something in the settings that could be causing this, or anything else anyone can think of? I've even tried getting the recovery images off nvidia but the windows ones won't work, i downloaded the linux version and managed to extract that through cygwin as according to one youtube video i found that would give me what i needed, but the extracted files are nowhere to be found.
I feel very tired, and very stupid right now.
HELP?
THE ORIGIN OF THE ISSUE:
Everything began 1 month ago. I was using my Nexus 5 like I always did. I had my WiFi turned on because I was chatting with my friends on Instagram and I left my smartphone charging. There were notifications and the notification light turned on showing me that I had two texts from Instagram app. When I tried to turn it on the screen, I pressed the power button, but the screen did not turn on. I pressed the power button again and again and again, but still the same. I tried to force-reboot my device and that's what I did. When the screen started again, my WiFi was stuck at "turning WiFi on...", also, my Bluetooth was not working properly too, because when I tried to turn it on, it automatically turned back off.
ATTEMPT TO FIX #1:
First thing I tried was unrooting and reinstalling stock using Nexus Root Toolkit. That didn't work... I tried doing a simple factory reset from the phone settings, also didn't work...
After those fails, I noticed that my MAC address was corrupted, showing this: 02:00:00:00:00:00 so I searched the Internet for stuff related to this MAC address error and found people with similar problem just like mine. I found solutions like deleting /persist/wifi folder (my friend did not recommended me to do so after I did this). So, I did the thing, AND IT DID NOT HELP. Tried returning to stock using Nexus Root Toolkit AND IT DID NOT HELP. I had an idea to delete my entire system using TWRP and I thought that reinstalling it would fix the problem. But I was noob at the moment, didn't know how to flash after deleting it. Anyway, I went on, and deleted system, but I didn't know how to reinstall and I was without a smartphone for 3 weeks. I was sooooooooo sad cause this was the worst issue I had to deal with... No smartphone... No WiFi.... life sucks (still does, I am sooo depressed for a stupid smartphone)... Well, obviously, NOTHING HELPED.
ATTEMPT TO FIX #2:
After those 3 weeks, I finally managed to find a way to reinstall OS on my smartphone again (using Nexus 5 factory image found in Google site for developers). I was sooo happy because at least I managed to turn the smartphone back on. So, step two was to check if WiFi worked. Well... not as I expected things to be. It didn't work... Obviously... Well, after doing simple experiments, I tried to do "the thing again". After deleting file .macaddr from /persist/wifi folder, without deleting the folder, only the file, WiFi turned back on!!! I went in tears thanking God. Sooooo much happiness!!! I desided to insert WiFi APs that I prevously saved in a wpa_supplicant.conf file, and guess what.... I F***** UP WIFI AND SENSORS!!! I was sooooo mad!
ATTEMPT TO FIX #3:
Well, the next day, I attempted to do a system delete again, but this time, I used another computer device, my family laptop. I deleted system, and this time, I didn't flash anything using Nexus Root Toolkit, but I used this Nexus 5 factory image again. WIFI WAS BACK ON!!! YEESSS!!! I was crying soooo hard!! I again thanked God!!! But it didn't last long... After two days, I turned on my WiFi to check my messages from Instagram, sadly, my WiFi was again stuck on "turning WiFi on..." and my smartphone rebooted by itself (again). So... guess what. I DEAR YOU TO GUESS WHAT HAPPENED NEXT!!! MAC address was back to this STUPID 02:00:00:00:00:00. I had enouch. I installed Termux, I installed a packet called "macchanger" and tried to change my MAC address to something random. I used command "macchanger -r wlan0" and I rebooted. This changed my MAC address to something random. Now, WiFi turns on and when I open an application to use WiFi with, it turns off immediatelly... Also, my MAC address is on changing again with command "macchanger -r wlan0" and is stuck in the previous randomized MAC address. Using "macchanger" command, I also noticed that my "permanent" MAC address is now: 00:00:00:00:00:00 (something that was never valid).
WHAT DO I DO?
DO I NEED TO BUY A NEW SMARTPHONE BECAUSE THIS ONE IS PRETTY F***** UP?
DO I NEED TO REPLACE THE ENTIRE MOTHERBOARD?
IS THIS EVEN A HARDWARE ISSUE?
IS THIS A SOFTWARE ISSUE?
DO I NEED TO REPLACE FIRMWARE? IF SO, HOW DO I DO THAT?
DOES THIS HAVE SOMETHING TO DO WITH /PERSIST?
WHAT DO YOU PROPOSE? BECAUSE I AM TIRED OF THIS STORY, REALLY...
SPECIAL URL: https://forum.xda-developers.com/t/...y-are-and-how-to-get-it-back-if-lost.3307793/
Retr0.Hacker said:
THE ORIGIN OF THE ISSUE:
Everything began 1 month ago. I was using my Nexus 5 like I always did. I had my WiFi turned on because I was chatting with my friends on Instagram and I left my smartphone charging. There were notifications and the notification light turned on showing me that I had two texts from Instagram app. When I tried to turn it on the screen, I pressed the power button, but the screen did not turn on. I pressed the power button again and again and again, but still the same. I tried to force-reboot my device and that's what I did. When the screen started again, my WiFi was stuck at "turning WiFi on...", also, my Bluetooth was not working properly too, because when I tried to turn it on, it automatically turned back off.
ATTEMPT TO FIX #1:
First thing I tried was unrooting and reinstalling stock using Nexus Root Toolkit. That didn't work... I tried doing a simple factory reset from the phone settings, also didn't work...
After those fails, I noticed that my MAC address was corrupted, showing this: 02:00:00:00:00:00 so I searched the Internet for stuff related to this MAC address error and found people with similar problem just like mine. I found solutions like deleting /persist/wifi folder (my friend did not recommended me to do so after I did this). So, I did the thing, AND IT DID NOT HELP. Tried returning to stock using Nexus Root Toolkit AND IT DID NOT HELP. I had an idea to delete my entire system using TWRP and I thought that reinstalling it would fix the problem. But I was noob at the moment, didn't know how to flash after deleting it. Anyway, I went on, and deleted system, but I didn't know how to reinstall and I was without a smartphone for 3 weeks. I was sooooooooo sad cause this was the worst issue I had to deal with... No smartphone... No WiFi.... life sucks (still does, I am sooo depressed for a stupid smartphone)... Well, obviously, NOTHING HELPED.
ATTEMPT TO FIX #2:
After those 3 weeks, I finally managed to find a way to reinstall OS on my smartphone again (using Nexus 5 factory image found in Google site for developers). I was sooo happy because at least I managed to turn the smartphone back on. So, step two was to check if WiFi worked. Well... not as I expected things to be. It didn't work... Obviously... Well, after doing simple experiments, I tried to do "the thing again". After deleting file .macaddr from /persist/wifi folder, without deleting the folder, only the file, WiFi turned back on!!! I went in tears thanking God. Sooooo much happiness!!! I desided to insert WiFi APs that I prevously saved in a wpa_supplicant.conf file, and guess what.... I F***** UP WIFI AND SENSORS!!! I was sooooo mad!
ATTEMPT TO FIX #3:
Well, the next day, I attempted to do a system delete again, but this time, I used another computer device, my family laptop. I deleted system, and this time, I didn't flash anything using Nexus Root Toolkit, but I used this Nexus 5 factory image again. WIFI WAS BACK ON!!! YEESSS!!! I was crying soooo hard!! I again thanked God!!! But it didn't last long... After two days, I turned on my WiFi to check my messages from Instagram, sadly, my WiFi was again stuck on "turning WiFi on..." and my smartphone rebooted by itself (again). So... guess what. I DEAR YOU TO GUESS WHAT HAPPENED NEXT!!! MAC address was back to this STUPID 02:00:00:00:00:00. I had enouch. I installed Termux, I installed a packet called "macchanger" and tried to change my MAC address to something random. I used command "macchanger -r wlan0" and I rebooted. This changed my MAC address to something random. Now, WiFi turns on and when I open an application to use WiFi with, it turns off immediatelly... Also, my MAC address is on changing again with command "macchanger -r wlan0" and is stuck in the previous randomized MAC address. Using "macchanger" command, I also noticed that my "permanent" MAC address is now: 00:00:00:00:00:00 (something that was never valid).
WHAT DO I DO?
DO I NEED TO BUY A NEW SMARTPHONE BECAUSE THIS ONE IS PRETTY F***** UP?
DO I NEED TO REPLACE THE ENTIRE MOTHERBOARD?
IS THIS EVEN A HARDWARE ISSUE?
IS THIS A SOFTWARE ISSUE?
DO I NEED TO REPLACE FIRMWARE? IF SO, HOW DO I DO THAT?
DOES THIS HAVE SOMETHING TO DO WITH /PERSIST?
WHAT DO YOU PROPOSE? BECAUSE I AM TIRED OF THIS STORY, REALLY...
Click to expand...
Click to collapse
You said you were rooted.
Any chance you made a backup, especially a backup from the efs partition?
User699 said:
You said you were rooted.
Any chance you made a backup, especially a backup from the efs partition?
Click to expand...
Click to collapse
What is EFS? What backup do I do. Cause, I'm a noob and all, and I am not the type of a developer... But, I guess I am able to do a backup using root. But how will this work? How will this help the situation. Could you explain to me friend? (If you are willing to do so of course)
Retr0.Hacker said:
What is EFS? What backup do I do. Cause, I'm a noob and all, and I am not the type of a developer... But, I guess I am able to do a backup using root. But how will this work? How will this help the situation. Could you explain to me friend? (If you are willing to do so of course)
Click to expand...
Click to collapse
Maybe you want to have a look on this thread: https://forum.xda-developers.com/t/...y-are-and-how-to-get-it-back-if-lost.3307793/
EFS stands for Encrypted File System. […]
It contains your IMEI, lots of files revolving around your SIM card and Wifi/Bluetooth (this includes your MAC address for all the radios of your phone), and lots of other things that should never ever under any circumstance be deleted or touched. […]
If you lose your EFS folder, you lose pretty much any chance of your phone being able to use data, Wifi, Bluetooth […].
Click to expand...
Click to collapse
If you had done a backup (e.g. via twrp) prior to rooting you might have also done a backup of that efs partition.
And if you had a backup you could restore that partition. Don't know if you somehow managed to mess this partition up (or if its related at all in your case. Someone with more knowledge hopefully sees your thread) but if you did, there would be no point in backing up that partition now (if its damaged, there is no use to backup a damaged partiton to restore it afterwards).
You can ask me everything you want, don't worry. But I don't know if I'll be able to explain it.
You could try to follow above mentioned guide. If it works, please upvote that guide so others find that helpfull content too.
User699 said:
Maybe you want to have a look on this thread: https://forum.xda-developers.com/t/...y-are-and-how-to-get-it-back-if-lost.3307793/
If you had done a backup (e.g. via twrp) prior to rooting you might have also done a backup of that efs partition.
And if you had a backup you could restore that partition. Don't know if you somehow managed to mess this partition up (or if its related at all in your case. Someone with more knowledge hopefully sees your thread) but if you did, there would be no point in backing up that partition now (if its damaged, there is no use to backup a damaged partiton to restore it afterwards).
You can ask me everything you want, don't worry. But I don't know if I'll be able to explain it.
You could try to follow above mentioned guide. If it works, please upvote that guide so others find that helpfull content too.
Click to expand...
Click to collapse
I did not mess with any partitions. I do not like to mess with my system. I never did. I always made a backup if I had to do something with the system. Before the incident, I never EVER messed with the system. I only started some experiments after the thing happened. I first deleted the whole content of /persist folder (which I restored, because I had a backup), then I deleted .macaddr file inside /persist/wifi folder which actually turned on my WiFi access again, only to f*** things up after doing something stupid, which is to replace wpa_supplicant.conf file inside the /data/misc/wifi folder with one I had with my previously saved WiFi Access Points and their passwords, which resulted to the corrupted MAC address again (02:00:00:00:00:00). No, my WiFi can be scanned successfuly and I am able to connect to it, but still, it does not work properly, because when it connects, it automatically disconnects when I try to use apps like Chrome and Instagram and other apps that need Internet to use. I am currently deleting and re-installing my Factory Image and this will be the last time...
Also, I will attach your URL for sure.
Thanks.
Retr0.Hacker said:
I did not mess with any partitions. I do not like to mess with my system. I never did. I always made a backup if I had to do something with the system. Before the incident, I never EVER messed with the system. I only started some experiments after the thing happened. I first deleted the whole content of /persist folder (which I restored, because I had a backup), then I deleted .macaddr file inside /persist/wifi folder which actually turned on my WiFi access again, only to f*** things up after doing something stupid, which is to replace wpa_supplicant.conf file inside the /data/misc/wifi folder with one I had with my previously saved WiFi Access Points and their passwords, which resulted to the corrupted MAC address again (02:00:00:00:00:00). No, my WiFi can be scanned successfuly and I am able to connect to it, but still, it does not work properly, because when it connects, it automatically disconnects when I try to use apps like Chrome and Instagram and other apps that need Internet to use. I am currently deleting and re-installing my Factory Image and this will be the last time...
Also, I will attach your URL for sure.
Thanks.
Click to expand...
Click to collapse
Another thing which would be helpful:
If your problem is still present you might want to have a look at the logs. That way it's easier to see what causes this behavior.
Code:
adb logcat > log.txt
Run this and try to reproduce the error.
Don't worry about messing with anything. We don't know what happened and sometimes the best of us do things they shouldn't do.
And it seems that also other things (like installing a custom OS) messed with partitions somehow.
But yes, doing a backup prior to modifing is extremly wise – keep up that habit!
I would suggest to try this solution I found:
Aniki43 said:
My Solution {Nexus 5 stuck on "Turning wifi on"}
MY Nexus5 got the same problem today WiFi just stopped working suddenly. The mac got some stupid address like 2.00.00.00. I tried every thing still nothing. I have already rooted my nexus so tried different roms but issue still remains.
Then i just remembered about the ROM UBUNTU Touch i have installed it and WiFi in Ubuntu start working again with original mac address. I am currently using Ubuntu touch and didn't try to reinstall or reset the android rom again.if some one try this and got WiFi working like me please inform me that if the WiFi still works if i reinstall android system.
If you want to download Ubuntu touch download it ubports
Click to expand...
Click to collapse
It is said that the "fix" stays after Android is reinstalled afterwards.
momojuro said:
I would suggest to try this solution I found:
It is said that the "fix" stays after Android is reinstalled afterwards.
Click to expand...
Click to collapse
I saw this thread before. I did not try to flash other OS than the one I use now. I was also thinking downgrading to Android 5.1.1 (because I am currently using 6.0.1 with MOB30H build) and I might try some time.
BTW there is another problem now. I installed a packet from Termux called "macchanger" and I used the packet in order to - what else - change my MAC address. The packet seems to work. It DID change my MAC address and I am now able to scan for local WiFi. But the thing is that every time my I try to connect ti the Internet, WiFi automatically closes, and the randomized MAC address is permanently stuck ( I think, because I can reset it sometimes, but still, it changes back the the one who got randomized first)
I may get a new smartphone for WiFi, calls and stuff and use my Nexus 5 in order to try and find a fix for it. Idk...