Hi
I just wanted to ask if anyone using an ICS ROM (e.g. Onecosmic's) is getting normal USB transfer speeds when using to copy from PC to Phone.
I'm using Oncecosmic's RC3 build (which states the speed issue should be fixed), but my speeds are only reaching 1.7MB/s. Can anyone confirm if they are getting faster?
Thanks!
All kernels that are based on 3.0 have a slow usb transfer.
Thanks Malcho,
So a speed of 1.5 - 1.7Mb/s is average?
I've already reported this problem to the google-code page.
I also have this issue. It is actually kinda fixed, but only on the recovery. Trough recovery I get a speed up to 10Mb/s data transfer rate, but if the phone is booted up, I cant go over 2mb -.- Thats kinda sad. Is there the same issue with nexus s? Does somebody know somethin about?
Thanks for the confirmation alexx910!
I had a quick search and I think Nexus S users are experiencing similar speeds. Someone mentioned it could be due to the system format ICS uses (not EXT4).. but it's a bit over my head
I think it's not ics related.I had same problem with fugu kernel on cm7.Fugu is 3.0 based kernel.
Well that is really sad. And because the nexus s have the same problems with the speed and we all know, that our ICS Rom is a direct port from nexus s, we suffer under the same problem :/
(they had 4mb/s, now 1mb/s, its ok to live with, we had from 8mb/s to 1-2mb/s, that is really bad)
And I dont think, that there wont be a bugfix in the next time (1-2 months)
I have this problem
alexx910 said:
I've already reported this problem to the google-code page.
I also have this issue. It is actually kinda fixed, but only on the recovery. Trough recovery I get a speed up to 10Mb/s data transfer rate, but if the phone is booted up, I cant go over 2mb -.- Thats kinda sad. Is there the same issue with nexus s? Does somebody know somethin about?
Click to expand...
Click to collapse
This worked for moving my files thanks! Was waiting hours for transfers and never thought about doing it in recovery!
Confirm, very slow.
got 2.5mb/s with icssgs 4.2 and devil 14.2
Tell now with all roms and kernels i get less than 2.0Mb. Around 10.0Mb using CWM.
Sometimes the device freez when trying to transfer from internal sd to external one.
Sent from my GT-I9000 (ICS AOPK #25 - Semaphore 0.9.1) using xda premium
It's fixed on rc4.2.
Sent from my GT-I9000 using Tapatalk
aaron_my said:
It's fixed on rc4.2.
Sent from my GT-I9000 using Tapatalk
Click to expand...
Click to collapse
That's news to me cause that's what I'm on and it's sloooooooooow.
finneginsfast said:
That's news to me cause that's what I'm on and it's sloooooooooow.
Click to expand...
Click to collapse
It is fixed for me at RC4.2 . Speeds around 7-10mb/s
AOKP build 23 beta 2.1 with latest Glitch
I noticed that when I'm copying files to SD, the phone CPU usage is high.
Maybe phone want to scan files that are currently writed on SD and that's the reason of slow transfer?
Ive been suffering slow USB transfer using TeamHackSungs CM9 alpha since the first build. Transfer rates are around 1-1.5mb/s.
Using stock Samsung ROMS (Gingerbread) id get around 5-6mb/s consistently.
No problem on speed on RC 4.2, almost same as the speed I'm getting when using stock rom.
USB Transfer Speed is too slow (only when transfer data from computer to phone - about 2.5 mb/s)! When transfer data from phone to computer , speed is near 10 mb/s!
Team ICSSGS 4.0.3 RC4.2 with semaphore 0.9.1
What is the problem!? how and what needs to be adjusted to work properly! on stock [kernel] everything is fine!
soooooooooo...
no fix? Slim ICS 3.1 + semaphore .0.9.8 - 2,5 mb/s max. =/
Related
Hi, I would like to know which is the fastest rom for Defy.
Thanks
probably one that is based on the blurless 3.4.2-131 rom.
so either jboogies or iaio's rom.
..or you can try orange firmware
Fast with overclock or no overclock ?
Would you like to use Android 2.1 or 2.2 ?
For Android 2.1 i think 2.34 Blurless with JIT
For Android 2.2 i like Pays v1.6
It's just for me but i don't use overclock but downclock i dont play game just email wifi gps phone internet .
..or you can see HERE...
Mick711 - You run at lower than 800MHz at all times?
i've set up the clock frequency to 1000 MHz while I'm running any application. 300 MHz while idle.
I don't want to let this thread down
So now what is the fastest Rom??
WIIstpM said:
I don't want to let this thread down
So now what is the fastest Rom??
Click to expand...
Click to collapse
Barebones<-CM7<-WiUi-<CMiUi<-MiUi
Cm7 is really fast!
my Quadrant benchmarks at 1000mhz/56 are around 2600!
The performance is much better than the stock one.
Julian
Miui is fast at first, but I experience major drops in speed after a while. Not to mention the power amp volume bar is messed up. Cm7 seems consistent for me(rc 1.5) haven't tried cmiui. Ms2ginger is just plain weird.
Sent from my MB525 using Tapatalk
zencoran said:
Miui is fast at first, but I experience major drops in speed after a while. Not to mention the power amp volume bar is messed up. Cm7 seems consistent for me(rc 1.5) haven't tried cmiui. Ms2ginger is just plain weird.
Sent from my MB525 using Tapatalk
Click to expand...
Click to collapse
power amp was fixed in today`s update for miui
Is there any fast ROM that allows to play smoothly the dailymotion videos using flashplayer with HD720p ON?
CM7 for me by far
CM7 da bomb
lol I was able to revive this thread I see XD
I'm using LiquidArc 2.0 and it's amazingly fast!! But I wonder if there is another ROM faster...
^ Yes, me too. Extreme fast rom, i can't believe if it has fastest...
I've just installed cm7. Was on nordic before that. I experience a lag or rather a loss of smoothness in certain cases in cm7. For instance when scrolling in browsers (tested many, they are all the same) or using pinch to zoom in gallery. Otherwise cm7 is very fast and efficient. Am I the only one having this lack of smoothness?
Sent from my MB525 using XDA App
I don't know how it was later but nighty from 21 was really bad for my moto. Try RC 1.5 it is really smooth.
If you are using nightly try maybe something older like RC 1.5 or
cm7-110911-1924-BOOTWIFI3-Jordan.zip (11 sep)
remuseu said:
power amp was fixed in today`s update for miui
Click to expand...
Click to collapse
Seriously?????? i think i may just switch back to MIUI now. Thanks for the heads up!
I mean really slow......200kbps ?!?! 100mb was going to take 20 minutes!
What's going on? it didn't do this when I was on stock froyo
I'm on gingervillain 1.5, could it be my rom?
Evofusion said:
I mean really slow......200kbps ?!?! 100mb was going to take 20 minutes!
What's going on? it didn't do this when I was on stock froyo
I'm on gingervillain 1.5, could it be my rom?
Click to expand...
Click to collapse
That's really odd. Hmm... am not really familiar with gingervillian... Try flashing a diffrent rom...
Sent from my HTC Vision using XDA App
Try flashing a different ROM like the above user said. It could also be your SD card messing up.
I had this problem for a LONG time... then it magically went away. Now I get about 1-2MBps
Sent from my T-Mobile G2 running Cyanogenmod.
Could be a multitude of issues.
SD Card? Try inserting it into another device and see if the performance is similar.
Different USB port on your computer?
Are you using the stock USB cable the phone came with?
If you found a solution to this please let me know because when I was running stock android and it had no problem then I installed cyanogen 7 stable and I started getting ridiculously slow speeds. I know it is not the sd card because, 1 it worked before i installed cyanogen and 2 because when I plug the sd card into an adapter it works perfect faster then ever. Please help!
That's one of the reasons why i'm not using CM7 based ROMs anymore. USB file transfer speeds are incredibly slow for me, specially when copying/deleting small files. I newer have seen this kind of anomalies when i was using CM6.1.1 or any Sense ROMs.
Windows 7 x64.
Sent from my HTC Vision using XDA App
Hi All
I've been using ICS since pretty much day one when i bought the phone.
I realized the USB transfer speed when I copy files is very low.
in my phone around 1.3MB/s and on another 1.9MB/s
both are incredibly slow.
Could you guys help me determine whether this is a problem only affecting my phones, or is something ICS related?
Seems to be ICS related, many threads saying the same problem. I'm getting a middle-ground speed personally on ICS.
If you want to transfer large files, you might prefer doing it via mounting the sdcard through recovery (assuming you have a custom one, don't think stock can do this).
It is Google who may completely solve this problem...
Harbb said:
Seems to be ICS related, many threads saying the same problem. I'm getting a middle-ground speed personally on ICS.
If you want to transfer large files, you might prefer doing it via mounting the sdcard through recovery (assuming you have a custom one, don't think stock can do this).
Click to expand...
Click to collapse
nope, GB has this problem too.
i opened a thread about this on the google support forums, but didnt get any helpful answers. nobody know how to solve this.
the transfer-rate just stays around 1.3 mb/s, tops (for me at least). this is painfully slow. i'm pretty sure google locks the speed somehow, for whatever reason.
on my n900 i get my usual 10-12 mb/s write speed, no matter if internal storage or microsd. why cant the nexus do this?
I wonder whether thee from devs are aware of this. Should be able to fix it.. how can we let them know?
I'm fairly certain the devs are aware of this. Maybe the CM team has something in mind here, i havn't tested sd speed on any CM9 ROM - or maybe they need some notification. It may not be a "bug" in the common sense, but possibly a series of underlying issues which increase the transfer rate. Maybe I'll test some things later to see if i can get a better idea on what is the cause.
For the record, I could get around 3-4MB/s on GB, i get around 2.5 - 3MB/s on ICS. In recovery i get closer to 4 - 4.5MB/s. The flash memory inside the Nexus S is quite slow write-wise, sadly. External SDCards rely entirely on the Class it is in, C2 will be very slow, C4 faster, up to C12 or whatever they have now which are happy to write Full HD video in real time.
got the same prob since beginning of the ics era ...
Currently using Kang Milestone 5. Tried CM9, Nightlies, CM9 HumberOS etc. and my tab still randomly reboots. Even rebooted while it was asking me for account info.
This is after fresh restocks from Overcome instructions too.
On Gingerbread I had absolutely no problems.
Seems to happen at least every two hours. Is it as bad for anyone else?
R Forrester said:
Currently using Kang Milestone 5. Tried CM9, Nightlies, CM9 HumberOS etc. and my tab still randomly reboots. Even rebooted while it was asking me for account info.
This is after fresh restocks from Overcome instructions too.
On Gingerbread I had absolutely no problems.
Seems to happen at least every two hours. Is it as bad for anyone else?
Click to expand...
Click to collapse
No, havnt had any reboots like that myself. CM9 runs brilliantly on my Tab, Just shows what Sammy could have done if they gave a sh1t about updating their previous devices.
Been happening a lot less lately. Might be partially due to the fact that I've stuck with milestone 5 as well as kept the 160 dpi instead of using 120 like I normally do.
Still, it happened on a fresh install while I was entering in details.
Seems entirely random.
So to bump this thread I have found that undervolting the CPU by 50-75 mV seems to have solved these issues, at least in the latest CM10 version in case anyone is curious.
R Forrester said:
Currently using Kang Milestone 5. Tried CM9, Nightlies, CM9 HumberOS etc. and my tab still randomly reboots. Even rebooted while it was asking me for account info.
This is after fresh restocks from Overcome instructions too.
On Gingerbread I had absolutely no problems.
Seems to happen at least every two hours. Is it as bad for anyone else?
Click to expand...
Click to collapse
My tab is GT-P1000N. My tab rebooted after every second. I was dieing to solve my problem. I searched everywhere but couldn't find any solution. Then I asked alroger how to solve this problem and thanks to him he said that the best thing to do is to stop overclocking the tab i.e to keep it max 998 MHZ. That's how my problem got solved. And also do a fresh install. Yor problem will be solved.
With best regards,
Adnan
And sorry for bad english. Because I am a Bangladeshi.
adnan.rakib said:
My tab is GT-P1000N. My tab rebooted after every second. I was dieing to solve my problem. I searched everywhere but couldn't find any solution. Then I asked alroger how to solve this problem and thanks to him he said that the best thing to do is to stop overclocking the tab i.e to keep it max 998 MHZ. That's how my problem got solved. And also do a fresh install. Yor problem will be solved.
With best regards,
Adnan
And sorry for bad english. Because I am a Bangladeshi.
Click to expand...
Click to collapse
I was using kanged gummy kernel with CM9.1 before upgrading to CM10 and running at 1.2ghz NEVER rebooted. Now that I'm using CM10 I can't go past 1ghz without reboots however it seems faster than CM9.1/kanged gummy/1.2ghz.
Would be great If I could get 1.2ghz though, speeds things up a lot.
Using gt-p1000 I get random reboots too, using cm9 & 9.1, never had prob with gb. Now using latest cm9 nightly -so far so good.
Sent from my GT-P1000 using xda app-developers app
R Forrester said:
I was using kanged gummy kernel with CM9.1 before upgrading to CM10 and running at 1.2ghz NEVER rebooted. Now that I'm using CM10 I can't go past 1ghz without reboots however it seems faster than CM9.1/kanged gummy/1.2ghz.
Would be great If I could get 1.2ghz though, speeds things up a lot.
Click to expand...
Click to collapse
You should be able to OC to 1.4 now.
See:
http://forum.xda-developers.com/showpost.php?p=34290097&postcount=514
I had 2 android devices before this one and this one is by far the most unstable device for custom roms. I had a motorola milestone and nexus one and i rarely get bootloops and never get broken recovery. With i9000 its atleast once a week and for no apparant reason. My battery was low so i turned off my phone and replace the battery and then BOOM broken recovery and bootloop and im stuck with this **** in school....
Hey!
I have not tested other devices yet, but if i think about what i did to my I9000 and always got it restored, and also overclocking (up to 1200 mhz) runs stable as hell. I tested AOKP ICS Milestone 6 and the X-Bean 2.0 (JellyBean). Everything stable as hell.
But i think this differs from phone to phone.
I am a happy camper with my I9000 :highfive:
quick question regarding how unstable the i9000 is.
I bought my i9000 from a friend a few weeks ago as i desperately needed an android phone after drowning my Desire S on holiday. It was in great condition for a 2 year old phone.
I am on my 5th ICS ROM and every single one of them has been lagging like crazy after i install all my apps. ie. it takes about 2 or 3 seconds for the touch to respond on the screen sometimes.
When i go back to the homescreen using Go Launcher it looks like it reloads the whole thing. It feels like the phone is constantly loading apps freshly every single time you use them. They always load eventually but takes a good few seconds. I never use Task Killers.
Is it possible the actual ROM chips are dying in the phone? Crappy quality chips to keep costs down perhaps.
It lags constantly no matter what you're trying to do. No matter what app i'm trying to load up. And this has happened on every single ROM i've tried.
Any ideas if the actual hardware is simply dying?
ps. the Desire S ran ICS custom ROMS perfectly with only the occasional lag when you were doing too much. So the hardware in the i9000 is defo capable.
My experience is that sometimes a "RESET" is needed to make the phone act like brand new.
That means, wipe everything on the phone.
Install an Gingerbread ROM (JW4 for example). Flash the right CF Root Kernel.. Wipe Again (Data/Cache/Dalvik).
Then install one of the stable ICS Roms (I had AOKP Milestone 6) and i am currently on JB (X-Bean 2.0).
Both are stable as hell, and it feels like i am on a Samsung Galaxy S3 sometimes, i never had any lag, its fast as hell after some tweaking.
I would also recommend using Devil Kernel on your phone, had the best performance/battery with those.
But again, every phone differs.
For the record, my phone is also 2 years old and is used every day (almost heavy use).
Good Luck
yes that is right it is so unstable in ics and jb ....so laggy,many fc s
Then you're probably doing it wrong. No above mentioned problems here. I'm running CM10 latest nightly (all stock) since day one. Latest nightly is super fast and responsive and it's been like that since 5 nightlies ago.
Either your phone is crap, your rom is crap or your installation is crap. I'am on my 3rd Rom and never had Bootloops, lags or any other Problems.
Gesendet von meinem GT-I9000
----------------------------------------------
ROM: | ICS333 2.0.1 |
Kernel: | Semaphore ICS 1.3.0s |
----------------------------------------------
You got unlucky with your phone. My friend has this issue to, and I never had.
Sent from my GT-I9000 using xda premium
No way! I9000 is perfect for testing ROMS. I've tested many custom ROMS and now on CM10 latest nightly, the phone is amazing!
Tsipo said:
No way! I9000 is perfect for testing ROMS. I've tested many custom ROMS and now on CM10 latest nightly, the phone is amazing!
Click to expand...
Click to collapse
+1
Overclocking should do the trick. I have about 90apps on my i9000 running ICS AOKP rom milestone 6. I've overclocked my phone to 1.4ghz and it runs smooth with an ocassional lag which is not bad but most of the time its smooth. Battery life is ok.
Sent from my GT-I9000 using xda app-developers app
Ive never had the problems you mention but that doesn't mean ive ever been satisfied using a Jelly Bean ROM. In fact, the one I have now has been installed for less than 24 hours and I'm umming and arring about removing it. Just the little things Im afraid.
AlwaysDroid said:
You got unlucky with your phone. My friend has this issue to, and I never had.
Sent from my GT-I9000 using xda premium
Click to expand...
Click to collapse
I think you guys are right, my phone is just faulty. Need to find a replacement asap then.
Even installed V6 Supercharger and Maximum Overdrive and phone still lags like hell after a few hours use. Its fine after a reboot for a while but then the lag kicks in and can take up to 10 seconds for the screen to respond. Rebooting every few hours ain't much fun lol
I've been using my SGSI9000 with custom ROM's for more than a year now. It always ran smooth, I never soft bricked it nor had any boot loops while installing ROM's. I've been using several flavors of DarkyROM, then CM since version 7 I think, to 9 and now 10 (including alpha's and beta's) and I almost install the daily as it is released (almost daily ROM installs) and still the phone does great, battery is still good (more than 1 day of usage) and everything works ok (have lag from time to time, but nothing major).
You should always start by something "clean", then test if it is laggy, buggy, etc.
Either start with the latest official rom with a clean system or with something reputed, like CM9/10.
Don't forget to start from a clean rom, IE: Format user data, cache, /system, etc.
Then, if it is still unstable, you might have a defective device.
I've had this devices since about 2 years, and I have installed numerous rom and I can tell you the ones available currently are rock solid!
Locke der Boss said:
Either your phone is crap, your rom is crap or your installation is crap. I'am on my 3rd Rom and never had Bootloops, lags or any other Problems.
Gesendet von meinem GT-I9000
----------------------------------------------
ROM: | ICS333 2.0.1 |
Kernel: | Semaphore ICS 1.3.0s |
----------------------------------------------
Click to expand...
Click to collapse
+1
Also, to one of the guys who was complaining, get go launcher off your phone for a start, it uses a huge amount of ram compared to other launchers. I'm running JB on my phone and its super slick and stable with tons of apps installed.
Maybe its something you're doing wrong, or a poor choice of kernel, or maybe you've not set it up well, because I have seen none of the issues that you speak of.
Sent from my GT-I9000 using Tapatalk 2
Like i said i'm on my 6th or so ROM some ICS, some JB and even ran the stock GB ROM and they are all FUBAR after a few hours use. Currently its running RemICS UX. And as i said before its slick as hell for 2 hours then grinds to a halt.
I'm not a n00b, i've been on XDA since Nov 2010 and have had 2 HTC devices which ran all ROMS solidly so i know how to install a ROM with all the proper wiping etc.
I just wanted to confirm that having a Samsung device is a bit of a lottery, u might get a good one or a duff one. I can accept that the one i got is duff. Not a problem, just need to seek out my next phone.
kennyhkw said:
I just wanted to confirm that having a Samsung device is a bit of a lottery, u might get a good one or a duff one. I can accept that the one i got is duff. Not a problem, just need to seek out my next phone.
Click to expand...
Click to collapse
I wouldn't generalize to all Samsung devices, it is fact that there were 2 types of I9000 hardware produced. To quote:
MoneyFace =p said:
Our beloved Galaxy S has 2 storage chips:
512MB Samsung OneNAND and 16GB Samsung moviNAND (or SanDisk iNAND for newer batches)
OneNAND is a SLC NAND which writes much faster more suitable for contaning app data so your apps runs faster as it can write faster.
moviNAND is a MLC eMMC NAND which writes slower, more suitable for app and personal data storage.
Click to expand...
Click to collapse
So there is 512MB fast storage and 16GB of other storage. The 16GB has two versions, slow moviNAND on the early batches and faster iNAND on the later ones. The problem is that with newer ROMs that take more space it is a juggle what to put on the fast storage and what to put on the slower storage. Inevitably something has to go on the 16GB chip, which will be moviNAND or iNAND depending on how new your hardware is. If it is moviNAND, like my unit that I bought the week it launched here over 2 years ago, there is going to be worse lag depending on how the developer has arranged things. (That post goes into detail about how that particular ROM, Helly Bean which I run, uses the flash chips. CM10 has switched to this as well.
This quote says how you can tell which chip your unit has:
fishears said:
So, Is this ROM right for me?
If you have the fast iNand then, yes, because you'll get more data storage space with no loss of speed If you have the MoviNand then maybe yes, maybe no. My advice is "Try both".
To see which Nand you have look at the following file in a text viewer:
/sys/devices/platform/s3c-sdhci.0/mmc_host/mmc0/mmc0:0001/name
If the content starts with "S" then you have iNand. If it starts with "M" then you have MoviNand.
Click to expand...
Click to collapse
In summary it's not some vague Samsung thing, it's a specific performance issue with the early hardware versions of the I9000 that they improved in later versions. Some ICS/Jelly Bean ROMs do a better job of managing this, the theory is that CM10 and Helly Bean are as good as it gets, but it is still not going to be perfect. I also think there are issues with RAM management on pretty much all ICS/JB ROMs for this phone (leaks) but that's another matter entirely.
OK, the only unstable thing I find about Jelly Bean (after a few days use) is flashing multiple .zips before a restart. On GB, I could flash, 2, 3, 4, 10, zip files via recovery and it would reboot fine. I find that Jelly Bean runs the optimizer then stops at 'Starting apps', I'd only flashed about 4 zip files. Maybe I didn't leave it long enough but after a few hard resets and what not JB came back but touchwiz was ****ed. It kept artefact'ing lol. However, when I flashed the 4 zips individually separated by restarts it was fine.
no problems here
hey,
well i have been flashing different roms, kernels, patches... for more than a year and never had issues on my galaxy s
could be something u're doing wrong, like no proper wiping maybe or partition problems...