Related
Hi *,
I have installed KJY2010 Honeylicious Icy Faux HC 3.2 but it complains about the missing sim card (model wo G3 connectivity).
I'v tried to disable all apk that have to do with telephony but they are started from rild (I guess) in init.rc which is hardwired in boot.img.
Any other solution than to take boot.img from mmcblk0p2 and modifying init.rc in order to disable rild?
Are you running an a501? or an a500?
EDIT: saw your ()
Did you check your build.prop?
Should say ro.carrier=wifi-only
So if you did your 3 wipes, coming from another rom, you shouldn't get the error.
No need to delete or freeze apk's, or do anything with the image files. Relatively few people have the "please insert sim card" on the 500 series. Usually, because some info wasn't completely wiped.
And if in doubt, you can go to Mounts etc.. And format these things. This will ensure you delete all previous info. Also, you can flash the upgrade to a newer Thor Recovery if you wish, now that we mention it.
Also, it may help, to post this in the specific ROM thread in the development forum. This way, the Dev can specifically answer your issue, instead of general Iconia Q&A
Thanks for the prompt answer.
Since I'm a good boy I did wipe all
but you are right I have [ro.carrier]: [unknown]
and I didn't post to development because this is my 4th post and I'm not allowed
I hope I can change ro.carrier wo reflashing by editing /system/build.prop
magnusPI said:
Hi *,
I have installed KJY2010 Honeylicious Icy Faux HC 3.2 but it complains about the missing sim card (model wo G3 connectivity).
I'v tried to disable all apk that have to do with telephony but they are started from rild (I guess) in init.rc which is hardwired in boot.img.
Any other solution than to take boot.img from mmcblk0p2 and modifying init.rc in order to disable rild?
Click to expand...
Click to collapse
If you're running an A500 and followed the install instructions to the letter that are posted in the OP, there's absolutely no reason you should have a sim card message whatsoever. Over 3,000 downloads between the two ROMs, and no errors as such, once again if you're running the A500, and followed the EXPLICIT install instructions (there's also an install video in the OP).
---------- Post added at 05:51 PM ---------- Previous post was at 05:32 PM ----------
Moscow Desire said:
Are you running an a501? or an a500?
EDIT: saw your ()
Did you check your build.prop?
Should say ro.carrier=wifi-only
So if you did your 3 wipes, coming from another rom, you shouldn't get the error.
No need to delete or freeze apk's, or do anything with the image files. Relatively few people have the "please insert sim card" on the 500 series. Usually, because some info wasn't completely wiped.
And if in doubt, you can go to Mounts etc.. And format these things. This will ensure you delete all previous info. Also, you can flash the upgrade to a newer Thor Recovery if you wish, now that we mention it.
Also, it may help, to post this in the specific ROM thread in the development forum. This way, the Dev can specifically answer your issue, instead of general Iconia Q&A
Click to expand...
Click to collapse
Thanks Moscow, you always hit the nail on the head!
magnusPI said:
Thanks for the prompt answer.
Since I'm a good boy I did wipe all
but you are right I have [ro.carrier]: [unknown]
and I didn't post to development because this is my 4th post and I'm not allowed
I hope I can change ro.carrier wo reflashing by editing /system/build.prop
Click to expand...
Click to collapse
There is no ro.carrier line in the build prop on Icy Faux. Attached is the build prop in a text file from the ROM. There is NO ro.carrier line in the build.prop.
You have an old build prop on your tab from a previous ROM from not installing as per instructions in the OP of the ROM!
You can download the file from the attachments below, rename it build.prop, delete your age old build.prop from God knows when, and replace it with the proper one in the attachment.
kjy2010 said:
There is no ro.carrier line in the build prop on Icy Faux. Attached is the build prop in a text file from the ROM. There is NO ro.carrier line in the build.prop.
You have an old build prop on your tab from a previous ROM from not installing as per instructions in the OP of the ROM!
You can download the file from the attachments below, rename it build.prop, delete your age old build.prop from God knows when, and replace it with the proper one in the attachment.
Click to expand...
Click to collapse
And.... don't forget to check your permissions through root explorer when you do it. And.... reboot.
Just to be a tad fair in this, It can happen (no sim card inserted). I get this on my 501 after extended periods on wifi (weekend for example). Reboot typically clears it, and I can promise, I DO have a sim card inserted
Not sure tho why it crops up, maybe I should get an iPad
Also, to be a touch fair, sometimes, the 3 wipes don't get rid of all the leftovers. I ran into this only with Taboonay on a few occassions. Long story. Just seemed there was some leftovers after doing the wipes, and I was forced to wipe again and reflash. Messy business those wipes But extra wipes ensure everything's clean
Moscow Desire said:
And.... don't forget to check your permissions through root explorer when you do it. And.... reboot.
Just to be a tad fair in this, It can happen (no sim card inserted). I get this on my 501 after extended periods on wifi (weekend for example). Reboot typically clears it, and I can promise, I DO have a sim card inserted
Not sure tho why it crops up, maybe I should get an iPad
Also, to be a touch fair, sometimes, the 3 wipes don't get rid of all the leftovers. I ran into this only with Taboonay on a few occassions. Long story. Just seemed there was some leftovers after doing the wipes, and I was forced to wipe again and reflash. Messy business those wipes But extra wipes ensure everything's clean
Click to expand...
Click to collapse
Yes Moscow, but you have a 501, and not a 500. No reason to get that message on a 500.
Furthermore, even just the three wipes will leave residuals on your SDCard, and that's why I have explicit instructions for wiping, and formatting not only typed out in my OP, but in video as well. Impossible to get errors if you follow the instructions to the letter, yet people refuse to, and then have the nerve to post they have a problem, when the problem is in fact "pilot error"!
Moscow Desire said:
And.... don't forget to check your permissions through root explorer when you do it. And.... reboot.
Just to be a tad fair in this, It can happen (no sim card inserted). I get this on my 501 after extended periods on wifi (weekend for example). Reboot typically clears it, and I can promise, I DO have a sim card inserted
Not sure tho why it crops up, maybe I should get an iPad
Also, to be a touch fair, sometimes, the 3 wipes don't get rid of all the leftovers. I ran into this only with Taboonay on a few occassions. Long story. Just seemed there was some leftovers after doing the wipes, and I was forced to wipe again and reflash. Messy business those wipes But extra wipes ensure everything's clean
Click to expand...
Click to collapse
YOU SHOULD WIPE INSTALL THE ROM.. GO BACK INTO CWM.. (BEFORE YOU BOOT FOR FORST TIME) BACK TO WIPE MENUE AND WIPE AGAIN.. .
this has always worked for me.. to keep from these tiny simple issues .
i have very good backups so i format partitions.. then wipe .. install rom then go back and wipe again.. then boot room.. you know its clean when you do this.. . you can also before you boot go into the media folder and delete everything in there if you want TOTAL DISTRUCTION of your personal data..
but im just a chic what do i know..
good luck..
Yeah, like we know, wipe 3 times, check, then wipe some more
You guys are missing the humor
Why so serious?
Oh... to have a 501, the red headed stepchild,,,,
Moscow Desire said:
Yeah, like we know, wipe 3 times, check, then wipe some more
You guys are missing the humor
Why so serious?
Oh... to have a 501, the red headed stepchild,,,,
Click to expand...
Click to collapse
The 501 is not the red headed step child, but there is no reason to get the "insert sim card" notification on this ROMwith an A500 if you do a full and complete wipe according to the instructions and video in the OP.
Sorry, but I have no patience, nor compassion for people that don't take the time to read simple instructions that I've taken the time to not only write, but put up in video format as well.
If they have problems from now on, they can go flash Thor's bug ridden ROM and kernel.
kjy2010 said:
but there is no reason to get the "insert sim card" notification on this ROMwith an A500 if you do a full and complete wipe according to the instructions and video in the OP.
Sorry, but I have no patience, nor compassion for people that don't take the time to read simple instructions that I've taken the time to not only write, but put up in video format as well.
Click to expand...
Click to collapse
I understand that it can be quite annoying to save people from their mistakes
but I read the instructions and I followed them
and I installed on a brand new a500. Probably I did a mistake in wiping.
In any case ro.carrier=wifi-only did the trick.
EDIT: I compared the build.prop I have with the one you posted and they are the same!
I'll experiment with debug.sf.nobootanimation=1 because your bootanimation is very nice but it uses cpu and battery in a world where charge is power
magnusPI said:
Thanks for the prompt answer.
Since I'm a good boy I did wipe all
but you are right I have [ro.carrier]: [unknown]
and I didn't post to development because this is my 4th post and I'm not allowed
I hope I can change ro.carrier wo reflashing by editing /system/build.prop
Click to expand...
Click to collapse
magnusPI said:
I understand that it can be quite annoying to save people from their mistakes
but I read the instructions and I followed them
and I installed on a brand new a500. Probably I did a mistake in wiping.
In any case ro.carrier=wifi-only did the trick.
I'll compare the build.prop I have with the one you posted to see the differences and
I'll experiment with debug.sf.nobootanimation=1 because your bootanimation is very nice but it uses cpu and battery in a world where charge is power
Click to expand...
Click to collapse
The fact that you even had a ro.carrier line in your build prop suggests serious pilot error with regards to following the instructions that were clearly posted in the thread. The build prop from Honeylicious contains no such line.
As to your comment about the boot animation eating up all your battery, I'll leave that one alone, as it speaks volumes on its own lol
magnusPI said:
........ because your bootanimation is very nice but it uses cpu and battery in a world where charge is power
Click to expand...
Click to collapse
...think this comment needs my "boot" where the sun don't shine
kjy2010 said:
The fact that you even had a ro.carrier line in your build prop suggests serious pilot error with regards to following the instructions that were clearly posted in the thread. The build prop from Honeylicious contains no such line.
:
Click to expand...
Click to collapse
You are right and I wrote in a not so precise way.
1) There was no ro.carrier in my build.prop
2) I got ro.carrier undefined from command prompt with getprop
3) I compared the build.prop you posted and it is equal mine (up to the line I added)
diff build.prop build.prop.txt
64,65c64
< # messo da me
< ro.carrier=wifi-only
---
>
magnusPI said:
Thanks for the prompt answer.
Since I'm a good boy I did wipe all
but you are right I have [ro.carrier]: [unknown]
and I didn't post to development because this is my 4th post and I'm not allowed
I hope I can change ro.carrier wo reflashing by editing /system/build.prop
Click to expand...
Click to collapse
magnusPI said:
I understand that it can be quite annoying to save people from their mistakes
but I read the instructions and I followed them
and I installed on a brand new a500. Probably I did a mistake in wiping.
In any case ro.carrier=wifi-only did the trick.
EDIT: I compared the build.prop I have with the one you posted and they are the same!
I'll experiment with debug.sf.nobootanimation=1 because your bootanimation is very nice but it uses cpu and battery in a world where charge is power
Click to expand...
Click to collapse
magnusPI said:
You are right and I wrote in a not so precise way.
1) There was no ro.carrier in my build.prop
2) I got ro.carrier undefined from command prompt with getprop
3) I compared the build.prop you posted and it is equal mine (up to the line I added)
diff build.prop build.prop.txt
64,65c64
< # messo da me
< ro.carrier=wifi-only
---
>
Click to expand...
Click to collapse
Which tab are you using the A500, or A501, even after all this it's still unclear to me.
kjy2010 said:
Which tab are you using the A500, or A501, even after all this it's still unclear to me.
Click to expand...
Click to collapse
A500-10S32
with original android version 3.0.x
kyj2010,
Same thing here tonight! Been using my a500 for about 12+ hours today w/o issue after flashing Honeylicious.
I just got a call and tab locked... When I hit to awake noticed the "insert SIM card" at top of screen and found it odd.
I first went into the build prop to check for the ro.carrier specs but not there! Just as you stated, there is no ro.carrier line...
Searched and found this post...
Also, as a note, I followed your steps to a T after coming from FlexThunder..
iamtek7 said:
kyj2010,
Same thing here tonight! Been using my a500 for about 12+ hours today w/o issue after flashing Honeylicious.
I just got a call and tab locked... When I hit to awake noticed the "insert SIM card" at top of screen and found it odd.
I first went into the build prop to check for the ro.carrier specs but not there! Just as you stated, there is no ro.carrier line...
Searched and found this post...
Also, as a note, I followed your steps to a T after coming from FlexThunder..
Click to expand...
Click to collapse
What do you mean you "got a call and the tab locked"?
Please elaborate on what was going on when this happened. Over 4,000 downloads now and still counting with you two guys on A500s, not A501s are the only ones reporting this issue.
I've got well over 100 flashes into this ROM, and have never seen a sim card message.
It's built on the stock 3.2 image, so there should be no logical reason for it, other than maybe residuals that the wipes and formats aren't cleaning?
Sorry, I got a phone call and my screen locked after 5 minute mark.
I used the Tab since about 5:30am (EST) and can honestly say I do not recall seeing it at any point throughout the day.
At about 9:30pm, my Tab got to 13% battery and I plugged in. I got a phone call and walked away, came back, hit power button to unlock and noticed SIM msg..t
Rebooting now and see if still there. I,ll report back as to status.
BTW: 15+ hours of pretty steady use, installing apps, browsing web, wife streamed MTV shows as I watched NFL games, played a few games on Tab and still have battery!!
Great battery life with Honeylicious!! Thanks!
Update:
Reboot and still present...
iamtek7 said:
Sorry, I got a phone call and my screen locked after 5 minute mark.
I used the Tab since about 5:30am (EST) and can honestly say I do not recall seeing it at any point throughout the day.
At about 9:30pm, my Tab got to 13% battery and I plugged in. I got a phone call and walked away, came back, hit power button to unlock and noticed SIM msg..
Rebooting now and see if still there. I,ll report back as to status.
BTW: 15+ hours of pretty steady use, installing apps, browsing web, wife streamed MTV shows as I watched NFL games, played a few games on Tab and still have battery!!
Great battery life with Honeylicious!! Thanks!
Click to expand...
Click to collapse
If you mean the screen locked at the lock screen, just click the power once, wait a sec, click it again and unlock. I'm working on something right now, give me a few, and I'll have a file posted in this thread for you to try. I need to test it first, but I'll need someone that's getting the message to test it after I make sure it's safe to flash
I know there is a thread right here:
http://forum.xda-developers.com/showthread.php?t=1231086
However, all the links are dead, anyone bother to update it for me please?
I want to use the phone with ATT without data plan with it (GPRS, 3G, stuffs..)
So is it the Android rom is good in this case yet because it says support the GSM "partially"?
Thanks
Well i need it toooooo .. anyone listening ?
I have a Fathom that I was messing around with Android on and still had the files on my HDD. Uploaded them to 4shared:
~90MB Android 2.3.5
http://www.4shared.com/rar/-w1AtQcu/fathom.html
Wifi Files (Don't know if you need them but I'll upload anyways)
http://www.4shared.com/zip/DA3KFkfx/fathom-wifi.html
It is stuck at "Jumping to Kernel". Any help? Step-by-step instructions?
Are the files placed in a folder called "fathom" which is placed in the root of the SD card.
spunker88 said:
Are the files placed in a folder called "fathom" which is placed in the root of the SD card.
Click to expand...
Click to collapse
Let me try that...
---------- Post added at 01:28 AM ---------- Previous post was at 01:18 AM ----------
OMG its working now! Well at least its showing the "X"...
---------- Post added at 01:38 AM ---------- Previous post was at 01:28 AM ----------
Man, this thing crashes a lot! Wonder why...
Android for fathom
Hey guys, can someone post a step by step method... for porting Android? The first post on that that thread was a little bit confusing abt the steps
muralz77 said:
Hey guys, can someone post a step by step method... for porting Android? The first post on that that thread was a little bit confusing abt the steps
Click to expand...
Click to collapse
Sure. Do this and you will be fine.
1) Download the files. https://skydrive.live.com/redir.aspx?cid=5a36dd445483e8d8&resid=5A36DD445483E8D8!1568&parid=root
2)Extract the "fathom" folder inside the archive.
3)Move the extracted "fathom" FOLDER and move/copy to the ROOT of your SD card. Not the files inside the folder, and not the zip file itself either.
4)Go to your LG Fathom. Go to the "fathom" folder in the SD Card, then click on the "CLRCAD.exe" file. I heard it enables the sound, but it doesn't work for me. But just do it in case.
5)Launch the "haret" exe file. It is a longer name, but it starts with "haret".
6)Wait and enjoy.
The thing is, when I run it Android crashes and restarts every 10 seconds. Literally. Is it the hardware's fault? Anyone have better files? Or maybe an older version of Android to let it run smoother? Well I am not running it again until there is a fix. -_-
andrew789 said:
Sure. Do this and you will be fine.
1) Download the files.
2)Extract the "fathom" folder inside the archive.
3)Move the extracted "fathom" FOLDER and move/copy to the ROOT of your SD card. Not the files inside the folder, and not the zip file itself either.
4)Go to your LG Fathom. Go to the "fathom" folder in the SD Card, then click on the "CLRCAD.exe" file. I heard it enables the sound, but it doesn't work for me. But just do it in case.
5)Launch the "haret" exe file. It is a longer name, but it starts with "haret".
6)Wait and enjoy.
The thing is, when I run it Android crashes and restarts every 10 seconds. Literally. Is it the hardware's fault? Anyone have better files? Or maybe an older version of Android to let it run smoother? Well I am not running it again until there is a fix. -_-
Click to expand...
Click to collapse
That's an amazingly quick reply... thanks a ton dude for ur help... in the other thread, someone was saying to format the SD card before copying the folder, anywayz i would also format the card before copying Fathom folder to root..
once again thanx a zillion
muralz77 said:
That's an amazingly quick reply... thanks a ton dude for ur help... in the other thread, someone was saying to format the SD card before copying the folder, anywayz i would also format the card before copying Fathom folder to root..
once again thanx a zillion
Click to expand...
Click to collapse
Your welcome
But I just have one question: does Android ever crash constantly in your LG Fathom? Since mine does, I can't use it
andrew789 said:
Your welcome
But I just have one question: does Android ever crash constantly in your LG Fathom? Since mine does, I can't use it
Click to expand...
Click to collapse
I just installed according to ur steps, but wat u say is right. The OS crashed after a few minutes... now when i restarted it has come back to winmo 6.5
Something that matters: Check your Android version. 1.6 is the oldest ones I've ever seen around...
muralz77 said:
I just installed according to ur steps, but wat u say is right. The OS crashed after a few minutes... now when i restarted it has come back to winmo 6.5
Click to expand...
Click to collapse
Hmm... That's weird... A few minutes?? Mine literally crashes after 5-10 seconds constantly! But when it crashes it reboots Android...
techelec said:
Something that matters: Check your Android version. 1.6 is the oldest ones I've ever seen around...
Click to expand...
Click to collapse
Like I said in the reply above, I can barely make it to the settings app before it crashes...
andrew789 said:
Hmm... That's weird... A few minutes?? Mine literally crashes after 5-10 seconds constantly! But when it crashes it reboots Android...
Like I said in the reply above, I can barely make it to the settings app before it crashes...
Click to expand...
Click to collapse
For the first time it was stable for nearly 20 minutes.. now it's started rebooting in a loop... anywayz i found another version given below... will try n let u know the results. I am not able to provide you the link here... check out the last page (i guess page 23) on the "Android for Fathom" thread started by Ajeet
--------------------------------------------------
Originally Posted by Giorgi-geo
this link works best for me at this moment. www posted it long time ago but it's the latest version. battery drain is big tho. <link>
it's 2.3.1 but folder says 2.2 don't pay attention. to run correctly click on clrad few times and then run haret. good luck.
---------- Post added at 09:17 AM ---------- Previous post was at 09:09 AM ----------
For the very first time, it went into airplane mode.. u gotta disable it to make calls... and one more thing.... when i browsed through the original thread on android for fathom, the makers Ajeet and WWW have said that they are working on a stable version and will soon come out with one... so let's keep our fingers crossed..
muralz77 said:
For the first time it was stable for nearly 20 minutes.. now it's started rebooting in a loop... anywayz i found another version given below... will try n let u know the results. I am not able to provide you the link here... check out the last page (i guess page 23) on the "Android for Fathom" thread started by Ajeet
--------------------------------------------------
Originally Posted by Giorgi-geo
this link works best for me at this moment. www posted it long time ago but it's the latest version. battery drain is big tho. <link>
it's 2.3.1 but folder says 2.2 don't pay attention. to run correctly click on clrad few times and then run haret. good luck.
---------- Post added at 09:17 AM ---------- Previous post was at 09:09 AM ----------
For the very first time, it went into airplane mode.. u gotta disable it to make calls... and one more thing.... when i browsed through the original thread on android for fathom, the makers Ajeet and WWW have said that they are working on a stable version and will soon come out with one... so let's keep our fingers crossed..
Click to expand...
Click to collapse
OK. Let me test it out too...
---------- Post added at 06:02 AM ---------- Previous post was at 05:57 AM ----------
OK. Now it's done copying...
---------- Post added at 06:08 AM ---------- Previous post was at 06:02 AM ----------
Now my device is stuck at "Jumping to Kernal" again... I tried booting from the 2.2 folder and tried renaming 2.2 to "fathom"... but no luck... How do you do this?
andrew789 said:
OK. Let me test it out too...
Now my device is stuck at "Jumping to Kernal" again... I tried booting from the 2.2 folder and tried renaming 2.2 to "fathom"... but no luck... How do you do this?
Click to expand...
Click to collapse
Same thing here too... have u tried spunker's build??? if i find it, will try it over the weekend!!
---------- Post added at 01:29 PM ---------- Previous post was at 12:57 PM ----------
muralz77 said:
Same thing here too... have u tried spunker's build??? if i find it, will try it over the weekend!!
Click to expand...
Click to collapse
got it!! on the last link that i gave you by Georgi-geo, don't change the name of the folder to Fathom.. after you extract the zip from the link, u get a folder named 2.2 just copy 2.2 to your storage card root and run and wait for at least 15-20 seconds... and it works gud, no lags, no reboots in a loop...
Go to network settings disable Airplane mode and wait for a few seconds until it disables fully and ur gsm network shows up...
PS: better to format ur SD card before u do this
muralz77 said:
Same thing here too... have u tried spunker's build??? if i find it, will try it over the weekend!!
---------- Post added at 01:29 PM ---------- Previous post was at 12:57 PM ----------
got it!! on the last link that i gave you by Georgi-geo, don't change the name of the folder to Fathom.. after you extract the zip from the link, u get a folder named 2.2 just copy 2.2 to your storage card root and run and wait for at least 15-20 seconds... and it works gud, no lags, no reboots in a loop...
Go to network settings disable Airplane mode and wait for a few seconds until it disables fully and ur gsm network shows up...
PS: better to format ur SD card before u do this
Click to expand...
Click to collapse
Ok. Let me try that...Wait, do I have to format the SD card? Can I just rename it?
------
Renaming doesn't work... When I get on to my PC Ill try transfering again...
andrew789 said:
Ok. Let me try that...Wait, do I have to format the SD card? Can I just rename it?
------
Renaming doesn't work... When I get on to my PC Ill try transfering again...
Click to expand...
Click to collapse
U need to have at least 400 mb space on the card.. i deleted all stuff n formatted n only had the 2.2 folder in it... but unfortunately GSM works only partially and i'm a GSM user... i can make outgoing calls but not able to end them.. incoming calls don't work. GPRS/3G don't work either
muralz77 said:
U need to have at least 400 mb space on the card.. i deleted all stuff n formatted n only had the 2.2 folder in it... but unfortunately GSM works only partially and i'm a GSM user... i can make outgoing calls but not able to end them.. incoming calls don't work. GPRS/3G don't work either
Click to expand...
Click to collapse
I have 3,000 mb on my storage card! What's wrong with my device? Probably because I screwed some files up by accident... And hopefully CMDA will work since I use Verizon.
Did u have any luck??? try using a lesser memory SD card (2 GB preferable) and try to format it using FAT32 before u copy 2.2 folder and try running Haret when still connected to PC via USB...
One more thing.. do u know of any good GPS software that works on GSM in Fathom? btw I am not from US
So I recently flashed Virtuous Affinity 2.05.0 on my MT4g glacier.
It is awesome. However, I have run across the issue that the wifi will not work.
In looking at the wifi MAC address in system info and in wifi settings it says "Not Available".
I'm sure this is a software thing, but I don't have the files to fix it.
This thread I think solved the exact issue, but the problem is that the files that were uploaded to solve the issue are no longer available at that download site. http://forum.xda-developers.com/showthread.php?p=23627603
I've tried doing multiple searches to get this same information, but I don't know really what needs to be changed how, and while I normally believe that as long as you back it up and if it's broken you only really can fix it or make it break differently, I would still rather not try checking random files in hopes that it will work.
So does anybody know where I could possibly get those files that are uploaded by bsbachert or have any idea how to fix it?
I really hope I'm not stuck on this rom, because this is pretty sweet.
ctschrodinger88 said:
So I recently flashed Virtuous Affinity 2.05.0 on my MT4g glacier.
It is awesome. However, I have run across the issue that the wifi will not work.
In looking at the wifi MAC address in system info and in wifi settings it says "Not Available".
I'm sure this is a software thing, but I don't have the files to fix it.
This thread I think solved the exact issue, but the problem is that the files that were uploaded to solve the issue are no longer available at that download site. http://forum.xda-developers.com/showthread.php?p=23627603
I've tried doing multiple searches to get this same information, but I don't know really what needs to be changed how, and while I normally believe that as long as you back it up and if it's broken you only really can fix it or make it break differently, I would still rather not try checking random files in hopes that it will work.
So does anybody know where I could possibly get those files that are uploaded by bsbachert or have any idea how to fix it?
I really hope I'm not stuck on this rom, because this is pretty sweet.
Click to expand...
Click to collapse
Try flashing a different kernel, the files mentioned seem like modules, and different AndroidOS use different type of modules. Any kernel for that AndroidOS should probably fix it.
Or just switch roms to something like Cyanogen9 or AOSPx.
But then again, I don't really know anything lol.
---------- Post added at 12:05 PM ---------- Previous post was at 11:54 AM ----------
Flash the Frosted Cherry Kernel by Synthetic.Nightmare.
It should work...
My s5 sends cripted sms' s by it's self to a number when I'm sleeping.
I changed my bank account password just in case, but even uf some hacker had my bank account and password he would still need my confirmation, so right now I think that's not a problem.
But it gets me extra costs for international sms' s on my sim contract, are there any commands in Terminal emulator to find out what is makes yhe mesages sent by themself?
This is the number where the mesages go:
+351 915 692 826 ( It looks like it's from Portugal, and I'm from Romania, right now traveling all over europe as I work as a Lorry driver, if that counts in any way.)
This are the mesages sent:
%mveIqeXKRPNPUocW9KzJaROsl5zxiQTA6CepgVWrOtaHAVi7uKuEbLKiYpCqN5h/EmNuNN/qqmnuI+uUnknv3bf/kWiDqMJxUc1PvaHRmAWmhcln7SE7DltxDFEWQmBL1cxeMO2
18 October 2014 01:14 (I was sleeping.)
%mveIqeXnu5KBS2YiaXsC3mYaqSJ2Zd79UOCl4gvZ1nGh0FrVfqJZIZbr+tdtyevqvoGmeCt6Ga7wHaYNQxjY0hM+iTan/iElDl8lIL1e9wkfxYa5nFHZYZECkQaktds2hHhJ2jw
20 October 2014 03:44 (sleeping also)
%mveIqeXUbhYBs1T0PDjyMdqAsuZbbi+/3sf/E2JNwY6SKjn000E/5nzYE4FdPe5nOWDqIOkQfZLhYm0OjKZeD280AP31PH/TmgVtmzMYmsDXID90cWg10Xv51rgcFDJ2ryirBzO
25 October 2014 02:48
%mveIqeXKzSvhX+RlgqNWrca0DmmygXW7/gBsXCi32sM9qLbLTmqPZlq2jUEdR3mEDdteID/rFZ1MTSisni4WQeg1wzUbk0kzqfrvap0nIfYSRCYLSnF+iBSvMoNkJ91INhf+KF5
25 October 2014 11:00
%mveIqeXT/ZW1IGPub1FVQHlAdYzP4Yley4qLQRZGnd9jFO5ljBRF2jfjM3wZ//ENgATFXFewQEFK+/b+Z5K50ZUJIPWresyXu/YQck+PMJjmmLhCVg=
10 Novembre 2014 12:41
%mveIqeXA9HSrF9DmLWW/GpJs1CNH6OwQShQbjHx4JnC94cLXsu4qQ/N1Uqsj9EUk0Gn8uuDOSib8UsGhlvMiYekKPjnGyL9bOwWygqRWuDJmBmopBZyl3MUpxLx4F28PLsim+6I
12 Novembre 2014 17:18
%mveIqeXx0zZEzIfGYWapQIqAaaRQ7N5miyMXq9fQ2TTW45kRylQML48gZhczV5p/AULKWEO39GLyHDI/t6CE6Ai2VN/ctP4PDwrEVTtPoHc451FR5g=
14 Novembre 2014 13:12
%mveIqeX2B4hsoD0/K3bdez9MCMrq3oeT1UDBh5UgRmeSng0FVACqr5arBMEX7lxeXcs6SgVjeC3XhuxxhObkpAe1iWcgc2pEtmgzEJuRdBFR1gG5IEV+YOMdnV6D0Z9Fv/KOxNa
14 Novembre 2014 13:48
Last one ( most recent)
%mveIqeXL5iWLCLAyKXGIqP37DDKLOh0ND+qkDUzVHPtBWT0yOCDfJtDDZTWX1dFy/6GhRzaro2pMpOyQswjzriQtKlZIyIF2XRyF4p74V6EbVVcz3fDqG1b8t/Q3X2yNMnW2piG
17 Novembre 2014 07:27 (sleeping)
What can I do? AI have my s5 rooted and I'm afraid to factory reset it, i fi'm rooted and factory reset can I get a bootloop?
Can I use Terminal Emulator to see any old logs to see what triggers the automated sms?
Please help me guys, I would really apreciate.
You can factory reset while rooted. You could look through what apps have send sms permissions, but a reset would likely be easiest.
looks like a virus, maybe try a virus scan 1st
if not if it was me full wipe and format on both card and phone then incrypt it
Could it be sending its location , because the previous owner made it doing this , wnen you change sim card..... Just suggestion..
I'm the first owner, I bought it new from Bulanger France, in box, never been used. I rooted it my self. And you made me verify that option, it's deactivated (sim change alert, i can track the phone with find my samsung website)
Miftolog said:
Could it be sending its location , because the previous owner made it doing this , wnen you change sim card..... Just suggestion..
Click to expand...
Click to collapse
I factory reset the device , unchecked back up and restore, so I started clean, first installed my premium antivirus vidsfone protect mcfee and then all my favorite apps, the ohone still sends thise crypted smss omg... I even received a strafe phonecall number when I answered it closed when I tryed to call it it doesn't exist...
alexpu1u said:
I factory reset the device , unchecked back up and restore, so I started clean, first installed my premium antivirus vidsfone protect mcfee and then all my favorite apps, the ohone still sends thise crypted smss omg... I even received a strafe phonecall number when I answered it closed when I tryed to call it it doesn't exist...
Click to expand...
Click to collapse
asks for a replacement at the store you got it from.
If it's rooted - install Xposed and Xprivacy then block everything from sending SMS's and log whats trying... I would think this is some kind of malware that is running up your bill
Failing that - I would remove your SD card, wipe in recovery and flash a virgin firmware (or even stock) this way you know the device is clean... then see if you're still sending the sms's...
Ok I installed Xposed and Xprivacy, blocked all messages from all applications, but I don't knowhowto track the logs, can explain to me how to do that? Thank you.
I have stock rom and I'm rooted of course. G900f
MadMic said:
If it's rooted - install Xposed and Xprivacy then block everything from sending SMS's and log whats trying... I would think this is some kind of malware that is running up your bill
Failing that - I would remove your SD card, wipe in recovery and flash a virgin firmware (or even stock) this way you know the device is clean... then see if you're still sending the sms's...
Click to expand...
Click to collapse
It's sending messages again, how can I specifically verify on logchat, what is triggering this?
alexpu1u said:
It's sending messages again, how can I specifically verify on logchat, what is triggering this?
Click to expand...
Click to collapse
please reflash ROM with odin to make sure it's not a persistence protection.
factory reset it's not enough, it just clears data partition, and since you have root you could have your /system changed.
---------- Post added at 04:58 AM ---------- Previous post was at 04:52 AM ----------
alexpu1u said:
Ok I installed Xposed and Xprivacy, blocked all messages from all applications, but I don't knowhowto track the logs, can explain to me how to do that? Thank you.
I have stock rom and I'm rooted of course. G900f
Click to expand...
Click to collapse
in xprivacy main screen select Calling from top drop box, then menu, Template, and create a template with everything unselect except in Calling, the sendsms, which should have a question mark. run the template and you will be prompted everytime a app tries to send message
also, when selecting calling from the drop menu, you can see a exclamation mark inside a yellow triangle marking app that used that permission including how long ago. be sure to toggle to system apps in filter, since you wiped already and it didn't disappear
Theres an app called SMSTracker that you can compile and install. Logs all SMS to logcat so you can track what apps are sending SMSes.
---------- Post added at 10:40 PM ---------- Previous post was at 10:35 PM ----------
quantumalpha said:
Theres an app called SMSTracker that you can compile and install. Logs all SMS to logcat so you can track what apps are sending SMSes.
Click to expand...
Click to collapse
http://katharnavas.wordpress.com/2012/01/18/listening-for-outgoing-sms-or-send-sms-in-android/
https://sites.google.com/site/katharnavas/android/SMSTracker.zip
If you google the number you will find more people complaining about it and associating that with a software named Vodafone Protect, although I doubt a legitimate app would hardcode a number like that
venereo said:
If you google the number you will find more people complaining about it and associating that with a software named Vodafone Protect, although I doubt a legitimate app would hardcode a number like that
Click to expand...
Click to collapse
Thank you! I've found the logs. the sms's are triggered by vodafone protect, an antivirus acting like a virus... good job vodafone protect... also the number +351915692826 and 722004000 ( if people google this numbers more have similar isues with them)
alexpu1u said:
Thank you! I've found the logs. the sms's are triggered by vodafone protect, an antivirus acting like a virus... good job vodafone protect... also the number +351915692826 and 722004000 ( if people google this numbers more have similar isues with them)
Click to expand...
Click to collapse
When you device is marked has "Lost/Stolen" this send Encrypted messages. ;D
venereo said:
If you google the number you will find more people complaining about it and associating that with a software named Vodafone Protect, although I doubt a legitimate app would hardcode a number like that
Click to expand...
Click to collapse
zorrigas said:
When you device is marked has "Lost/Stolen" this send Encrypted messages. ;D
Click to expand...
Click to collapse
the thing is it's not stolen, I'm the first owner.
Once I pressed on show my location, that's it... it's there bug, it anoys me that it makes extracost on my contract, for something that is not my fault, uninstalled there antivirus...
When you press "show my location", automatically active Lost/Stolen mode
This project has been moved to the G+ community.
*Battery Life*
Parameters : Wake enabled, Email sync every hour, Calander sync, Weather sync
Companion Mode (BT with tethering): 3-4 days w/ 50-70 notifications a day
Standalone Mode (Cellular data): 1-2 days w/ 50-70 notifications a day
As you may have noticed. This is now a DevDB project. Across the top of the thread you will see "Downloads, Reviews, Feature Requests, Bug Reports". Please utilize these features.
Please use this template for filing bug reports on the "Bug Reports" page. This will make things go much smoother for everybody;
Release version-
Issue-
How often the issue occurs-
What you have done to try to resolve issue-
.
Thank you very much for the work you put into this. I don't have my D5 yet (should arrive before weekend if i am lucky). I'll happily flash this rom as soon as i have it and report back.
I'm so glad we have the last firmware update in the new custom rom, too. I wasn't able to use the latest watchfaces because they required the new firmware already for counter-clockwise rotation features.
I just installed the new rom over twrp like in the instruction. I wiped system, dalvic and cache only, didn't wipe 'data' though and didn't lose any apps/data. As far as I can see it works good, the watch got really warm and laggy at first but I will give the system some time to 'settle in'.
At first the recovery didn't find the 'backup' to restore. I had to put it in the directory ...\TWRP\backup\0000000000000000 . I discovered this by making a little backup from the old cache ( just a few MB) over twrp to look in which folder it will be put in. Sherlock
Thanks for the great work!!!
Thanks again mate
Out of interest - did you decide to stay with mailwise because it is a lighter client?
Thanksyou but 3G network not active. 2G mobile network ok
the steve said:
I'm so glad we have the last firmware update in the new custom rom, too. I wasn't able to use the latest watchfaces because they required the new firmware already for counter-clockwise rotation features.
I just installed the new rom over twrp like in the instruction. I wiped system, dalvic and cache only, didn't wipe 'data' though and didn't lose any apps/data. As far as I can see it works good, the watch got really warm and laggy at first but I will give the system some time to 'settle in'.
At first the recovery didn't find the 'backup' to restore. I had to put it in the directory ...\TWRP\backup\0000000000000000 . I discovered this by making a little backup from the old cache ( just a few MB) over twrp to look in which folder it will be put in. Sherlock
Thanks for the great work!!!
Click to expand...
Click to collapse
I know Loki didn't put this in his instructions so it's not absolutely necessary but:
The problem with this approach (not wiping everything) is that if you do experience issues down the track, it makes it much more difficult to pinpoint the cause.
Another serious point is that when you move to a fairly major update - which this is - a factory reset of the watch is best practice.
I would say even if you use the SP Tools version you should factory reset after the first full boot.
About recovery not seeing the data to restore - that's why Loki normally gives the whole folder structure starting with "TWRP" as top level. It also contains a small file which recovery looks for when it boots.
---------- Post added at 08:18 PM ---------- Previous post was at 08:15 PM ----------
hoaihaiduong said:
Thanksyou but 3G network not active. 2G mobile network ok
Click to expand...
Click to collapse
More information please.
Did you do a full wipe?
SP or TWRP install method?
Did you check your APN?
Have you checked that the "screen off = data off" setting is not the problem?
Which band does your sim use for 3g 850 or 2100 ?
PS in future these reports would be recorded under the "bug report" tab.
Cheers
pablo11 said:
I know Loki didn't put this in his instructions so it's not absolutely necessary but:
The problem with this approach (not wiping everything) is that if you do experience issues down the track, it makes it much more difficult to pinpoint the cause.
Another serious point is that when you move to a fairly major update - which this is - a factory reset of the watch is best practice.
I would say even if you use the SP Tools version you should factory reset after the first full boot.
About recovery not seeing the data to restore - that's why Loki normally gives the whole folder structure starting with "TWRP" as top level. It also contains a small file which recovery looks for when it boots.
---------- Post added at 08:18 PM ---------- Previous post was at 08:15 PM ----------
More information please.
Did you do a full wipe?
SP or TWRP install method?
Did you check your APN?
Have you checked that the "screen off = data off" setting is not the problem?
Which band does your sim use for 3g 850 or 2100 ?
PS in future these reports would be recorded under the "bug report" tab.
Cheers
Click to expand...
Click to collapse
Thank you for the advice! Of course you are right that a full wipe would be better but I did't want to setup everything from the beginning again. My watch actually works fine now and I don't experience any issues so far. I promise that in case of any problems with this rom I will do a full wipe and a clean flash first before bothering anyone here
It's all good. If it's working well then that's what it's all about.
I was giving general advice really
pablo11 said:
Thanks again mate
Out of interest - did you decide to stay with mailwise because it is a lighter client?
Click to expand...
Click to collapse
Yep. Even with nano gapps, I'm down to less than 200MB free space in system. So at this point, every MB is starting to count. I'm even looking at removing any launcher watchface that can be duplicated with a clockskin except for the default.
I can never get the keyboard the same as it was in your last release. That was perfect. Is there a trick to it?
I have the folder on the SD card and the keyboard is invoked correctly but the layout with mic activation on long press is what I miss.
@pablo11 I'll have to get back to you one that, I'm trying to track down a more serious issue.
pablo11 said:
More information please.
Did you do a full wipe?
SP or TWRP install method?
Did you check your APN?
Have you checked that the "screen off = data off" setting is not the problem?
Which band does your sim use for 3g 850 or 2100 ?
PS in future these reports would be recorded under the "bug report" tab.
Cheers
Click to expand...
Click to collapse
Did you do a full wipe?
SP or TWRP install method?
Did you check your APN?
Have you checked that the "screen off = data off" setting is not the problem?
Which band does your sim use for 3g 850 or 2100 ?
This call in 2G network ok no call amd data on 3G, In vietnam Vinaphone use B1 (2100) UMTS
hoaihaiduong said:
This call in 2G network ok no call amd data on 3G, In vietnam Vinaphone use B1 (2100) UMTS
Click to expand...
Click to collapse
There may be an issue with the D5 base firmware that's causing this but both of you posts provide little information than other than "It don't work". In the future your posts should look something like THIS. They should also never be posted in general discussion but in "Bug Reports"
Reverted back to v1.2.0
All future W812 development can be found HERE
Lokifish Marz said:
All future W812 development can be found HERE
Click to expand...
Click to collapse
I apologize in advance if I repeat or I repeat someones question, but why you cannot delete the system the dials are in this firmware? Some of them are so ridiculous and not relevant, for example the snowman with the snow!