Develop Bugs

Xda Exec - hangs right after restart...

I did NOT (for example) changed/upgraded ROM. I just put new 2GB SD card and scanned some folder on it in Today Player for mp3s. It hanged. So I restarted it, aaaand I can't get to my phone at all
Sometimes it gave me message with something about Voice Commands (and hanged) and now it just hangs on Today screen - bottom "buttons" (Calendar/Contacts) aren't displayed on the screen, but everything else looks "proper". It just isn't reacting to _anything_ (I mean keyboard or touch-screen).
update1: I just noticed that Calendar and Contacts _do_ appear for less-than-a-second then disappear - and at this moment system gets unresponsive
update2: the message that sometimes appear is: "Voice Command has encountered a problem. Restart Voice Command and try again.". I googled for it but nothin helpful.
HELP!
Of course I will probably try to perform some ROM upgrade, but... (for various reasons - don't ask) ...I didn't perform any synchronization. Is there any way to backup data (most important being Contacts and SMSes) ..before performing any ROM upgrade (and assuming it will going to work)... ((
Funny thing is: I was postponing ROM update (from current 6.0) for some time, because I didn't want to loose any data...

Have you checked your battery?
Are you sure you flashed a ROM according to your RAM capacity? (128Mb or 64Mb)
Have you done a hard reset?
Please have a deep read here:
http://forum.xda-developers.com/showthread.php?t=549207 (post 2)
Hope it helped,

1. I did NOT flash the ROM. It happened "by itself". the only thing that I could suspect is TodayPlayer trying to read folders recursively and writing something in memory.. (some kind of buffer overflow?) ..damaging the content.
2. I don't want to loose my SMSes and Contacts, so I didn't try hard reset *yet*. It's the last resort and basicaly I would be willing to even desolder the memory to get the data from it - even loosing the phone. (yes. everyone -including me- will now say: if those data were so important - why didn't you made a backup? that's why I said in my post above: "don't ask")
Is there ANY way to get to those data from software that boots from SD card? I mean - when upgrading the ROM - is there any way to backup other-than-rom contents to SD card?

Sorry to ask a simple question, but can you connect via active sync, or is the system unresponsive to this too?
I don't know what 'Today Player' is, but it sounds like that it cached stuff to the main memory (maybe making a database of music files) and has filled it up without respecting to leave any memory for the OS to use.

no prob.
I tried that and apparently it freezes cold within that fraction of a second. computer reacts to "new device" but then ActiveSync hangs because it's already unresponsive...

Lingering EVO issues (SD Card, Camera, etc.)

I'm having some lingering issues with my EVO even after running OTA updates. I am running a rooted stock ROM, currently software version 1.32.651.6 (I have not attempted the latest OTA update yet).
In particular are two problems - SD card issues have remained even after the OTA update. This was present even before rooting but after installing the first update (I went to a "full-service" store on opening day and they set it up themselves, assuming everyone would want it - luckily I could still get root). Issues include the Camera application reporting permissions problems randomly when trying to save pictures to the SD card, HTC's music application freaking out and coming to a near freeze trying to crawl the SD card during one of its troublesome spurts, and files disappearing from file explorers. So basically run of the mill, pre-first-OTA sd card problems. But occurring after the update and both before/after rooting.
Second is a problem with the camera itself. When first booting, HTC's included photo/video application will instantly crash after showing the camera icon on the black background. Google Goggles freezes for about 10 seconds then reports it was unable to connect to the camera. After the phone being on for about half an hour, these issues (seemingly) go away until the next reboot.
Last, and least frequent but still troubling, is a problem with the device powering on. At least twice I have been unable to get the device to turn on after powering it off, forcing a pull and replace of the battery to get it working again.
As far as I know, all of these issues could be either hardware or software. Even the power problem - my best guess is that the phone never powers off fully, but is instead locked inside of a deep sleep state and thus can not turn on until a battery pull forces the entire system off.
The questions being - first, are there any known solutions to the above problems? I have found many threads in particular regarding SD card issues, but none that seem to report these problems post-update. The others I have seen little to nothing about.
Second - if there are not known solutions, would it be prudent to return the phone as it may likely be a hardware problem?
Since it seems I'm forced to take the last update if I get a replacement, I may likely have problems getting a full root back. I'd like to avoid that if possible - having root works wonders for doing application development using non-native (unexposed) API's (Which - side note - since I'm developing for 2.1 at the moment, other than hacking for direct access to a Surface, does anyone know of a _fast_ way to do direct blits from native code? glTexImage2d is insanely slow).
Thanks all any help. Again, apologize if any of these are solved and gone problems, but I wasn't able to procure anything myself.

I'd go for the replacement, sounds like a defective unit..
Be sure that the folks here at xda will get root working regardless of OTA.

replace the unit, i'm very particular about my phones, if there is anything wrong with it I replace it.

I too have the SD card issue, I have updated, i have rooted, re-rooted, flashed new rom, different roms (fresh and sd) and it has always given me the sd card issue. Sometimes it wants to be a pain and not work at all, sometimes its good for at least a week or two. I am waiting for a little longer to make sure when I get a replacement its a newer version.

SD card permission errors --- POSSIBLE FIX
I hope/think/believe I fixed this error for those interested, I use my EVO for work and need it to work without a hitch....
Here goes (**Note i am a noob with smartphones with a dangerous amount of IT knowledge - disclaimer for those brave enough to browse around the root files and SD card files; I am not responsible for you bricking your phone, I am only trying to help those in need and putting in my 2 cents_)
Download and open the app ---> Root Explorer (or any other root explorer for that matter) from Android market.
Once Root Explorer is open (look up top/left it will say) Mounted as r/o (means read only) - press the white button to mount it as r/w (read & write)
Press and long hold on the SD card directory (folder) - you will get another window from which you must select the permissions option.
Under top option USER - check all marks -- READ WRITE AND EXECUTE & click OK.
VERY IMPORTANT - Click on the (white button) Mount as r/o to write protect your root files on your phone again.
I just applied this fix about 45 mins ago and seems to be working......updates to come if issues persist or re-surface. (**Note I could not see photos or play music and some apps were also giving me FCs (intermittently) due to permission or write errors to SD card; and now it seems to be working like nothing ever happened.)
What I have ::: stock ROM on EVO supersonic with recent HTC updates applied - standard 8Gig SD card provided with phone / had rooted but put back stock ROM for preference issues.
Hope this info helps some folks...very frustrating issue.
Cheers

SD card permission errors --- POSSIBLE FIX
ONE LAST SIDENOTE COMMENT -
I transfer data to my PC often (running Win 7 32bit_)
It is crucial that you right click on "safely remove hardware" icon on the lower right side (next to date and time) and WAIT until windows tells you
..."It is now safe to remove your hardware" --- I was just taking the plug out when done and it appears as if that could have started or compounded these issues with the SD card.

I too get the could not connect problems at times. And I have lost access to the SD card a few times. Some say its Fring that causes the problem. But after removing it I still have camera issues. I noticed that having the LED Light on while trying to open the camera will cause this problem.
I am running CM6 RC1 so this is to be expected from Release Candidates. Sit tight. It will get fixed.

Well after a full 24 hrs...no issues with the read write error on my EVO SD card, I think that when the phone is removed from PC incorrectly (i.e. pulling USB cable out in mode other than "Charge only" i.e. HTC sync, Disk Drive, Internet sharing - it causes it to "corrupt" the permissions on the SD card - It is still working like a champ and i am waiting impatiently for my EVO Froyo update ... feedback appreciated for those whom tried this fix and had it work....txs

@LF142
Hi there. So I followed all of your instructions above and downloaded Root Explorer. However, every time I change the permissions, they don't save. User, Group and Other is always switched off at root level. Do you think this may mean my SD card is corrupted?
I rooted it with BakedSnack.
I now want to un-root it as I miss taking shots, looking at my shots, listening to my tunes etc.
But I want to keep all my apps. All my texts and everything else. Whats the best way to go about this? I am also a bit of a n00b and I apologize if this is in the wrong forum, but when Froyo releases tomorrow (apparently) do I have to unroot to receive the update?
Thanks

[Q] Tiny's CM10.1 Nightlies and bcache

Hiya Folks,
Long time listener, first time poster.
I have a few questions:
a) Tiny, thanks a lot for your CM10.1+evervolv device tree builds, these are awesome. One question for you: Is there any chance you might be willing to post a short changelog when you post new builds? I understand that's a bit of an administrative headache, but it would be really nice to be able to get a sense, at least on a coarse level, as to what's new in each build... (ie: merged new display driver, picked up CM10.1 changes from x date to x date, explicitly tried to fix x)
b) With the initial jump to these builds, I took a full backup and started over. I've found that for some of the nightlies, I can just wipe caches and install the new OS image and everything seems to work. This, of course, is largely dependent on binary compatibility between sqlite versions, etc and high level compatibility between database schemas. Is there any way you could perhaps give a sense as to whether or not anything has changed that would definitely require a full wipe versus this build contains stuff that probably won't make a difference with each build along with a big disclaimer absconding any responsibility if things go wrong?
c) The camcorder is recording at a very low framerate, this is a known issue. Is there a fix coming down the line any time soon? I'm proficient with both userland and kernel hacking, and know my way around Android's internals pretty well. Do you have any information on what's causing this bug. I might be able to hack around a bit with it, but some sense of the history and the components involved would be helpful. (I have a sneaking suspicion this has to do with the video drivers and the sync to vsync stuff that is new in 4.1)
d) I've long been fascinated by the strange situation involving the scantily documented /datadata partition. My understanding is that this is some kind of faster chunk of hardware flash that is used by application databases with the idea being that it speeds them up. I believe ext4all mod moves the stuff onto the sdcard or regular internal storage and then symlinks. Has anyone considered playing with the Linux bcache module that allows faster storage block devices to serve as a cache over slower storage block devices in the storage hierarchy? I've been thinking about hacking on this myself, but I wanted to see if anyone has considered it and if it would cause problems that I don't see now (I could see it causing a problem with the current way nandroid backups are taken, or something along those lines, for example).
In any event, thanks for listening!

I'll try to summarize a, b, and c.
A. No official change log. I don't have time to write one. I try to post significant changes when I can.
B. I almost never wipe with cm. In theory you can even upgrade from cm10 to cm10.1. Wiping is overrated and its usually only useful to troubleshoot really weird issues.
C. The camcorder lag is likely a software or codec issue. Technically its not a bug but more of optimization issue. Preview glitching I'd call a bug.
Sent from my Galaxy Nexus using Tapatalk 2

a-dub said:
Hiya Folks,
Long time listener, first time poster.
I have a few questions:
a) Tiny, thanks a lot for your CM10.1+evervolv device tree builds, these are awesome. One question for you: Is there any chance you might be willing to post a short changelog when you post new builds? I understand that's a bit of an administrative headache, but it would be really nice to be able to get a sense, at least on a coarse level, as to what's new in each build... (ie: merged new display driver, picked up CM10.1 changes from x date to x date, explicitly tried to fix x)
b) With the initial jump to these builds, I took a full backup and started over. I've found that for some of the nightlies, I can just wipe caches and install the new OS image and everything seems to work. This, of course, is largely dependent on binary compatibility between sqlite versions, etc and high level compatibility between database schemas. Is there any way you could perhaps give a sense as to whether or not anything has changed that would definitely require a full wipe versus this build contains stuff that probably won't make a difference with each build along with a big disclaimer absconding any responsibility if things go wrong?
c) The camcorder is recording at a very low framerate, this is a known issue. Is there a fix coming down the line any time soon? I'm proficient with both userland and kernel hacking, and know my way around Android's internals pretty well. Do you have any information on what's causing this bug. I might be able to hack around a bit with it, but some sense of the history and the components involved would be helpful. (I have a sneaking suspicion this has to do with the video drivers and the sync to vsync stuff that is new in 4.1)
d) I've long been fascinated by the strange situation involving the scantily documented /datadata partition. My understanding is that this is some kind of faster chunk of hardware flash that is used by application databases with the idea being that it speeds them up. I believe ext4all mod moves the stuff onto the sdcard or regular internal storage and then symlinks. Has anyone considered playing with the Linux bcache module that allows faster storage block devices to serve as a cache over slower storage block devices in the storage hierarchy? I've been thinking about hacking on this myself, but I wanted to see if anyone has considered it and if it would cause problems that I don't see now (I could see it causing a problem with the current way nandroid backups are taken, or something along those lines, for example).
In any event, thanks for listening!
Click to expand...
Click to collapse
d) The /datadata partion is just a normal partition but is formated yaffs2, which is a little faster than ext 3 which is what /data and /cache normally use out of the box. However this partition is small, and fills up quickly. The ext4 mods do 2 things, they convert /data and /cache from ext3 to the slightly faster ext4. It also moves all of the files from the /datadata partition and instead placed the files on the /data partition in a data folder. So it still ends up having the path /data/data just as it did before the mod. This leaves the yaffs2 /datadata partion empty and unused.
I havent heard of bcache, so im not sure on that question. If you could get bcache to use the old /data/data partition as cache for the other partitions it might provide better performance. It shouldn't cause backup issues as /datadat is already backed up by nandroid, so all required filed should get backed up. If you get it working, i would definitley check it out.

[Q] [Please Help!] Recovery of Data from Factory Reset on SGH-I747

My company's IT department set an enterprise-level Exchange 2010 ActiveSync mailbox policy that enables a local device wipe after multiple failed password attempts. My child was playing with my phone and apparently enacted this, creating a factory reset and complete wipe of my phone. I am now looking for any way to recovery the hundreds of pictures (and videos and other data) that were stored locally on the phone's internal memory. Note: I do NOT have an SD card and unfortunately I did not back up the files in the cloud or anywhere else. (shame on me)
I have scoured this board and others and been unable to find a solution or work around. Or, the things I've tried have been thwarted by issues. (example: apparent inability to enable USB Mass Storage (UMS) on an un-rooted device?) I'm fairly savvy with computers (mainly Windows) and am very logical and methodical in troubleshooting but I don't have dev experience, Linux familiarity, file recovery experience or any advanced knowledge in this area. I would be very grateful for any insight. My basic question is this:
Question: How can I recover deleted files from a stock 4.1.2 SGH-I747 after a factory reset?
I will actively monitor this thread and answer any additional questions. Thanks in advance for any help or guidance!
admitch4

Just wanted to bump this thread as I am still desperately trying to find a solution.
Also, here is an update/recap:
I have a Samsung Galaxy S3 (SGH-I747) running Android 4.1.2. My phone is rooted. A factory reset was inadvertently performed on the phone that wiped the entire internal memory (I do not have an external SD card). I had many very important pictures of my children, family, etc. that I would really like to get back if it’s at all possible. I installed DiskDigger and performed a scan for all .jpgs. The tool sees “/data” of 12.24 GiB (and other devices) but the scan does NOT result in any files. Does this mean none of the files are recoverable? Or, would it help to try another tool? I’m happy to purchase DiskDigger Pro or try anything else if it will help at all. Or, I'm also up for trying much more drastic measures if there is a reasonable likelihood of some recovery. Thanks in advance for any information or feedback.

Snipped
Hi, you should try "UnDelete"
https://play.google.com/store/apps/details?id=fahrbot.apps.undelete&hl=en
This may or may not work on the phone as long as you didn't overwrite many files. ( I have not tested hard resets.)
Thanks
EDIT : Sorry! I was wrong! I just tried a different app, and it recovered half of a deleted image on a phone I was repairing. Its called DiskDigger.
Search in /data (that is the internal SDcard)
https://play.google.com/store/apps/details?id=com.defianttech.diskdigger&hl=en

[Q] Phone resets to Jan 1, 7:00pm after restarts. Many apps not working.

I've been having a very odd bug that started to occur today.
Whenever I restart my phone, battery pull, or turn it off and on it resets to Jan 1st at 7:00pm. Some apps are not working, including BBM (msgs don't attempt to send), Snapchat (gives me a "Google Play not supported by device" notification), and Google Play (no connection error).
Because my phone is "in the past", whenever I send or receive texts they do not appear on the message log due to their time stamps being in the future (I assume so).
What should I do? Should I wipe and re-root. I'm running Liquid Smooth JB 4.2 ROM and have been for nearly 6 months for no issues. I wouldn't expect it to be the ROM.
Another thing, If I do wipe and re-root, how would I completely wipe everything minus the core things? Let me elaborate: I've been having a problem caused by CWM where it is creating multiple "0" folders (which are created to store all the files every time I install a new ROM). I think it's at about 7 files deep now due to switching ROMs daily about 6 months ago. This leads to a very messy internal SD with files all over the place. How would I fix this so it goes back to the normal file structure, pre-root? Do I have to go delete the files by hand on via my PC?
Another thing, what method is recommended to save my People contacts, messages, app data, etc (preferably on an external back up: PC or external SD)?
Thanks in advance!