benslgdroid
rockstar
I've always had to do ext4
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
I'm assuming you've made a nandroid of your current setup, done a complete wipe and format of boot system data and cache, and reflashed the ROM and gapps, rebooted, signed in, synced, and then attempted to get MMS to work?Jerry, today I tested the MMS thing a little. My wife sent me 2 pictures and I never received them. I had her resend one of them and again nothing.
At lunch I did a restore of my stock backup from 9202011 and was able to get the picture message from her almost instantly. When I made my stock backup I was running Link2SD (an am no longer) so I have virtually no apps able to be used (including market, root explorer and GO SMS) and am unsure how to get them back onto the phone. I guess I could do a factory reset from recovery and then reroot et al.
After I did a restore, I tried again to get an MMS from my wife and still couldn't.
The main difference between the two is GO SMS and right now I can't get GO SMS onto the stock. I did load the stock messaging app in the BACKside and didn't get anything that way.
No, you shouldn't need to flash gapps anymore. I worked out the signing issue a few builds back.
Just FYI if anyone wants themed versions (including an Ice Cream Sandwich theme) of Swype I found it here: DA Swypes DJDarkKnight ^_^
This happened to me with one of the builds I flashed back in September, but only when using the flashlight app I have.one problem i have thats been happening with all of the builds i have tried thus far, is that when i tap my power button to turn off the screen, very often it shuts off the screen for just a second and turns back on. So to turn off my screen and keep it off, sometimes i have to push the button a few times.
ok, i'm updating Bob Z's new rom as we "speak" so i'll give you link2sd play by play.I just tried following those steps and I keep getting this error message in link2sd. I'm not sure how to fix it. The 2nd partition on my sd card is fat32. I tried unmounting and remounting the sd card. Didn't help.
I restored my backup of the 10/17 build for now.
This build, no I have not. I did after the 1017 build I believe it was. Usually every other build or so. I will do so tonight.I'm assuming you've made a nandroid of your current setup, done a complete wipe and format of boot system data and cache, and reflashed the ROM and gapps, rebooted, signed in, synced, and then attempted to get MMS to work?
Unsure of a logcat and a dmesg. I can and will do both, but do not know how.If that's the case, please give me a logcat while attempting to use MMS (have your wife send you an MMS, and send to yourself both and SMS and an MMS), and a dmesg at bootup.
ok, i'm updating Bob Z's new rom as we "speak" so i'll give you link2sd play by play.
i back up Jerry's latest and do a complete wipe
restore the last bob z from back=up
reboot/ recovery wipe cache and dalvic cache only
flash the new bobz zip
reboot and wait for the link2sd "mount warning" in the notifications bar
when i press this i get mount warning notification, ignore this DON'T quick reboot
i hit the return key am on the link2sd page
press menu, press "more", press "recreate mount scripts"
"select file sys." comes up. if you are FAT32 press it and press ok
it says "restart your phone" so press ok and reboot
waiting, waiting
phone comes on grooveip and lookout self-activate and all the link2sd
apps are back
one problem i have thats been happening with all of the builds i have tried thus far, is that when i tap my power button to turn off the screen, very often it shuts off the screen for just a second and turns back on. So to turn off my screen and keep it off, sometimes i have to push the button a few times. Also when the screen is off and i go to turn it on, sometimes the hardkeys or whatever light up and the screen doesn't, so i have to wait a few seconds for the screen to come on or keep pushing the button till it corrects its self. Any ideas to what may be causing this?
This build, no I have not. I did after the 1017 build I believe it was. Usually every other build or so. I will do so tonight.
Unsure of a logcat and a dmesg. I can and will do both, but do not know how.
su
dmesg > /sdcard/dmesg.txt
su
logcat > /sdcard/logcat.txt
NICE work on the update checker app. Works great. For some reason, it doesn't detect that I have the latest version installed (still says update is available), but it's a great start.
The update checker has a really stupid bug in it, I put a ">" when I should have used a "<" to check the dates. I'll have it fixed in the next build.
I did the full wipe of everything and everything is working currently. If that changes I will post the logs. Although I'm not sure what kind of log I'd get from not receiving an MMS.To grab the dmesg, open terminal and type in:
Yes, it's my first attempt at this type of app. I hope to extend it to include an option to receive update notifications in your status bar. This will be optional since it will use a bit more battery, though I only plan to have it check for updates once a day, so any battery drain shouldn't be too noticeable.
I did the full wipe of everything and everything is working currently. If that changes I will post the logs. Although I'm not sure what kind of log I'd get from not receiving an MMS.
It isn't that bad. Just glad it is working again. This was a much more thorough wiping than I normally give when I do a fresh install. I'll make sure I clear everything like this next time I do a wipe.Glad it's working for you again. It's a pita to have to do that, but it's the only solution when you get corruption in certain parts of the system.
What you are describing mostly sounds like proper behavior. There is a delay that must be reached after turning the screen off before it should turn back on. This is to keep the screen from coming on when you put it in your pocket right after pressing the power button to turn the screen off.
However, the non-proper behavior you describe could be due to background processes lagging at that moment.