Related
Guys, please advise me. Is there any new reliable android build that have no lock screen of death? By lock screen of death i mean that it's unable to unlock device after some sleep because nothing swipes on unlock screen.
It's really pity, i can't find any recent one or any clear explanation why it's happening, instead may be, it has something to do with WIFI reconnect and appears on newer kernels. Since older builds doesn't stuck.
D
david_beholder said:
Guys, please advise me. Is there any new reliable android build that have no lock screen of death? By lock screen of death i mean that it's unable to unlock device after some sleep because nothing swipes on unlock screen.
It's really pity, i can't find any recent one or any clear explanation why it's happening, instead may be, it has something to do with WIFI reconnect and appears on newer kernels. Since older builds doesn't stuck.
D
Click to expand...
Click to collapse
I have tried all android builds for HD2 and none of them give me SOD. All run pretty smooth without screen freeze. As a matter of fact, I am running only android for my phone now for the past few months.
Sent from my HTC HD2 using XDA App
david_beholder said:
Guys, please advise me. Is there any new reliable android build that have no lock screen of death? By lock screen of death i mean that it's unable to unlock device after some sleep because nothing swipes on unlock screen.
It's really pity, i can't find any recent one or any clear explanation why it's happening, instead may be, it has something to do with WIFI reconnect and appears on newer kernels. Since older builds doesn't stuck.
D
Click to expand...
Click to collapse
hmmm.. never heard of the lock screen of death.. i know some kernel has some issues waking up the device.. anyway, you can try all the evo based or the desire HD based builds.. i know those builds doesn't suffer from SOD, in case that's actually what's causing your lock screen problem.. mdeejay Froyo HD and mdeejay Evo Sense those two are my daily drivers.. the only thing is you sacrifice the camera on those builds.. on Froyo HD you won't have a camera at all while on Evo Sense, it has a premature flash issue, but they're both stable..
david_beholder said:
Guys, please advise me. Is there any new reliable android build that have no lock screen of death? By lock screen of death i mean that it's unable to unlock device after some sleep because nothing swipes on unlock screen.
It's really pity, i can't find any recent one or any clear explanation why it's happening, instead may be, it has something to do with WIFI reconnect and appears on newer kernels. Since older builds doesn't stuck.
D
Click to expand...
Click to collapse
settings---wireless & Networks-----wifi-settings----windows key------advanced----wifi sleep policy----check "never" then restart and pray
About problem in general, try search for 'lock screen' in any recent build. You'll see tens or hundreds results with similar complains. Like here: http://forum.xda-developers.com/search.php?searchid=46782526
justwonder said:
settings---wireless & Networks-----wifi-settings----windows key------advanced----wifi sleep policy----check "never" then restart and pray
Click to expand...
Click to collapse
Thanks. I tried it before and it doesn't that help if your wifi have to reconnect.
krat0s123 said:
hmmm.. never heard of the lock screen of death.. i know some kernel has some issues waking up the device.. anyway, you can try all the evo based or the desire HD based builds.. i know those builds doesn't suffer from SOD, in case that's actually what's causing your lock screen problem.. mdeejay Froyo HD and mdeejay Evo Sense those two are my daily drivers.. the only thing is you sacrifice the camera on those builds.. on Froyo HD you won't have a camera at all while on Evo Sense, it has a premature flash issue, but they're both stable..
Click to expand...
Click to collapse
Thanks, will give em a chance, since search doesn't show any comments about lock screen of death (yet? )
Winmo : Latest Energy Rom
Android : Darkstone Desire HD Beta 2.7z
works great no SOD i can use it for Daily OS ( of course without playing games but with FB and Twitter and some net browsing )
from 100 down to 20% battery playing games or browsing net straight maybe 2.5 hours ( just like the 2g iphone batt life when you use it alot)
I recommend the evo build since the kernel source is available and everything works while in the be builds, camera does not work. It won' be fixed until HTC release the kernel source. This is usually few months after the phone release. I am running an evo build , no screen freeze, no data freeze
Sent from my HTC HD2 using XDA App
krat0s123 said:
i know those builds doesn't suffer from SOD, in case that's actually what's causing your lock screen problem.. mdeejay Froyo HD and mdeejay Evo Sense those two are my daily drivers.. the only thing is you sacrifice the camera on those builds.. on Froyo HD you won't have a camera at all while on Evo Sense, it has a premature flash issue, but they're both stable..
Click to expand...
Click to collapse
ginbuntu said:
I recommend the evo build since the kernel source is available and everything works while in the be builds, camera does not work. It won' be fixed until HTC release the kernel source. This is usually few months after the phone release. I am running an evo build , no screen freeze, no data freeze
Click to expand...
Click to collapse
Thanks guys, I have to admit that mdeejay Froyo HD doesn't hang, and work really good (altho I don't like sense, there's a way how to change it.)
Thanks for advises
I have had this problem on every build I have tried so far...will give the two builds listed here a try, hopefully one of them will work
All builds with lastest Evo base kernel will work.
justwonder said:
All builds with lastest Evo base kernel will work.
Click to expand...
Click to collapse
negative, just tried the latest mdeejay eVo sense build and it happened first time the screen went to sleep.
socrated13 said:
negative, just tried the latest mdeejay eVo sense build and it happened first time the screen went to sleep.
Click to expand...
Click to collapse
+1
Only Mdeejay FroYo HD works stable and have no lsod/bsod/osod and camera working.
david_beholder said:
+1
Only Mdeejay FroYo HD works stable and have no lsod/bsod/osod and camera working.
Click to expand...
Click to collapse
downloading this again(stopped it last night because it was slow-going on the download)
I'm praying this works
[princess leia voice]Mdeejay, you're my only hope[/princess leia voice]
There a bug with the evo kernel. That effects the light sensors. Turn off automatic. Brightness and ur lockscreen of death is gone..
Sent from my HTC HD2 using XDA App
froyo HD didn't work...still had a lsod. I'm about to give up on android all together...
I'll give the evo build another try and disable automatic brightness, but I'm not getting my hopes up
@David
What older builds worked for you? I'd consider regressing if it means I can be rid of this problem.
Well that's it guys. Every single build I have tried to use has given me a LSOD. There is absolutely no hope of having a useable android build on my phone.
I've tried this one and have no lsod
Mdeejay_FroYo_HD_v._3.4.1 -- in my earlier post i've stated unclear -- camera is not working
My everyday build is
Xcelsior Android FroYo BASIC V1.00a
Dude, which Radio Do you use? Ive got the 2.12 and everything works fine for me. I Heard about several different things which can cause freezes (g-sensor, light-sensor, underclocked CPU..) I always thought the Winmob-Rom dont play
Sent from my HTC HD2 using XDA App
Your sdcard is probably the issue...
Sent from my HTC Desire using XDA App
Second frazertag
What SD cards are u running off? I had this issue and solved it by changing my sdcard from sandisk 16gb class 2 to Samsung 4gb class 6. I used exactly the same build files on both cards.
Sent from my Nexus One using XDA App
I'm considering selling my MyTouch3g 32a for a HD2 device... But, I need to know some things before I make this move.
It looks like you can't yet replace the WinMo 6.5 with Android, so it has to run off SD. At least that's what I can infer. How does this effect performance?
Is battery life good on the HD2? My MyTouch3g can get about 17-18 hours off the charger.
What does and doesn't work on the HD2 running Android? Any quirks I should know about? ...Is it stable and reliable enough to be a daily driver?
Also since I'm on T-Mobile, I'd be looking for a T-Mobile branded HD2... does this matter?
Sorry for all the noob questions.
replacing winmo will be possible in near future by a nand rom. i guess noone knows by now what will work better with a nand rom. most people think that battery life time will increase dramatically, but i won't count on that...
for me, running android from sd-card has no disadvantages but as i said before, we have to wait for nand roms.
with new kernels like S1 or S2 from mdeejay battery life is great (for me). it lasts minimum 24 hours on normal usage.
as far as i know there is just one big and some small issues with android on hd2:
big one: data disconnects with ppp. this is nearly fixed for me with S1 kernel, but approx. once a day i still get data lost...
small one(s): very few touchscreen freezes (escpecially when trying to answer a call).
just now i can't remember other issues, but since about 2 months winmo is just used for booting android on my hd2.
my conclusion: android is a very well daily driver
fruchtfliege said:
replacing winmo will be possible in near future by a nand rom. i guess noone knows by now what will work better with a nand rom. most people think that battery life time will increase dramatically, but i won't count on that...
for me, running android from sd-card has no disadvantages but as i said before, we have to wait for nand roms.
with new kernels like S1 or S2 from mdeejay battery life is great (for me). it lasts minimum 24 hours on normal usage.
as far as i know there is just one big and some small issues with android on hd2:
big one: data disconnects with ppp. this is nearly fixed for me with S1 kernel, but approx. once a day i still get data lost...
small one(s): very few touchscreen freezes (escpecially when trying to answer a call).
just now i can't remember other issues, but since about 2 months winmo is just used for booting android on my hd2.
my conclusion: android is a very well daily driver
Click to expand...
Click to collapse
Thank you for the info.
What does "data disconnects with ppp" mean? and if this happens, what do I do to resolve it? Throw into airplane and out of airplane mode?
you're welcome. as far as i know there are two internet protocols:
rmnet and ppp. because of low speed, rmnet seems to be vanished in nearly all builds. the good thing about it was stability! ppp has the opposite properties: very fast but till now a bit unstable.
data disconnects means that it's not down- or uploading any data while connection seems to be established regular. as you guessed right, you can handle it with airplane mode or by disconnecting and reconnecting internet connection. there is also a (semi)fix for that, which will reconnect for you automatically. but i'm pretty sure that this data loss problem will be gone in the near future (devs are still working on it).
p.s: sorry for my poor english, i hope you understand everything.
As for me it is very usable on a daily basis. I didn't think it was possible until I started flashing Android. Everything is great except for what fruchtfliege was saying. But even then, I have never gone back to Winmo.
fruchtfliege: is your LED notification light working properly? Mine only lights up once and that's it.
compared to that old 32a, the hd2 is an absolute monster!
theres an ocational minor glitch, but nothing like things were on ported roms on a dream/saphire....
its smooth sailing...
fruchtfliege said:
with new kernels like S1 or S2 from mdeejay battery life is great (for me). it lasts minimum 24 hours on normal usage.
Click to expand...
Click to collapse
sorry a bit out of topic: can i install mdeejay kernel to my mccm build? and where can i find it? thanks.
I'm using the MDeeJay evo 2.3 build and i haven't found anything not working at all. The battery last longer than it did on winMO. Been using this build constantly for about a month now, apart from the odd reboot I've had nothing but fun and games
I would personnaly recommend this build also.
jason2234 said:
I'm using the MDeeJay evo 2.3 build and i haven't found anything not working at all. The battery last longer than it did on winMO. Been using this build constantly for about a month now, apart from the odd reboot I've had nothing but fun and games
I would personnaly recommend this build also.
Click to expand...
Click to collapse
no ppp disconnects?
Thanks for all the replies, this has been real helpful in my decision and will probably grab a HD2 when/if a WP7 rom comes out just to have the best of both worlds in my pocket.
One last question, I see the MDeeJay evo 2.3 build mentioned here, but I'n not a fan of sense. Is there a CyanogenMod port that's really stable?
exiva said:
Thanks for all the replies, this has been real helpful in my decision and will probably grab a HD2 when/if a WP7 rom comes out just to have the best of both worlds in my pocket.
One last question, I see the MDeeJay evo 2.3 build mentioned here, but I'n not a fan of sense. Is there a CyanogenMod port that's really stable?
Click to expand...
Click to collapse
i'm using mccm and it's great (especially the looks) except for internet drops.
fruchtfliege: is your LED notification light working properly? Mine only lights up once and that's it.
Click to expand...
Click to collapse
you're right. this seems to be another small bug. mine's not working properly, too. doesn't matter much for me, because i never used the led lights as indicator for calls.
sorry a bit out of topic: can i install mdeejay kernel to my mccm build? and where can i find it? thanks.
Click to expand...
Click to collapse
i'm not sure which build mccm is, but if it's from mdeejay it SHOULD work (as posted in his kernel thread)
The LED notification light 'usually' works fine for me. Under 30% battery and it stays lit though
Only thing that doesn't really work is the camera on HD builds.
So far I've been disconnect free since I changed to S3 kernel from Mdeej - however I also disabled the stock tab and uninstalled my taskkiller which might've helped.
chris_ah1 said:
The LED notification light 'usually' works fine for me. Under 30% battery and it stays lit though
Only thing that doesn't really work is the camera on HD builds.
So far I've been disconnect free since I changed to S3 kernel from Mdeej - however I also disabled the stock tab and uninstalled my taskkiller which might've helped.
Click to expand...
Click to collapse
Which build are you using? You mean it works for missed calls and sms?
Wich is the best working clean froyo build, actually which is the clean froyo version, that you would suggest for daily use.
My personal favorite would have to be Darkstone1337 Super RAM Froyo v 1.5. Its amazingly fast, faster than most native android phones.
http://forum.xda-developers.com/showthread.php?t=870518
Enjoy!
+1 Darkstone1337 Ram froyo 1.5. Hoping for another upgrade from darkstone
+1
Sent from my HTC Desire using XDA App
Does everything work on that build?
Thanks,
+1 good BUILD ,thanks Darkstone
+1 on the Darkstone SuperRAM. It's absolutely perfect. I use the 7-screen T-Mobile G2 launcher on mine, which is exactly like the stock launcher but with two extra screens. It is the fastest and smoothest Nexus One build ever produced. It actually puts NAND to shame, in my opinion.
MulTiPass said:
Does everything work on that build?
Thanks,
Click to expand...
Click to collapse
Oh yes! havent run into anything that doesnt work yet.
MartyLK said:
+1 on the Darkstone SuperRAM. It's absolutely perfect. I use the 7-screen T-Mobile G2 launcher on mine, which is exactly like the stock launcher but with two extra screens. It is the fastest and smoothest Nexus One build ever produced. It actually puts NAND to shame, in my opinion.
Click to expand...
Click to collapse
According to Darkstone since the build runs off the RAM it is superior to all NAND builds and puts very little stress on the sd card and battery life.
Only AngryBirds doesn't work for me for some reason?
Angry Birds is a must and works fine on mine. I am using the STOCK T-Mo USA ROM with the same Radio as you.
One thing is that I cant wait until the SUPER RAM with SENSE is 100% because I like SENSE better.
Im also glad to hear that the RAM is better than NAND as I cant afford to void the warranty or brick my cell.
MulTiPass said:
Angry Birds is a must and works fine on mine. I am using the STOCK T-Mo USA ROM with the same Radio as you.
One thing is that I cant wait until the SUPER RAM with SENSE is 100% because I like SENSE better.
Im also glad to hear that the RAM is better than NAND as I cant afford to void the warranty or brick my cell.
Click to expand...
Click to collapse
like many others here, im waiting for SUPER RAM + SENSE
as for the clean froyo build, SUPER RAM 1.5 by Darkstone is the Leader however there has been less updates for now, since NAND came out and is all craze and hyped up
using ADW Launcher or the one recommended above, TMOBILE G2 Launcher is probably the recommended ways to go
Sohip said:
Only AngryBirds doesn't work for me for some reason?
Click to expand...
Click to collapse
in order to get angry birds to work just unmount your SD card before you download it in your settings. Then once its installed just mount the SD card and your set.
I tried the super ram build but it has 2 issues, which make it unusable for me:
1. Robot voice but i gues if i upgrade to the latest radio rom it would be fixed
2. Slow and sometimes not responsive screen when waking up the phone, this issue occurs everytime when i try some android build
3. The light sensor is slow too
any ideas ....
dddnnnggg said:
I tried the super ram build but it has 2 issues, which make it unusable for me:
1. Robot voice but i gues if i upgrade to the latest radio rom it would be fixed
2. Slow and sometimes not responsive screen when waking up the phone, this issue occurs everytime when i try some android build
3. The light sensor is slow too
any ideas ....
Click to expand...
Click to collapse
1. Get latest radio
2. Get a new and decent SD card!
3. light sensor? You mean the LED? Every build has problems with it.
Darkstone SuperRam 1.5 Froyo is super flying fast.
Still like it so far.
MulTiPass said:
Angry Birds is a must and works fine on mine. I am using the STOCK T-Mo USA ROM with the same Radio as you.
One thing is that I cant wait until the SUPER RAM with SENSE is 100% because I like SENSE better.
Im also glad to hear that the RAM is better than NAND as I cant afford to void the warranty or brick my cell.
Click to expand...
Click to collapse
jcsy said:
like many others here, im waiting for SUPER RAM + SENSE
as for the clean froyo build, SUPER RAM 1.5 by Darkstone is the Leader however there has been less updates for now, since NAND came out and is all craze and hyped up
using ADW Launcher or the one recommended above, TMOBILE G2 Launcher is probably the recommended ways to go
Click to expand...
Click to collapse
Why are you waiting? The SuperRAM Sense build has been out a few days now. http://forum.xda-developers.com/showthread.php?t=892797
it has problems and bugs , which I dont want to venture into
especially at 0.1
distruct said:
1. Get latest radio
2. Get a new and decent SD card!
3. light sensor? You mean the LED? Every build has problems with it.
Click to expand...
Click to collapse
1. I installed the new radio and i still hear the robot voice, maybe i should install the build on the new radio again
2. My mem card is the stock card supplied with SE's Satio, it is 8 GB HC whatever that means, please suggest a decent card, should it be empty?
3. No i am talking abaout the light sensor, not the LED, this is the sensor, which turns the display off when you hold the phone to your ear, and it turns the display on when you are done
dddnnnggg said:
1. I installed the new radio and i still hear the robot voice, maybe i should install the build on the new radio again
2. My mem card is the stock card supplied with SE's Satio, it is 8 GB HC whatever that means, please suggest a decent card, should it be empty?
3. No i am talking abaout the light sensor, not the LED, this is the sensor, which turns the display off when you hold the phone to your ear, and it turns the display on when you are done
Click to expand...
Click to collapse
1) If you read through the first post in his thread he addresses the robot voice. If you hear robot voice just make a phone call, press the speaker button, and then hangup. voila!! no more robot voice.
2) As far as the touch screen im not too sure, but ive never had a problem, its super responsive. Its best to reformat your card (using your windows sd card formatter) before installing any android app in order to make sure you have everything working properly when installed.
3) i believe there is an option for that, its pocket mode or something, wish i had a better answer for you but i have limited access at the moment.
The first post in the super ram froyo thread addresses heavy battery drain and robot voice and pretty much any major issue the build has.
I
Angry birds working her. I have darkstone ram, and believe me... it is so fast... You need to try it before you can understand me. Everything is working, no issue her...
MulTiPass said:
Angry Birds is a must and works fine on mine. I am using the STOCK T-Mo USA ROM with the same Radio as you.
One thing is that I cant wait until the SUPER RAM with SENSE is 100% because I like SENSE better.
Im also glad to hear that the RAM is better than NAND as I cant afford to void the warranty or brick my cell.
Click to expand...
Click to collapse
Hello, I I am going to Roskilde festival in Denmark next week, and I need a copy a cheap phone, as my Galaxy Nexus is too expensive to bring :/
Would the 540 be a good choice? How is the screen, the battery time and the speed of the phone? What version of android can it be upgraded to (any stable custom Roms?). My biggest concern is the resistive screen :/ How about flash in browser? Is multi touch supported?
The other phone I am looking at is Vodafone 828
Flash? --> No.
Multi-touch?--> No.
Custom Rom?--> 2.1 , 2.2 , 2.3 , 4.0
Battery life?--> Better then the nexus for sure (even better then my sgs2)
This phone is good for calls and sms. If you are coming from a nexus browsing will be a big headache due to the shear difference in web page loading times.
It should be fine as a cheap replacement, battery life is good, phone itself is pretty solid. Resistive screen is fine unless you'll mess with custom roms as these doesn't have screen working calibration which makes operating on the device without stylus pretty difficult. Performance on on the stock 2.1 is rather decent, browsing experience is rather poor on it, gaming and system responsiveness are fine. The situation does change when you're using custom roms ( especially those with .32 and .35 kernels ) but you'll lose screen calibration. You won't notice much difference in browsing between your nexus and gt540 if you'll use .35 kernel and OC. There are two almost perfect custom roms ( with .32 and .35 kernels ) In other words gt540 may not be perfect but it will be definitely better than vodafone 858, unless you want phone only for texting and calling.
shadovraven said:
You won't notice much difference in browsing between your nexus and gt540 if you'll use .35 kernel and OC.
Click to expand...
Click to collapse
You will definitely !
-
if your on custom rom you'll never get perfect stabilty. from time to time it will lag a bit but for a few days a custom GT540 might be ok.
If you really choose it you will have to take your time to get it from 1.6/2.1 to e.g 2.3 with adequate kernel
Hell yeh if i ever make a vid comparing browsing speeds you will tell!
-Grift- said:
Hell yeh if i ever make a vid comparing browsing speeds you will tell!
Click to expand...
Click to collapse
I had old nexus in my mind, that's why.
andreas__ said:
You will definitely !
-
if your on custom rom you'll never get perfect stabilty. from time to time it will lag a bit but for a few days a custom GT540 might be ok.
If you really choose it you will have to take your time to get it from 1.6/2.1 to e.g 2.3 with adequate kernel
Click to expand...
Click to collapse
I tested almost all customs roms, some of them for few months or more and i didn't experienced any lags and problems ( miroslav lewa os, sdsl v2.1 ). If you can't take care of your rom even stock rom will lag and pose problems.
sdsl 2.1 is good
shadovraven said:
If you can't take care of your rom even stock rom will lag and pose problems.
Click to expand...
Click to collapse
don't you think its normal to install 10-20 apps ?
u have to re-size system partition and have a swap partition the phone will work flawlessly i get a charge of 2 days using complete WiFi
andreas__ said:
don't you think its normal to install 10-20 apps ?
Click to expand...
Click to collapse
Of course it's, im having like 30 apps installed on my phone now ( SDSL v2.1 with .3 5 kernel ) and everything works fine. The problem's that most of the people doesn't even bother to resize system partition size or do a full wipe. Installed apps are not a problem, the ones that are running in the background all the time, taking cpu time, memory and killing battery ( load of various widgets and other useless stuff, launchers that are heavy on memory / cpu and such ) 90 % of people problem with certain custom roms would be solved by just reading properly, that's the truth. Unless you can explain how i managed to get SDSL v2.1 to work with .35 kernel ( and other roms as well ) while others can't. That's enough of an offtopic, i'm sure OP does know his answer now.
i know we dont need to resize system partition but i had partitioned it for miroslavs ics and kept it like that since i had 256mb swap
How is the screen to use on this phone? I have almost no nails, so I am afraid of the resitive screen :/
Sebz4n said:
How is the screen to use on this phone? I have almost no nails, so I am afraid of the resitive screen :/
Click to expand...
Click to collapse
2.3 roms + new display are ok
Sent from my GT540 using xda premium
If you're afraid of the screen, you can always get some cheap stylus or make it yourself ( from a pen ) and it will be fine.
Sebz4n said:
How is the screen to use on this phone? I have almost no nails, so I am afraid of the resitive screen :/
Click to expand...
Click to collapse
I think screen responsiveness it's a lot better on miroslav ICS than on previous roms. On GB I had to push very hard on the screen or it won't catch the touch.
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...