So, I have one of the first Vibrants to hit the store. I'm running Neobuddy ICS Passion V8. Before the *****ing begins I want to say that I love this rom.
I followed the install instructions to a "T".
I used antutu cpu master to overclock to 1.3 because I read that other people were doing it and didn't see any complaints. When my phone booted to the point where the message that cpu master had superuser privileges came up, it froze and the display changed colors getting lighter and washed out looking. That scared the crap out of me and I thought I had just cooked my cpu. I pulled the battery and rebooted then tried to open the app and change the settings before it froze and failed, rebooting 6 times, battery pull each time. I finally relented and did a factory reset. Previous to this adventure I had it clocked at 1Ghz max and 100 min and was experiencing no lag. I just got greedy. I only changed it at all because I was getting 16 hours of battery life and thought I could trade some battery for speed. I have it running at 1.2 now and it's fine. So this is not so much a question but an answer to anyone who might be asking themselves if they should overclock to 1.3.
Bugs
mute/unmute necessary for incoming call audio
automatic brightness not responsive
complaints
contacts app doesn't match the rest of the theme
no text button next to phone button on contact
no long press functionality on contact
When it comes to Vibrants, all our phones are different. Some users will be able to run at 1.3 from now until our Zombie overlords take over and we're forced into indentured servitude. Others, like you and I will be lucky to run a mild OC without freezes.
I used to oc to 1.6 ghz on cm7
sent from the xda app on my android smartphone.
What he said!
younix258 said:
I used to oc to 1.6 ghz on cm7
sent from the xda app on my android smartphone.
Click to expand...
Click to collapse
My first Vibrant T959, manufactured prior to Oct 2010, used to fly, and overclock like there wasn't any tomorrow, and would flash anything! Was the most cooperative phone I ever had! Wish my wife was like that. LOL
Then I unfortunately got into a true HardBrick with it, and stupidly, instead of JTAGing it, got T-Mobile to exchange it, for a same model, but with a manufacturing date on it of 8-2011!
And this replacement phone, hasn't even ever performed as well as the old one, despite how I set it up, And at first it was stuburn as hell to get it to cooperate with flashing, until I unlocked it, and it calmed down alot, even though that makes no sense at all, but nun the less, it is what it is!
Point is, that each week, month or quarter, the phones aren't consistent in manufacturing qualities or how they run and perform, or the components they use. I had a Thoroughbred in the beginning, and now I how a plow horse, yes she still works well, but needs alot of coaxing, I had to re-do the GPS contacts right so there was firm pressure, and the SW flashes were a ***** in the beginning!
But I believe when this phone first came out, there was better quality of manufacturing and they used the same consistent components, until they shifted their focus on other models to push onto the market!
So again, what Billy Bobs got going with his, Isn't what it ll be with yours!!
Related
I apologize now for the long explanation but feel the info is needed.
I had a replacement phone in March so I could root and after that all was good, I finally in May got frustrated with my lead bunker of a house and no cell signal so I got a Verizon Network Range Extender (Samsung). After I got it and a week of getting it working right my cell signal hasn't been the same, I know the bar graph isn't an accurate representation of the signal so I was watching the Db levels and the fact when I was in the middle of town in the open I had one or no bars and a -104 signal.
After Kaos and Conap got Froyo up and usable I tried using the ROM's but after a week the phone would be so unresponsive it would take literally 5 minutes to find a number and dial it. I would miss calls all the time and constantly would have to reboot. I was at first trying 768 on the OC but eventually stepped it down to 710. I have tried KaosFroyo V19-33 with no luck, each update I do has less and less time between flashing and when it becomes unresponsive. I have Tried CLEB 1.6-2.4 same thing. The only ROM that I can use with the best results is Plain_JaneT2 OC'd at 710.
I currently still have cell reception issues and sluggishness on most ROM's, I am on the current 4.27 radio and have formatted several times the SD card to start with a blank slate. I am not using swap or ext3 for AP2SD. I have unrooted and rerooted 2 times. This phone was pre legit 2.1 OTA.
Not sure what I did or what to do next to get it back in order
morphius2036 said:
I apologize now for the long explanation but feel the info is needed.
I had a replacement phone in March so I could root and after that all was good, I finally in May got frustrated with my lead bunker of a house and no cell signal so I got a Verizon Network Range Extender (Samsung). After I got it and a week of getting it working right my cell signal hasn't been the same, I know the bar graph isn't an accurate representation of the signal so I was watching the Db levels and the fact when I was in the middle of town in the open I had one or no bars and a -104 signal.
After Kaos and Conap got Froyo up and usable I tried using the ROM's but after a week the phone would be so unresponsive it would take literally 5 minutes to find a number and dial it. I would miss calls all the time and constantly would have to reboot. I was at first trying 768 on the OC but eventually stepped it down to 710. I have tried KaosFroyo V19-33 with no luck, each update I do has less and less time between flashing and when it becomes unresponsive. I have Tried CLEB 1.6-2.4 same thing. The only ROM that I can use with the best results is Plain_JaneT2 OC'd at 710.
I currently still have cell reception issues and sluggishness on most ROM's, I am on the current 4.27 radio and have formatted several times the SD card to start with a blank slate. I am not using swap or ext3 for AP2SD. I have unrooted and rerooted 2 times. This phone was pre legit 2.1 OTA.
Not sure what I did or what to do next to get it back in order
Click to expand...
Click to collapse
i cant attest for the network extender but i have noticed if the rom has an overclocked kernal and i use setcpu it turns into a slugg real quick especially with autokiller installed. u might just try a rom and not overclock it and and uninstall autokiller that is if you have that..
Are you using the setcpu widget? That messes things up quite a lot. The degradation in performance is enough that you'll have to pull the battery waking up, even when you're overclocking to 768mhz.
No I never use that I just go on the hopes that the OC is working but I wasn't aware that the OC Kernel and the Autokiller was an issue. May give that a try.
Usually the sluggishness is there but not terribly bad but I am lazy after I flash a new rom and don't set up my screens or apps for a couple of days so that may be the reason there is a window of time that the performace isn't teribble and tollerable but as soon as I do a SetCPU it goes out the window.
Thanks for the advice, just wish you had something for my cell signal.
I don't know about the extender. But yeah don't use the widget. What settings do you use for SetCPU? You may want to call Verizon for the extender.
Ok so day 2 of CELB 2.6 and all is good I didn't go to SetCPU and I noticed when I put the Facebook widget on the screen things got somewhat slow so I took it off. Still have some slow response in the app drawer but that may be from my screen replacement. It is a Verizon screen not a third party but don't know.
As for signal I am just going to suck it up and wait till August and get a newer phone.
Thanks for all the ideas
I would remove setcpu altogether and maybe try a different rom just to be safe.
Sent from my BLACK RAIN V2 using Tapatalk
Hello everyone,
Has anybody else who updated to 4.1.57 find that their Atrix is now kinda sluggish? I don't mean all the time, but every now and then I get random stutters or sluggishness when switching between programs. A couple of times, it even screen locks for a few seconds when waking up. This has never happened to me before with the 4.1.26, where programs just run without hesitation. They either run smoothly, or FC in the process. But now, some of them just becomes jittery.
I wonder if it has something to do with Motorola's battery improvement in the update. When it got sluggish on me, I decided to go to into setcpu to see at wat speed the phone was running. I noticed that the phone was throttling severely all the way down to 216 mhz the second the phone is not being used. it fluctuates up and down but it seems to always drop down there once i dont touch the phone. I think this is causing an issue cuz there's a lot of background apps and widgets running and once you try running an active program, it takes a split second to start, and that split second causes it to stutter.
I haven't had the screen lock in a while, so that's a good thing. But it seems setcpu can't seem to force the cpu to constantly stay high, even if i put the minimum to 1000mhz, so I get those stutters every now and then.
Anybody has any suggestions on this matter? Im thinking if this persists, I might just go back to 5.1.26 until they come up with a major update. Really the only reason I updated was cuz the prompt was driving me mad.
p.s. another way I know how the cpu isnt running a constant 1ghz --- my phone isnt as hot as it used to be. it used to be so warm in my hand, my hand would turn red from holding it.
It takes very, very little time for a modern CPU to change its clock speed. Monitor your computer's CPU clock closely sometime, it almost certainly does throttling to a similar degree. I also observed similar levels of throttling via tegrastats on my Atrix prior to the update.
Personally 1.5.7 has been good for me, at least in the sense that nothing appears to be worse after.
Sent from my MB860 using XDA App
Only heard good reviews on 4.1.57. Can't wait for Bell to issue it too
lol, i dont like throttling. All my PCs n laptops run on full speed (throttling disabled) whenever they're on. I expect the same with my phone x) I just don't like any lag but I understand wat you mean. I still wanna hear what other's feel about the update.
note: I'm about to deodex the phone in a bit. Let's see how it ends
Moving stuff around in device memory is an order of magnitude slower than your CPU changing clock speed, and moving stuff between flash and device member is an order of magnitude or two slower than that. CPU throttling isn't the right place to look for this sort of issue.
As for your computers and not allowing them to throttle...enjoy the power bill I suppose. Even in overclocked scenarios modern processors work just fine with throttling enabled.
Sent from my MB860 using XDA App
Atrix 4.1.57 issues
I have had my Atrix for over a month with no issues. After the 4.1.57 update I have the following 3 issues:
1. The phone randomely reboots (never did this before the update)
2. The cell signal is much weaker; no signal in areas where it had signal before
3. Apps seems to start slower.
I called motorola technical support and asked if there is a way to un-install this update; the answer is NO, all they can come up with is a factory RESET which will not remove the update but will remove all my data and Apps.
I finally sent the phone to AT&T and got a replacement with 4.1.26 and it works fine, especially the battery life and the cell signal and no reboots so far.
I'm awaiting delivery of my new unbranded and unlocked Galaxy S2 really looking forward to having the best phone on the market, since March last year ive had a HD2 which was/is a superb phone and has served me well but ive sold it on to fund buying this, i notice some user names on here who used to be post on the HD2 forums just have a couple of questions regarding the few ROM's which are currently available for the GS2.
The most popular appear to be Villian ROM and Litening ROM, both seem to have superior battery life and are very fast, the Litening ROM sems to be easier to flash (i stand corrected on that) and you can flash this without having to root your phone first, im experienced in flashing ROM's for the HD2 but this is all new ground for me so out of those 2 ROM's which would you recommend beginning with, any pro's and con's,etc,etc ive read both threads and both appear to be excellent ROM's, Pulser in particular appears to be a very skilled developer.
Also any other recommendations/tips you have starting out, is it a good idea to get rid of all the Samsung bloatware to preserve battery life,etc,etc.
I've read quite a bit on here so im aware of certain things already but even though ive been on XDA a long time im so used to the HD2 i feel like im starting over again (well i suppose i am in a way)
Cheers folks..
I made the same jump as you and Im very happy with it.
With regards to the "easiest" rom to flash, I dont think theres any difference really, as long as you follow the instructions carefully its really very simple.
The VR thread has very clear and simple instructions. You'll get used to it
Bloatware, I would reccomend just leaving it as it is and seeing how your battery life is. If you feel it could improve then start stripping things out and see if it gets better. I've only got rid of the wifi sharing crap and can still make it through a day with 40% left. That could probably improve as well if I bothered to tinker some more.
You could always flash the lite version of villain rom, which contains NOTHING.
Not really willing to compare the two you mentioned as I havent tried litening so that would be unfair. For me, the main advantage of using VR is the VillainTweaks app and the level of support available, should you need it.
Cheers for the response and tips, just one thing about the Villian ROM is it very stable with minimal or no bugs/lag?
I've already acesertained that the battery life is superior so that is great to hear,and i can see that Pulser unlike some devs does seem to be involved in the thread (support) which is also a positive thing.
I might keep the stock on it for a few days then flash, I suppose if your on XDA it obviouss your gonna be flashing a custom ROM at some stage.
In all honesty I can think of only one bug I have suffered and I have seen it reported on other ROMS not just VR, sometimes my screen timeout settings will return to the default 30 second setting.
I have had 2 random reboots in the month or so that I've had the phone and both of those only occured after I had gone over 100 hrs without a reboot....
As for lag.....
Run your stock ROM for a few days, enjoy the blazing speed and responsiveness of this beast of a phone.
Then flash VR and marvel in complete amazement at the fact that this thing can get even faster
I keep mine underclocked to 800Mhz (sometimes I'll bump it up to 1Ghz for gaming) and its way snappier than my HD2 ever was.
Was similar to the first time I flashed an energy rom instead of stock winmo...
conantroutman said:
In all honesty I can think of only one bug I have suffered and I have seen it reported on other ROMS not just VR, sometimes my screen timeout settings will return to the default 30 second setting.
I have had 2 random reboots in the month or so that I've had the phone and both of those only occured after I had gone over 100 hrs without a reboot....
As for lag.....
Run your stock ROM for a few days, enjoy the blazing speed and responsiveness of this beast of a phone.
Then flash VR and marvel in complete amazement at the fact that this thing can get even faster
I keep mine underclocked to 800Mhz (sometimes I'll bump it up to 1Ghz for gaming) and its way snappier than my HD2 ever was.
Was similar to the first time I flashed an energy rom instead of stock winmo...
Click to expand...
Click to collapse
Just out of curiosity mate why do you keep your phone underclocked to 800Mhz?
jonny68 said:
Just out of curiosity mate why do you keep your phone underclocked to 800Mhz?
Click to expand...
Click to collapse
Just a balance between speed and extending battery life that little bit more. It really doesn't feel any slower at 800 than it does at 1.2 but it uses less power.
Sent From My Fingers To Your Face.....
Recommend:
Sounds good when i get mine i think ill try that.
Just 2 more questions i forgot to ask first time
I haven't seen anyone mention using X-Scope browser on these forums just Dolphin and stock, X-Scope for me was the best browser i know of and i used it all the time with my HD2 am i to assume this browser also works fine with the GS2?
Also does ROM manager work on the GS2, reason i ask is because when i had the HD2 sometimes after installing certain apps or a new ROM i would get force closes but after fixing permissions in either ROM manager or CWM it usually fixed that problem.
Cheers
Just tested x scope and it seems to work fine.
Rom manager is not something I've ever been a fan of, theres no way of knowing what your flashing. You can fix permissions through cwm anyway.
Sent From My Fingers To Your Face.....
I'm running JT's vanilla GB [over Heimdall'ed stock EH03] on my fascinate.
I use my fascinate as my alarm clock, and I woke up this morning to a extremely choppy ringtone. < and that is is the understatement of the day.
Anyway, I try to press "dismiss" to dismiss my alarm, and it feels like the screen is not responding. I press the power button, and it takes probably like 5 seconds to complete the CRT animation. After that, I can see the screen is still on (hard to tell unless in the dark with the AMOLED), and it won't do a thing after that until I 3-button-combo or take out the battery.
As a side note, it was also doing this on my previous rom, SuperClean3 v8.1. One of the main reasons I switched back to JT's vanilla gb.
The first night the alarm worked fine. [2 days ago] Yesterday, I was watching some video files, I pressed the power button, I left for a few minutes, I came back and it was frozen. [Took foreverrrrrr for the CRT turn-on animation, and screen did not respond].
This is really really annoying, and I would really like to find out what is wrong with my phone.
One more thing I should mention.. this same kind of thing happened once in a while on the stock froyo firmware, when I bought it on craigslist. I would come to it sometimes and turn it on, and the lockscreen would show and the touchscreen wouldn't respond. I had to take the batt. out then cuz I didn't know about 3-button-combo.
The USB would only charge and not transfer files and only would charge.
So I sent it in cuz samsung said I had 1 mo. warranty left, and then they said they fixed everything in the ticked, and I got it back and it seemed to work. [the usb file transfer worked..]
So can anybody give me any advice? Like logcat? Would that tell me what is causing this problem?
Any help is appreciated!
Are your CPU settings stock? I've noticed the "sleep of death", which sounds similar to your issue, when I was undervolted too much at 100mhz.
k_nivesout said:
Are your CPU settings stock? I've noticed the "sleep of death", which sounds similar to your issue, when I was undervolted too much at 100mhz.
Click to expand...
Click to collapse
Thanks for the reply. I will look into this 'sleep of death' thing.
And I haven't edited my cpu settings. I went to superuser to be sure and the only apps listed are Superuser, Terminal Emulator, and Titanium Backup.
So I just went on a 1-hour trip, and when I got to where I was going, this happened to me again. The screen-on animation was slower than a slug on salt. 3-button-combo reset, I let it reboot, and it was fine.
I just got home 1/2 hr ago and it did it again.
Sigh.. well I only have like 2 apps that always run, 3G Watchdog and Equalizer. I've uninstalled 3G WD just to see if it does anything.
Edit: I will install ROM Manager and set the absolute minimum freq to 200mhz, and see what happens. That would make sense if it's messing up at 100mhz when the screen goes off, and then it's not able to think fast enough to up it back to 1ghz.
It sounds like it might be an issue with your phone if the problem follows you between roms and your kernel settings are stock. That is unless this is a more common issue with those roms, but I don't think they are. The sleep of death issue that I've run into before is simply the phone refusing to wake up, requiring a 3-button reset/battery pull, so I'm not sure about the slowness to respond before freezing that you've run in to.
I'd try setting the minimum frequency to 200mhz with an app like voltage control (rom manager is for rom flashing, backups/restore), maybe that would help the phone's responsiveness regarding waking up properly. I'm not sure though since when I had the sleep of death issue mentioned before, I just lessened the undervolting I had done and it seemed to resolve it. I don't have much expertise to share on your specific issue though, I'm sorry. I'd almost be inclined to believe that it might be a more phone-specific problem if you're running stock kernel settings on roms where other users haven't reported the same issue, but trying the 200mhz thing can't hurt.
k_nivesout said:
It sounds like it might be an issue with your phone if the problem follows you between roms and your kernel settings are stock. That is unless this is a more common issue with those roms, but I don't think they are. The sleep of death issue that I've run into before is simply the phone refusing to wake up, requiring a 3-button reset/battery pull, so I'm not sure about the slowness to respond before freezing that you've run in to.
I'd try setting the minimum frequency to 200mhz with an app like voltage control (rom manager is for rom flashing, backups/restore), maybe that would help the phone's responsiveness regarding waking up properly. I'm not sure though since when I had the sleep of death issue mentioned before, I just lessened the undervolting I had done and it seemed to resolve it. I don't have expertise to share on your specific issue though, I'm sorry. I'd almost be inclined to believe that it might be a more phone-specific problem if you're running stock kernel settings on roms where other users haven't reported the same issue, but trying the 200mhz thing can't hurt.
Click to expand...
Click to collapse
My bad, I meant ROM Toolbox. It has lots of apps built in including a CPU slider. Anyhow disabling 100mhz did not fix anything. So tonight I will set the minimum frequency to 800 or even 1000 mhz because I want to see if that stops the freezing up. If it does, then I'll know it's a clock speed issue.
I should also mention I sent it in for USB repair. It wouldn't connect to PC, it'd only charge. I also mentioned to Samsung it would lock up every so often from waking up. They upgraded froyo to gingerbread and said it passed all tests, sent it back, I never stayed on the firmware they gave me long enough to see if it froze up.
So on the stock roms, do they underclock the cpu frequency by default??
I don't believe that the cpu is underclocked or undervolted by default. I'd try flashing the stock firmware (EH03), and seeing if the issue happens there as well. Although I thought you mentioned it happened to you on superclean before, and I think that's just a modified stock rom? But it would be worth trying I suppose, then you could be sure it's a hardware issue and see about possibly getting a replacement. I'm assuming that you're still under warranty if you've sent the phone back recently enough for them to put gingerbread on it?
Other than that, I can't really think of anything else.. Maybe try jumping on IRC sometime and hitting up some of the people (that are generally more knowledgeable than myself) on there, they'd probably be able to give you a good idea of whether or not it's an issue with your specific phone. Although that's what it sounds like to me, I'm no expert.
k_nivesout said:
I don't believe that the cpu is underclocked or undervolted by default. I'd try flashing the stock firmware (EH03), and seeing if the issue happens there as well. Although I thought you mentioned it happened to you on superclean before, and I think that's just a modified stock rom? But it would be worth trying I suppose, then you could be sure it's a hardware issue and see about possibly getting a replacement. I'm assuming that you're still under warranty if you've sent the phone back recently enough for them to put gingerbread on it?
Other than that, I can't really think of anything else.. Maybe try jumping on IRC sometime and hitting up some of the people (that are generally more knowledgeable than myself) on there, they'd probably be able to give you a good idea of whether or not it's an issue with your specific phone. Although that's what it sounds like to me, I'm no expert.
Click to expand...
Click to collapse
Lol, when I sent it in there was like half a month or so left on the warranty, the person said it expires at the end of this month [Dec] so I figure maybe a day or two.
What's the IRC channel info? freenode?
EDIT: I forgot to ask something. So you are saying, the stock firmware [EH03 or froyo EH09] runs the cpu clock constantly at 1GHz? Even when it's sleeping? Wouldn't that give bad battery life? [lol, speaking of batteries, I just got a new one and it's charging]
I had this happen to me 6 months ago. You my friend need a replacement phone. It has nothing to do with the rom/kernal. I tried everything. Sometimes phones just take a crap. Got a replacement. Ran the same thing I ran when it was happening and haven't had a problem since. Sorry to hear. Just explain it it Verizon and see what they do.
gotsflat4love said:
I had this happen to me 6 months ago. You my friend need a replacement phone. It has nothing to do with the rom/kernal. I tried everything. Sometimes phones just take a crap. Got a replacement. Ran the same thing I ran when it was happening and haven't had a problem since. Sorry to hear. Just explain it it Verizon and see what they do.
Click to expand...
Click to collapse
This is bad news indeed, since I am not even sure how many days I have on the warranty. But I think I will Odin EH03, and then set the alarm tonight. If I wake up and it's done it again, I will call up samsung and tell them and hopefully I have warranty.
But please, tell me, when you tried to turn on the phone did the CRT animation go very slowly? and then when you pressed power, it wouldn't come on again?
Edit 2: alright! I call samsung and I have warranty until Jan 9. Woot.. So I set up an RMA with samsung, I will Odin EH03 tonight. If I wake up to a choppy alarm and a non-responsive screen, I shall send it to samsung ASAP and I hope they gimme a brand new Fascinate. that would be awesome..
Nice, glad to hear you got the warranty thing figured out. I was thinking it sounded like an issue with your phone in specific and it sounds like the other poster's experience would suggest that. Hopefully it's an issue that they can replicate and don't give you any issues getting a replacement.
To answer your question, no, the stock kernel settings wouldn't keep the processor at the highest frequency. The only way I can see that happening is if you set the screen-off profile to "performance", and I'm not sure why anyone would do that because it would indeed yield bad battery life I'd think. I'm guessing the stock kernel defaults to an "ondemand"-like profile, where it would scale the frequency according to load and favor lower frequencies or go in to a deep sleep when the screen is off.
k_nivesout said:
Nice, glad to hear you got the warranty thing figured out. I was thinking it sounded like an issue with your phone in specific and it sounds like the other poster's experience would suggest that. Hopefully it's an issue that they can replicate and don't give you any issues getting a replacement.
To answer your question, no, the stock kernel settings wouldn't keep the processor at the highest frequency. The only way I can see that happening is if you set the screen-off profile to "performance", and I'm not sure why anyone would do that because it would indeed yield bad battery life I'd think. I'm guessing the stock kernel defaults to an "ondemand"-like profile, where it would scale the frequency according to load and favor lower frequencies or go in to a deep sleep when the screen is off.
Click to expand...
Click to collapse
Oh. well the reason I asked is because you said this: I don't believe that the cpu is underclocked or undervolted by default.
So this morning, I woke up to my iPod's alarm, which I had set as a backup a few minutes after my Phone alarm should have gone off. I went to see if the phone was frozen, like I was hoping, so that it would reliably broken , but instead it was off. I turn it on, it shows the full green battery.. then it boots up like nothing was wrong. But I think that turning off randomly every night [which I assume it should do every time] is enough for Samsung to realize my phone really is screwed and that they need to do something about that.
So anyway, I printed out the label, packed my phone, and dropped my phone off at the local UPS drop off.
Hopefully I will be receiving some good news from samsung soon [i.e. that they will give me a replacement... ]
mvmacd said:
Oh. well the reason I asked is because you said this: I don't believe that the cpu is underclocked or undervolted by default.
Click to expand...
Click to collapse
Yeah, looking back on that, I misspoke. Technically, UNDERvolting/clocking is just reducing the voltage or clock speed from the "default" kernel settings. So technically, since the stock settings are the "default", they (by definition) would not be "undervolted" or "underclocked". I guess all I was trying to say is that I'm sure whatever the default settings are, they're set for a balance of performance, battery life, and stability. Just because the default max frequency is 1000mhz, doesn't mean that the CPU will stay there, that's what kernel governors are for essentially: to tell the CPU how to scale based on load (as I understand it at least).
Hopefully things go well with the replacement. Just curious, why are you dealing with Samsung directly as opposed to Verizon?
k_nivesout said:
Yeah, looking back on that, I misspoke. Technically, UNDERvolting/clocking is just reducing the voltage or clock speed from the "default" kernel settings. So technically, since the stock settings are the "default", they (by definition) would not be "undervolted" or "underclocked". I guess all I was trying to say is that I'm sure whatever the default settings are, they're set for a balance of performance, battery life, and stability. Just because the default max frequency is 1000mhz, doesn't mean that the CPU will stay there, that's what kernel governors are for essentially: to tell the CPU how to scale based on load (as I understand it at least).
Hopefully things go well with the replacement. Just curious, why are you dealing with Samsung directly as opposed to Verizon?
Click to expand...
Click to collapse
1. I'm not the original owner
2. I'm not a Verizon subscriber. PagePlus Celluar [A verizon MVNO] is my service provider. They have much better plans, including monthly, and prepaid, if you ask me.
Kernel issue.
sent from my Sensation XD
Yess..
Good news! Got an email saying my phone has been shipped:
Code:
Original Problem:
TECHNICAL INQUIRY - PHONE FREEZING / LOCKED UP - FREEZE/DELAY BETWEEN MENU FUNCTIONS
Problem found:
BAD BGA COMPONENT
Solution:
REPLACED PBA
I guess the PBA is basically the motherboard? I suppose that could have been the cause of overnight freezing, and so my phone should be fixed.
Nice.. Just 2 days left on my warranty. Cutting it kinda close, I know lol
Very well done sir
sent from my Sensation XD
Please go easy on me, here. I know how to search forums, I just don't always understand what I read on here. :laugh: My husband has always helped me with most of my Vibrant issues, but he has recently defected to his HTC One S.
My Vibrant is getting unbearably slow. I'd been running a Fishman rom on it, and it seemed very, very slow. We then decided on the Slim Ryder rom. The first day or so it was unbelievably fast. That, unfortunately didn't last.
I have only the minimum apps on there and only one updating widget (BeWeather time and weather. Used to use Beautiful Widgets but it began superimposing the time over itself so I couldn't read the time...).
I'm a realist, and I know that my Vibrant is old. I know it isn't as fast as The Hubs' new HTC. I'm only comparing it to itself. Here's where I've noticed the slow downs:
*when switching portrait/landscape (sometimes tries to show half a landscape screen in portrait mode)
*when touching a text field, it is very slow to bring up the keyboard...sometimes i have to tap multiple times
*when Swyping or using Swiftkey, it sometimes hangs on a letter
*it takes several seconds to bring up my text messages, dialer, call logs...basic phone functions.
*using the browser is unbearable.
I've done the old standard...Master Reset, cleared history, caches, cookies, etc. I have wiped call logs and clear out my texts every other day. I don't store music on my phone (Google Music) and have my photos upload to my Google+ account via wifi so I don't get a lot of that stored up. I do not use a live wallpaper.
I'm not eligible for an upgrade until November. I am absolutely open to trying other ROMs, but as a mama with little people and no landline, having the ability to reach 911 from my phone is non-negotiable. Can anyone offer me any ideas on how to limp through until my upgrade?
Thanks in advance.
My vibrant was pretty slow with 2.1~2.2 using almost any rom;gingerbread was a huge improvement and ice cream sandwich is just blazing fast. I would suggest flashing ICS passion http://forum.xda-developers.com/showthread.php?t=1362961 or another rom that supports 911. Right now, the developers are working on porting jelly bean to our phone, and when its stable, go grab it!
2.1 and 2.2 roms I heard are a lil slow so try to use an ics rom like passion chimera or zenwick
Sent from my SGH-T959 using xda app-developers app
You can check out the kernel bible thread and maybe get a kernel with voodoo lagfix, seems to make my phone faster. I'm running 2.2 Blue Frankenstein ROM, it comes with voodoo lagfix.
Sent from my SGH-T959 using xda premium
Try a kernel with voodoo lag-fix as iTz KeeFy mentioned and in the meantime disable any animations.
tc
The_MamaBee said:
My Vibrant is getting unbearably slow. I'd been running a Fishman rom on it, and it seemed very, very slow. We then decided on the Slim Ryder rom. The first day or so it was unbelievably fast. That, unfortunately didn't last.
<snip>
*when switching portrait/landscape (sometimes tries to show half a landscape screen in portrait mode)
*when touching a text field, it is very slow to bring up the keyboard...sometimes i have to tap multiple times
*when Swyping or using Swiftkey, it sometimes hangs on a letter
*it takes several seconds to bring up my text messages, dialer, call logs...basic phone functions.
*using the browser is unbearable.
Click to expand...
Click to collapse
Fellas, if she is using Slim_Ryder, then she is using a kernel that already has Voodoo included, IIRC.
To me, these symptoms sound like you may be getting bogged down on your low-end CPU frequencies. Maybe get something like SetCPU or CPUmaster from the market and up your lowest frequency to the next step. When I am on a 2.2 ROM, I use BaliX1.2 and I have mine overclocked to 1.2ghz but my lowest frequency is 400ghz and not the standard 100-200 that most use. I find that this bogs my system down a bit more than it should. So that is when I decided to test it out and up the lowest in step increments.
You can go to my Battery Guide and in the 3rd post, there is a link to get SetCPU for XDA users for Free. When you use this, you might also want to check the governors as well. Some 2.2 kernels do not play well with On-Demand (BaliX most definitley does not-proven a long time ago). I have mine set to conservative and no profiles set at all. My I/O is Deadline also.
Woodrube said:
Fellas, if she is using Slim_Ryder, then she is using a kernel that already has Voodoo included, IIRC.
To me, these symptoms sound like you may be getting bogged down on your low-end CPU frequencies. Maybe get something like SetCPU or CPUmaster from the market and up your lowest frequency to the next step. When I am on a 2.2 ROM, I use BaliX1.2 and I have mine overclocked to 1.2ghz but my lowest frequency is 400ghz and not the standard 100-200 that most use. I find that this bogs my system down a bit more than it should. So that is when I decided to test it out and up the lowest in step increments.
You can go to my Battery Guide and in the 3rd post, there is a link to get SetCPU for XDA users for Free. When you use this, you might also want to check the governors as well. Some 2.2 kernels do not play well with On-Demand (BaliX most definitley does not-proven a long time ago). I have mine set to conservative and no profiles set at all. My I/O is Deadline also.
Click to expand...
Click to collapse
Thank you very much. It was the Blue Frankenstein 2.2 ROM I switched from to go with Slim_Ryder. Both have been very laggy.
I will definitely try the steps you've outlined for me, Woodrube. I really appreciate it. I know I'm using a Bali Kernel. It says Bali v1.8.8UV.
I spoke with a second-level tech at Tmo this morning and he said I've done all the troubleshooting steps they could recommend. He said at this point it is a hardware issue.
I will try these steps today and research how I can test my 911 capabilities legally. If if can get over those obstacles, I will definitely try an ICS Rom. I just have to limp through until early November.
Thanks again for the help, guys!