Database Develop

[Q] Some remaining probs with doc 7.6.2

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

SGS Running CM10 Turns off automatically

Hey I hope one of you guys can help me.
I have a galaxy s running cm10 and I have had this persistent problem with my phone turning off automatically.
When I use it, I press the side button to turn off the screen and it is fine for a minute or so, but if I leave it any longer than that it turns off.
I have heard of something called Deep Sleep, is this the problem?
Is there a way to change how long it has to be locked to go into deep sleep?
Please help
I am losing hope
Cheers

HazzaGalaxy said:
Hey I hope one of you guys can help me.
I have a galaxy s running cm10 and I have had this persistent problem with my phone turning off automatically.
When I use it, I press the side button to turn off the screen and it is fine for a minute or so, but if I leave it any longer than that it turns off.
I have heard of something called Deep Sleep, is this the problem?
Is there a way to change how long it has to be locked to go into deep sleep?
Please help
I am losing hope
Cheers
Click to expand...
Click to collapse
Sounds interesting i know this from the first custom roms i tried a year ago!
Which build of cm10 are you using? Any "faulty" app installed? for me dropbox made cm10 instable and laggy, so i stopped using it.
Have you checked the md5-sum of the .zip file of your downloaded rom? Maybe the download was faulty... Happened to me twice on cm-nightlies.
Cheers
EDIT: Which kernel are you using? For me Stock-Kernel ist aboslutely rocksolid! My phone had 140 hours ontime this morning, before i flashed the newest build.

Hi,
Is you IMEI ok ? I had this problem with CM10 too but now my IMEI is ok I have no pb at all

have you overclocked your phone? i had the same thing happening with other roms...as soon as i had overclocked and turned the screen off, my phone got stuck after a while. try cleaning nstools settings. if that doesn't work, you might try turning off deep idle if it's active, could also be the reason

SKArabaeus said:
have you overclocked your phone? i had the same thing happening with other roms...as soon as i had overclocked and turned the screen off, my phone got stuck after a while. try cleaning nstools settings. if that doesn't work, you might try turning off deep idle if it's active, could also be the reason
Click to expand...
Click to collapse
Hey
Where is deep idle?
I have no idea where it is and ive looked everywhere in settings.
Do you have photos?
That would help.
Cheers

ThrashJan said:
Sounds interesting i know this from the first custom roms i tried a year ago!
Which build of cm10 are you using? Any "faulty" app installed? for me dropbox made cm10 instable and laggy, so i stopped using it.
Have you checked the md5-sum of the .zip file of your downloaded rom? Maybe the download was faulty... Happened to me twice on cm-nightlies.
Cheers
EDIT: Which kernel are you using? For me Stock-Kernel ist aboslutely rocksolid! My phone had 140 hours ontime this morning, before i flashed the newest build.
Click to expand...
Click to collapse
Hey
I would not know the first thing about what to look for?
How do i know its faulty?
Cheers

HazzaGalaxy said:
Hey
I would not know the first thing about what to look for?
How do i know its faulty?
Click to expand...
Click to collapse
Okay, let's start from the beginning :silly:
Whats the exact name of the rom you flashed?
How do you flashed it? (Wipe, etc.)
Have you flashed any other stuff? (Inverted Gapps, Battery mod, Kernel, etc.)
Have you many apps installed?
If i where you, i would flash the newest build with a full wipe, so you got a new, bugfree and stable system

same issue
I have been having the same issue ever since switching to CM10, I have been installing nightlies hoping it will end, but appears to be isolated. Would it help to manually flash boot for each ROM? It cuts off randomly and won't turn on unless charged by a wall charger, or other high-power input (doesn't turn on or charge from car outlet). It doesn't appear to be caused by an app.

Did you wipe when installing nightlies?
If you try to go stock with Odin, and the issue is exactly the same, I think you should consider it could be battery malfunction.
Sent from horseback.

Random crashes and reboots on Thrillseeker 3.1

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

Random Reboots?

Not sure what is going on. I experienced it on stock rom, and I'm also experiencing it on Android Revolution HD Rom.
It seems like whenever the phone is tasked by an app opening or closing, I experience a random reboot.
Anyone know whats causing it?

Yeap me too, but only after closing final fantasy IV.. Dunno what's the deal here
°° no rest for the wiCKed °°

anyone?

S_Dot said:
anyone?
Click to expand...
Click to collapse
Me, too, but I didn't catch any regularity, yet.
I am on stock ROM.
One time a had a crash report from htc, but most times I only realize it, because I have to re-enter my pin.
Today I realised, that long-pressing the power-button does restart the phone without any other input.
Maybe it's that?

I'm using developer edition and have been suffered from heavily random reboot.
The phone rarely rebooted (2 or 3 times) while I was using it but just kept rebooting if I left it idle (5 reboots in 20 mins). I cannot reproduce the reboot because it was so random. One day, it just kept me annoying by rebooting itself more than a dozen time. The other day it just went super smooth and stable. This reboot has been happening on both completely stock and custom (Rom, kernel).
Anyone got a clue?

If you know a certain action is causing the reboot get a logcat, there's an app called catlog on the play store. Press record, repeat the action, after it reboots get the logcat and post it here
Sent from my Tricked out HTC One

Same issue here! I'm using TrickDroid though. Has anyone tried this with 4.2.2 to see if it still happens?

Sylpher said:
Same issue here! I'm using TrickDroid though. Has anyone tried this with 4.2.2 to see if it still happens?
Click to expand...
Click to collapse
I'm using Android Revolution ROM on 4.2.2., same thing. It happens once in a blue moon, and it's only on wake when I hit the power button. The whole phone freezes and reboots.
Is everyone here on the Developer's Edition?

I'm having the same issue, dev edition stock except recovery, and root. Some days it reboots, other days its fine. Not exactly sure whats up w/ that
Sent from my HTC One

I'm gonna go ahead and bump this, seeing as I'm facing the same issue on my 2 day old device.
At first I thought it was a problem with 4.1.2, but even after upgrading to 4.2.2 the issue is still there.

ViperOne 2.1.0 the same trouble
Hello,
I confirm the same problem on ViperOne ROM. I have tried out ElementalX 3.4 and Bulletproof kernels. But it seems to be kernel independent.
I attached the log, my configuration is as described in my signature except that I use Bulletproof kernel right now.
It is quite frustrating cause I just wanted to play a movie on my TV using Hama MHL cable, but everytime I connect my phone to the adapter the phone reboots, then it gets stuck on HTC logo, then I have to reboot it manually holding power button. I am also experiencing a reboot right after phone boots up.
This is such a serious issue that I am thinking of going back to stock kernel, but I am not sure if it will help
Any hints?
EDIT: I just installed stock kernel, but still the same, really does not seem to be a problem of the kernel
EDIT2: still trying to find the out whats the problem, I did a clean reinstallation of everything, even w/o using Titanium Backup, well, MHL still causes reboots

[Q] Droppings calls. Lots. Argh.

Hello!
I'm running Beanstalk 4.4 and the latest Meeow kernel. My phone works well (mostly) and has great battery life. It also drops calls ALL the time. Like all the time between 5s and 2mins.
I also have a problem whereby the screen is kinda screwed for touch. Like a touch is already registered and stuck on rendering the phone useless until a reboot. Probably not related. Can live with that even.
But the call dropping is way bad. I've installed ROM from fresh and tried latest kernels. Don't really notice when it started.
Any one have ideas pls? Thanks!

i
bonstio said:
Hello!
I'm running Beanstalk 4.4 and the latest Meeow kernel. My phone works well (mostly) and has great battery life. It also drops calls ALL the time. Like all the time between 5s and 2mins.
I also have a problem whereby the screen is kinda screwed for touch. Like a touch is already registered and stuck on rendering the phone useless until a reboot. Probably not related. Can live with that even.
But the call dropping is way bad. I've installed ROM from fresh and tried latest kernels. Don't really notice when it started.
Any one have ideas pls? Thanks!
Click to expand...
Click to collapse
so it s Bug of this custom ROM and u should ask to solve from its developers.
if u wanna check ur hardware is fine u must back to stock ROM or install trustful & famous rom like CyanogenMod & etc
if ur phone works fine with them so previous rom wasn't good enough
:good: