Database Develop

[Q] GT-I9000 Bootloop with Wifi on

Hi All,
I have a strange problem for the last month or so which is giving me a lot of headache. I was hoping someone here could help me.
I have a galaxy s i9000 which I got on contract from 3 UK a few months back which came with Froyo 2.2.1. Everythng was fine and sometime later, i was offered an upgrade to Gingerbread and I went ahead with it. Then, I decided to root the phone as well with CF-Root, something I had never done before (rooting Androids that is).
It went well with that as well, and I got CWM and Superuser installed but I discovered that I can't use the Wifi anymore. The moment I switch on the wifi, within a few seconds the phone goes off into a bootloop. Switching off, battery pull, nothing works and the bootloop just comes back when the phone is booted back up. Apart from a full factory reset and a restore from a nandroid backup I haven't found a way of correcting this. So effectively, I am without Wifi at this point. Since then, I have switched to a different cf-root kernel, added lagfix etc. and everything works...except the wifi. I have not touched the ROM in any way, despite being tempted to do so many times. Didn't want to break anything else in the phone being quite new to this.
The current setup of the phone is the following:
Firmware: 2.3.3
Baseband: I9000JV5
Kernel: 2.6.35.7-I9000XXJVO-CL182937se.infra
Build: GINGERBREAD.NEJVD
I had other cf-root kernels before, and all of them have the same wifi issue. This one at least gives me a very smooth interface.
Would really really appreciate if someone out there can help me or point me in the right direction. Why am I getting this bootloop when I switch on the wifi and is there a way of stopping this? Many thanks in advance.
Abhi

I'd come off that baseband as its your network operators release, flash JVH, JVP, JVR or JVB or something, then all should be fine dude
Sent from my GT-I9000 using XDA Premium App

Many thanks. Finally took the plunge and used rom kitchen for jv5 with full wipe. Things seem to be working fine now. Am still using the same kernel and it looks ok so far!

Word of advice....galaxian kernel will double your phone speed it *whoosh* super quick lol
Sent from my GT-I9000 using XDA Premium App

djice000 said:
Word of advice....galaxian kernel will double your phone speed it *whoosh* super quick lol
Sent from my GT-I9000 using XDA Premium App
Click to expand...
Click to collapse
Thanks for that! But now, using my new found confidence on all things Android have installed GB 2.3.4, again from ROM kitchen. The kernel is the Chainfire kernel of JVP. Its fantastic and the phone has speeded up tremendously!! Will still try Galaxian to see if it gets better.

[Q] Phone crashes randomly

Hi,
I recently updated from an old 2.2 rom to 2.3.4, (surface rom), and have noticed that occasionally the phone seems to crash for no apparent reason. It is however, not a reboot, as far as I can tell. phone locks up, within 5-10 seconds i'll see lock screen, (there's no boot animation or anything, or error message), with all previously running applications closed. Can't reproduce reliably, last occurred when I was just listening to music on it.
Any idea what sort of crash/problem this is, and what might be affecting it? (ie launcher, rom, kernel etc)
Running surface rom, semaphore kernel, zeam launcher, not OC'ing
Thanks for any help!

Mate i think surface is not too much good....i think u should go with Blockbuster rom....u just flash and you ll find difference....if u like enery efficent then dnt flash anyother kernel remain on stock....and if u likr Overclocked kernel then go with GalaixanGt or Semaphore 1.5.0.....then u see the really stable and energy efficent rom.
Sent from my GT-I9000 using XDA App

Hmm, so you think it's an issue with the rom?

Yes i try almost every rom from last few months there is some problem in this rom which needed to be fixed
Sent from my GT-I9000 using XDA App

charging taking to long. not throttling down.

When I plug my phone in to charge it stays at 800mhz instead of throttling down to 100-400mhz like its supposed to. I'm on pinnacle ROM and its taking forever to charge. Anyone else have this issue and maybe have a fix for it? Thanks.

Are you using Tegrak?

Yes, I do have it set to throttle down and using Ondemand scheduler.

Kill it and check if it get fixed. I recommend rebooting it after you change tegrak's settings.

Killing it seemed to have worked for now. How can I fix it so I can still overclock? It hasn't done it all the time, Just recently but I haven't installed any new apps or anything.
Sent from my Cappy using the XDA app.

Try clearing the app's cache. Maybe even Dalvik if you have too? Don't know.

I'll try, thanks man.
Sent from my Cappy using the XDA app.

well, getting rid of tegrak didn't help. Still charges and stays at 800mhz.
Sent from my Cappy using the XDA app.

Try unistalling it then installing it? I've used tegrak on 2.3.3 and 2.3.4 and never had any issues with it.

prbassplayer said:
Try unistalling it then installing it? I've used tegrak on 2.3.3 and 2.3.4 and never had any issues with it.
Click to expand...
Click to collapse
Tried that and still no difference......can't figure it out.

What Freq and Voltage you running on each level? Are you using Tweaks? You said you had it "Ondemand" scaling but what min-max Freq?
Edit: I decided to test Tegrak on a 2.3.5 Beta Fusion build, seems to work fine.
Edit 2: Flashed another 2.3.5 beta build and I got that problem you had. Ill keep looking in to it

prbassplayer said:
What Freq and Voltage you running on each level? Are you using Tweaks? You said you had it "Ondemand" scaling but what min-max Freq?
Edit: I decided to test Tegrak on a 2.3.5 Beta Fusion build, seems to work fine.
Edit 2: Flashed another 2.3.5 beta build and I got that problem you had. Ill keep looking in to it
Click to expand...
Click to collapse
It might be a problem with something included in Pinnacle but I can't narrow it down.
Ondemand 100min-1200max with stock voltage settings.

Na Fusion VII Beta is doing the same thing. I think its a tweak on the kernel maybe? I've been kinda busy and will be for the next few days, so don't know when I'll mess with different kernels.

I'll try the other kernel option and see what I can find.
Sent from my Cappy using the XDA app.

I'm having the same issues on continuum with latest talon kernel. And it's been installed on my phone for weeks now and the problem just started. I also have an issue with media server running constant and it gets the phone hot and drains the batt....not sure if the two things are related, but it all just happened all of a sudden.

rmntruexjr said:
I'm having the same issues on continuum with latest talon kernel. And it's been installed on my phone for weeks now and the problem just started. I also have an issue with media server running constant and it gets the phone hot and drains the batt....not sure if the two things are related, but it all just happened all of a sudden.
Click to expand...
Click to collapse
Using cpuspy or other monitoring software, what speed is it stuck at when charging? Are you running tegrak as well?
Sent from my Cappy using the XDA app.

Well tried a fresh install of Fusion and it still does it......

Geezer000 said:
Well tried a fresh install of Fusion and it still does it......
Click to expand...
Click to collapse
Ya Just used Fasty KI2 and It does it with out Tegrak. What ever it is, its anoying not enough to reflash to stock to check if its the rom or kernel.

prbassplayer said:
Ya Just used Fasty KI2 and It does it with out Tegrak. What ever it is, its anoying not enough to reflash to stock to check if its the rom or kernel.
Click to expand...
Click to collapse
I have flashed Fasty ki2, Fusion, Pinnacle, Apex and so far they all do it with or wothout tegrak.

Fresh look bump.....

Very slow Galaxy S

I have galaxy s since last one year and i love it... However my phone has become very slow these days.. I tried several roms and kernels.. Formatted both internal and external SD cards... But still it is very slow... I remember that I dropped it 3-4 times... Is it because of it?
Can someone suggest me please... What should I do...
Sent from my Galaxy S using Tapatalk

Maybe over clock it ...? I thought the new ROMs would have helped. It could be the fact that your phone is older now and some internal hardware has been worn out
Nexus S (GSM i9020a)
CM9 Nightly Kang (Build 5 of 2.1)
Eugene's Kernel (Speedy-7)
OC 1100/100 (lulzactivev2)

309041291a said:
Maybe over clock it ...? I thought the new ROMs would have helped. It could be the fact that your phone is older now and some internal hardware has been worn out
Nexus S (GSM i9020a)
CM9 Nightly Kang (Build 5 of 2.1)
Eugene's Kernel (Speedy-7)
OC 1100/100 (lulzactivev2)
Click to expand...
Click to collapse
Can I do anything related to the hardware? I mean how can i check if it is not giving 100%?
Sent from my Galaxy S using Tapatalk

I'm no expert so I'm not sure. Best bet would be to replace the hardware which Costs a ton of money. Its better to just a get a new phone. Either that or maybe mess around with new ROMs some more. Maybe you are wiping your phone incorrectly or maybe you use it too much
Nexus S (GSM i9020a)
CM9 Nightly Kang (Build 5 of 2.1)
Eugene's Kernel (Speedy-7)
OC 1100/100 (lulzactivev2)

my suggest...
1. update your firmware to last version (2.3.6).
2. try to change kernel and custom rom.
3. maybe, with some different kernel and custom rom, you can choice the better option for your device. for example, try using kernel semaphore (gingerbread) and custom rom F1 or other.

I would be very surprised if physical trauma has simply caused a slow-down in speed. It would more likely show itself as random reboots and other more obvious symptoms.
Much like Windows, after a lot of use, it slows down - you have said that you've flashed other roms, maybe you just haven't come across a good one; there are after all a lot of different ones...
I would suggest the deodex-ed / rooted stock rom from RAMAD Gingerbread JVT. As I remember it was always quite stable and fast.
The hardware components inside a modern phone will not wear-out after a year - they are not moving parts! - when ram or a processor wears out it usually results in total system crashing not just a slow down.

Thank you all for your feedbacks and suggestions. I use my phone a lot. Usually i use TV out a lot as i do not have a cable connection in my hostel room. I use my phone a lot. I flashed it atleast more than 100 times. I have not seen any reboots, crashed , soft reboots etc very often. When i use MIUI rom my phone is very fast indeed however , it does not have a TV Out and therefore i have to use a stock based rom.. i will try Rammad's GB Rom as per your suggestion and will report back. As i told you that i dropped it a couple of times, is it possible that any of the Internal components have become loose?

Have you ever tried Advanced task killer? Or even killed tasks?

zadusimple said:
Thank you all for your feedbacks and suggestions. I use my phone a lot. Usually i use TV out a lot as i do not have a cable connection in my hostel room. I use my phone a lot. I flashed it atleast more than 100 times. I have not seen any reboots, crashed , soft reboots etc very often. When i use MIUI rom my phone is very fast indeed however , it does not have a TV Out and therefore i have to use a stock based rom.. i will try Rammad's GB Rom as per your suggestion and will report back. As i told you that i dropped it a couple of times, is it possible that any of the Internal components have become loose?
Click to expand...
Click to collapse
Did you try the ics roms. These r pretty fast..specially team icssgs.
Sent from my GT-I9000 using Tapatalk

Try ICSSGS RC 4.2. I had the same situation as you. It was fine for one year and I was using Darky rom by that time. Suddenly I started feeling that my phone is too slow. Lot of stuck. Sometimes I had to remove battery just to restart.
Now running above ICS rom with Devil 14.2 Kernel its rocking ...

yeah I'd suggest u the advanced taskkiller too
in options you can set the auto killlevel to safe, so that it kills smth like games in the background but not important apps
since then my phone is quite fast even with stockrom

gezze said:
yeah I'd suggest u the advanced taskkiller too
in options you can set the auto killlevel to safe, so that it kills smth like games in the background but not important apps
since then my phone is quite fast even with stockrom
Click to expand...
Click to collapse
Yeah, and you can just use the ATK widget when you close out of something press the icon and it kills all the background apps...

I will surely try ATK and ICS roms as per your suggestions...
Sent from my Galaxy Nexus using Tapatalk

keep us updated...

Just get stock jw1, flash with reparation to wipe everything, then do a factory reset via secret dial code. Now install semaphore 2.5.0 kernel. Dl superuser to get root. Now install thunderbolt tweaks the main package and the 60lmk other addon(read thread how to) . This is the best setup i can think of in terms of speed bat life and functionality. Next step look in pikachus Android optimization thread and remove the bloatware listed there, basically remove as much bloat as possible. Enjoy ur fast phone.
Sent from my GT-I9000 using Tapatalk

Perhaps you should try the ICSSGS RC4.2 with Devil 14.2 LED VC Kernel. I'm on it and its awesome, my phone lags no more and I'm using it for my primary phone.
Sent from my Galaxy S using XDA Premium

[Q] Phone defect? Going on and off all the time

Hi,
today my phone P990 starts always going on and off after a while (in rom, in recovery always, not able to start the rom anylonger). Battery is fully charge, phone is rooted, worked since half a year without problems. Using TonyP Para Rom V12 and Pengus Kernel V120. I formatted system, have done a full wipe etc.
But after some minutes, the effect always comes up again? Battery defect? Or any other ideas?
thanks a lot
tomtom

I would suggest putting some logs on PA thread, if you are using paranoid android. It is useful to help you.
Sent from my LG-P990 using xda app-developers app

maybe the problem you have is that you have a high OC, and try using a stable KK, not an experimental