Related
I am trying to get a solution for these 3 problems I am facing with Doc´s 7.6.2.
Maybe it is not a big deal to make it a perfect ROM but these 3 topics are annoying:
I wrote the same message already in Doc´s threat but no answer at all. in 5 min 10 new messages so nobody really takes care for a new question
Hi Guys,
Some problems I do have with the 7.6.2 and for sure I am not alone with these errors.
1 From time to time high energy consumption but sometimes not - this is crazy. One thing I realized when alarm is switched on for all weekdays then it sucks almost 20% in 5h - just in standby mode. Whats wrong here?
2 GPS signal is bad. When you using this tracking tools eg. cardio trainer it looses half time the GPS signal. Was definitely not with older ROMs.
Is that the modem version?
Is this part of the kernel?
3 Bluetooth works but whenever activating and deactivating getting a stupid message about an opp bla bla.
What is wrong?
Who can help?
Thanks
boris03
quite alot galaxy s users have reported issues with the gps reception i used to think its just a driver issue but upon reading into it would seem its related to the antenna. The wifi also suffers from this problem for me it does anyway. you can try out gps booster lite from market it does help outdoors to get a faster fix as for battery issues well im not so sure you would prob better asking in that thread if your still not heard try sending a pm that should work. good luck
boris03 said:
I am trying to get a solution for these 3 problems I am facing with Doc´s 7.6.2.
Maybe it is not a big deal to make it a perfect ROM but these 3 topics are annoying:
I wrote the same message already in Doc´s threat but no answer at all. in 5 min 10 new messages so nobody really takes care for a new question
Hi Guys,
Some problems I do have with the 7.6.2 and for sure I am not alone with these errors.
1 From time to time high energy consumption but sometimes not - this is crazy. One thing I realized when alarm is switched on for all weekdays then it sucks almost 20% in 5h - just in standby mode. Whats wrong here?
2 GPS signal is bad. When you using this tracking tools eg. cardio trainer it looses half time the GPS signal. Was definitely not with older ROMs.
Is that the modem version?
Is this part of the kernel?
3 Bluetooth works but whenever activating and deactivating getting a stupid message about an opp bla bla.
What is wrong?
Who can help?
Thanks
boris03
Click to expand...
Click to collapse
1.) Turn off your lagfix, run stock RFS see if you still get the issue.
Do a fresh install dont add ANY apps other than stock, observe for 1-2 days of battery usage.
2.) GPS is a hit or miss, hardware is broken.
3.) Never had issues with BT, I use it on a day to day basis to pass around files at the office.
Are you using one of those OC kernels? Or any of the suggested kernels for the matter? I was using Super Optimized Kernel for a while and the battery drain was outstanding even on the non-OC versions. Switched to SpeedMod 300hz. Haven't monitored the battery though but it seems better with normal usage. Also, what lagfix are you using? For a time I was using the Ext-4 Overkill lagfix from the ULF and I noticed considerably less battery life.
As Earlz suggested, try disabling lagfixes and tweaks and monitor..then if it is better than before perhaps using a different lagfix would be a solution. Try switching up kernels (remembering to disable lagfixes prior). Try running different launchers too. I'm no expert on how these things work and affect battery life, but this is all based from personal experience.
My GPS never worked from the start no matter what firmware/ROM I'm on so it seems to really be a hardware issue as EarlZ mentioned. If the problem came about after flashing 7.6.2 then try reflashing to stock firmware with repartition and installing 7.6.2 again after clearing cache and factory reset. Somehow that (having a super clean install) usually fixes random problems I get with any ROM. I'm not certain if it will have any affect on GPS performance but it's worth a try.
Bluetooth is still working fine for me. Perhaps the aforementioned clean install advice I gave could remedy this.
Hi there, i rescently installed DJP5 v8.0.1 . And have some problems with it. When i'm making call i hear the other side perfect, but they dont hear me well. Is it some issue with the ROM or ? Have someone else experienced similar problems?
darkfire_bg said:
Hi there, i rescently installed DJP5 v8.0.1 . And have some problems with it. When i'm making call i hear the other side perfect, but they dont hear me well. Is it some issue with the ROM or ? Have someone else experienced similar problems?
Click to expand...
Click to collapse
There is investigation on that one...
For now, it seems to be a modem issue from the stock modem of ADJP5
Flash another modem seems to fix this issue
darkfire_bg said:
Hi there, i rescently installed DJP5 v8.0.1 . And have some problems with it. When i'm making call i hear the other side perfect, but they dont hear me well. Is it some issue with the ROM or ? Have someone else experienced similar problems?
Click to expand...
Click to collapse
Sigh....Thats covered in the main thread for this rom, try a different modem.
Sent from my GT-I9000 using XDA App
hi to everyone,
I instaled to my SGS new room JVH from samfirmware.com and it works great except one very important thing.
Very often when somebody calls me, the screen dosn't wake up and I can't see who is calling
The same happened when I try to use the cell phone and push the home button, the screen also dosn't wake up and the screen always remain black.
sometimes after a few attempts it started to work well untill the next time...
I have already posted this problem on another forum but nobody helped me.
thanks in advance for your help.
Try installing autokiller, set to optimum. Sounds like you are running out of ram/memory management.
markdj57 said:
Try installing autokiller, set to optimum. Sounds like you are running out of ram/memory management.
Click to expand...
Click to collapse
Unfortunately it didn't help, still the same problem.
Which kernel are you using?
-IK- said:
Which kernel are you using?
Click to expand...
Click to collapse
I only installed the firmware I9000XWJVH from samfirmware.com with release date May 4 and nothing more.
http://www.samfirmware.com/WEBPROTECT-i9000.htm
in my phone I found this information:
2.6.35.7-I9000XWJVH-CL184813
[email protected] #2
I suspect its known issue with external sd card.
If you have ex-sdcard inserted, try taking it out and see if the problem still present.
Do you use setCPU?
ulsa said:
Do you use setCPU?
Click to expand...
Click to collapse
I dont use it.
dirn1111 said:
I suspect its known issue with external sd card.
If you have ex-sdcard inserted, try taking it out and see if the problem still present.
Click to expand...
Click to collapse
dear dirn1111,
It seams you were right
After removing the external SD card and testing during the whole day the problem has never appeared again !
Do you know if the Samsung programmer are working to solve this bug ?
Thank you very much for this advice !
doll00 said:
dear dirn1111,
It seams you were right
After removing the external SD card and testing during the whole day the problem has never appeared again !
Do you know if the Samsung programmer are working to solve this bug ?
Thank you very much for this advice !
Click to expand...
Click to collapse
I don't know if Samsung will fix this issue or not,
but I think no..
In my opinion, since SGS has huge internal storage, many people will use without sd card..?? Also not many people actually reported that issue even if it is present.
just my opinion..
its problem with sgs, just try not to use ex-sd..
and also it affect the device overall function,
I just read from somewhere that it decreased quadrant score by 100~200.( although it can be merely numbers, but thats strange)
I've facing this problem as well...
but mine is not related with the ext-sd card problem because im not using it...
anyone can help?
I just had the problem this morning, had to hold power button for 10 seconds to reset. Stock JVH.
AFAIK, the phone was still running but wouldn't turn on as the battery usage showed the battery discharging overnight.
Did any other else facing this problem as well?
because i face again with stock JVO + CF root for JVO.
Yeah I have this problem occasionally, hitting the power button sometimes doesn't wake up the phone, I have to hit the home button or the power button several times I think, cannot remember exactly, but I always manage to bring it up. It's annoying I agree.
I can always bring my phone back by hitting the power button around 10 sec, the boot up screen will occur if it success...
but this is really annoying, and totally a big problem, just wonder is there other else facing the same problem like us or only few users facing it?
Is the GB problem? because i nvr facing this kind of **** when using 2.2.1...
hi i also upgraded my phone from 2.2.1 to 2.3.2 gb i am also facing the same problem. can any body help in rolling back to original oem foryo 2.2.1?
pls help
Has happened on froyo too.
Sent from my GT-I9000 using XDA App
whats the solution for this?
Use stock lock screen has helped me. Probably reducing number of widgets, therefore ram use will help too.
SetCPU app with a minimum of 200 or more Mhz might also help??
i was facing the same problem since i started to use JVH and JVO with Cf-root.. i was using froyo JS8 with speedmod kernel because of the problems coming with JVB so far but when JVH was out i decided to flash it.. first i was using it with Cf-root.. after a long reading time i decided between CF-root and fugumod.. i have chosen fugumod and never experienced not-waking up issue..
but then i switched to JVO and realised its not good with fugumod, i came back to Cf-root and had those "eternal sleeps" 2 or 3 times.. but yesterday i made a whole clean flash of JVO and Cf-root.. so far, no problem..
i red people complaining about the same issue with Cf-root under the fugumod topic.. but i dont know if Cf-root is to blame.. it might be JVO and JVH to blame because fugumod is JVB based, so its normal that i didnt have any not-waking up problems..
PS: i dont think its because the memory is not enough.. because i never use any task killer (not even the task manager itself) but only watchdog for android OS and my RAM usage is normally like 225/329 Mb..
I have installed different ICS roms to 3 different i9000s. All of them has touchscreen problems.
Some parts of the touchscreen does not react to your touch sometimes. You have to lock and unlock your phone to regain the full touchscreen. I have tried different kernels etc... No go. It really annoys when you are dialing a number, writing a message etc.
And interestingly no one mentions about it at ICS Rom and ICS kernel threads. Can I be that unlucky to have the problem on 3 different i9000s (They are not from the same batch, each one is bought from another part of the world, at different years).
I would really like a solution or suggestion. Till now i have tired different kernels, different ROMs (mostly ICSSGS (different versions), and Dark Knight (different Versions)). I even tiried diffrent schedulers and governors.
Peace.
That's weird, I have used SlimICS and have never had TS problems... Are you sure you flashed everything right? Please explain the way you've done it
with one phone installed team icssgs as it should coming from the stock , other phones back to stock with odin than cf root and flashing the roms after wipes factory resets. the usual flashing procedure....
Try flashing the team hacksung base first, afterwards flash your desired custom ROM. That should do it.
could you try to explain the diff. between flasiing without cm9 or or with cm9. whar would
be the difference at the end?
I don't exactly know why this is needed, but I would assume that TeamHacksung or CM9 have some frameworks included which are perhaps missing in custom ROMs. I'm just guessing, don't really know =/
Have you tried it? For a CM9 based ROM, flash CM9 first and for a TH based ROM, TH first
Hello,
Have you checked if the Problem still remains when you are on Stock ROM?
CU
tenos
Gesendet von meinem GT-I9000 mit Tapatalk 2
no i havent but it was working just before i flashed icd.
also i have 2 more phones with the same problem. So it is not my phone malfunctioning.
In ICS-333 from you can turn on show touches in developer options in settings menu you could see if its registering your touch immediately or at all. The browser is the only place I've experienced touch lag though.
Sent from my GT-I9000M using XDA
Hey I got ur prob and I know what causes it, it not a bug, its dirt or water on your screen that causes the prob if u keep the screen spotlessly clean u don't get it
Sent from my GT-I9000 using XDA
I have activated show touch before, it does not register your touch at all. also I have tried cleaning it no go, since this is happening with 3 different phone, i doubt it is dirt etc.
belmethos said:
I have activated show touch before, it does not register your touch at all. also I have tried cleaning it no go, since this is happening with 3 different phone, i doubt it is dirt etc.
Click to expand...
Click to collapse
I know what causing it. It a bug where dirt or water or something gets on the screen and because the drivers on ics is so sensitive it picks it up, try changing sensitivatiy or keep that screen very clean
Sent from my GT-I9000 using XDA
i have the same problem. its very frustating. never happened in gingerbread. only on ICS.the bug happened occasionally, the funny thing is it only affect the first row area of the screen. (lower left altheway up to upper left corner), it doesnt register tapping on the screen but it still register swiping from outside of the area..., like ussual i need to lock and unlock again to make the touch working again.
I have installed GB back and problem is gone? I am out of ideas anyone?
Flashed back ics bug returns, flashing jb same thing.
Exactly the same problem here
With Stock GB everything works fine, with custom roms the right side of the touch screen doesn't react. You have to lock and unlock your phone to regain the full touchscreen.
This is interesting this is far more than i anticipated anyone with a clue?
same problem here. my screen was working when i bought it (obviously). it was froyo then. the touchscreen problem appears when i upgraded to custom ICS rom. the middle part of my touchscreen does not respond to touch. none. nada. although the rest of the screen seems to be responding to touch so far. turning the screen off the on again temporarily fixes the problem, but not always. i put back a gb rom, the problem was gone. i was thinking maybe there's a different digitizer driver samsung put on their stock gb roms. it's really annoying.
any more ideas? should i replace my touchscreen digitizer?
Yes it's really annoying :crying:
What is different between stock gb/froyo and ics/jb custom roms that have such an effect on the touchscreen?
I will try the app SGS Touchscreen Booster to decrease the screen sensivity, maybe it helps
never heard of this problem in all the time i was ics.maybe time for some jellybean
Hi everyone,
I bought a Samsung galaxy s last week from an eBay auction. The phone was described as touch screen lag. I was thinking that flashing a new firmware will solve the problem. I got really cheap though
The touch screen stops suddenly in every 5/6 minutes and I have to lock the screen using power key and unlock again to make it working.
when I got the phone:
Non Samsung battery and chargers were used, I changed and using original ones.
Stock XXJVS firmware in it.
First I flashed stock 2.2.1 froyo and test the screen using *#0*# code. it got pass. But when I start using it, the problem was still there.
Then I flashed stock GB, same story, now slim ics, same thing.
Please someone help me, there is nothing I can do with it now.
I search few threads related to screen problem but couldn't find one with similar problem. So asking here.
mregmi121 said:
Hi everyone,
I bought a Samsung galaxy s last week from an eBay auction. The phone was described as touch screen lag. I was thinking that flashing a new firmware will solve the problem. I got really cheap though
The touch screen stops suddenly in every 5/6 minutes and I have to lock the screen using power key and unlock again to make it working.
when I got the phone:
Non Samsung battery and chargers were used, I changed and using original ones.
Stock XXJVS firmware in it.
First I flashed stock 2.2.1 froyo and test the screen using *#0#* code. it got pass. But when I start using it, the problem was still there.
Then I flashed stock GB, same story, now slim ics, same thing.
Please someone help me, there is nothing I can do with it now.
I search few threads related to screen problem but couldn't find one with similar problem. So asking here.
Click to expand...
Click to collapse
Sounds like a hardware problem to me..but it's really hard to say if it is. But it would definitely seem like it since it isn't ROM related. Maybe a water damage or faulty digitizer?
Sent from my GT-I9000 using Tapatalk 2
This happens to me sometimes very rarely though, it will be weird and hard to touch but speaking to someone with the same phone they said they had this problem to all I do to resolve the problem is lock and unlock the screen, I thought this was normal?
Sent from my GT-I9000 running remICS-UX using XDA premium
It shouldn't be normal. I am using another galaxy s for almost two years. But never had this problem in such extent, little bit lag on touchscreen when on froyo. But never after. Now with slim ics Temple run is more smooth then iphone 4.
Sent from my Galaxy S using xda premium
Kurre said:
Sounds like a hardware problem to me..but it's really hard to say if it is. But it would definitely seem like it since it isn't ROM related. Maybe a water damage or faulty digitizer?
Sent from my GT-I9000 using Tapatalk 2
Click to expand...
Click to collapse
Thanks for reply. When I got it first time, it was really annoying, the problem was so frequent that it was almost unusable. Now in new rom, after unlocking the screen it works little longer then before. Works like a charm when it works. So not sure this is hardware problem.
Sent from my Galaxy S using xda premium
I don't think this is a hardware or problem either, I broke the screen and replaced it and I still have the same thing when though it is very rare, so if it was the screen it should of gone after I installed the new one, btw I installed a whole new pre built front so the bevil and LCD, and my phone has never hib water damaged? Maybe its something to do with the bootloader? As that doesn't change through ROM flashes
Sent from my GT-I9000 running remICS-UX using XDA premium
mregmi121 said:
Please someone help me, there is nothing I can do with it now.
I search few threads related to screen problem but couldn't find one with similar problem. So asking here.
Click to expand...
Click to collapse
try using a LCD modder LCD density modder https://play.google.com/store/apps/details?id=com.birdapi.android.dpi&feature=search_result
@xsenman;
I did that couple of times going through Advance slim setting. That didn't change anything. Now I'll try this as well.
I change touchscreen into chainfire sensitive option in semaphore app. Still lagging.
Tried over clocking to 1200 but it freezes and automatically reboots into recovery mode. I can use only after changing to default
Sent from my GT-I9000 using xda premium
Guys its really annoying now. Its behaving strangely. I played with it few hours and found out that the screen near the home button freezes first. I cant press the dock but still pull the notification bar? then stops working whole screen. I checked the show touches in developers options setting. Sometimes it works randomly actually without touching it , I just place my finger near the screen but didn't touch and on few occasion it works opposite direction, like I scrolled down but it gone up:crying:
Is this the sensor issue? Is there any way to fix? Any idea please?
mregmi121 said:
Guys its really annoying now. Its behaving strangely. I played with it few hours and found out that the screen near the home button freezes first. I cant press the dock but still pull the notification bar? then stops working whole screen. I checked the show touches in developers options setting. Sometimes it works randomly actually without touching it , I just place my finger near the screen but didn't touch and on few occasion it works opposite direction, like I scrolled down but it gone up:crying:
Is this the sensor issue? Is there any way to fix? Any idea please?
Click to expand...
Click to collapse
try this tool to verify where the problem is , if its hardware, you have no choice but to take it to a technician
https://play.google.com/store/apps/details?id=com.gombosdev.displaytester&feature=search_result
and this
https://play.google.com/store/apps/details?id=com.vital.tst.n7000&feature=search_result
https://play.google.com/store/apps/details?id=zausan.zdevicetest&feature=search_result
xsenman said:
try this tool to verify where the problem is , if its hardware, you have no choice but to take it to a technician
https://play.google.com/store/apps/details?id=com.gombosdev.displaytester&feature=search_result
and this
https://play.google.com/store/apps/details?id=com.vital.tst.n7000&feature=search_result
https://play.google.com/store/apps/details?id=zausan.zdevicetest&feature=search_result
Click to expand...
Click to collapse
Screen+digitizer panel can be changed by yourself. For it, you just need couple of tools and little nerves
Instructions can be found from YouTube, this forum and many other places..
Sent from my GT-I9000 using Tapatalk 2
Kurre said:
Screen+digitizer panel can be changed by yourself. For it, you just need couple of tools and little nerves
Instructions can be found from YouTube, this forum and many other places..
Sent from my GT-I9000 using Tapatalk 2
Click to expand...
Click to collapse
I tried all of those apps, nothing wrong. I think I should change the screen and digitizer, I might need to go to the repair center because my hands shake (my usual problem) and hard to fix tiny things. I want to do few experiments before taking it to repair. I already put it in the freezer for two hours it was acting like crazy after.
Suggest me more...
Sent from my GT-I9000 using xda premium
Me too!
and i thought i'm the only one experiencing this kind of problem. it is exactly what i'm having on my sgs. seems to be temporarily fixed by turning the screen off and then on again, but after a while, the screen doesn't respond on the same spot as you're having.
i've managed a low level debug on screen touch response using adb logcat, and my touch doesn't really register any on adb logcat console.
they might be correct on the hardware problem, but when i'm on any gingerbread rom (2.3.6), the problem is gone.
guys, any idea what kind of drivers they're using on gingerbread for our touchscreen?
I have this too on ics, left half of screen stops responding, lock on/off sorts it....until the next time! Bugs the hell out of me!
Me too! on ICS
btw, i'm already on ics team nyx
change
flash CF KERNEL and put ICS CM9
middle screen not responding
- when in stock gb firmware (official from samsung), the touchscreen problem is gone.
- but i want the features of an ics rom, so i flashed one (first was slim ics); the problem appeared first; first guess was the custom rom was still in its early stages.
- flashed back to gb, no touchscreen problem.
- flashed new ics rom from cm9 (nightlies), problem appears again (ugh!).
- flashed backed to updated slim ics since this was the fastest and easiest to install, touchscreen problem still persist.
- found a temporary fix by turning the screen off then on again.
did a adb logcat full trace log of touchscreen input: what i noticed was the whole vertical middle part of the screen is not responding to touch; dragging touch from one side to middle is working just fine, but not starting from the mid vertical part.
the problem may sometimes go away after a while, and sometimes persist even after the temp fix. it's very intermittent indeed.
help please.
psycotrompus said:
- when in stock gb firmware (official from samsung), the touchscreen problem is gone.
- but i want the features of an ics rom, so i flashed one (first was slim ics); the problem appeared first; first guess was the custom rom was still in its early stages.
- flashed back to gb, no touchscreen problem.
- flashed new ics rom from cm9 (nightlies), problem appears again (ugh!).
- flashed backed to updated slim ics since this was the fastest and easiest to install, touchscreen problem still persist.
- found a temporary fix by turning the screen off then on again.
did a adb logcat full trace log of touchscreen input: what i noticed was the whole vertical middle part of the screen is not responding to touch; dragging touch from one side to middle is working just fine, but not starting from the mid vertical part.
the problem may sometimes go away after a while, and sometimes persist even after the temp fix. it's very intermittent indeed.
help please.
Click to expand...
Click to collapse
So your sgs touchscreen working fine on stock gb rom! It might not be a hardware problem then. We have similar problem, only difference is I have problem on GB too. I've even tried stock froyo, same story
Sent from my Nexus S using xda premium
same problem here, left part of the screen would be unresponsive at times
can fix by locking the phone through power button and unlocking it, thats why i think its a software problem.
I dont remember having this problem in GB also.
maybe something is messed up during flash?
I have the same problem with ics and jb roms from the onecosmic ics times and i had a topic http://forum.xda-developers.com/showthread.php?t=1648287
I have written here but no one seems to now what it is, i have been using ics from onecosmics first release and had the problem from that moment on, different kernels, roms etc it is still here i have flashed gb again and problem is gone, flash again with ics the middle part still acts sometimes. ?...
We should request from kernel developers and rom developers to look into it. I have tried almost everything no luck so far
I installed Thrillseeker 3.1 about 2 weeks ago, and have been noticing a few things. Sometimes the phone stops responding to touches for a while, like its locked up, or lagging, or maybe the wrong CPU governor. I don't know what's going on. Sometimes it randomly resets. One repeatable problem is that if I turn Wifi on, then off, then on again, the phone resets.
I have tried the 1.30Ghz kernel included in 3.1, the 1.38Ghz kernel, the 1.0Ghz "Saver" kernel, and the 3.12 update, but the same reset-on-wifi problem persists.
Is anyone else having similar problems? Simple fix?
I would try reflashing back to stock. Reinstall CWM, then try installing the ROM again.
Beyond that, maybe you should PM the guy who made the rom.
brianosaurus said:
I installed Thrillseeker 3.1 about 2 weeks ago, and have been noticing a few things. Sometimes the phone stops responding to touches for a while, like its locked up, or lagging, or maybe the wrong CPU governor. I don't know what's going on. Sometimes it randomly resets. One repeatable problem is that if I turn Wifi on, then off, then on again, the phone resets.
I have tried the 1.30Ghz kernel included in 3.1, the 1.38Ghz kernel, the 1.0Ghz "Saver" kernel, and the 3.12 update, but the same reset-on-wifi problem persists.
Is anyone else having similar problems? Simple fix?
Click to expand...
Click to collapse
I haven't had the reboot problems since 3.12 update from 3.11 clean install. Have had lag issue a couple times..for me restarting holo launcher corrected...tried to recreate wifi issue bit is working for me. All three kernels are very similar the saver has 1.3 and 1.2 disabled and the hotplug gov tweaked
Also posting this in my thread might get you more help.. since your running thrill seeker its ok to post problems you are having in that dev thread as others may be having same issues and ill see it quicker and try to help fix it if I can.
Sent from my LG-P925 using xda premium
yeah, i'm a noob
I'll try going back to stock and then reflash the latest thrill seeker. I would have posted in the dev forum, but I don't have 10 posts yet, so I'm restricted from posting in dev. only 8 more to go
3.12 hasn't had a random reset on me, just the wifi reset, but that one "works" every time.
Thanks,
brian
found lag problem and found possible fix
lag problem on thrillseeker 3.11/3.12 appears to be the CPU somehow resetting the Max MHz to 100MHz after the phone sleeps for 10-15 mins. Having Romtoolbox installed, then adjusting the CPU sliders quickly bypasses this issue. Although a true fix is in the coding, this workaround appears to be permanent once preformed. At least we now know it is not a flaw in the Rom as far as an overload or hang-up problem. I have not experienced the Wifi issue yet. If I can get a heads-up on how to induce it, I can look into it. Great work on the Rom!
problems im having
The rom itself is near perfect to me...I give thanks to all that put the hours and hardwork into this
I am a complete noob so any help or answers I will greatly appreciate. The only trouble I have from rom so far is if I'm using the browser while its plugged in.. might be a bad install after all. I really jumbled a few things like not making a nandriod. So I'm kinda stuck with with out a return to stock option...I have been trying to work through this but im a bit unsure how to get a stock Back on here. ..????? Any help....... back to rom I love thrillseeker 3.1....I been testing what I need in a rom and well I couldn't be happier that this rom seems to to do the job and then some....everything works perfect ....like I said the only thingthat seems fuzzy is when I plug in to wall charger and then it gets glichy.....
cpu
I adjusted sliders as well the second one seems to revert back to 100mhz often so its not a permanent fix. It does help....
Yeah. Funny thing. My phone broke (cracked screen), so I did an exchange at best buy and this rom works just fine on the new one. I guess my old one was kind of janky on the inside.
Sent from my LG-P925 using xda app-developers app