yashsingh1/xdaforums huggingface dataset:
[myTouch 3G, Magic General] mumilover:
Well... you need a compatible spl before you can change the spl/radio combo.

To do that, i need your software version... run this code:

fastboot getvar version-main

We can take from there :0)

Just don't flash or mess around your OS... we may need it to flash a different misc partition to change the software version... more on that later
[myTouch 3G, Magic General] o0ojco0o:
3.04.401.2

i have tried higher roms but always blacks out at radio install
[myTouch 3G, Magic General] gilliardmelo:
It is happen with me. Did you solve this problem?
[Epic 4G Q&A, Help & Troubleshooting] nuclear_android:
Has anyone here had any experience (preferably success) running Odin under Bootcamp on Snow Leopard? Any advice? I can't get my iMac running Win7 under Bootcamp to even recognize my Epic 4g...
[Epic 4G Q&A, Help & Troubleshooting] Esteway.619:
Did u install the Samsung drivers?
[Epic 4G Q&A, Help & Troubleshooting] s84471:
I actually always use my MacBook Pro running W7 Pro x86 via bootcamp to flash my Epic. So far I have a much higher success rate using my Mac than my desktop (though that could be because I use the front ports, which I've heard is no good).

As long as you installed the correct (x86 or x64) Samsung drivers, it should pick it up no problem.

If it doesn't, maybe try a different cable/USB port.
[Epic 4G Q&A, Help & Troubleshooting] nuclear_android:
Yes, I have the Samsung drivers installed.
[Epic 4G Q&A, Help & Troubleshooting] s84471:
Alright, try heading over to Device Manger and see if your phone shows up (even as an unknown device) when you connect it.

If it does, I'm guessing (for some reason) it's not using the Samsung drivers (you might be able to use Device Manager to tell it to use the Samsung drivers).

If it doesn't, I assume there's something wrong at the hardware level (ie. a bad cable).
[Epic 4G Q&A, Help & Troubleshooting] farmsatguy:
Your OS setup is fine, unfortunately it's a well documented problem that the USB cable Samsung ships with our Epics are of low quality (or atleast, not of high quality). Since you've installed the drivers, I'd first try any other USB ports you have to see if it works.

I've heard of several people having success by pulling the battery (and leaving it out) then going into download mode (holding the 1 key and power) after plugging it into the USB port. Goes without saying BE CAREFUL doing this - your rewriting your phone and its only source of power is via that USB cable since you've left the battery out for the entire process - I feel for the damn cat that was to jump up on my desk and knock the cable loose effectively bricking my phone! But I've read several articles/posts of people swearing to this method.

I've also heard of folks having success by removing the SD card (maybe one less thing for the computer to "see" and have to figure of what to do with) and not putting it back in until the process is entirely completed.

Fortunately, I've always had success so I can't say from first hand experience if either of these will work before resorting to buying a better quality cable or using someone elses computer.

Hope this helps...
[Epic 4G Q&A, Help & Troubleshooting] daddymikey1975:
if you have the drivers installed and it's still not recognizing your phone, try uninstalling the drivers and installing PDAnet. I had to do this w/ my Win7 laptop and my wife's.

If that doesn't help, I have no idea. If it does help, hit that thanks button :)
[XPERIA X10 Q&A, Help & Troubleshooting] wskannan:
Hi,

I'm looking to swap my unlocked X10i for an X10a.

(For those who don't know, in the US:

X10a --> will access 3G only on AT&T

X10i --> will access 3G only on T-mobile

has to do with the radio band hardware)

The phone's in good condition and it looks like it has a screen protector (if it is a screen protector, it came with the phone, I didn't add it)

any takers?? frustrating being stuck on EDGE with AT&T!!

have froyo 2.2 ROM running on it, but will restore original sony 2.1 if you want..

Kannan
[XPERIA X10 Q&A, Help & Troubleshooting] Garbo14:
I have AT&T with CM 6.1.3 V054 by Wolfbreak on my X10i. However, i have and H which is better than 3G.
[XPERIA X10 Q&A, Help & Troubleshooting] wskannan:
Hi,

I was under the impression that the X10i radio will _not_ support the 3G band that AT&T uses.

I'm not allowed to postr links yet, but search for "xperia x10i vs x10a" will tell you what I mean.

btw.. does CM = Cyanogen Mod? Could you tell me a bit more about what you did pls? I'd just been running zdzihu's froyo rom..

Thanks.

Kannan
[XPERIA X10 Q&A, Help & Troubleshooting] aval1392:
yes CM is cyanogenmod. There is no significant difference between x10a and x10i. x10a= americas.. x10i= international. When you flash cyanogenmod is says that its supporting x10i and not x10a, im running ATT and i'm running x10i just fine. I wouldn't stress over a simple letter. Everything will work as it should.
[Fascinate Q&A, Help & Troubleshooting] lane32x:
I'm starting to see a correlation between absolute crap-for-crap batter life and having the ambient light detector enabled. I'll do a test tomorrow, but I'm pretty sure if I just left my screen on full brightness all day, that I wouldn't get as bad of battery life as I do with the ambient light detector turned on.

Is there a problem with the fascinate's polling period? or possibly how much power is being sent TO the sensor? This might explain the problems on hacked roms where people are noticing a buzzing/hissing noise coming from the phone right around the area of the ambient light sensor when in the middle of a call (and the screen is on).

Has anybody seen where in the code the ambient light sensor is handled? (is it in the kernel, or somewhere in the drivers?).

*EDIT*

Thanks for moving my post. I was pretty annoyed with myself for posting in the wrong section.
[Fascinate Q&A, Help & Troubleshooting] lane32x:
*edit* Now that the thread has been moved, This post could probably be deleted.

--------------

Well, since nobody has moved this to the other forum yet and it's received a few views, Has anybody else noticed this before?
[Fascinate Q&A, Help & Troubleshooting] soba49:
My personal experience had been full brightness ate battery fast and low brightness was a combination of hard to read and similar drain to auto. Then again my phone has never hissed at me except for godawful noises using skype wifi sometimes, and I have never messed with brightness under froyo.

My only observation with froyo roms is that "stock" eb01 was awful but superclean and AOSP were pretty good, particularly under EB+ kernels.

Also, I lose more battery than I would like to from signal loss overnight, but turning off 3G seems to help with that.

Swyped grumpily from my advertised as "can be upgraded to Android 2.2" device.
[Fascinate Q&A, Help & Troubleshooting] phooky:
i noticed that the automatic brightness setting is absolutely terrible at choosing the correct brightness.

the froyo roms added the ability to hold down on the status bar and move left and right to adjust the brightness, so i just use this to adjust it on the fly when necessary.

this doesn't really answer your question, but i figured i'd add my 2 cents :)
[Fascinate Q&A, Help & Troubleshooting] burlingtonbob:
The noise comes from having the key backlights on during a call.
[Fascinate Q&A, Help & Troubleshooting] lane32x:
If you are referring to the softkeys, there were some assumptions that this was the case, but I have tested this out and have heard the noise even when those lights were turned off.

Also, I ran my phone at about half brightness today all day. I've had it off the charger for 15 hours, made 3 hours worth of phone calls, and it's still at 41% battery life.

2 days ago when I just had my phone in the pocket, not doing anything and leaving the screen off (with auto brightness enabled) my battery was dropping significantly after only 6 hours and no phone calls or Internet usage.
[Galaxy S I9000 Q&A, Help & Troubleshooting] eeney:
I know before I start that this is a dumb question, but are there any utilities for Android/Galaxy S for Data Recovery?

I have just had a difficult time flashing a new ROM, and at the end of it the system has been wiped, including all data on the internal SD card, in the past when flashing new ROMs only the internal memory was affected, but like I said, this time I had a few issues.

What I'm most concerned about are my photos and videos, I know in a Windows environment recovery tools work well, I'm just hoping Android is the same, but I think I'm wrong.
[Galaxy S I9000 Q&A, Help & Troubleshooting] rschenck:
I have seen it suggested that once you can mount the internal SD to your PC, you can use the same tools you would use to recover data from any SD card. I can't confirm that however.

I would imagine that the main problem will be having data overwritten when you installed the new ROM. However, you can't lose anything by trying.

I try to save all such things on the external SD as much as possible, out of fear of just this sort of issue. Also it is a good idea to backup to your PC or to Dropbox any pictures or videos on your phone you couldn't bear to lose if someone swipes your phone...or if the SD is formatted.
[Galaxy S I9000 Q&A, Help & Troubleshooting] JJEgan:
Google Recuva and try what you can recover .

But wipe means wipe even under windows .

jje
[Galaxy S I9000 Q&A, Help & Troubleshooting] eeney:
Thanks guys, I did try a standard windows based data recovery on the mounted SD, which found a lot of data, however I am unable to locate my photos and videos.

I can find a lot of the photos by searching for jpegs, however all the ones I retriever are very small, much smaller than the original resolution. I'm starting to wonder where the full size images are stored and if they are stored as jpgs.

Seems odd that I can find the small image files but not the originals, the smalls ones are between 40 and 100kb each.

any more ideas?
[Galaxy S I9000 Q&A, Help & Troubleshooting] rschenck:
This is a strange question, but are you SURE the photos themselves were stored on the internal SD? I often store things on the external card and forget I set it up that way. You may want to check through all the folders on the external SD and see what is hiding there.
[Galaxy S I9000 Q&A, Help & Troubleshooting] stellarphoenixs:
Data recovery froom Android/Galaxy S

Hi,

Sorry to hear of your difficulty. You are absolutely correct you can use any of the data recovery software to recover your lost data.

Regards,

Stellar Phoenix Solutions

datarecovery@stellarphoenixsol.com

"trusted data recovery solutions"
[Droid Incredible Q&A, Help & Troubleshooting] 7he Messiah:
Firstly, I apologize if this is in the wrong section.

Secondly, my purpose for posting is to find out a thing or two about the approximate size limit of a ROM. I must admit to being new to Android development, so this may seem naive, but I hope not.

To explain, I am attempting to port the shipped ROM of the Merge to the Inc and keep getting bootloops that I believe are caused because the ROM is too large. I have the size of the ROM's files on my file system down to 235MB (this ROM started much closer to 300MB), but I believe our /system/ partition is 256MB, is it not? I know I need to leave room for app installation and the like, but at this point I was hoping to make sure the thing would at least boot. However, I am getting errors in my logcat about the Dalvik cache, and it looks to me like I've pushed the size limit too far.

My issue at this point is that I do not know what more I can safely do to strip the file size down. I have currently removed a good number of apps, as well as deodexed, even though I didn't want to do that this early.

Any guidance in the right direction would be greatly appreciated.
[Droid Incredible Q&A, Help & Troubleshooting] alanthemanofchicago:
Deodexing, at least to Incredible framework roms, can increase size of the Rom by up to 50mb.
[Droid Incredible Q&A, Help & Troubleshooting] 7he Messiah:
Ah, I see, thank you. When I get home from work this evening I'll look into that. Are there any other areas where I can safely remove content in order to decrease the should I have need to do so?
[Droid Incredible Q&A, Help & Troubleshooting] incubus26jc:
Deodexing does not increse the size of a rom. It decreases it.

Odex files make the rom much bigger. By removing those files(deodexing), the rom is much smaller.

With my roms, if i go over about 251mb if im looking at the system folder in 7zip wont even finish installing. Gives an error.

If your rom is installing completley without giving you error messages, The size is probably not the issue.

You need to logcat your boot so you can see what is causing the loop.
[Droid Incredible Q&A, Help & Troubleshooting] 7he Messiah:
Thank you, that is what I thought on the size issue. I noticed it drop from ~280MB or so to somewhere around ~240MB after deodexing.

The ROM is in fact installing, but when I logcat during boot, I get errors in regard to not being able to open or find certain files in /data/dalvik-cache/ (it appears to be attempting to build the cache and failing due to insufficient disk space).

My reasoning behind suspecting size also comes from what you said in that I had been unable to finish the install with a prior build and it was reporting out of disk errors in my recovery.log file. I'm guessing that I just don't have it small enough yet.
[Droid Incredible Q&A, Help & Troubleshooting] wdfowty:
Did you make any modifications to your framework besides deodexing?
[Droid Incredible Q&A, Help & Troubleshooting] 7he Messiah:
I do not believe so. I am using dsixda's kitchen for the most part, and I don't think I told it to do anything beyond the deodex that would affect the framework.

I had to install bash, and I manually removed apps to save space/hassle. But beyond that, I am trying at this point to boot it as close to stock as possible.

Is it theoretically possible that something happened in the process of using the kitchen's porting tools that would affect the framework?
[Droid Incredible Q&A, Help & Troubleshooting] donnyp1:
So, size does matter?
[Droid Incredible Q&A, Help & Troubleshooting] wdfowty:
I don't use the kitchen's porting tools, so I don't know what it does exactly. You might be able to find the script in the kitchen and find out how it works.

That's what she said.
[Droid Incredible Q&A, Help & Troubleshooting] 7he Messiah:
Yeah, I took a look and did not see where it was making any specific changes to the framework.

I think at this point I am going to back up what I have and start again to make sure I'm not doing something stupid.

lol, that she did.

EDIT: After having started completely from scratch, the result was the same bootloop and errors. The logcat output is identical. Hmm..
[Droid Incredible Q&A, Help & Troubleshooting] Conap:
the system partition and data and cache partitions are seperate on the phone. Having too much in system should not cause an issue with it creating the dalvik-cache or app space either. It's always possible that deodexing the rom could have messed up the framework-res.apk. Have you edited the boot.img at all? Have you changed the updater-script at all? It look like it can't find or access the data partition. Are you flashing anything to the data partition or just to system?
[Droid Incredible Q&A, Help & Troubleshooting] 7he Messiah:
This second time, I did get a couple of errors during the process of deodexing /system/framework (I deodexed framework and app separately so I could watch them) that I did not get last night, but they did not appear to be fatal (at least not as far as the kitchen was concerned, but I guess that doesn't say anything about a production environment).

EDIT: Upon some investigation, said errors are stemming from a failure to be able to deodex com.htc.rss.odex.

As far as the boot.img, that would be whatever was output by the kitchen's porting process, I have not explicitly modified it.

The updater-script is unmodified by me, and it is only writing to system.

For what it is worth, I took the effort of noting my process, step by step as I did them this time:

- Ported

- Installed Bash

- Installed Root

- Manually removed unwanted apps

> Current /system/ size on disk: 278MB

- Deodexed /system/app/

> Current /system/ size on disk: 261MB

- Deodexed /system/framework

> Current /system/ size on disk: 239MB

- Packaged and flashed
[Droid Incredible Q&A, Help & Troubleshooting] Conap:
I would say the problem is probably the deodexing of the framework-res.apk then. You could try booting it without it being deodexed. Any error in that part of the system can cause significant problems even if the deodexing finishes. Even though it finished deodexing it doesn't always mean that it built it correctly.
[Droid Incredible Q&A, Help & Troubleshooting] 7he Messiah:
I will go ahead and give that a try. Thank you!
[Droid Incredible Q&A, Help & Troubleshooting] 7he Messiah:
Well, I guess I'm back to why I deodexed in the first place.. the ROM will not flash properly as it runs out of disk space during the install.

minzip: Error writing 8192 bytes from zip file from 0xbe96f38c: No space left on device
minzip: Process function elected to fail (in inflate)
minzip: Can't extract entry to file.
minzip: Error extracting "/system/lib/libwebcore.so"
wrote boot partition from /tmp/boot.img

Install from sdcard complete.
~ #

So I guess my question at this point goes back to being, what materials can I look at to determine what I can attempt to remove?
[Droid Incredible Q&A, Help & Troubleshooting] wdfowty:
Silly question: Is your kitchen up to date? I try to update every week or so, just in case.

You can also symlink things from /data to save space. Take a look at a current desire z port, study the structure of the rom, and the update(r)-script. I had to do a lot of that in the Incredible 2 port.
[A7 General] Genialor:
Hi, thank you very much bestialbud , for your contribution now enjoy factory firmware and all functions work perfectly in A7. and also I have the Market.
[A7 General] bestialbub:
thanks for the positive confirmation. ;)

i'll try and throw out some more stuff for you the a7 users this weekend to accompany the gapps fix; some build prop improvements to get you access to more apps.

i'll try and throw out some more stuff for the rom chefs to kick up the activity in rom and mod development for the a7; map out all the files, permissions and uid/gid's, and then MAYBE if i have the time this weekend go experimental and package the factory rom into what i consider a normal update zip; zipped up rom instead of a system image w/ a script that sets all the roms permissions, symbolic links and busybox install. once its in a more manageable format like that you'll get more would be chef's and themer's contributing.

been thinkin' about it all week, i just don't have a tablet of my own (i'm the misses android fixit tech), so my works restricted to weekend mornings. ;)
[A7 General] Genialor:
would be great, that within your improvements we have an ad-hoc connection to work properly.

the market does not have all the permissions, but wiht the permissions you indicate the fix the problem.

I'm anxious to see your improvements. Thanks again.

i'm sorry my english.
[A7 General] bestialbub:
genialor; yeah, i never had any success w the adhoc wifi fixes myself. adhoc limitations are pretty common for mobile devices, not just android. i actually picked up a dsl connection due to this limitation, quite reluctantly i might add.

there is some 25 other similar tegra tablets. a portable solution could still present itself. i wouldnt count on any manufacturer adding adhoc connectity if they didnt provide it in the initial release.

i can say the usual passion finger, or release keys added to the stock one didnt make any difference. but im only using skyfire for an app name to search.

if folks could list other apps they dont see, it may help to make some gradual steps.

otherwise as far as savey folks looking at direct manipulation; the fingerprint that the market app reads after being copied from build prop is stored in /data/data/com.android.vending along w the characteristics your device supports. im a compare the tabs to my phone for fun to see if i can manipulate the data, because fingerprint replacement, w this gapps package in the rom isnt working. if that works, i can post instructions for the savvy, and MAYBE dig up some way to creatively automate adding those details.
[A7 General] Genialor:
Thanks buddy install UPDATE04-16 market + google apps and it works perfectly.

Bestialbud excellent job. Full Market yes, yes, yes ...
[A7 General] tumpy:
What is the latest market app, on Dexter mod I am running 2.3.6..
[A7 General] rphilippe777:
Hey, Tested your update and it seems to work fine except for some game apps. These aren't crucial but may indicate some permission issues: "crazy snowboards" seems to have a orientation problem.( only work in portrait mode.) "mau mau"intermittent FC.

*** note these apps worked in Dexter's latest mode ***

Otherwise Good Job!!:)
[A7 General] muxecoid:
I find the installation notes for gapps mod in original thread extremely confusing.

I just installed official firmware (BTW the installation notes on official site were crystal clear). What should I do now?

A video of the entire process would be great.

P.S: NP, I just did not understand that to navigate between recovery menu items I must use "back" button.

Looks like gapps works now
[A7 General] bestialbub:
sorry, i didnt provide step by step details for recovery use. i wont update that information either, as recovery is likely to change soon w lightly different instructions..
[A7 General] muxecoid:
Some market applications can't see sdcard...

Looks like it is mounted as /storage/sdcard-disk0 while these apps expect it to be at /sdcard. Also /sdcard is mounted somewhere on internal memory, same place as /storage actually :(. Is there any way to change it?
[A7 General] okantomi:
Some market applications can't see sdcard...

Looks like it is mounted as /storage/sdcard-disk0 while these apps expect it to be at /sdcard. Also /sdcard is mounted somewhere on internal memory, same place as /storage actually . Is there any way to change it?

Ummm, there's so much information on this...please do a search in these threads on SD card and you will understand why no one wants to answer that question............
[A7 General] muxecoid:
I did search and could not find any comprehensible information.
[A7 General] okantomi:
I didn't say it would be comprehensible.

The external sd card is mounted as /storage/sdcard-disk0. The A7 can read from it but not write apps to it, or at least the market doesn't and I don't think you can run apps from it, just install from it. There is an internal sd card 4GB total, but with 1+GB available for apps, and we can also add our own sd card (up to 32GB) stuffed with our music, videos, jpgs, documents, etc....that way we can access them through gallery and media players, etc, without having to download a bunch of junk onto our internal memory.

1GB is a huge amount of internal space for the kind of apps that I suspect most of us are using. Sorry if I'm not clear, but in truth this topic has been done to death.

Maybe our intrepid developers can find a way to rewrite the way this thing works now that they have the kernel source but maybe not.
[A7 General] bestialbub:
there are ways and roms that may change the sdcard mount location. the apps may com thru the google market, but their ability to run is another function of the rom.

this is only a google apps addon.

you'll have to wait a lil bit longer til you see a rom from me. i'm interested in recovery and themeing for this device right now..
[A7 General] rphilippe777:
This is an on going problem with the sd card and the way its mounted by elocity's implementation of Android 2.2. To male a long story short, Elocity's android version is 2.2 compatible not a true implementation of Android 2.2. As far as I know no one has been able to work around this problem. Dexter tried starting with mod 1.3 but people started having problems with sd and usb detection. I'm waiting for Stream Tv to finally decide to fix this problem.