Am having random reboots - just had one mins ago posting reply w/xdafree app here but not sure if ROM related as xda app auto installed itself on sdcard which also caused its icon to disappear from home screen at reboots and this has been found to likely not be ROM related. Also having random power offs and random browser FC. Am running 1200 OC & on demand CPU governor & trying to run as min as poss to save battery. Hardly ever get past 3 days uptime.
Model: YP-G70
Android: 4.4.4 CM11-20140712-UNOFFICIAL-venturi
Kernel: default = 3.0.101-G70UEK18 [email protected] #1 Sat Jul 12 13:13:50 PT 2014
Build#: cm_venturi-userdebug 4.4.4 KTU84P 997e99f83e test-keys
Oclocking on this ROM does lead to some random reboots. Try to go back to default.
Sent from my YP-G70 using XDA Free mobile app
Had thought that once before too and tried it but maybe something else was also causing reboots so I went back but will try again thx.
Sent from my YP-G70
Just had another browser FC just reading news - it froze and finally came back with a dialog box to say browser has stopped running. I tried it again and same thing happened but this time it came back with a dialog box that systemui had stopped. Trying to OK that msg cause it to just loop the same msg over again. I was able to short press the power button to get the power menu to show behind the msg box and in between OKs just enough time to request reboot.
Sent from my YP-G70
Re: CPU settings - I went back to default = max 1000 & interactive but more random reboots set this way - couldn't get past 18 hrs. So only changed back to ondemand and now going thru 28 hrs so will see....
Sent from my YP-G70
:what: <grin> Made it to 3 days and so many hours, either 8 or 18, can't recall eventho I just viewed it - thought it might make it thru 4 days for a first - wishful thinking I guess. The app I'm using is called system uptime but doesn't tell how long the last run was. I wasn't really doing anything heavy - reading news - and put it down - a few mins later it auto locked the screen - then a few mins later it just reboots just sitting there!
Sent from my YP-G70
brwntree said:
:what: <grin> Made it to 3 days and so many hours, either 8 or 18, can't recall eventho I just viewed it - thought it might make it thru 4 days for a first - wishful thinking I guess. The app I'm using is called system uptime but doesn't tell how long the last run was. I wasn't really doing anything heavy - reading news - and put it down - a few mins later it auto locked the screen - then a few mins later it just reboots just sitting there!
Sent from my YP-G70
Click to expand...
Click to collapse
Just curious if you've tried other KitKat Roms, and if you have, what your experience has been with them. Right now for me, Carbon using the default performance settings has been the most stable and best performing.
No, I haven't. Am new to this thx to dosdude1 and his YouTube vid how to get sgp5 to cm and my constant search how to safely do these flashes. So not complaining about these reboots - its only annoying if ur in the middle of doing something - else can live with it so far - it reboots pretty fast and sometimes only realize it because of uptime. Just curious about it and sharing my experience with it.
Have started looking around at ROMs - I tend to min types and saw carbon & slim & others. But realized I had vid help with my first and now a larger learn curve for next steps. I need to read about ADB & fastboot & TB-pro & kernels & more before considering another safe move - brick fears! But thx for the tip.
Sent from my YP-G70
One other thing I noticed - apps were newly auto updating for some reason - didn't know it but play store had auto update option on - so turned it off - might help.
Sent from my YP-G70
Well, I'm not too sure about this, but try keeping overclock off unless your phone is running irritatingly slow. From my experience with the YP-G70 (US) model, there were usually three main factors in those oh - so - annoying random reboots: 1) there are some mischievous, misbehaving apps running, 2) the phone is being overclocked, or 3) the ROM you currently have is buggy or not working properly. I think your problem is probably a combination of 2 and 3. Hope this post helped
__________________________________________
Samsung Galaxy Player 5.0 (Model YP-G70)
• Carbon ROM 4.4.4 by Meticulus Dev Team
• Daily Drivers Kernel
Yes this helps. Would love to try a new ROM too but still in learning mode. I wanna get good w/TiBu.
I stopped using system uptime app and found device uptime (has a log file & no widget) and got to 5 days before reboot. Thought using the orig app might've been contributing but only got to 1 or 2 days max after & one more random power down.
But I realized system uptime app was still installed and, even though not running it directly, it was maybe still running in background. So I uninstalled it completely to see if this app was poss a factor for now.
Sent from my YP-G70
beeewell said:
Just curious if you've tried other KitKat Roms, and if you have, what your experience has been with them. Right now for me, Carbon using the default performance settings has been the most stable and best performing.
Click to expand...
Click to collapse
I have been running Carbon on my Player 5.0 (YP-G70) for the past 3 months without a hiccup. Excellent battery life and very smooth. The OP may want to give that a try.
I liked Carbon so much, I put it on my Player 4.0 (YP-G1) and my Tab 7.0 Plus (GT-P6210).
---------- Post added at 09:16 PM ---------- Previous post was at 09:10 PM ----------
brwntree said:
Yes this helps. Would love to try a new ROM too but still in learning mode. I wanna get good w/TiBu.
I stopped using system uptime app and found device uptime (has a log file & no widget) and got to 5 days before reboot. Thought using the orig app might've been contributing but only got to 1 or 2 days max after & one more random power down.
But I realized system uptime app was still installed and, even though not running it directly, it was maybe still running in background. So I uninstalled it completely to see if this app was poss a factor for now.
Sent from my YP-G70
Click to expand...
Click to collapse
The best way to learn is by doing.
First of all, make a nandroid backup so you have a safety net in case things go wrong. Then you can try flashing another ROM.
If you don't like it, just restore and try something else.
Good luck!
Related
Hi.
Havnt seen this problem described here so ill just ask and hope to be shown in the right direction.
When i, either through KIES or Odin, upgrade my phone to ICS (4.0.3 XXLPQ) it gets quite varm by just sitting at the homescreen doing nothing, I have tried both antutut's and SetCPU's apps to check the CPU-speed and it is almost constantly at 1000-1200Mhz and it is just for a few short seconds now and then that it drops to maybe 800 or 500Mhz just to get back up to 1200Mhz again.
I have wiped and cleared everything before upgrading but thing helps.
When i restore my 2.3.6 backup eberything works fine and the CPU is steady at about 100-200Mhz when i am not doing anything with the phone except having for example SetCPU open, I have also very very very rarely had any reboots or other strange things with 2.3.6 (or any of the previous versions of GB), so wouldnt expect the phone to be faulty in its hardware.
Sorry for the wall of text, but does anyone have any ideas on what could be wrong, or is it a trip to a service center that is needed for my phone? :S
I have emailed Samsung sweden about this but as i am quite sure i will get a generic response I thought i should ask here instead
I have also been getting that problem. No clue why.
unselect internet sync in google sync account.....
Sent from my GT-I9100
I've read from another thread that it can warm up because of new swype always trying to download some languages.
Sent from my GT-I9100 using XDA
karthik.shreeram said:
unselect internet sync in google sync account.....
Sent from my GT-I9100
Click to expand...
Click to collapse
Lol, what does Sync Internet Sync?
Mine was off.
in GB, it was hot. And at ICS cool device
I have the same problem and unfortunately it causes extreme battery drain. Like 70% in about 5 hours while the phone is idle.
This sucks.
Swype was causing battery drain for me after ICS upgrade. After force closing it the drain has ended and S2 does not get hot anymore. Swype was shown using 50% of battery in Settings - Battery.
Ask samsung for kernel sources
Sent from my GT-I9100 using xda premium
Install antutu benchmank and check what is the CPU frequency.
As far as I know from all the previous betas ICS takes ages to do the media scan and hence it warms up. You will know its doing it when trying to use the camera or open the gallery. It will say media scan running.
If media scan has finished but its still heating up I would recommend a factory reset.
Sent from my GT-I9100 using xda premium
girishr said:
Install antutu benchmank and check what is the CPU frequency.
Click to expand...
Click to collapse
It's always at 1200 Mhz. I can't force close Swype because it isn't even open on my device. Should I try a factory reset?
sxi200 said:
As far as I know from all the previous betas ICS takes ages to do the media scan and hence it warms up. You will know its doing it when trying to use the camera or open the gallery. It will say media scan running.
If media scan has finished but its still heating up I would recommend a factory reset.
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
Inoticed this also the fifth time i reflashed, I think i should wipe my phone, format SD-card and internal memory.
Sitting in meetings all day today (even right now) so I will do some testing when i get home.
Other problem i got when i had ICS and it was hot (scanning), my Phone locked up when i got a call... Saw some other bugs and problems, so maybe I should wait for the next release....
Since I'm on ICS I have this strange problem with the official FB client.
As Soon as i start FB my processor gets pumped up to the maximum of 1ghz. Even when i click the Home Button and start up Voltage Control i can see the processor is at max.
Only when i close FB (with task manager or long press back key on CM9) the processor goes down to 200mhz and stays there...
effect : as soon as i start FB and don't quit it right my battery will be drained in a short time..
Since the first ICS release I am googling this problem but can't find any information about this. Now I'm a little bit fed up with it, thats why i'm posting it here...does anyone else recognize this? is there a workaround?
thanks for the help...
check your battery info,get cpuspy to see what speed your cpu has been going at and the deepsleep and betterbatterystats for wakelocks etc
this guy has similar issue
http://forum.xda-developers.com/showthread.php?t=1571518
i already checked with all mentioned tools.
strange thing is there is no wakelock... it's only when screen is on but application is in background.
i have this problem on different ICS Roms. at the moment i am on cm9 and it is still present. when i check with "top" in terminal i can see that facebook.katana is at the top keeping the cpu pretty busy.
with samsung roms and the original samsung task manager i can see that it's always using over 50% cpu power.
i tried older versions. tried deinstalling. nothing helps.
i just dont know what it is doing in the background. cpuspy shows me that the cpu is mostly in 1ghz and deepsleep.
edit: i double checked and its also killing deepsleep. sometimes it enters sometimes not...
pmcee said:
Since I'm on ICS I have this strange problem with the official FB client.
As Soon as i start FB my processor gets pumped up to the maximum of 1ghz. Even when i click the Home Button and start up Voltage Control i can see the processor is at max.
Only when i close FB (with task manager or long press back key on CM9) the processor goes down to 200mhz and stays there...
effect : as soon as i start FB and don't quit it right my battery will be drained in a short time..
Since the first ICS release I am googling this problem but can't find any information about this. Now I'm a little bit fed up with it, thats why i'm posting it here...does anyone else recognize this? is there a workaround?
thanks for the help...
Click to expand...
Click to collapse
Same here. I've Galaxy S2 and since update to ICS official firmware have i have this problem. I noticed that all rom that have as baseline official Samsung ICS have this problem, while other (e.g. CyanoMod 9) don't have. The only fix is to kill application from task manager.
Which is your device?
NothFlo said:
Same here. I've Galaxy S2 and since update to ICS official firmware have i have this problem. I noticed that all rom that have as baseline official Samsung ICS have this problem, while other (e.g. CyanoMod 9) don't have. The only fix is to kill application from task manager.
Which is your device?
Click to expand...
Click to collapse
It happens to me on cm9 also... Every ICS Rom.
So No one has a solution for US?
Just to let you guys know that this also happens on my Nexus S with ICS 4.0.4 stock
In fact it happened also with Gingerbread... it started happening when Facebook made a major app overhaul to what is currently the new "user experience" for the past 4-5 months or so... that's when Watchdog which I have installed suddenly started complaining
Sorry for digging out this bit older thread, but have you found a solution yet ? I got the same problem since i changed to ics roms - first sammy leaks, then official, now nightlies. Tried wiping cache, dalvik, userdata, reinstalled app, ... to no effort.
Thinking about coding a facebook-killer widget. Take a look on this screens, 2 hours of cpu time for nothing...
Sent from my GT-I9100 using xda premium
I just use Watchdog what normally complains about Facebook a few minutes after I stop using it. Then I just kill the process from within Watchdog.
Using the browser is fine though.. however some things don't work so well in the mobile browser version.
To me this problem is quite symptomatic however from what I read on the internet it doesn't happen all the time.. even sometimes for me it doesn't stay clogging the cpu but most of the times it does.
I guess they will fix it one day but I wouldn't hold my breath that it will be soon. I read that on the iPhone the way they designed the app is pretty bad (it's sort of a skin over the actual mobile website). For Android it might be the same..
That the facebook devs are coding big BS (sorry) is really known.
Can you provide me a link to the google play site of Watchdog ? Too many results, i don't know which one... thanks
Sent from my GT-I9100 using xda premium
Here! This is the one I use
https://play.google.com/store/apps/details?id=com.zomut.watchdoglite
Thanks.
Which modem do you use ? I am on XXLPS, and afaik with XXLPQ i did not have the problem - will try at home
Edit: tried, the same with lpq...
Sent from my GT-I9100 using xda premium
I'm using the XXLA2 radio that came with the yakju update. But I got the same problem with the XXKK6 yakjuxw radio
smells more like programmer error than phone configuration..
since i am using foxhound rom (sniper wolf), the facebook app (and same for all other apps that dont automatically close) is automatically ended when closed with the back button...
Seems that it's a problem with the official ICS ROMs. Try Friendcaster and see if that's any better.
drizzle1 said:
since i am using foxhound rom (sniper wolf), the facebook app (and same for all other apps that dont automatically close) is automatically ended when closed with the back button...
Click to expand...
Click to collapse
Theres a funtion which kills a process if you hold the back key.
i360* said:
Theres a funtion which kills a process if you hold the back key.
Click to expand...
Click to collapse
even by closing with a short press on the back button it will end the process
i uninstalled facebook for this
friends caster is A LOT better than facebook app
personally I didn't like Friendcaster. It was smoother in operation that Facebook's official app but it had some quirks (now can't remember them but there were a few things you couldn't do as opposed to FB's official app). But what stopped me from using it was the extended awake times I was getting even without automatic refreshes set up.
Haven't got a single problem
Sent from my GT-I9100 using Tapatalk 2
Experienced this just a couple of days ago My screen will go blank, like it went to sleep but what actually happened was it just simply shut off! I installed two logcat applications, but I don't know jack about reading logs I want to know what causes these shutdowns The latest ones happened between 6:32-6:33AM and 6:54-6:55AM (it's 7:26AM now, my time). Please help
iampoch said:
Experienced this just a couple of days ago My screen will go blank, like it went to sleep but what actually happened was it just simply shut off! I installed two logcat applications, but I don't know jack about reading logs I want to know what causes these shutdowns The latest ones happened between 6:32-6:33AM and 6:54-6:55AM (it's 7:26AM now, my time). Please help
Click to expand...
Click to collapse
check if you've installed any apps that prompt the auto shut-off of your phone
previously I had this problem before by then I realized it's due to the installation of one of my fault apps.
felixtom said:
check if you've installed any apps that prompt the auto shut-off of your phone
previously I had this problem before by then I realized it's due to the installation of one of my fault apps.
Click to expand...
Click to collapse
Really hate to sound like a total noob, but how do I do that?
iampoch said:
Really hate to sound like a total noob, but how do I do that?
Click to expand...
Click to collapse
first of all,i think this is happening because of any new app,try to remember when it was started(maybe that time you installed any app and now that app shutting down mobile? or just go to task manger and clear each app that was running and also clean memory. if problem is gone and its occur again after rebooting mobile its maybe a Rom Bug,you need to change your Rom,but before doing that try to clear apps through task manger. and see what happens
i hope that helps you
Well first of all ...
Are you rooted? What is your Rom/kernel?
Sent from my GT-N7000 using Xparent SkyBlue Tapatalk 2
Thanks for the replies guys ok, here are some more info and observations.
I was originally using CyanogenMod 9.1 when this happened. At first, I tried wiping cache and dalvik cache. But it was still the same. After a few more shut downs, it got worse. It got to the point that it shuts down after the boot animation. So, I used Clockwork Mod to revert me back to rooted stock ROM. It's not as worse as CM9, but I still get shut down. Now, here are the observations I made:
1. This only happens when my phone is unplugged. It works fine otherwise.
2. This consistently happens when I connect to the Internet, for example via a browser, didn't matter whether it was Chrome or Dolphin. Offline reading via RSS or Pocket is fine. I opened FB unplugged and I got shut down as well, so I guess it's safe to say that connecting to the Internet triggers it. When accessing the Internet while unplugged, shutdown is immediate and imminent. Plugged, I can surf just fine.
3. It also gets triggered when I play a game, but my shutting down is not immediate, unlike the one above. I am playing only one game at the moment (Great Big War Game). And I am able to play a long while before getting shut down (around 30 mins)
It wasn't like this a couple of days ago, and I didn't install anything new outside Google Play updates, this is not counting the two logcat apps I installed this morning to try to diagnose the problem.
Is there a way for me to find out what's wrong via the logcat?
Sent from my GT-N7000 using Tapatalk 2
for your Help
iampoch said:
Thanks for the replies guys ok, here are some more info and observations.
I was originally using CyanogenMod 9.1 when this happened. At first, I tried wiping cache and dalvik cache. But it was still the same. After a few more shut downs, it got worse. It got to the point that it shuts down after the boot animation. So, I used Clockwork Mod to revert me back to rooted stock ROM. It's not as worse as CM9, but I still get shut down. Now, here are the observations I made:
1. This only happens when my phone is unplugged. It works fine otherwise.
2. This consistently happens when I connect to the Internet, for example via a browser, didn't matter whether it was Chrome or Dolphin. Offline reading via RSS or Pocket is fine. I opened FB unplugged and I got shut down as well, so I guess it's safe to say that connecting to the Internet triggers it. When accessing the Internet while unplugged, shutdown is immediate and imminent. Plugged, I can surf just fine.
3. It also gets triggered when I play a game, but my shutting down is not immediate, unlike the one above. I am playing only one game at the moment (Great Big War Game). And I am able to play a long while before getting shut down (around 30 mins)
It wasn't like this a couple of days ago, and I didn't install anything new outside Google Play updates, this is not counting the two logcat apps I installed this morning to try to diagnose the problem.
Is there a way for me to find out what's wrong via the logcat?
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
maybe its a cache problem of your Browser,so try to clear cache of your Browser and if its not working Flash a new stable Rom( i recommend you Sweet Rom,find it on XDA,its very stable and smooth)
and flash that rom with Hydracore kernel.
hope that helps you
have a nice day
Hi thanks for the additional info. It seems that you have the issue persisting on a stock Rom?
Have you tried to wipe on a safe kernel (if on ics)?
Do disable any overclocking or any scripts.
Sent from my GT-N7000 using Xparent SkyBlue Tapatalk 2
Guys, just a quick update. I sent it off to the service center (reverted to stock and hid all traces of being rooted). They reflashed the phone (they say it's their standard practice to do that before considering hardware defects) but the problem still didn't go away. So, I think my issue is hardware-related
This problem is not software related. It is most definitely hardware. The phone is flawed and shuts off on it's own under various conditions, all hardware related. I am not able to post externally due to not having enough posts yet. However, I have had the same issue on 3 Galaxy Note 2's from Verizon. I made a video that shows exactly what is going on and posted it on the following website...
wwwDOTgalaxynote2shutsoffDOTcom
You will have to paste that link in to a new browser and replace the DOTs accordingly to get to it, but once you see the video, you will be enlightened. Be sure to read the details I provided on that site as well. They go in to detail about the problems that I have had and the lack of proper support that Samsung is willing to provide.
Take a look at the video I made here if you can't get to that site: http://www.youtube.com/watch?v=SjLn2yikYnI
As the title states. Those using the newest roms do your phones ring as should? Been using and always going back to Baked 6 because every newer rom I try the phone frequently does not ring. To name a few, I tried Hellybean, Slim, Carbon, Baked 8. I have tried every solution that I can find in these forums. I depend on my phone for work so it has to be reliable. Does it not bother others that the phone does not ring as should or does yours work?
I'm on Helly Bean and it rings every time... although I don't get phone calls very often at all, so maybe if I did it would miss a few. This is a common issue unfortunately and I've yet to hear of an easy solution.
Not Ringing Either
My phone doesn't ring either. Hasn't through out the whole time I've been using HellyBean. I've been searching the forums and thus far haven't found a fix. If anybody has the fix thread can you post it here, thank you. Looks like I'll have to look into another rom as suggested in the start post.
it;s probably a ROM that doesn;t get any attention but i have been using JellyBro and the ringing and notifications work fine.
Look here for a fix
http://forum.xda-developers.com/showthread.php?p=42185823
louiehummv said:
Ugh, not again. Well... for what its worth, I found a way to stop losing em.
First, a little background... I discovered that the "media store" app will index ur phone's media after every reboot (as expected), but hangs before committing its findings from the temporary "wal" file to the "internal.db" database (where all ur media locations are stored). Then, when attempting to access the database while configuring ur ringtones/sounds, the media store app craps out and drops it findings altogether. Basically, the wal file disappears and the database file size decreases. So, all we have to do is force the wall file to commit before the media store drops it. Afterwards, the media store app doesn't appear to have a problem maintaining the database... even after rebooting. Definitely a bug with the app; see for urself by observing internal.db in /data/data/com.android.providers.media/databases.
Now, the workaround (ull hafta reassign all ur ringtones/sounds after this... not like they worked anyway)...
1 - Delete the contents of the folder /data/data/com.android.providers.media/databases.
2 - Reboot and wait ~5 min after startup to let the media store reindex all ur media. DO NOT configure any app's ringtones/sounds just yet.
3 - In terminal, enter the following commands. You should see "x | y | z" after the checkpoint command... where x is 0 (database is ok), y is the number of modified pages, and z is the number of pages successfully committed to the database. y and z should be equal and much greater than 0. If the result is not as described, the database is probably screwed up and u were too late. Go back to step 1 and repeat.
$ su
# cd /data/data/com.android.providers.media/databases
# sqlite3 internal.db
> pragma wal_checkpoint(FULL);
> .exit
# exit
$ exit
4 - Trust the workaround and start configuring ur ringtones/sounds now... or reboot again and ensure the media store database stays fixed. I recommend the latter.
5 - 3 sir!
Sent from my SCH-I535 using my wit and brilliance
Click to expand...
Click to collapse
hhp_211 said:
Look here for a fix
Click to expand...
Click to collapse
Can't find "/data/data/com.android.providers.media/databases"
Edit: Found
Hello,
I also suffered this issue, i think the rom you flashed was to blame.
This issue has been long discussed in our Chinese fascinate forum.
I strongly recommend you flash the lastest cm10.
自由自我
hhp_211 said:
Look here for a fix
http://forum.xda-developers.com/showthread.php?p=42185823
Click to expand...
Click to collapse
Tried the workaround. Ringtones lasted longer, but stopped after a couple hours. Tried on latest Helly. Curious which roms it's working for others on.
dukeoid said:
Tried the workaround. Ringtones lasted longer, but stopped after a couple hours. Tried on latest Helly. Curious which roms it's working for others on.
Click to expand...
Click to collapse
well i'm currently on Slim 04/09 build -
previous Slim 3/17;; ParanoidAndroid March Builds;; Baked Bean, 6/7/8;;; HellyBean;;; AOKP PUB;;;
that gets me back all the way to the beginning of the year
I have had working ringtones on ALL of these as my daily use phone...
on my test phone I cant test ringtones cause [ its not activated] but notification tones for things like hangouts, twitter, gmail, etc have ALL worked without fail on every build I've loaded,,, [ which is virtually ""ALL"" the others at one point or another]
but kind of like that work around is saying I always wait after a clean/data wipe about 10 minutes [before setting ringtones] while figuring out my other settings, adding apps and what not, usually give at least 1 more reboot and wait again another 10 minutes then set ringtones,,, but I also have my 2 personal use ones [ringtone = pyxis ,,&,, Notification = cyanping] stored in a file on my sd card [a couple ROMs have not had these and I don't really care to use anything else right now] and always making sure to choose media player/server as the default app if I've wiped media storage settings data,,, [that way I can add them back into the appropriate folders if needed]
I did have this issue way back about August/September of last year running on AOKP builds, but I remember odin to stock, then THS 1/2 build then flashing to an older glitched build before the original partition changes or the later partition changes, and probably flashing new aokp,,, wiping data, etc and I got mine fixed...butt... it could have gone back to me waiting out those initial scanning times plus reboots ~ before ~ setting ringtones/data,,,
then again,,, some peoples fascinates have just given them major issues with this and they have rarely seemed to fix the problem,,, so it could be hardware tolerances and those are just really off on some setting somewhere...???
Good Luck
I really dont feel it is a ROM issue...maybe an Android issue, like the voicemail notification prompt problems [because we dont have LTE and that is coded into jb software now, so the fascinate freaks out when it cant find lte settings...]
.
---------- Post added at 05:48 PM ---------- Previous post was at 05:38 PM ----------
you could try ,,, now that it borked on you,,, clearing out the android.providers.media / data , boot into recovery, wipe dalvik and cache partition, and reboot then wait out the time, reboot and again wait out time,,, then set ringtones,,, and try...don't know what else to say...
Thanks for the suggestions. Will try them.
Hey guys!
I'm new in this forum and this website, so that's why I'm posting my problem in Q&A section instead of development thread ( 10 posts rule )
well I'm using the PAC-ROM by iurnait for over a month and I really like it.
But a while ago these strange reboots started. I was listening to music, using PowerAmp, when the music stopped. I pressed the Home - Button to look at the screen and see what's wrong but the device did not response. A few seconds later the PAC-Bootanimation started but without kernel logo. When the players booted it is fully functional again. So the last week it happend a few times so I decided to make an update and hoped this bug will be fixed. But instead it happend again...
Well I read in the Forums and decided to install an Logcat app and tried to reproduce the Error to post it here in the forum.
You may know that if you something want to happen again it naturally doesn't happen
But this night I caught the Error. I just pressed the Home-Button to have a look at the Lockscreen because i wanted to know what time it is. But instead of shut of the display after a while the Bootlogo was shown...
So I hope our developers can find out what's going wrong. I attached the Logcat for you. It is really long but I think the main error occured at this time: "07-12 01:55:05.070"
Hope you can help me I really like this ROM.
I'm using the International Player with PAC build from July 9th and Koala888 KKernel R2 intl with LiveOC but I don't use it. The player is overclocked at 1100 MHz and the voltages are default.
Hope I didn't forget something and thank you
John
I had the same problem with an old stock ROM, I don't know if it was CPU Tuner or the ROM. It stopped when I installed the latest stock ROM from here: http://forum.xda-developers.com/showthread.php?t=1446774
It's probably the overclock's fault.
Try using a program called nstools and enable liveoc at 1.2 GHz only and set it to 115% at 1375mv. That fixed it for me almost entirely.
Sent from my YP-G70 using xda app-developers app
Thank you for the reply i'll try the thing with the oc hope it works
Thanks for the help
Random reboots are usual in roms not stock-based. And PAC every day have a new build without so much testing so it's really possible that this is a rom fault.
If you want keep with the unique characteristics of pac (like dpi settings and halo for example) you can try to flash one of the iurnait's releases (not basketbuild) and if you don't use this pac characteristics, then I highly recommend you cm 10.1. It's smoother and more stable
Enviat des del meu YP-G70 utilitzant Tapatalk 4 Beta
---------- Post added at 02:13 AM ---------- Previous post was at 02:11 AM ----------
And if you want to try liveoc, for me the perfect is 1400 with 112% liveoc to the latest frequency only (1400) with 1375 arm voltage and 1200 int voltage (only to the latest frequency step again)
Enviat des del meu YP-G70 utilitzant Tapatalk 4 Beta
thank you txordi i think i'll flash cm10.1 and test it .
When I tried liveoc the player was very laggy and did not perform very good... but i'll try it again
thank you
lihildry mimie
This happens to me too. Might be a bug or something.
10114jose said:
This happens to me too. Might be a bug or something.
Click to expand...
Click to collapse
Yes, I think it's a bug.
If you find it as annoying as I do, I recommend to switch to CyanogenMod it's a lot more stable and faster
You should search around xda forms, now there is CyanogenMod 10.2 (JellyBean 4.3 yes 4.3) build for the galaxy player series
JohnBergago said:
Hey guys!
I'm new in this forum and this website, so that's why I'm posting my problem in Q&A section instead of development thread ( 10 posts rule )
well I'm using the PAC-ROM by iurnait for over a month and I really like it.
But a while ago these strange reboots started. I was listening to music, using PowerAmp, when the music stopped. I pressed the Home - Button to look at the screen and see what's wrong but the device did not response. A few seconds later the PAC-Bootanimation started but without kernel logo. When the players booted it is fully functional again. So the last week it happend a few times so I decided to make an update and hoped this bug will be fixed. But instead it happend again...
Well I read in the Forums and decided to install an Logcat app and tried to reproduce the Error to post it here in the forum.
You may know that if you something want to happen again it naturally doesn't happen
But this night I caught the Error. I just pressed the Home-Button to have a look at the Lockscreen because i wanted to know what time it is. But instead of shut of the display after a while the Bootlogo was shown...
So I hope our developers can find out what's going wrong. I attached the Logcat for you. It is really long but I think the main error occured at this time: "07-12 01:55:05.070"
Hope you can help me I really like this ROM.
I'm using the International Player with PAC build from July 9th and Koala888 KKernel R2 intl with LiveOC but I don't use it. The player is overclocked at 1100 MHz and the voltages are default.
Hope I didn't forget something and thank you
John
Click to expand...
Click to collapse
I have had the same problem with the SGP 4.0 YPG1 for the longest time. I have run out of ideas. It started just after I flashed CM11, although I don't think it has anything to do with the rom, as I have since done the following:
Move from CM 11 to CM 10.2
flashed back to stock
replaced the battery
reformatted the sd card
removed the external sd
None of the above seemed to help. The device has the following symptoms. It reboots, almost always in the middle of the night, and boot loops at the Samsung logo. Otherwise the device works fine. I still haven't ruled out a permanent hardware defect but I am hoping that that is not the case. Any help would be appreciated.
Go to a different ROM because PAC ROM is unstable with their night lies.
Sent from my YP-G70 using XDA Free mobile app
Before I upgraded my YP-G70 by flashing a custom kernel and ROM, those random reboots used to occur all the time, mostly when my screen froze. I would suggest upgrading your ROM to Carbon ROM from meticulous(.)co(.)vu. Remove parentheses because of 10 post/no offsite link rule. It's pretty good for both US and International YP-G70 versions; I haven't experienced any errors/bugs with it yet. I think it would probably be the best solution for fixing your restart problem.
__________________________________________
Samsung Galaxy Player 5.0 (Model YP-G70)
• Carbon ROM 4.4.4 by Meticulus Dev Team
• Daily Drivers Kernel