ok, for some reason, thought build.prop q's were relevant to the kernel...
anyway, I edited build.prop in /system with RootExplorer's text editor. changed the value for wifi.supplicant_scan_interval from 30 to 120. no extra lines or spaces, etc- just changed the number, saved, then rebooted. it took an obscene amount of time to boot up and the device stopped going into deep sleep after a short while. I installed better battery stats to see what was wrong and the app indicated mmc_delayed_work under kernel or partial wakelocks (i forget which). I restored the original build.prop and the device worked like normal.
Is this a bug or is ICS/JB different enough from GB that you have to go through alternate means to change build.prop (eg flashing an update script from CWM, or something similar)?
I've tried this twice already and gotten similar results and the method by which I edited the build.prop was exactly the same as I used to edit it on GB without issue.
another thread I checked out in the S II dev thread indicated that this is possible- editing build.prop (wifi scan at least, on top of a few others parameters)- w/o issue, so....yeah.
alljokingaside said:
ok, for some reason, thought build.prop q's were relevant to the kernel...
anyway, I edited build.prop in /system with RootExplorer's text editor. changed the value for wifi.supplicant_scan_interval from 30 to 120. no extra lines or spaces, etc- just changed the number, saved, then rebooted. it took an obscene amount of time to boot up and the device stopped going into deep sleep after a short while. I installed better battery stats to see what was wrong and the app indicated mmc_delayed_work under kernel or partial wakelocks (i forget which). I restored the original build.prop and the device worked like normal.
Is this a bug or is ICS/JB different enough from GB that you have to go through alternate means to change build.prop (eg flashing an update script from CWM, or something similar)?
I've tried this twice already and gotten similar results and the method by which I edited the build.prop was exactly the same as I used to edit it on GB without issue.
another thread I checked out in the S II dev thread indicated that this is possible- editing build.prop (wifi scan at least, on top of a few others parameters)- w/o issue, so....yeah.
Click to expand...
Click to collapse
I have no idea why that would happen, but I guarantee you the interval is fine where it is. I've left my player on with wi-fi over a week.
Mevordel said:
I have no idea why that would happen, but I guarantee you the interval is fine where it is. I've left my player on with wi-fi over a week.
Click to expand...
Click to collapse
I'm recording atm but problem isn't replicating. go figure; well, if it does, I'll post a logcat. if not, good for me since I forget to turn the wifi off most of the time and especially in places with no open wifi. anyway, I was posting this in case someone else did come across a similar problem and had a solution since my searches led nowhere (searching for anything mmc_delayed_work related comes up with little useful info/apparently a lot of once-valid GB tweaks are "busted"/not in ICS code base)
whether or not the scan interval isn't exactly the point, why I'm pursuing it; it's the specific point atm, but the general point is device ownership- tailoring your device to your heart's desire; complete ownership. that's the premise behind this whole site as I'm sure everyone here is aware. if I did something to mess it up along the way, great. but if it is a bug or something with ICS code base, it's be nice to know. a lot of folk like messing with build.prop so it'd be nice to know what can or cannot be messed with.
atm, it does look like I messed something up when editing and saving- perhaps I added a space or line where it shouldn't've been- since the device is sleeping as it should, again, if I find something, I'll post the logcat.
thanks for the re:
alljokingaside said:
I'm recording atm but problem isn't replicating. go figure; well, if it does, I'll post a logcat. if not, good for me since I forget to turn the wifi off most of the time and especially in places with no open wifi. anyway, I was posting this in case someone else did come across a similar problem and had a solution since my searches led nowhere (searching for anything mmc_delayed_work related comes up with little useful info/apparently a lot of once-valid GB tweaks are "busted"/not in ICS code base)
whether or not the scan interval isn't exactly the point, why I'm pursuing it; it's the specific point atm, but the general point is device ownership- tailoring your device to your heart's desire; complete ownership. that's the premise behind this whole site as I'm sure everyone here is aware. if I did something to mess it up along the way, great. but if it is a bug or something with ICS code base, it's be nice to know. a lot of folk like messing with build.prop so it'd be nice to know what can or cannot be messed with.
atm, it does look like I messed something up when editing and saving- perhaps I added a space or line where it shouldn't've been- since the device is sleeping as it should, again, if I find something, I'll post the logcat.
thanks for the re:
Click to expand...
Click to collapse
I understand.
Thinking about it, mmc_delayed_work seems like it's tryng to catch up the SDcard or something. Did you reboot cleanly? That may be the issue.
Mevordel said:
I understand.
Thinking about it, mmc_delayed_work seems like it's tryng to catch up the SDcard or something. Did you reboot cleanly? That may be the issue.
Click to expand...
Click to collapse
No clue. what do you mean by "reboot cleanly"? if by that you mean, did I reboot using the reboot option in the power menu, then yes. always.
After restoring a backup and re-editing build.prop, sleep worked like gamebusters. Except, bluetooth auto-toggled on ("bluetooth is turning on"). After rebooting, it was stuck on the boot animation screen for a few minutes. A reboot after that pretty much boot looped it. I restored my backup afterwards...
Looking in the logcat (after editing), I noticed a ton of errors and permission denials.... Since I don't have much expertise here, I can't say for sure that they're normal but they seem to be abnormal. Wayyy more than I remember seeing when I browsed through before on a "clean" boot. But again, with the lack of expertise (or any functional knowledge for that matter)
==
Now, after having restored the backup before making the edits and rebooting, it seems to be stuck in a bootloop....huh. ok, after rebooting it 2x, it finally seems to have booted up "normally." Both before restoring (w/ edits and BT error) and after restoring (w/o build.prop edits), it's taking a lot longer to boot up than it used to....guesstimating 3-4 minutes. When it boots up, I get/got: "process system isn't responding" (both before and after restores now) and something about alarm error.
I've attached logcats of both pre- and post-event, if you're curious. As to "solving" this,I'm just gonna re-flash the PA ROM and wipe caches to get rid of these problems. ergh. device meets my foot against the wall is next on the checklist.
thanks again. I'd like to say, Stay classy, San Diego, but we all know San Diego and its class
Related
Ok guys, I've read a lots of posts of people having sleep problems with frx07.
I installed it and I didn't had them...in the very first days...
After something has changed and my phone never went to sleep again.
I've read lots of post trying to fix it (hoping that someone already found what was keeping the phone awake) but I didn't found anything useful.
So I tried to solve it by myself and... i did it.
Using getlogs I tried to diagnose the problem but it contained nothing useful.
I killed every process, uninstalled from /system/app the apps I don't use (like chinese/japanese IME) and I left running only "really necessary" processes.
PS show only few (system's processes) but the phone didn't go to sleep aswell.
(I can upload the ps results if you need it)
Initially I thought it was something I installed (because the stock FRX07 didn't had the problem) so I made a complete backup (of the sleepless system) with titanium.
I removed the data.img and I started "from scratch" without replacing kernel/rootfs.
The phone could successfully sleep again.
I did a total restore from titanium and the sleep problem appeared again.
I deleted data.img again, letting the system to create again an empty one.
As I said before the default data (empty phone) works and the phone sleeps.
I thought "if an app I installed caused the problem let titanium restore system data only (without restoring any user app)"
I restored system data only and... SLEEP PROBLEMS APPEARED AGAIN.
It was not an app I installed!!! I deleted again data.img.
I restored only GREEN items in titanium (that means only user-changed data like messages, apn, contacts, accounts, wifi, calls and so on) AND my applications (and their data).
The phone can successfully sleep now.
So..if you have a sleep problem:
open sd card and move titanium apk from andboot/apps/other to andboot/apps (in this way you will have titanium installed by default when you delete data.img)
boot into sleepless FRX07.
open titanium backup and make a full backup.
reboot into winmo.
delete data.img
boot into android (you will have a "just installed system")
open titanium backup and restore "user apps+data" and the green system data.
reboot android.
you should not have sleep problems again.
Now... it should be useful to investigate further and find out what system app DATA is causing frx07 to stay awake (because the system app only without data actually work).
Let me know if this works for you
I'm not sure I can agree with you. I use TB to backup all the time, and use the batch features to backup every thing in addition to restoring everything... So I am questioning those results... I've never had issues with sleep - assuming I don't have GPS enabled or there's not some app screwing it up, honestly...
I'd have to say your experience was unique - unless someone else can reproduce these results, I'm going to say there's something else going on here...
this orange light is killing me too n i really dont knw wat to do....i have to quetion ur #8 step thou...how do i reboot to android? never heard of that
prexzone said:
this orange light is killing me too n i really dont knw wat to do....i have to quetion ur #8 step thou...how do i reboot to android? never heard of that
Click to expand...
Click to collapse
Ehh... shut off phone, boot WM, launch haret?
P.S: English is not my first language and I had trouble understanding parts of your post, hope that's what you asked.
prexzone said:
this orange light is killing me too n i really dont knw wat to do....i have to quetion ur #8 step thou...how do i reboot to android? never heard of that
Click to expand...
Click to collapse
I'm sure he means reboot the phone to WinMo, then hit HaRET to get back to Android.
You really should take a little more time compiling your posts. They are quite difficult to read at times... It would be appreciated, as others obviously have problems reading your posts as well...
arrrghhh said:
I'd have to say your experience was unique - unless someone else can reproduce these results, I'm going to say there's something else going on here...
Click to expand...
Click to collapse
+1.. Haven't experienced this issue.
Eodun said:
Ehh... shut off phone, boot WM, launch haret?
Click to expand...
Click to collapse
Yes. Did someone with the sleep problem tried my steps? Did you solve the problem?
arrrghhh said:
I'm not sure I can agree with you. I use TB to backup all the time, and use the batch features to backup every thing in addition to restoring everything... So I am questioning those results... I've never had issues with sleep - assuming I don't have GPS enabled or there's not some app screwing it up, honestly
Click to expand...
Click to collapse
If you don't have the problem then you don't need the solution and you don't have the possibility to agree. I have titanium backup too with scheduled backups. The problem is not in tb, I never said it, it's in FRX07 actually. I'm saying that there's something in frx07 that causes the phone to stay awake. (And trying step by step I found the problem to be related to some system app data).
You could say "you messed up your install" (I thought it too!!) but this "phone not sleeping" seems to be a common problem (so maybe I messed up but more likely there's something that's not working as expected and on some models or after some user operations the system "hangs")
So... If you have (or will have) sleep problems then you can try to do the steps I suggested to fix it. In my case it worked and it solved my problem it could be worth to try, no?
BTW: even the clockworkmod recovery restore problem seemed to be only mine.. lots of people said "it always worked, I'm using it since I was a baby".. but on some special conditions the bug was replicable and I fixed it.
http://forum.xda-developers.com/showthread.php?t=1154892
http://review.cyanogenmod.com/#change,6872
LinoX said:
You could say "you messed up your install" (I thought it too!!) but this "phone not sleeping" seems to be a common problem (so maybe I messed up but more likely there's something that's not working as expected and on some models or after some user operations the system "hangs")
So... If you have (or will have) sleep problems then you can try to do the steps I suggested to fix it. In my case it worked and it solved my problem it could be worth to try, no?
Click to expand...
Click to collapse
Ok, so you messed up your install. Happy? .
I'm honestly not sure. Until it can be recreated, I'm going to have to err on the side of user err .
I'm honestly glad that you resolved the sleep issues on your device. I just don't think it's a very good assessment of the sleep issues (you never really seemed to pinpoint it?) and I don't think it's a very good solution for newbies to try. Perhaps if they've exhausted all other avenues and your solution works - then we do have a bug. But now let's try to track it down... where is this happening? Why is this happening? I have a feeling that something you have done has caused this, but there's no way I can be for sure... other than not many people have persistent sleep issues. If they do, it's pretty much always been an app/widget assuming they follow the rules on GPS .
One thing I just found: com.android.email has a MAJOR cpu hogging bug. If you have an exchange account set up and have it polling instead of push or manual, AND you have a situation where data is unavailable, it goes into this braindead malloc/free cycle that eats up CPU like no tomorrow. If you google com.android.email cpu, this is a known issue that has been unfixed forever.
Not sure how many of those having sleep issues have this setup, but I recommend anyone using email to access an Exchange server to set it to manual or push. You can check this bug by running top, and cross-check via logcat -v time where the pid for email is doing a malloc spam.
-- Starfox
That was not my situation. Before wiping the phone I disabled the automatic data-sync (sync on background) and I didn't have an exchange account set up. (but i's nice to know about this bug maybe someone could benefit from your hint)
Okay so I took the plunge and installed my first ROM (ICS Collective Base4) among other things with my SGH-I717M (Bell). Everything went very well and here are the issues that despite reading over 500 pages in threads related to these issues, I have not been able to solve them (workarounds, sure). I'm hoping that others can confirm these glitches and whether or not they have been able to remedy them:
-Upon boot, "Unfortunately, the process com.android.phone has stopped". Annoying, but doesn't seem to affect anything. No workaround or solution.
-Baseband "unknown". Tried ODIN flash install AND coming from completely stock phone via CWM flash, neither has remedied this problem. Doesn't seem to affect anything so don't really care.
-Stock calendar application missing - really don't like some of the other calendars, but I can't seem to find the APK file in any other ICS ROM's out there, so I gave up on this. So workaround, no solution.
-Time zone wrong. Workaround is to deselect automatic network management and select the correct timezone. Reverts back to incorrect upon rebooting so apparently only a workaround and no solution.
-Upon booting setCPU max/min speeds are incorrect and you have to open the application for it to correct the speeds. Perhaps it's just the widget that's broken, but for now it's a workaround and I can't seem to figure out a solution. Quandrant benchmarks seem to indicate that if I don't do this, the performance is affected as if the speeds are 1242max/384min and not 1512max/384min.
-Phone freezes on "Power Off", have to hold power button - camera flash goes off and then restarts. Workaround seems to be to use terminal emulator or other applications to reboot, etc. Don't know if there's a solution to this.
-Wallpaper incorrectly zooms - workaround: market applications. No solution that I can find yet.
-Unrelated to the ROM, but V6 Supercharger - I can only get it to report 50% supercharged, even after modifying my services.jar file and following all "step 8" instructions (that was an undertaking!!!). Don't know what's up there, but maybe some of you super-techs have figured it out.
-Only 624MB of RAM available instead of 700MB+ with GB. Haven't heard anything about why this is, so no solution or workaround.
-Doesn't seem to be an ICS keyboard available? I think this can just be installed from the market but I haven't tried it so not sure.
I'm sure there's other things like with Swype, tethering, etc.. etc... that are not working but this is just what I've noticed within the last 8 hours of flashing and trying to set-up and configure. Any comments or helpful suggestions for a n00b like me?
Thank you for any and all feedback. Thank you to all the developers working hard on this fresh release to bring us a solid ROM!
Calender: http://dl.dropbox.com/u/569065/Calendar.apk
Remember, this is a leaked firmware, these bugs are within that leak itself and a few of these issues have been addressed (unknown baseband, etc..) And will be fixed when we release the actual full ROM. this is just the base we shared in the mean time. A few are still present likesome settings not sticking through boot, and the power menu hanging.
Ithink is ur phone acting weird. Only the setcpu speeds not sticking and issue about wallpaper which can easily be fixed by using quicpics are the two issues my phone had. Just dnt use any cpu controller i noticed phone goes to sleep when no cpu controller while when there is cpu controller screen off speed sticks to 384 or 192
Sent from my SAMSUNG-SGH-I717 using xda premium
studacris said:
Remember, this is a leaked firmware, these bugs are within that leak itself and a few of these issues have been addressed (unknown baseband, etc..) And will be fixed when we release the actual full ROM. this is just the base we shared in the mean time. A few are still present likesome settings not sticking through boot, and the power menu hanging.
Click to expand...
Click to collapse
Absolutely. And considering what I've read about previously leaked versions of Android over the years, this one performs like a champ. Can't wait to see what comes out next, but I figured from what I've read this one works well enough to go the distance and install. Thanks again collective!
Felinos11 said:
Ithink is ur phone acting weird. Only the setcpu speeds not sticking and issue about wallpaper which can easily be fixed by using quicpics are the two issues my phone had. Just dnt use any cpu controller i noticed phone goes to sleep when no cpu controller while when there is cpu controller screen off speed sticks to 384 or 192
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
Yeah, just thought I would put my experience out there if it helps anyone or if someone could help me lol. It's very likely some of these are isolated problems, but most of them are problems with the leaked version. I uninstalled setCPU because I think you're right, something likes to nom nom the battery when the screen is off.
Oh and here's something odd which I don't know if anyone else has experienced with ICS or GB, but Terminal Emulator doesn't allow me to type anything unless I capitalize each individual letter. Which of course is useless because it can't accept commands in caps. When I press any key in lowercase it's like I haven't done anything. I had to switch to the pen mode where I scribe each letter and then it puts lowercase letters in for me. Anyone know what's up with this?
This is probably not the best Rom to run for your first flash. I would try one of the official releases in the development thread, unless you are an official tester for The Collective...
Can't wait till they release an official ROM ...
Sent from my SAMSUNG-SGH-I717 using Tapatalk
mk2 love i see im a vr lover Mr helios
Sent from my SAMSUNG-SGH-I717 using XDA
Helios909 said:
Oh and here's something odd which I don't know if anyone else has experienced with ICS or GB, but Terminal Emulator doesn't allow me to type anything unless I capitalize each individual letter. Which of course is useless because it can't accept commands in caps. When I press any key in lowercase it's like I haven't done anything. I had to switch to the pen mode where I scribe each letter and then it puts lowercase letters in for me. Anyone know what's up with this?
Click to expand...
Click to collapse
I had that issue in GB... In ICS it seems to be intermittent- sometimes it just works others it doesn't...
And regarding the baseband, not sure about the Collective rom, but DAGr8's ICS rom displays the modem correctly on my Bell Note.
I also had the timezone issue- strangely enough when I disabled network time and timezone, I also stopped get random slowdowns and ANRs.
Sent from my SAMSUNG-SGH-I717 using XDA
We've got the baseband unknown issue fixed in the full ROM. We just haven't released it. Still working on a couple things before we're comfortable sharing.
Hi, here are my thoughts;
1. Flash a CWM ICS modem(fixed it for me). If you cant find a modem use Dagr8's inital version of the ICS leak, it will successfully flash the modem(unlike the initial collective version(post 501 thread). The main point is to ensure you have the correct baseband(should not say unknown).
2. For now, dont supercharge the ICS leak until you have a stable running OS.
3. After fixing the baseband unknown issue(#1), reflash the collective post 501 ICS rom. It is stable, and the cleanup of the bloat was started already.
4. After installing #3, factory reset your phone.
At this point you should have a bloated, but error free ICS on your computer. Make a CWM backup, install titanium backup, and rip out the junk APK's(widgets, samsung/att garbage). Doing this will provide longer battery life and better performance.
No other wipe scripts are needed.
Factory reset BEFORE flash. The cwm script in the zip itself formats /system and /cache before it writes anything.
And the baseband unknown thing isn't a big deal. Its not that you don't have a modem at all, everything still works you get mobile data, its just the os doesn't properly report it.
if you like what you got, i say sit tight, we're working on the full ROM. You won't be disappointed
studacris said:
No other wipe scripts are needed.
Factory reset BEFORE flash. The cwm script in the zip itself formats /system and /cache before it writes anything.
And the baseband unknown thing isn't a big deal. Its not that you don't have a modem at all, everything still works you get mobile data, its just the os doesn't properly report it.
I say if you like what you got, i say sit tight, we're working on the full ROM. You won't be disappointed
Click to expand...
Click to collapse
Would be cool if you guys could make a minimalistic style rom without all the makeup and cosmetics and focused on performance
We think its cooler to do BOTH
Cause the guys at Samsung must have left their seeing eye dogs at home when it came time to theme
most of us don't usually do minimalistic... once a stable rom gets out you can expect a variety of themes. Sit tight.
studacris said:
We've got the baseband unknown issue fixed in the full ROM. We just haven't released it. Still working on a couple things before we're comfortable sharing.
Click to expand...
Click to collapse
THanks Cris, thats all im waiting for to make the jump to ICS-----is the collectives official - unofficial ics dev thread.
Studacris said:
"We think its cooler to do BOTH
Cause the guys at Samsung must have left their seeing eye dogs at home when it came time to theme"
LOVE IT!... and CAN'T WAIT! Thank you for all you do... and have a few beers on me. PayPal confirmation number: 6RE28092GB801952P
fishing.laguna.madre
NoteI717
Powered by The Unofficial
Thanked you in the ROM threads, but again, very appreciated. Thank you.
Sit tight. what we got cooking is gonna be tasty
Same experience here
well done guys excellent base.... Having the same experiences as helios909...
Really looking forward to the the fully packaged version. Not experiencing problems with cpu speed set on boot.
Face unlock not work properly yet. Device hangs on reboot as reported. Auto update time bug exists. Baseband version unknown. Phone crashes on initial boot. But recovers.
New voice type engine is amazing. As demonstrated here.
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.
i've recently been encountering random reboots on my Galaxy Note 3 (N9005), on stock 4.4.2 ROM.
The reboot occurs regardless of time, foreground/background running apps, battery level and anything else i can think of. for instance, it can just instantly hang+auto-reboot while i'm browsing facebook, surfing on chrome, switching tracks on poweramp, or even when the screen is off doing nothing (deep sleep)!
I've tried to uninstall some of the recent installed apps, but still unable to find any culprit. is there any way i can identify the culprit, without resorting to factory-reset for my device? i spent a lot of time doing the configuration for each app that i use, and wouldn't want to repeat the whole process..
Thanks in advance for your help!
could anyone help please?
Only way to know would be to get a logcat or last_kmesg. You might try something like this since it is so random:
https://play.google.com/store/apps/details?id=org.jtb.alogrec
es0tericcha0s said:
Only way to know would be to get a logcat or last_kmesg. You might try something like this since it is so random:
https://play.google.com/store/apps/details?id=org.jtb.alogrec
Click to expand...
Click to collapse
i downloaded aLogRec as requested and recorded the log for the entire day.
this is the log for the first 16hours - i opened it with notepad++ and the log was super short - is it normal?
Link 1
this is the log for the next few hours, where the random reboot occurred halfway - seems that it's empty. does that mean there's no way for me to know how the reboot came about?
Link 2
dylansmith said:
i downloaded aLogRec as requested and recorded the log for the entire day.
this is the log for the first 16hours - i opened it with notepad++ and the log was super short - is it normal?
Link 1
this is the log for the next few hours, where the random reboot occurred halfway - seems that it's empty. does that mean there's no way for me to know how the reboot came about?
Link 2
Click to expand...
Click to collapse
Yea, that app definitely didn't work. Not really sure why. But other than catching it in the act using the logcat, whether it is another automatic one or just the manual way via the phone or computer, there's no other way to tell. You do know that you can backup most of your apps and settings with a variety of tools? It won't make everything perfect, but cuts the time of restoring your phone after a factory reset way down. I literally wipe my entire phone and reset it up like 3 times a week on average. It usually takes me about 20 minutes to an hour depending on if I just need it usable or exactly the way I like it.
es0tericcha0s said:
Yea, that app definitely didn't work. Not really sure why. But other than catching it in the act using the logcat, whether it is another automatic one or just the manual way via the phone or computer, there's no other way to tell. You do know that you can backup most of your apps and settings with a variety of tools? It won't make everything perfect, but cuts the time of restoring your phone after a factory reset way down. I literally wipe my entire phone and reset it up like 3 times a week on average. It usually takes me about 20 minutes to an hour depending on if I just need it usable or exactly the way I like it.
Click to expand...
Click to collapse
thanks for the reply. got a few questions:
1. other than aLogCat, any other app i can try to catch the random reboot in the act?
2. yes, i could backup all my apps+settings using TB, but would i also be restoring the 'random reboot' in this case as well?
3. another symptom just occurred and i'm not sure whether it's relevant to the random reboot. after the random reboot (or so it seems), all my saved WIFI passwords get forgotten, and i need to re-enter the passwords for it to auto-login to my home/office network. i also realize it loses one of the settings i previously adjusted in Developer Options - the transition animation scale was set to 0x last time and set back to 1x.. but when it random reboots nowadays, it will just default back to 0x (which isn't the correct default).
i'm so frustrated at the number of problems my phone is facing right now..
dylansmith said:
thanks for the reply. got a few questions:
1. other than aLogCat, any other app i can try to catch the random reboot in the act?
2. yes, i could backup all my apps+settings using TB, but would i also be restoring the 'random reboot' in this case as well?
3. another symptom just occurred and i'm not sure whether it's relevant to the random reboot. after the random reboot (or so it seems), all my saved WIFI passwords get forgotten, and i need to re-enter the passwords for it to auto-login to my home/office network. i also realize it loses one of the settings i previously adjusted in Developer Options - the transition animation scale was set to 0x last time and set back to 1x.. but when it random reboots nowadays, it will just default back to 0x (which isn't the correct default).
i'm so frustrated at the number of problems my phone is facing right now..
Click to expand...
Click to collapse
https://play.google.com/store/apps/details?id=scd.lcex - looks pretty solid and more updated than the other one.
Possibly, but since we don't know what caused it, no way to know. What you do is backup everything, reset, then test, then start to add apps back in and test. Sucks, but just one of those things. Software issues can be tricky because there are so many different factors in play.
But it seems like this might be an issue with certain Samsung phones with batteries that are not performing as they should:
http://forum.xda-developers.com/showthread.php?t=2567941&page=3
es0tericcha0s said:
https://play.google.com/store/apps/details?id=scd.lcex - looks pretty solid and more updated than the other one.
Possibly, but since we don't know what caused it, no way to know. What you do is backup everything, reset, then test, then start to add apps back in and test. Sucks, but just one of those things. Software issues can be tricky because there are so many different factors in play.
But it seems like this might be an issue with certain Samsung phones with batteries that are not performing as they should:
http://forum.xda-developers.com/showthread.php?t=2567941&page=3
Click to expand...
Click to collapse
alright, will try the Extreme version and hopefully it catches the culprit.
As for the battery problem, it doesn't seem like the same case as mentioned in the other thread - he had a reboot loop and crazy drain, both of which are not existent (luckily) symptoms on my end.
Your issues could definitely be explained by battery issues though. Have seen stuff like this before at my shop. Batteries are less than $10 typically and worst case, you have a spare battery so if you go out and about and the phone dies, you don't have to run to a charger / outlet.
es0tericcha0s said:
Your issues could definitely be explained by battery issues though. Have seen stuff like this before at my shop. Batteries are less than $10 typically and worst case, you have a spare battery so if you go out and about and the phone dies, you don't have to run to a charger / outlet.
Click to expand...
Click to collapse
hmm, pretty sure it's not a battery issue then. just bought a new battery and the same problem exists.
my logcat files appended as follows: https://www.dropbox.com/s/yjtio2je6h71mre/LogCat.zip
would appreciate everyone's help!
thanks!
I was experiencing random reboots on the stock ROM for my KFHD when I was running stock. Turns out it was caused by me adjusting the DPI to a custom value.
>>>Sent from my homebuilt TARDIS running Android 4.4... or maybe it's a Kindle Fire HD running Cyanogenmod 11<<<
Ph0enix_216 said:
I was experiencing random reboots on the stock ROM for my KFHD when I was running stock. Turns out it was caused by me adjusting the DPI to a custom value.
>>>Sent from my homebuilt TARDIS running Android 4.4... or maybe it's a Kindle Fire HD running Cyanogenmod 11<<<
Click to expand...
Click to collapse
that could be one possible cause as I have certain preset dpi's for apps using Xposed.
any other possibilities and any other way to avoid it?
dylansmith said:
that could be one possible cause as I have certain preset dpi's for apps using Xposed.
any other possibilities and any other way to avoid it?
Click to expand...
Click to collapse
The only thing I can suggest is resting the DPI to stock, unfortunetly. Or a DPI that is known to work well with your device.
Ph0enix_216 said:
The only thing I can suggest is resting the DPI to stock, unfortunetly. Or a DPI that is known to work well with your device.
Click to expand...
Click to collapse
just curious - did anyone look through my logcat to see if there are other causes? i already restored to default DPI but still experiencing the same issues.
I have been experiencing a series of force closes. I am posting this to see if anyone else has experienced this, and whether anyone can suggest a fix. I'm pretty sure it was something I did, but I'm not sure what. I'm hoping that this can maybe narrow it down.
Device: SM-N900P
Firmware: OC5, stock, rooted, with several tweaks and modifications(detailed below).
The problem: I am getting several force closes. They only occur when I am trying to open certain settings. So, they aren't just popping up at random. They are slightly troubling, but not really problematic. Which is to say, aside from the actual force closes themselves, I don't really seem to be experiencing any major problems. Here are the FC's I am experiencing:
-Menu> Settings> General> Battery: This one results in a "Unfortunately, Settings has stopped" dialog box, and an immediate return to my home screen. So, I can't check out my battery usage. I'm not seeing any crazy battery drain. By opening Root Explorer and navigating to data> system> batterystats.bin, and deleting batterystats.bin, the problem is kind of fixed- I can open battery from the settings menu after that. But there is only battery level and state displayed, no usage information(just a message saying it is not available).
-Menu> Settings> General> Developer options> Process Stats: Results in the same dialog box, and the background turns black if I don't press "OK". I'm not even sure what this does, but after my Battery started force closing, I started checking the rest of the settings out.
-Menu> Settings> Connections> Data usage: Dialog box, immediate return to home screen.
The probable cause: hard to say, I've done a few things to it. Like I said, I was hoping that someone would be able to figure out what I've done from the following information about what I have done so far. So, here goes.
I was on NK4, running Priest Punch ROM. I reverted to stock and took the OTA about a week or so ago. I immediately rooted and installed TWRP using the method in this thread: http://forum.xda-developers.com/note-3-sprint/general/how-to-root-note-3-lollipop-t3089382 .
After rooting, I didn't see a whole lot of OC5 development, so I started poking around to see what kinds of mods I could use. First thing I wanted to do was remove bloat. I started off using Root Explorer, then I happened upon this thread featuring a bloatware removal tool for the T-Mobile variant: http://forum.xda-developers.com/note-3-tmobile/development/tool-utility-sgn3-sm-n900x-bloat-t2813036 . It worked. I removed a bunch of apps, but nothing I wasn't sure I could safely remove(I had to check Google a few times). I did not notice any problems at this time.
Then I installed this mod to pump sound out of both speakers: http://forum.xda-developers.com/note-3-sprint/development/mod-sm-n900p-surround-sound-t2966042 . I did not notice any problems at this time.
Next, I decided I wanted more fonts, so uninstalled the preloaded fonts and pushed the apk from this thread: http://forum.xda-developers.com/showthread.php?t=2752379 . Again, no problems.
I decided that a working hotspot would be nice, so I used the method in this thread to get one: http://forum.xda-developers.com/note-4-sprint/general/lollipop-hotspot-root-flashing-t3048163 . I tested it and it worked. No problems.
I really wanted to silence my shutter sound, and I happened upon this Galaxy S4 thread: http://forum.xda-developers.com/showthread.php?t=2261789 . It worked, and there were no issues. This was my first exposure to csc codes. I found a similar thread for the s6( http://forum.xda-developers.com/galaxy-s6-edge/general/quick-guide-enabling-hidden-features-t3087506 ), and followed the instructions. I was able to enable the camera during calls and enable call recording. No problems here. I tried a keyboard mod from the same thread, which had no effect at all(good or bad), so I reverted the code for that one back.
This is when I think I started to go off the rails a bit. I saw a thread for the Polish variant of the Note 3, N9005. http://forum.xda-developers.com/gal...camera-mod-note-3-n9005-lollipop-5-0-t3067827 -it had a neat sounding mod designed to improve camera quality, remove recording time and snapshot restrictions, and make 60fps HD the default camcorder mode. It took a little trial and error to get it installed, but I was making backups of files I was messing with, and was able to quickly and easily reverse any missteps. Again, the mod works fine, and I have noticed no issues. So, I started looking at the dev's other work. Which led me to this thread: http://forum.xda-developers.com/galaxy-note-3/themes-apps/secsettings-mod-17-swipe-charging-t3046032 . I wanted some different unlock effects, and I wasn't really finding them, so I tried his mod out. It was a 3 step process: replace a SecSettings app, copy paste some .ogg files, and finally, copy paste a SustemUI .apk. The first two steps went fine, but the third resulted in a persisitent, repetitive dialog box. I forget what this dialog box said, but it popped up almost as soon as I could press "OK", and I had to restore the backup of SystemUI to make it usable again. Oddly enough, about half of the new unlock animations still worked fine, and I wasn't seeing any problems after that, so I left everything else there. I liked the unlock animations, and they didn't seem to be causing any problems after I restored the original systemUi .apk.
Let's see, what else might be relevant? I was using the built-in task killer quite a bit. I'm also using SetCPU. I have 2 profiles: Screen on, 1728 MHz max, 300 MHz min, governor ondemand. And Screen off, 1036 MHz max, 300 MHz min, governor interactive. And I have installed the Material Power Menu from this thread: http://forum.xda-developers.com/android/apps-games/app-materialpowermenu-reveal-animations-t3059169 .
I started to notice the battery FC last bight. So, I wiped the battery stats as outlined above. Noticed it again today, wiped stats again, and kept checking it. After about an hour, it was force closing again. That's when I started poking around and found the others.
I dunno if anything can be done about this, or if anyone might know what's wrong. And, like I said, Aside from these FC's I'm not experiencing any real problems. I'm a little worried that they may get worse, or turn into something more serious, but I can always restore a backup if that happens. But if there is some kind of fix for these issues, I would use it. Thanks in advance to anyone who takes the time to read this wall of text, and tale of irresponsible phonery.
These are all settings that monitor usage.... should that tell me anything? I have tried wiping cache and dalvik, but that only seems to fix battery usage and data usage very temporarily(like, for a minute or less). And it doesn't seem to have effect on Process Stats.
My thoughts:
Seeing as you have flashed a lot of mods, it could be anything. If it were me, I'd start the rom from scratch. Then for the first step, instead of removing apps, I'd freeze them with titanium backup and give that a day or two to check the stability.
If that works, I'd continue with the mods one by one, giving a day or so for stability checks.
If you'd rather not do all that, you could use a logcat to find the origin of the problems.
Sent from my SM-N900P using XDA Free mobile app
jlechner said:
My thoughts:
Seeing as you have flashed a lot of mods, it could be anything. If it were me, I'd start the rom from scratch. Then for the first step, instead of removing apps, I'd freeze them with titanium backup and give that a day or two to check the stability.
If that works, I'd continue with the mods one by one, giving a day or so for stability checks.
If you'd rather not do all that, you could use a logcat to find the origin of the problems.
Sent from my SM-N900P using XDA Free mobile app
Click to expand...
Click to collapse
I'd probably try the logcat first. One, because I hate doing stuff over, and two, Ive neber done it before and it should be a learning experience. Is it complicated? I'm assuming there is a thread here on xda about it...
GAPO said:
I'd probably try the logcat first. One, because I hate doing stuff over, and two, Ive neber done it before and it should be a learning experience. Is it complicated? I'm assuming there is a thread here on xda about it...
Click to expand...
Click to collapse
It's fairly straight forward. I did one to see why an app wasn't loading, didn't need instructions. But that was a fairly simple check, yours sounds more complicated. I'd do a bit of reading on it.
Sent from my SM-N900P using XDA Free mobile app
jlechner said:
It's fairly straight forward. I did one to see why an app wasn't loading, didn't need instructions. But that was a fairly simple check, yours sounds more complicated. I'd do a bit of reading on it.
Sent from my SM-N900P using XDA Free mobile app
Click to expand...
Click to collapse
Will do. Thanks for your help!
Okay well I decided to re flash OC5 and start from scratch.
I took it back to stock and re rooted. Am now debloating....no isssues yet.
I have flashed everything except the Polish camera mod and the wallpapers. Having zero issues of any kind. I know it can take difficulties some time to manifest themselves, but I'm betting it is either the lock screen animations or the camera mod. Leaning towards the lock screen animations because it involves messing with system.ui...
Okay, made a new backup and flashed the camera mod. No issues. After every mod, I have been going back and checking for issues. This is all stil pretty new, but if everything is still fine after a couple of days, well, I will be convinced that it was the lock rings. Not surprising obviously that flashing stuff meant for foreign variants can wreck your sh*t, lol.