Database Develop

A stable configuration

Hello everyone,
I would like to start this new thread with a different purpose than trying to explorer the latest and gratest of releases of ROMs, extensions, software and patches.
I have tested many of the releases posted here and I have yet to find one that offer a rock solid unit that can be depended on in all situations.
What I would like is to put together a package based on the best of all available that offer the highest reliability available for our device.
It's very annoying to have to reset the device, somtimes more than one time in one day because you loose GPRS connectivety or because you turn on the WiFi card at an unlucky moment and lock up the device.
It's very annoying that you press the answer button repeatedly but have trouble picking up the rining phone.
It's very annoying that you try to make a call, but the phone keeps hanging up without making the call until you reset the phone subsystem.
It's very annoying that you pick up the device to make a call only to find that for some reason the phone has been locked up for hours with the screen on and now you are out of power and far away from your charger.
It's very annoying that your screen gets garbled and you find that you are unable to get the display back to normal without resetting the device.
It's very annoying that bluetooth more or less have turned out to be a marketing item only, since we have yet to se an implementation on the device that works (and maybe we never will)
If you agree with me or/and have experienced some or probably all of the above and have some input you would like to share on what is the best release, or have software and patched that have made a difference to you, then please contribute and maybe we could one day have a reliable operating system and software pack on our PDA that we can actually trust to handle the important task of keeping us connected to the rest of the information based world 24/7.
I hope many people will participate in this thread and that we can get to a release of software that we can all feel happy about, since it seems that none of the providers have been able to accomplish this task.
Michael

Fully agreed with you. And here is my BA config:
- MDA III with 1 Gb SD (Trandcent 80x)
- ROM 1.40 & radio 1.12
- Big storage - No Extended ROM
- Excluded nearly all software from WWE 1.40 ExtROM. Install only patched
Most apps are installed to storage :lol:
- Pocket Informant 2005 (In main memory)
- Pocket breeze 5 (In main memory)
- Pocket Player 2.6
- Sound Explorer 2005
- Pocket Navigator 2.74
- Sprite backup 3.1.4
- Mobile Pocket reader 5.0
- Total Commander 2.0
- Adobe Acrobat Reader 2.0 for PPC
- Tools: Cab Installer, vxUtils, Tascal Reg. Editor TRE 0.9, calculator, stop time ...
Full backup with Sprite backup 3.1.4, excutable archive file so that I can restore to a fully loaded system righ after hard reset. The backup is also in storage.
With this config the phone is very stable. On average 1 soft reset/week, mostly due to phone problem (I work in a building with very week GSM signal).

here here!
while ive not bothered to update for exactly one year now, i truely couldn't be bothered with the rom backup, new rom, install settings, settings restore, all to find out that... oh others are still having a problem with phones hanging/not connecting, because you used bluetooth and didn't reset before using gprs. of course, silly me!
right now i'm looking for a stable basic setup, with Tomtom 5 (bt gps mouse) and gprs useage... and possibly, using them together!
it does seem experimenting is only way to do so...

What a good idea - however, after one year of updating ROMs I do not think that there is a stable system for this device after all ...
I cannot use my Qtek for business because
- I am not sure whether I will miss a call because my Qtek somehow decides not to ring
- I am never sure whether I can finish a call decently (or the devices shuts down on its own)
And I am tired of resetting the device before and after
- using WLAN
- using BT
Currently, I am on
ROM 1.42.01 GER
Radio 1.12.00
ExtROM 1.42.116 GER
which still has all the flaws mentioned above.
This is the 4th different ROM I have installed (WWE, GER). I mainly use it for storing contact info and meetings.
A

I still wan't to try.
I'm using a configuration of 1.40 and 1.12. This is OK, but the phone app is still quite unstable and the device itself will hang. Most trouble seems to be when you press a key at an unlucky split second when the unit is trying to do something else, this often leads to lockups.
Does anyone have any input regarding the version numbers to use? Especially is 1.42 or 1.31 better than 1.40? and is 1.12 better than 1.13 or vice versa?
What about patches and registry hacks, what do you consider being a vital patch or hack to improva stability dramatically ... ? If any.
I hope to get some input from you guys that install every single thing and have gained allot of input on what works and what doesn't?
Michael

This combination seems to be vert stable for Scandinavians
I have had very good results so far with this combination:
BA_DT_WWE_NorwayRetail_14000_149_11200_Ship.exe
Then install:
86794-9090_radio_upgrade_1.15.00.zip
This is so far the bes experience I have had while I had the device.
Michael

Update
After a while, I have observed that I'm still having the GPRS connect problem and I have therefore installed the:
IA_CallerID_1.20_WWE.CAB
I will update my experience in a while. So far I like this combination, except that GPRS cinnection problem. I haven't had many other problems. There has been a little "flutter" around Blue Tooth and TomTom, If you try to start TomTom with BT disabled, you sometimes seem to grid lock until you re-boot.

Extended ROMs
Is it my imagination? The higher the extended ROM version the less stabillity? It seems to me that way. The more stuff they add, the less overall stability you get. Does anyone have a different experience?
Michael

jamcow said:
here here!
while ive not bothered to update for exactly one year now, i truely couldn't be bothered with the rom backup, new rom, install settings, settings restore, all to find out that... oh others are still having a problem with phones hanging/not connecting, because you used bluetooth and didn't reset before using gprs. of course, silly me!
right now i'm looking for a stable basic setup, with Tomtom 5 (bt gps mouse) and gprs useage... and possibly, using them together!
it does seem experimenting is only way to do so...
Click to expand...
Click to collapse
i find that when upgrading to the new WM5 roms, that all my files, programs and settings, even contacts and messages are all still as i left them, i just put the device into bootloader and plonk into the cradle, then start upgrade 2 mins later its done, all new features and nothing that is usually backed up is changed.

The best stabillity so far
I'm still running with the configuration outlined in my previous posts. And it's pretty stable, the only problems I seem to be affected by are:
After 1 to 7 days the GPRS connection fails and I have to reset the device to get it working.
Rarely some applications and the phone gets in a bind somehow, probably by starting at the same time in an incompatible way and lock up the phone. I have to reboot the device to get out of that.
The phone part itself seems to be stable and I have no missing sound or low volume issues.
I had good bluetooth functionality, but since paring my device with my GPS I can't get the device to connect correctly to my headset. I will pair up and then when it tries to connect it fails. I'm unsure what that's about. I don't use the bluetooth headset much, so I haven't been bothered much by this, but I would ofcourse prefer if everything was working as you would expect it to!
I would upgrade my base ROM to 1.42, but my testing and experiences with that have been that it's more unstable than 1.40.
I'm even more convinced now that I'm right about the extended ROM thing, the higher the version of extended ROM to more problems (potential problems).
Any input on stability are very welcome, I would love to find a near perfect configuration where most things work 100% and all the time.
Michael

Cing8125 users: 217 ROM w/CF2,ringers,themes and A2DP on ftp

I suspect this is as close to the perfect ROM as I can make for you folks, until I find something else universally useful to add..
This ROM has the following characteristics:
-Based on QTek 2.17.7.102
-OS 5.1.195 Build 1487.2.0.0
-Radio 02.07.10
-Protocol 412.1.03
-Includes assorted ringers, themes, OmapClock, and yes, A2DP
- .NET Compact Framework is integrated. It is build 2.0.5238.0
- .NET Compact Framework 1 has been left in. Build 1.0.4292.2
-Did I mention it has A2DP integrated?
-It is not coded to a specific carrier, so theoretically you shouldn't have to CID unlock. HOWEVER, I ask, no, I demand that you CID unlock before installing. Only then will you be allowed to grovel in the forum for help if you run into problems achieving a successful flash.
-Each morning at 7am it will gently vibrate, go start the coffee maker, fetch the newspaper, feed the dogs, and start your bath. Should you leave it at home it's likely to cuddle with your wife...it has no loyalties.
It can be found here until it gets moved:
ftp://xda:[email protected]_RUU_WIZARD_217_AKU2_WWE_CF2_A2DP.exe
If anyone asks me to make this ROM using 2.08 I'll send my legions of monkeys to harass and belittle you in public.

Thanks man, this is kick ass.

MY HERO!
Dude, you ROCK!!! You have made my decision to get this phone more and more worth it. Thanks again!

A2DP Not Working
So, I CID Unlocked and installed this new ROM successfully. Then I went to the connections screen and enabled bluetooth. Opened up Bluetooth Settings and created a new partnership with my Moto HT820. Went through all the normal steps and it found Hands Free and Wireless Stereo services on my headphones device. I saved the settings.
In 2.08/2.87, at this point I would press the right ear button, which would activate Wireless Stereo mode and I would see a music icon in the top bar. It didn't happen on this new ROM. Another method is to go back to the Bluetooth settings and click&hold on the device and you see a list of services (Hands Free and Wireless Stereo) and then choose Wireless Stereo. On this new ROM, only Hands Free is listed. If I choose to edit the device, it lists that Wireless Stereo is supported on the headphones, but it is not available as a mode on the phone.
I will be going back to 2.08/2.87 for now. Let me know If you happen to figure out what's might be going on.
Thanks!

Hey Summiter .... canyou? .... are you going to? .... I need? .... would you? .... nevermind can't think of anything

A2DP not working with HT820
I've successfully flashed this ROM and tried to pair Motorola HT820 headset but it was not recognized as Wireless Stereo. It was recognized like Hands-free only.
Anyone knows how to make it work? Thanks

Does this ROM still have the issue where the device won't vibrate from standby?
Also... for those of us just tuning in...
What's the benefit of having additional components (like CF) loaded through the extended ROM? When they're installed, will they live in ROM instead of taking up precious storage space? Or is it just the convenience of having everything install from one place?
Maybe Voice Commander in the next release...?

the non-vibrate thing is part of the rom, as MS made it that way. and voice command isn't free, so i doubt he'd include it in the rom.

amg212 said:
Does this ROM still have the issue where the device won't vibrate from standby?
Also... for those of us just tuning in...
What's the benefit of having additional components (like CF) loaded through the extended ROM? When they're installed, will they live in ROM instead of taking up precious storage space? Or is it just the convenience of having everything install from one place?
Maybe Voice Commander in the next release...?
Click to expand...
Click to collapse
CF goes to main memory regardless of the settings you choose at installation (you can choose Storage Card >>> it installs w/o error message to main memory).
You can see the appropriate files in the \windows directory. They all start with GACxxxx.
Cheers
hrb

Good Stuff...
One question though. Does this still have the battery indicator moved to the top. I just flashed yesterday without issue but I'm thinking the battery indicator can be optioned. Obviously this is a miniscule issue compared to the other great work you've done. Thanx guy.
J

the battery icon at the top is part of the AKU2.

darkjedi said:
the non-vibrate thing is part of the rom, as MS made it that way. and voice command isn't free, so i doubt he'd include it in the rom.
Click to expand...
Click to collapse
I was talking about Voice Commander - not MSVC

Oi Vey!
I'm all settled in on v2.87. everything works, wifi, a2dp, btaudio e.g.
What extras is this going to buy me??
Maybe I'll hold off for a little longer.
Still, thumbs up to Summiter. :wink:

as much as a pain in the ass it is, the 2.17 rom with A2DP is MUCH more stable than the test rom.

Hi Summiter,
I'm set to receive my 8125 this week. I've been doing as much reading and bookmarking as I can until I have the phone in my hands, but I haven't seen this question posted yet.
When a user loads your ROM, does the phone start at the beginning of the customization process (setting time zones, preferences, etc) or do your customizations piggyback as the defaults? What's making me ask is I see you've mapped your camera button to the omap 252 overclock setting and I'm curious what to expect when I load this ROM. Thanks!

100Tbps said:
Hi Summiter,
I'm set to receive my 8125 this week. I've been doing as much reading and bookmarking as I can until I have the phone in my hands, but I haven't seen this question posted yet.
When a user loads your ROM, does the phone start at the beginning of the customization process (setting time zones, preferences, etc) or do your customizations piggyback as the defaults? What's making me ask is I see you've mapped your camera button to the omap 252 overclock setting and I'm curious what to expect when I load this ROM. Thanks!
Click to expand...
Click to collapse
Your phone looses all setting and resets as if you just took it out of the box. Its a pain to do over but most of us have become pretty proficient at it with our mulitude of ROM reloads ;-)

Can anyone confirm that they have A2DP working on this ROM?
For folks that have reported not being able to get A2DP working - can you confirm whether the file "bta2dp.dll" exists in your windows directory? It's a hidden file so you'll need to set your file manager to view all files.
Thanks.

Is there an upgrade in one of these ROM versions for the Bluetooth? Im having issues with my 8125 and my BMW hands free car kit. My contact list doesnt show up on my display in the car. I had a SE 710a and it worked perfectly. With my 8125 I cant get the contact list on the hands free.

If you've CID unlocked previously, and you have 2.17 now, can you just use this ROM directly? Or is it necessary to downgrade and then CID unlock again? Sorry for the noob question.

Summiter...
There has been talk and concern about the 8125 erasing data on the sd card if you set your email options to save attachments to it. I was wondering if you knew anything about this and/or the new ROM version might fix the issue.

Flashing not over SD (eg via USB)

i just received my G1, well 1.6 was installed, but: No WLAN, No SD, No Bluetooth and no File-Transfer with Win7 x64. So i'm thinking of a flash, but how?
I wanted to get diagnostics mode, but what is the capture-key?
any other possibilities to rescue this device? (I think, the SD-Card driver was somehow deleted. Tried a software-Wipe, but it didn't help.
I hope someone can help me.
Thx in advance.

Well thats sorta like asking to get into a box sealed off with ducktape using the mailbox=p. You are going to need an sdcard so you can root it. Find any microsdcard and load up rc29, root it, then flash some custom firmware on top. If you don't have an sdcard, then you can't set up root therefore no new roms. The only thing that would work without an sdcard is ADB, but you need root to do something meaningful like pushing an app, etc..

I got similar problem.. My SD card slot seems to be dead. Android and recovery as well, doesn't see any SD card slot so the SD card can't be mounted. And yes, I've already tried with another card. No luck.
So there's my question that OP already asked: Is there any way to flash update.zip without sdcard?

Short answer: No
Long answer: you can change specific parts of a rom without an sdcard (kernel, apps), but not an entire rom or update.zip.

That's what I thought... Unfortunately. So I guess it's time to buy a Sapphire.

i have a program for windows called android commander. it has the option to flash an update. i dont know if this will help but it might. i found it on XDA somewhere. i just dont remember where.
edit: it also has some other really cool features, like push and pull and copy. great if you want to push an apk to the system/app folder
edit here is the link for download of the of the version that works for me http://androidcommander.cyf.pl/?file_id=1

ok, gonna try that android-commander.
If even a hard-reset doesn't bring up the 3 issues, i think, these are Hardware-Errors. (it COULD also be, that the "drivers" from these parts have been removed/deleted from the rom by the previous owner, but a hard-reset WOULD restore the missing "drivers" or am i wrong? (i have not much knowledge about Linux, i'm more a Windows-Freak.)
I mean is it possible to "remove" parts of the "drivers" from the ROM and the Flash/EEPROM that even after restore the part would still be missing?

Until it's rooted you can't make major firmware/bootloader modifications just by sticking a usb cable into it.

sturmeh said:
Until it's rooted you can't make major firmware/bootloader modifications just by sticking a usb cable into it.
Click to expand...
Click to collapse
you mean "unless it's rooted", 'cause i think, it's not rooted (how to find out, if it is?)

satani said:
you mean "unless it's rooted", 'cause i think, it's not rooted (how to find out, if it is?)
Click to expand...
Click to collapse
Turn the phone off, hold down the CAMERA button read off the top four lines.
That will tell you if it is using a custom spl.
Alternatively you could go in the rom and type su in the terminal, that would also show if it's rooted.

the booloader info sais:
DREA110 PVT 32B
HBOOT-0.96.0000
CPLD-4
RADIO-2.22.19.261
Sep 2 2000

i tried around with the Android-Commander as said before, i also connected the phone but I was not able to copy ANY data to the phone or create any folder anywhere (so not even a custom ringtone or wallpaper), for rooting is a SD-card required, which is not useable due to (maybe) hardware defect, so i ended up the following:
I agreed with the seller to reship the G1 and he refunds my money.
From that short time playing with G1 and Android, i say as conclusion:
Well, the touchscreen works far better than any Windows-Phone, but the Compatibility with Windows is nearly completely missing - and so some for me required aspects of that phone. So i'll just buy another Windows-Device. (i's easier to flash, spl or unlock and you have better and easier possibilites or modifying/customizing your phone.

From that short time playing with G1 and Android said:
well if you would have recieved a working phone you might have a different opinion of android. i have used windows mobile as well as blackberry and simbian too. all of them have their good points but i found android to be the easiest to use and to customize(as long as the device works). but good luck
Click to expand...
Click to collapse

saprano614 said:
well if you would have recieved a working phone you might have a different opinion of android. i have used windows mobile as well as blackberry and simbian too. all of them have their good points but i found android to be the easiest to use and to customize(as long as the device works). but good luck
Click to expand...
Click to collapse
that might be true, but pay more than 150 for a phone, I only use as secondary phone for a few internet/data-activities is, considered the fact, that in 6 weeks, I'm unemployed again, a bit much to ask for, either a complete new phone or a cheap (ie less than 150 bucks) phone, that has wlan, 3g and a hardware-keyboard - rest is irrelevant - that is being used as secondary phone.
Sure, if the G1 would have been fully working, it would have been a nice device (not a replacement to my Xperia, of course, as the G1 has a minus in resolution compared to WVGA), but so is only to note: if you want a cheap Android-Phone, wait another 3-6 months, there are a lot of them coming out and so the elder ones (magic and g1) should go down in price a bit.
Sometimes, prices on ebay drop around 50 bucks within 3 months - checked on that.

Thread moved to Q&A.

[Q] USB Host support(solved)

Does nook color have usb host support??
Has anybody tested it?
If not, is any body working on it coz hardware definitely supports at least usb 1.3.
Edit: the applications are endless
usb drives,external hdd, internet data cards depnding on drivers avaliblity u can attach any hardware and ditch ur notebook.
EDIT 2 : Verygreen has it working
http://www.youtube.com/watch?v=Bovg4aBFnA8
I can't thank you enough for this green, i wanted this really bad, that's why decided to look into it too(that didn't work out too well though).

Don't believe it supports it. No idea if anyone is working on it either, but I know id definitely want it.
Sent from my D1

Looking at the nook color teardown, it seems the nook has a chipset which SHOULD support USB OTG, but it would required the drivers and OS supporting it as well.

Personally I think bluetooth support will be the closest we'll get (at least for quite a while)

rigy73 said:
Does nook color have usb host support??
Has anybody tested it?
If not, is any body working on it coz hardware definitely supports at least usb 1.3.
Click to expand...
Click to collapse
What would you do with it, beside a keyboard and a mouse?
I'd rather have bluetooth instead of usb host support.

I'd like to be able to ditch my laptop while running around the Gulf of Mexico. Between helicopter weight limits and the limits of what I can carry swinging from boats to platforms. Less is more. Id like to carry my nook and ext. Hard drive for movies.
zoom2

btw, those eager to try external keyboard already can give it a try with all the BT progress made by fattire (the real hero).
Since I want to stay on the safe side myself, I compiled this 2G SD image that you can boot into and have working bluetooth (keyboard and external audio confirmed working). Of course use at your own risk and such:
htt p:// handhelds.ru/nook/2g_bt_card_image.img.gz
go to settings -> wireless & networks
make sure that bluetooth is enabled and then you can explore and pair devices in "bluetooth settings" there.
Range so far is in the area of 13", so usable for a keyboard at least.

verygreen said:
btw, those eager to try external keyboard already can give it a try with all the BT progress made by fattire (the real hero).
Since I want to stay on the safe side myself, I compiled this 2G SD image that you can boot into and have working bluetooth (keyboard and external audio confirmed working). Of course use at your own risk and such:
htt p:// handhelds.ru/nook/2g_bt_card_image.img.gz
go to settings -> wireless & networks
make sure that bluetooth is enabled and then you can explore and pair devices in "bluetooth settings" there.
Range so far is in the area of 13", so usable for a keyboard at least.
Click to expand...
Click to collapse
May i ask about this image... is it Froyo or Gingerbread (CM7)? Working BT sounds great, but a bit more info couldn't hurt..

Divine_Madcat said:
May i ask about this image... is it Froyo or Gingerbread (CM7)? Working BT sounds great, but a bit more info couldn't hurt..
Click to expand...
Click to collapse
Ah, sorry, did not mention it.
It's CM7 from yesterday with bt patches applied on top (they were committed later on after I tested that they worked).

BTW, it's the image used by IOMonster in that video from yesterday that you referenced in the BT progress thread (I just don't have enough posts to actually post to dev forum I originally wanted to reference it there sine it seems people are eager to play with thing at least somewhat).

verygreen said:
Ah, sorry, did not mention it.
It's CM7 from yesterday with bt patches applied on top (they were committed later on after I tested that they worked).
Click to expand...
Click to collapse
Awesome! Its also nice to see CM7 as an SD runnable build. Thank you!

Divine_Madcat said:
Awesome! Its also nice to see CM7 as an SD runnable build. Thank you!
Click to expand...
Click to collapse
I think it would be useful for a wide testing if you post the link in the dev thread about bt work.
and I am sure tons of people are waiting to get their hands on this.

1.86GB .img doesnt fit on 1.84GB SD Card...bummer.

verygreen said:
I think it would be useful for a wide testing if you post the link in the dev thread about bt work.
and I am sure tons of people are waiting to get their hands on this.
Click to expand...
Click to collapse
Here is the dev thread for you - please join in when you can, and thanks again for your work!
http://forum.xda-developers.com/showthread.php?t=989637

acomiskey said:
1.86GB .img doesnt fit on 1.84GB SD Card...bummer.
Click to expand...
Click to collapse
just write what fits and then reformat 4th partition as fat.
the fat partition is empty anyway.
that way you can even write to 1g sdcard if you must, the fat sdcard partition would just be really small.

Since I cannot still post in development forum, for those who try the image and it does not work, I had some problems if you d oa soft reboot from other image into SD.
Try powering off your nook and then booting from SD.
Also if that did not work, you might want to change /system/etc/wifi/tiwlan.ini
(you need to remount /system read-write first of course)
look for BThWlanCoexistEnable = 2 line
change it to BThWlanCoexistEnable = 1
save the file
power off the nook again and then turn it back on and boot from SD.

verygreen said:
just write what fits and then reformat 4th partition as fat.
the fat partition is empty anyway.
that way you can even write to 1g sdcard if you must, the fat sdcard partition would just be really small.
Click to expand...
Click to collapse
I only have a 1Gb card handy right now so that would be great, what the best way to right that? Would Win32DiskImager do the job for writing? Not sure about the reformating part though. Thanks !

webvan said:
I only have a 1Gb card handy right now so that would be great, what the best way to right that? Would Win32DiskImager do the job for writing? Not sure about the reformating part though. Thanks !
Click to expand...
Click to collapse
I am not familiar with windows tools, sorry.
I imagine whatever you use to write the image will just write as much as it can and then abort
after this happens, start a tool you use to manage partitions on windows (volume manager? I dunno, used to be fdisk in DOS and Windows95 days).
point it at the SD card.
Tell it to delete the last partition.
Then tell it to create another partition on SD card that would span the rest of the free space and set the type to fat.
If a separate format is required, I imagine there would be a way to then format this new partition.

Thanks, will try that and see what happens.

bswett said:
I'd like to be able to ditch my laptop while running around the Gulf of Mexico. Between helicopter weight limits and the limits of what I can carry swinging from boats to platforms. Less is more. Id like to carry my nook and ext. Hard drive for movies.
zoom2
Click to expand...
Click to collapse
This would be great for me once someone get video working properly (no audio delay). Right now I would have to reencode all the video I have which is too much work.

[Q] Access Denial on Interop Unlocked ATIV S. System Apps Fail to Start

Howdy,
Lately I started experiencing access issues with the phone. One of these is the screenshot issue. The screenshot gets taken, although the phone says Couldn't take screenshot and saves the screenshot. The screenshot does not get shown in the Photos app like the app can't access the file.
Here are all of the access issues I experience, I believe they are connected all together and have the same root cause.
1. Whenever I press WindowsKey+Turn off button to take a screenshot, the phone says Saving to Screenshots... and then Couldn't take screenshot. The screenshot does not get saved to Screenshots folder. If I check this same Screenshots folder via Windows Explorer, it shows the taken screenshot is there
2. No camera app, including the built-in one, can save the taken photo. Whenever I start the camera and press the Camera button, the Camera app either disappears as if it crashed (and Start screen is shown) or the Photos app is shown instead of just taken photo. Checking the Camera roll section in the Photos app does not reveal the photo as if it wasn't taken. If I check this same Camera roll folder via Windows Explorer, it shows the taken image is there!
So the phone does take photos and screenshots but can't read them! Why?
3. Most of the time Photos app fails on start. You tap photos, it shows Loading... and then the app closes and Start screen gets shown. The other time it shows Loading... then Resuming... then Loading... again and does that multiple times. Sometimes it starts well but shows only old photos and screenshots that were taken before I started experiencing issues with taking screenshots and starting system apps.
4. Often so the Phone storage app available in Settings doesn't start either and closes after showing Loading... Sometimes it starts with no issues.
5. Music app fails to start every now and then. If I am being preserving, the app starts after multiple attempts to launch it. When it starts, it does not return to album view when you click Play on a song in an album. The app just freezes.
6. Finally, my System section in Settings|Phone storage|Phone now shows 4.29 GB (!) although it consumed 2.12 just before I started experiencing these strange issues. Seem like it has been flood with dumps and logs.
It appears the issues arisen when I replaced my 32GB Transcend UHS-I QSDXC card with a 64 GB by µSDXC from Sandisk and attempted to synchronize photos via Zune application and both WinRT and Desktop versions of Windows Phone apps.
More detail:
1. I interop-unlocked the phone and it worked for a while.
2. My 32 GB SD card ran out of memory and I replaced it with a 64 GB SD card.
3. The 64 GB SanDisk SD card appeared incompatible with Samsung ATIV S and looked as if it had been dismounted every now and then. The phone had been rebooting every 10 minutes or like and CPU was heating high.
4. I removed the 64 GB card and started the phone without the card. It worked well. The phone stopped heating and rebooting ever since I removed the card.
However, I noticed that I no longer can start the Photos app. Moreover, Phone storage also was failing start and Camera app did not make screenshots and photos.
5. I inserted the 64 GB card to my wife's Nokia Lumia 620 and it worked fine there. I put the 32 GB card back into my Samsung ATIV S but access issues are still there.
How do I fix this? Any clue is highly welcome.
I remember in Windows Phone 7.0 days, MSFT was joining SD card File System with the one on phone's memory. Could it be that storage array has been broken when I replaced the memory card?
Also could it be that something screwed with bootstrap (the phone is interop-unlocked and has been boot strapped before it's been unlocked).
Once again, the phone is developer unlocked and interop-unlocked.
I plan to hard reset but am worrying of getting my phone bricked. What if re-imaging or whatever the phone does when it resets itself (I assume it applies a WIM file like Windows 8 does it on PCs)?
Seems like inserting 64 GB SanDisk screwed the phone.
Important note: I did NOT use remove SD Card button on Settings|Phone storage|SD Card when replacing the cards. It just felt no sense to do that provided that I had switched the phone before I replaced the card.
I appreciate your help. Don't want contact Samsung service; my phone wasn't produced for the country where I live.

Hard reset is probably your best bet, since simply power-cycling didn't fix anything. You could check in SamWP8 Tools (assuming you have it installed) and reset all options to their defaults... The danger in hard reset is that you can't interop-unlock if you have GDR3 installed with the official updates from Samsung (as opposed to just the GR3 early release from Microsoft, which is fine).
For what it's worth, my GDR3 (MS bits only) SGH-T899M has a 64GB microSD card in it, has for months, and has no problems like you describe. Sorry I can't help more.

GoodDayToDie said:
Hard reset is probably your best bet, since simply power-cycling didn't fix anything. You could check in SamWP8 Tools (assuming you have it installed) and reset all options to their defaults... The danger in hard reset is that you can't interop-unlock if you have GDR3 installed with the official updates from Samsung (as opposed to just the GR3 early release from Microsoft, which is fine).
For what it's worth, my GDR3 (MS bits only) SGH-T899M has a 64GB microSD card in it, has for months, and has no problems like you describe. Sorry I can't help more.
Click to expand...
Click to collapse
Thank you for your response. After I talked with W.O.L.F and other gentlemen over here, I came to the conclusion that the issue is that I toggled the Full access to file system in WPH Tweaks. Looks like the option is non-revertible, moreover, it looks like turning the Full FS access off in fact LOCKED access to file system for some system API.
Silly me, I should've used my mind before doing that, but what's done, done.
Using SamWP8 Tools made things even worse, my phone stopped showing in Windows Explorer and started to hang as if it was busy all the time. The fact that it was heating all the time made me think that this toggle-in/toggle-off operations with Full File System access did make something to some drivers is Windows Phone. I don't know what exactly happened but the phone stopped being detected by OS as ATIV S, disappeared from Removable Devices in Windows Explorer and showed only in USB devices section. Also in Device Manager it went from Samsung ATIV S to MTM USB Device or something. Screwed completely.
I had to hard reset the phone, but the 'luck' that I had GDR3 preview (8.x.512.x as far as I remember) turned it into brick. After I hard reset the phone, all I saw was the standard Samsung welcome screen with dandelions and a black screen that showed instead of Start screen.
I understand it like I have to Flash the phone back to GDR2 using publicly available ROMs but am confused with two things:
1. Last time I checked, when the phone was still usable, the phone showed that I had XEN as a CSC.
Now what if I flash it with a different CSC like SER; since I live in Russia?
2. If I use 64-bit flavor Windows 8, would Samsung driver work fine there, I don't want to mess with incomplete flash.
I am pretty confident that I know how to turn off signature verification for bootmgr in Windows 8, but I am not sure I know how to make sure installed driver works fine (except for checking its return code on starting).
I would appreciate your recommendations. I would've sent my phone to Samsung service, but I bet it won't give me anything except for additional problems.

The "Full FS access" hack in SamWP8 Tools has nothing to do with the actual file system. It just modifies the way that the MTP service on the phone - the one that normally lets you only see the documents and media folders - launches so that it can access all of drive C:. It doesn't actually *change* the file system in any way - the tweak to the service configuration is in the registry - and in any case, the MTP service isn't even running when the phone isn't connected to a PC.
With that said, you might have screwed something up when you had such access. For example, if you deleted or renamed the Pictures folder, that would break things. However, I don't think that's the problem. I think your phone has a hardware issue with its internal Flash storage. The key evidence of this is the failure of the hard reset. GDR3 (it's not really a "preview"; it's the release bits, just only the MS portion rather than the combined "retail" update that also has Samsung firmware updates in it) didn't "brick" your phone. I'm afraid it's almost certainly just a case of defective or damaged hardware.

GoodDayToDie said:
The "Full FS access" hack in SamWP8 Tools has nothing to do with the actual file system. It just modifies the way that the MTP service on the phone - the one that normally lets you only see the documents and media folders - launches so that it can access all of drive C:. It doesn't actually *change* the file system in any way - the tweak to the service configuration is in the registry - and in any case, the MTP service isn't even running when the phone isn't connected to a PC.
With that said, you might have screwed something up when you had such access. For example, if you deleted or renamed the Pictures folder, that would break things. However, I don't think that's the problem. I think your phone has a hardware issue with its internal Flash storage. The key evidence of this is the failure of the hard reset. GDR3 (it's not really a "preview"; it's the release bits, just only the MS portion rather than the combined "retail" update that also has Samsung firmware updates in it) didn't "brick" your phone. I'm afraid it's almost certainly just a case of defective or damaged hardware.
Click to expand...
Click to collapse
Uhm, Mattemoller90 over here told me this is an issue with GDR3 Preview:
Quote:
Originally Posted by Luxon View Post
I did a hard reset. Now all I see when the phone starts is a black screen. If I press the Power button, the standard Samsung desktop welcome screen with dandelions appears. Dammit! Nothing else but this welcome screen.
Now would flashing Wolf's custom ROM help here or the phone is completely bricked?
ReFlash GDR2 and your phone start normally, after, if you want update with GDR3
Black screen after an hard reset is a bug of GDR3 preview
Click to expand...
Click to collapse
I definitely did NOT delete anything from Phone or SD Card the only bad thing I did is I swapped my SD cards from Transcend 32 GB to SanDisk 64 GB that's it. Then I was trying to turn the full access off multiple times using both SamWP8 Tools and WPH Tweaks all to no avail and after one of such Turn full access off -> Restart -> Turn full access on -> Restart cycles I noticed Windows has completely stopped recognizing my phone.
The worse thing I could do is I could pulled out the USB cable from the PC without first detaching the phone programmatically when I presumably had the full access feature turned on, but that's all to it.
Who knows, possibly the NAND memory inside the phone has been damaged somehow, I don't know how.
Currently, when I am trying to flash the phone with GDR2, I get the following:
Gentlemen, I have a problem here:
When I click Start in the Flasher tool, I get the following message box:
---------------------------
Warning!!!
---------------------------
Partition information is Not equal.
Download all binary?
---------------------------
Yes No
---------------------------
Open WP8 SMD image at : D:\Setup\Apps\Flash GDR2\Flash ROM\GDR2\GT-I8750 XXBME1_R_signed.wp8
Open WP8 SMD image at : D:\Setup\Apps\Flash GDR2\Flash ROM\GDR2\GT-I8750_OXABME1_R_SIGNED.csc
Open WP8 SMD image at : D:\Setup\Apps\Flash GDR2\Flash ROM\GDR2\GT-I8750 OXXAMB1_P.csc
[Channel 0] Start Download Success !!
[Channel 0] Start AskSamsungUEFIDwonloadVersion !!
[Channel 0] UEFI version is 10 !!
[Channel 0] Start AskSecurityType !!
[Channel 0] Device Security Enable and Secure Binary!!
[Channel 0] Start AskDeviceType !!
[Channel 0] AskDeviceType is Product !!
[Channel 0] Partition info does not Match !!
Click to expand...
Click to collapse
What does this mean and what should I do? I am trying to flash from GDR3 Preview to GDR2.
I this somehow a confirmation to the fact that phone's memory is broken?
Heck, bad news then. This phone cost me near $500 in Russia...
Thank you.

Okay, the issue is resolved. The phone successfully flashed to GDR2 once I set the All option in the Flashed program and specified the XEH CSC code (which was the code my phone has had before it started to do quirky things).
Thank you everybody for your support.