Related
I am posting a new thread because I'm experiencing the issue with several diffrent ROMs so obviously it's a general issue not a ROM specific one. Also I have read through countless pages of posts with no luck so hopefully someone can shed some light. Over the past few days I've flashed (forgive my spelling) dude's .5, ravenge, cynogen 3.4 and I have been having issues with the phone not waking after either I put to standby myself or the screen times out. I know it's not an issue with my phone or card because I go back to virtudude's ROM without the issue. I have tried everything, formatting my partition, ext2, ext3, wipe, no wipe, everything I can think of and still have the issue accross mutiple ROMs. I know it's not just me because my friend with a G1 is having the same issue, as well as many people posting in the threads. Can someone please point me in the right direction to fix this issue please?
My phone:
G1 with JF 1.42
Newest SPL 2005
Newest 26I radio
8gb SD card, class6, ext2 or ext3 partition (same issue on either)
Thanks in advance for any help!
me too
I noticed this same problem, its related to wifi, when I disable wifi my phone wakes up, also I have searched everywhere too for a solution. I think the compiled wifi deiver in these roms are not compiled right. So its either this or some other problem.
Is your phone connected to wifi with wpa2 personal? One other thing I noticed is this happens at random, when it does happen adb and ddms say device is offline when the led is blinking, also bottom of phone gets hot.
Can any devs shed some light on what exactly happens when the phone shuts off? Because something is locking the phone up when the light goes off and is in standby.
I am doing a test, im leaving wifi on while the screen is off in settings, will report back
This happens to me also but its only with hero I also have the new radio and spl. I can run hero with no problems as long as I don't use apps to sd or lucids txt. The wired thing is that after I use any apps to sd it works great but only for a day sometimes a few hours. Then I will start to see freezing up or it won't wake up at all, unless I reboot or pull battery. I've tried to reformat my card, resize my partition I'm also lost on this one fresh out of ideas.
Do you guys think it might have somthing to do with the sdcards? Im useing a 4g class 6 transcend micro SD, its only about 2 weeks old. Jason what other roms gave you these problems?
defconoi said:
Is your phone connected to wifi with wpa2 personal? One other thing I noticed is this happens at random, when it does happen adb and ddms say device is offline when the led is blinking, also bottom of phone gets hot.
Can any devs shed some light on what exactly happens when the phone shuts off? Because something is locking the phone up when the light goes off and is in standby.
Click to expand...
Click to collapse
I personnally don't see the correlation between locking and WiFi, I was at work the other day and flashed a ROM and it was doing it. I have my WiFi off at work so that wouldn't have been the case that day. I do notice the bottom of the phone getting hot though.
In response to the other person with the sd card question I really don't think it's that as I have a class 6, have formatted every way possible. Unless the issue has to do with apps2sd, I use apps2sd on every ROM.
Glad to see I'm not the only crazy one on xda!
joe v said:
Jason what other roms gave you these problems?
Click to expand...
Click to collapse
Almost every ROM to come out in the last couple weeks has done it. TheDude's .5, Ravenge's ramjet, Cyanogen's 3.4.1, and the Cyanogenized Rogers ROM.
You know looking at these the one thing these all have in common is being Cyanogenized. And the only ROM to come out in the past few weeks that hasn't had that issue is Virtuedude's Rogers ROM, which isn't Cyanogenized.
If any devs are reading this thread if you can make a version of your most recent ROM without Cyan's build kernel and boot and see if that helps. I'd be happy to test it for you to try and get to the bottom of this. If you wanna shoot me an email hit up jasonsyn at gmail.
I've had the same problem, but for me it started after flashing Cyanogen's 3.4 release. Since then I've reverted back to his 3.3.3 release and everything is fine again. Perhaps it has something to do with the new SPL and these ROM's?
That seems to be the one constant among all of us with problems, we've all flashed the new SPL and radio.
EDIT: I asked cyanogen about it, we'll see what he says.
indiekid97 said:
I've had the same problem, but for me it started after flashing Cyanogen's 3.4 release. Since then I've reverted back to his 3.3.3 release and everything is fine again. Perhaps it has something to do with the new SPL and these ROM's?
That seems to be the one constant among all of us with problems, we've all flashed the new SPL and radio.
EDIT: I asked cyanogen about it, we'll see what he says.
Click to expand...
Click to collapse
Yeah but I've had the new SPL and Radio for a month and this just started a week or so ago...
I am having the exact same issue. I usually have wifi bluetooth and 3g disabled (saves battery) I noticed this started after grabbing the new spl, ever since it's been freezing in standby randomly. I'm going to try Virtudude's rogers rom to see if the combination of Cyanogen's boot image and the new spl is causing the freezing. Hopefully seeing as Virtududes rom isn't based on Cyanogen's boot image it won't freeze. I'll report back with my results.
I thought my button got worn out. I never had the symptoms on rc33. When I switched to cupcake back during hatkuros prime just before dudes first releases I noticed it. I thought if it wasn't my button it might be somehow related to jf kitchen since almost all my roms touch it at some point. Just speculation though, donno what causes it.
Hey what recovery image are you all running?
I'm gonna flash the new Cyanogens 1.2 Recovery image and see if that's the issue.
Ok so how gay is this? I just hung up from a phone call and the phone is stuck sleeping! I was using it and it won't wake up, this is so incredibly frustrating!!
I have the new recovery image, 3.4.1, and still issues.
Jason Syn said:
Ok so how gay is this? I just hung up from a phone call and the phone is stuck sleeping! I was using it and it won't wake up, this is so incredibly frustrating!!
I have the new recovery image, 3.4.1, and still issues.
Click to expand...
Click to collapse
try holding down menu or the power button...i had this issue and my sd card would "unmount unexpectedly" and then this ended up into my sd bein fried
for those who are having this issue, try saving a log of it from ddms after that adb shell reboot thats what ive been doing ... instead of removing the battery, though my issues seem to happen every 24 hours i was on cy's 1.1 just flashed 1.2 perhaps that was is the issue?.. either way... we should try to collect all the info we can while this is happening to us.
dbhatesyou said:
for those who are having this issue, try saving a log of it from ddms after that adb shell reboot thats what ive been doing ... instead of removing the battery, though my issues seem to happen every 24 hours i was on cy's 1.1 just flashed 1.2 perhaps that was is the issue?.. either way... we should try to collect all the info we can while this is happening to us.
Click to expand...
Click to collapse
Ok I'll be happy to but I'm a linux virgin...would you mind giving me step by step in adb and I'll give whoever the log that can make sense of it.
This happens to me also on The Dudes Roger built. I don't have WiFi enabled so it isn't that it seems pretty random and just I get no response from the phone and have to so the soft reset (Call Menu Power) and then it'll work again. Normally only happens like once a day though so I can live with it but it is a inconvenience and can be annoying if it does it when you actually need to use your phone for something with some importance.
well if you're on linux and have it to where adb runs from terminal , just type
Code:
adb shell reboot
but before all that ddms (dalvik monitor) just type ddms in terminal it will boot up and show everything your phones basically working with.. and issues,
now if your linux terminal doesnt work well with adb (cant get it to work , google "50-android.rules" and "51-android.rules" n see if those help, and also set your echo path right )
now if you're on windows just hit windows key + r type cmd , and set yourself into the sdk/tools directory, then type ddms that will start the dalvik monitor (try and save a log) make sure the log saves before rebooting the phone, when you're done you can just ctrl+c and type adb shell reboot, and your phone should reboot.
[just the basic]
i've ran into this intermittently...most of the time while using the browser or using the onscreen keypad during a phone call.
I'm on JF CRB43(which is 1.51 i think) with the Hard SPL and JF Recovery.
Only thing I've been able to do to get the phone to wake up is wait. eventually it'll come around. or pull the battery, which i try not to do.
Hey guys, I had a TP2 Sprint, now upgraded to MiteyMikes ROM (+WM6.5 I might add) but my fone doesn't mention "loading touch Flo 3D" upon loading up and also there is also Lag in software, turning the screen but a BIG lag when using the windows explorer.
Can anyone explain why that occurs and more importantly how to change prevent it...
Added info:
I think it cud be a shortage of memory. i have ordered a 16Gb mem card from china but its taking ages coming. so to test the fone, I have had to load apps on the phone memory.. could that be a/contributing reason to the lag and should i save the apps to memcard memory when i get it. Can I install them on mem card...
thanks for your help.. well in anticipation of it, anyway...
c0nv1ct
I had MightMike's newest build on my phone and it ran just fine. No lag or anything. It is one of the best roms i have used on my tp2. I always install all my apps to the internal memory of the device, unless the software says to install it to an external card. I have a 4Gb micro sd card and have no problems also. I just have all my music on there. I also have all my .cab files incase i need t hard reset.
If i were you i would either hard reset the device and see if that fixes your problem. If it does not fix it, reflash the same rom or a different rom.
Which MightyROM? Is it his 2.1 or 2.5?
Damn, Lag, really..?? I'm runnin his 2.1.10 release of his 2.1 ROM and this thing is blazin fast...! I have an 8gb minisd but I'm runnin just about everything off the phone and even with the apps I have loaded it still is fast as ****...?? Maybe try to reflash and do a hard reset after u flash, than give it a go, hope that works cuz ur missin out if ur laggin...
Easy one.
The below explaination assumes you have already HardSLP'd your TP2 and have some clue as to how to get around the WinMo OS.
Now, l337 code convict, If you don't mind reflashing your phone (again):
For future reference (becuase you'll flash again, I guarantee it): WHEN reflashing any rom you should "Clear Storage" before running the new rom's .exe on your 'puter --> this soft-resets the phone and your info will be gone, so use a program like PPCPimBackup, it's easy, fast, and cuts out the BS of having to use Outlook to sync pim information.
After the initial "Clear Storage" above, the phone will boot back into your rom, wait for everything to load (a good indication that the boot has arrived upon smooth or smoother operating efficiency, wait for the "three white horizontal lines with a down arrow" also known as the task manager to load. *its the thing in the upper top right hand portion of the black bar located at the top of your screen.* (this is imperative in any flash, even the stock rom)
After the boot has stabilized, sync your phone to your 'puter. (Per a previous post, if you're having probs syncing, go into your USB to PC settings and disable the "Enable faster data syncronization" option and say okay.)
Start your MightyMike installation and go thru the steps. Your phone will inevitably reboot. You'll probably have some waiting to do the first time it boots, with yet another restart.
Now, when the system boots your new rom installation, "Clear Storage" yet again (to clean up any installation files)
You'll reboot yet another time.
After this reboot, restore your pim info, load your extras, and for God's sakes, install At0mAng Enhanced D3D Driver. Reboot. Tweak away.
OH, and heed the words of Mr. MightyMike:
"——————————————————————————-
Please remember to provision your phone before configuring it!
Start > System > Carrier Provisioning
Not doing so before setting up your email, personalized settings will result in unforseen problems.
——————————————————————————-"
Lessons to take away from all of this:
Bottom line, wait for your phone to boot. You don't automatically start World of Warcraft and log into your Dalaran logged player while your computer is loading its AV software and startup entries, so give your little 520-some mhz PPC a chance to shine.
And a large HCSD card isn't going to make your PPC any faster. Your phone doesn't cache it like you have the availablity to do in Window$. Just install visual styles and "always running programs" into internal memory and games and other bullsh*t into your SD card.
Also, it's a good idea to do the following.
Reflash your stock ROM, then run a clear storage as indicated above.
Then flash the MightyROM, wait til it's fully loaded and run clear storage again.
After that it should be just fine.
Hello friends! I'm back again with the newest configuration I've found.
It's an Eclair build that runs exceptionally, with wifi, GPS and sleep working from the very first time.
If you want to try and forget your Donut build (1.6) you will have to do the following:
Choose a POLAIMG dated 20-Feb-2010 with your correct paneltype (1 is very common) and resolution from this site: http://sourceforge.net/projects/androidhtc/files/. Mine was POLAIMG-PANEL1-320.NBH (the most downloaded of them).
Download this file (http://www.homecncfun.com/wp-content/plugins/download-monitor/download.php?id=2) and extract androidinstall.tar from it. Copy it to your SD Card under a folder called "andboot":
Flash the previously downloaded .NBH file as usual.
During the boot you have to enter the Android Installer. A message will appear on the screen saying that you have to press and hold a button in order to start it. There are some buttons that are valid, for example, pressing the center button into the jog-wheel will work. Press it and hold it until the installer appears.
Select both System from NAND, Data from NAND.
Select Install.
Quit.
Let it start (slow).
What's working?
Wifi
GPS
Data connection
Phone - Calls, SMS
Sleeping (as far as I know)
USB Tethering (with PDANet)
Not working?
Camera
Audio input fails after the first use
Bluetooth
Live wallpapers
NOTE: If the screen resolution is wrong for you, you can change it modify system/build.prop. Guide here: http://forum.xda-developers.com/showthread.php?p=5709153
Enjoy!
More info:
http://forum.xda-developers.com/showthread.php?t=634782
To report bugs:
http://bugs.homecncfun.com/
i think poly's 2.1 beta is newer
http://forum.xda-developers.com/showthread.php?t=600154
anyway on both roms on polaris nand wifi is turning on but almost
non productive-slow
as well as battery issues u need to calibrate as mentioned on other posts
reiteravi said:
i think poly's 2.1 beta is newer
http://forum.xda-developers.com/showthread.php?t=600154
anyway on both roms on polaris nand wifi is turning on but almost
non productive-slow
as well as battery issues u need to calibrate as mentioned on other posts
Click to expand...
Click to collapse
*sigh*
was ALMOST about to finally try it out..
what's the gps like? is it just tomtom or whatever apps or some google thingie?
I've tried this one yesterday on SDCard with a partitioned system (cause I can't flash to NAND...) and it's very very slow
Don't know if it's better on NAND but I doubt that the difference could be so big...
I don't find it really that slow... It's a little slower than 1.6 of course, but it's still quite usable.
One thing that really put it down is that I know have an audio bug that affect the phone calls.
After calling one (or beeing called) the sound will not work (either people won't hear what I say or I won't heat people).
I have yet to try the other 2.1 build but I think this could be the end of 2.1 for the time beeing and going back to 1.6 while waiting nexus to be out in france
Is there any way to run this with the classic haret method (all files into the root of sd card)?
k_o_t_s said:
Is there any way to run this with the classic haret method (all files into the root of sd card)?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=600154
and follow the sdcard install method.
Hi, I installed this with the SD Method to use it from WinMobile
I once was in android but had to restart because I did not turn off key lock in windows mobile before.
But now i can't boot into android or only at 2% chance.
I get ther error "msm_i2c msm_i2c.0: Error waiting for notbusy" and android wont boot. What should I do?
I have partitioned my 8GB SDHC with gParted to "7GB Fat32/270MB EXT2/271MB EXT2"
Polarfuchs said:
Hi, I installed this with the SD Method to use it from WinMobile
I once was in android but had to restart because I did not turn off key lock in windows mobile before.
But now i can't boot into android or only at 2% chance.
I get ther error "msm_i2c msm_i2c.0: Error waiting for notbusy" and android wont boot. What should I do?
I have partitioned my 8GB SDHC with gParted to "7GB Fat32/270MB EXT2/271MB EXT2"
Click to expand...
Click to collapse
Just reboot to WM and run haret again. After two or three attempts the
Android boot works without "Error waiting for notbusy" messages.
Regards,
Stefan
You are right, but now I enter my pin it says sim is locked and i can't unlock the phone.
I already did deactivate throttlelock and keypad lock in winmo.
Also the pin-pad is too large for my polaris.
What can I do?
And another question:
In the haret.zip there were two images, zImage and zImage-eclair.
Did I install Donut, because in my default.txt there is
set KERNEL zImage
Click to expand...
Click to collapse
and not zImage-eclair
if installing 2.1 than change in default.txt to zimage-eclair
if 1.6 leave it as zimage
Ok then obviously I installed donut 1.6
And I will redo with eclair 2.1 and see if I have the sim locked error and too large screen there too.
For you information, I just went back to Warm's Donut as any 2.1 build only allows me to call once then the audio will stop working. Ergo I need to reboot after each call... not usable !
Maybe people can tell me if they have the same problem or not ? Maybe it has to do with the radio that I'm using ? (I haven't updated since more than 1 year)...
st_voss said:
Just reboot to WM and run haret again. After two or three attempts the
Android boot works without "Error waiting for notbusy" messages.
Regards,
Stefan
Click to expand...
Click to collapse
This is really annoying, because it means you can only boot at 20-30% chance.
And every time I have to wait until win mobile has rebooted.
raist1976 said:
I don't find it really that slow...
Click to expand...
Click to collapse
Don't know why, but it's really slower than all hero or tattoo builds I tried, to make a comparison.
Maybe my SDCard isn't in its best days...
Same with eclair, keypad really to big. One complete row is missing, numbers 7,8,9,0 and enter. (even though I set lcd.density to 128 in default.txt)
And the display always turns off after one second till i use the jog wheel again.
I cant enter the pin.
OK, I just read that with "turn off pin in win mobile" it is meant to turn off phone-sim pin. And not device pin. Then I will turn on my phone in win mobile to turn off pin requirement and see if android works.
--------------------------------------------------------
Need help again.
Eclaire runs pretty smooth, I had worse expectations.
But when I click on the android logo to start, I then click skip and the only option left is to create a google account or log into an existing google account. Even if I log into the account it says I can add more google accounts or press back. But if I press back I get to the google thing again.
And more worse it costs 3G data, 0,09€/minute
EDIT: I did turn off my phone function in win mobile and instead did turn on wifi. Then it took my again 3 times to boot android, but now the wizard no longer blocks android gui. yeay
How can I turn off the phone function in android?
EDIT: found it under "Modem" pretty weird
EDIT2: Im not quite sure, but i think phone is still on, where the hack can I shut off the usage of phone
Kiiv said:
Don't know why, but it's really slower than all hero or tattoo builds I tried, to make a comparison.
Maybe my SDCard isn't in its best days...
Click to expand...
Click to collapse
Well ... after putting back the warm donut I do can see the speed difference...
But over the two eclair builds, the kaiserdroid seemed the fastest.
There are some speed problems for some actions, but most of the time it's usable.
Anyway I went back to donut hoping to fix my problem of "one call allowed or reboot" without success... might be the new nbh that I flashed lately ... or the radio not compatible ?
I can't boot again. I tried 9 times and it show "error waiting for notbusy" every time.
Does this come from taking out the SIM card? I did this because I found no option to deactivate the phone function in android.
EDIT: Now I set the "ppp.nostart=1" and could boot into android after 2 tries withot SIM card inserted"
Wifi is really sloooooow
It is only tech-demo, wifi not really good, market place does not open, keyboard too large (fills 80% of screen), many other things.
I'll wait either for a better version of android for polaris or till I can afford a HTC desire
I have flashed my Polaris using the same nbh and rom as described in the first post. To fix the density, I tried to edit build.prop file from 160 to 120 using Astro but Astro will not save my changes to the file. I checked the file properties and I do not appear to have rw access even after issuing the $"su" and #"mount /system -o rw,remount" commands using the terminal program. I am not very Linux savvy ... have I missed something? Thanks!
I'm going through this problem for almost 4 weeks, just when I was away of a computer by 1 mile..
I was getting problems to connect to internet with my PDA, and nothing worked.
Then some apps stopped working (like Messenger, Internet Explorer, and such included apps) and I decided to format my phone by using the HardSPL method. Installed everything again, and then everything was working fine.
After a few days, the buttons stopped working: Couldn't answer calls, or use D-Pad, couldn't get off standby mode and so on. Every time I needed to use my phone, I got to hardreset the PDA, wait it to power on, and use it. It was VERY annoying. So, formatted again and installed a new ROM. Everything worked fine and after a few days, again.. Couldn't get off standby mode.
I read somewhere that it happens when the SD card becomes faulty. It was. I formatted the SD and copied all the contents again. Formatted again the phone, and installed everything again. After a few minutes (yes, minutes), the phone wasn't responding again. I got to plug the headphones and press the HF key and sometimes it got back from standby.
When phone is kind of.. "null", I can't receive calls. SMS are rejected. But the power, Bluetooth and Wifi light keeps blinking as it was active.
I'm using a temporary phone right now. I can't handle it anymore. But I miss my PDA :S
A bit more info: I'm using Spanish NiAX WM6.5.3 ROM. And first ROM was Spanish NiAX WM6.5.1. Maybe it's a ROM fault. I don't know :S
Suggestions?
Thanks in advance..
PS: Read some other threads about this. Switched 3G/2G, changed SIMCARD and SDCard and still not working
EDIT
The problem is my Polaris has a couple bad blocks on its NAND.
In traditional english: The support of the OS (AKA Windows Mobile, or Android, for example) is damaged, so in certain points the data written becomes inaccessible or has trash data. That's the reason the phone doesn't wake up.
I can happen too if you have a faulty SDCard. The point is: Some data couldn't be read.
Currently I'm researching about how to live with this. There's nothing to do with Windows Mobile as far as I know, but we can make it work by using some custom set-up of Android.
I'll let you all know if I get some news, or see HERE where I'll post everything I find
Regards!
Bump!
Please, I'm travelling this week and my temporary phone now is broken, too...
PabloMDiez said:
and copied all the contents again.
Click to expand...
Click to collapse
That could be your problem(corrupted files) Check for viruses too(Not too careful)
Thanks A LOT for your answer.
I think that can't be the problem, since I formatted the SD card and put all the fresh content again (music an cabs from my home PC).
I found out that a new fresh installed rom works fine, until I install any cab.
The cabs I have, are stored on SDcard and installed to Phone Memory.
Maybe CABS are faulty. Or it's not recommendend to install from the SDCard.
I'll try installing the new rom again, and Installing all cabs from Activesync.
I'll publish any news.
Thanks!
Still not working.
I read somewhere that this is caused by SRS WOW with Security off patch.
tomorrow I'll reinstall the rom again, and all the software without that cab.
Worked fine for 3 minutes, SDCard wasn't plugged and failed once installed Simcard.
What comes into my mind, try downgrading everything to official HTC ROM, by everything i mean also radio(unplug sdcard and simcard when flashing)
Then check if it works, if not maybe there's hardware fault.
Try different simcard too.
What software are you using?
I suggest you follow pcarvalhos or alexander-voigt instructions on how to flash (basically you have to flash official wm6.1 before flashing a ROM if you observe stability issues) and then flash pcarvalho, alexander voigt (or mines). It should work if you follow the instructions exactly. Then try again Niax' rom
Post #1 updated about the reason of this.
Regards!
Greetings people!
Yesterday I got this message while booting up my TP (latest official ROM):
"The device is unable to boot because either you have turned off the device incorrectly or tried to install an application from untrusted source. Press END to reset your device or press any other button to cancel. This operation will delete all your personal data and restore the device to its factory default settings"
However apart from that message, phone works flawlessly without any noticable change in speed or stability! The only apparent problem is that it takes a while longer (about 10 seconds) to boot up because of that message. I tried a couple of backups, problem was solved at first, but returned later...
I do take daily backups, but since I hardly monitor my phone when I reset it, this problem could have been caused by an app or reg entry a while ago... and searching for the appropriate backup will be a pain in the ass.
Since there's no change in speed or stability, do you think it would be wise to keep using the phone as is, or is it possible this would cause further problems down the road?
Any other way to troubleshoot it (at least to find the program that's causing this) other than a hard reset?
Edit: couldn't wait so I reverted to a week-old backup, installed back most of my applications, and it seems to be fixed (for now)
Update! I just tried a new SD to try XDAndroid, and guess what, the error disappeared!
So there must be a program I had installed in the storage card, possibly trying to start a service or something on every reset... and failing.
Is there a way to troubleshoot this? Maybe through SKTools or anything similar? I have a ton of apps installed into storage card and it will be a pain in the back cover to try by trial-and-error.
Thank you in advance
edit: inserted my old storage card again, error did not appear, problem solved! At least for now
Still if anyone knows how to troubleshoot this, please let me know
Update: Seems this error occurs every time I use SPB backup.
Yesterday, after a scheduled backup, the error came back. To troubleshoot this, I removed the SD card, did a soft reset, the error was gone! I took another manual backup, and again, the error came back.
So there must be something happening with SPB Backup and my SD card. Probably messing with files on the SD, or the driver or whatever (no idea there, I'm a total noob when it comes to software).
Moved the issue to the SPB forum
I have this message to, but I have never used SPB Backup
Well, in my case, it was obviously something tampering with the SD card (even if not SPB backup, something else)
Have you tried rebooting your phone with the SD card taken off? I just wait till it boots normally, and then insert it back. Works for me every time.
If that still happens, that probably means whatever is causing the problem is in your main memory.
akpidis said:
Well, in my case, it was obviously something tampering with the SD card (even if not SPB backup, something else)
Have you tried rebooting your phone with the SD card taken off? I just wait till it boots normally, and then insert it back. Works for me every time.
If that still happens, that probably means whatever is causing the problem is in your main memory.
Click to expand...
Click to collapse
Well I tried that just to see what would happen and I did not get the error message. So it is something on the SD card, but booting without it is not an option for me as I have several boot-start apps that are housed on it.
Perhaps one of those apps is broken?
As far as my case goes, I kept on using it for three months after the error appeared, without noticing any lag or issues at all. The only downside was that it took me three minutes to boot up, something I got used to.
If that's no big deal for you, I'd suggest you just leave it as it is for now, and check for lagging or specific applications failing (maybe one of them will be the app that's causing the problem?). If nothing happens down the road I think it could be safe to leave it as it is.
Now, if you can't stand this, I guess the only practical solution would be a hard reset. You can always play around with removing/reinstalling those apps you mention (or even better, installing them in the phone's memory) to check if and which one is broken, but I can understand that this not only will be a huge burden, but you may come to the conclusion that no specific app is causing this and something went south in the OS.
Personally the only apps which include a boot-up service I have installed into my SD are Football Monitor and PocketWeather. I tried removing both of them them back when I first had that issue, it didn't work...
Sorry I couldn't help more :/