So i posted this in the Unoffical Xposed Lollipop thread but i figured i'd make a new post since it isn't really related. Looking around i also can't really find similar issues to try to diagnose and solve myself unfortunately. Today after testing out GB on my S5Active and then removing it, since i found no real use other than slowing my system down i found myself with an interesting new Xposed log after, my phone ended up bugging out asking me to "Sign into a network" that i already had internet access through and been set up. It then restarted itself and sat in boot. Wouldn't finish so i pulled the battery and it started back up, checked the log and this issue started arising. I'm not even certain GravityBox is the culprit, but i got a damn good feeling considering how it's supposedly not TW compatible even though a bunch of TW users are posting about their successful experiences with it.
So, Since i lack an Nandroid backup because i had already lost everything previously including Nandroid in previous issues, would my best fix be reset and start from scratch for the third time? Or is there anything from the tombstone & log that would help figure out a solution rather than a fresh start.
Tombstone & Log attached
Edit: also it's on boot when this appears, doesn't really seem to effect anything. And only other thing I could see it maybe coming from is me editing my .xml for sd permissions, but I don't quite understand the code.
Xposed Framework crashing. You should contact the devs of framework for Samsung devices, or visit respective thread, to provide details.
Related
My boyfriend and I both have CyanogenMod 4.0.4 on our phones. I have to say, again, compared to JF ADP, it has been wonderful (Though since my boyfriend's wasn't done on a wipe, I can see he still has issues, and I knew he should have done a wipe!). (His phone went from stock Android to Cyanogenmod, and mine was easier - JF to CM)
One issue on his phone is tethering. I have updated the Radio, thinking that was the problem, but still nothing, details:
I have installed Wireless Tether for Root Users
I have changed the channel to 12, just like mine, because all channels are too commonly used where I live except the illegal ones. And since our phones don't generate a lengthly signal to begin with,I find it okay to use channel 12. (It's only illegal if it ever interferes with governmental signals, I looked deep into that one since I have DD-WRT on my router, though a router is more likely to interfere than our phones.)
I have changed the SSID to G1Tetherer
Since I picked the easier way in the beginning when I had JF ADP, I had been using aNetShare, and that actually asked for me to install something to use for tethering on my phone, so I also tried this method to see if it would work on his phone, to no avail.
So when I turn on the tethering App, none of our laptops see the SSID, no matter how close it is to our laptops. It does not show up at all. It doesn't appear to work either.
Is there something else I'm missing?
Now onto themes.
I had followed the simple route of installing a theme. Prior to this, I mindlessly deleted my recovery image, and since this has been my only source of internet, I feel pretty lucky having it back. I installed this theme: http://forum.xda-developers.com/showthread.php?t=555155 First I was and decided to install the first one. It only replaced my icons, some of my other settings, and my thingymajig at the bottom. Well, I WANTED the whole thing to have a black theme, so I decided to install the OTHER one ontop of that. Next boot screen takes FOREVER. Then the Android screen takes EVEN LONGER. Next I know I have a black, blank screen.
Now I was lucky that the CM-updater that was used on my boyfriend's phone was still just sitting there! I used that and finally got up and running again, but I am just wondering, why is that happening? Or was it just a bad idea to install one theme on top of the other? OR MAYBE, since it's 2:48AM, I should go to bed and wake up to wondering what the hell did I post this for? Also, is there anything I should be cautious about next time around, so I don't screw something up?
Thanks much for any responses,
Kelpie
Well I can somewhat answer the theme issue: Don't flash a theme on top of another. What I suggest is go to the CM Rom thread for stable release, download the theme template he provides and keep it on your sdcard's main folder. Whenever you want to switch themes, I suggest you first go back to default theme by flashing the template file. Then adding the new theme after it reboots fully into the default theme.
It seems like whatever the second theme you flashed probably had the new lockscreen or other sort of HTC related apps that uses different frameworks and flashing it on top of one without can cause a long boot process, then I'm assuming it hangs since the first themes uses edited colors in it. But thats all technical stuff, you just need to remember to go back to default 4.0.4 template first and only flash themes made for 4.0.4 rom.
Tethering..
I know this is probably a silly question, but did you click "always allow" when it asked for SU (root) permission?
BlackElvis79 said:
I know this is probably a silly question, but did you click "always allow" when it asked for SU (root) permission?
Click to expand...
Click to collapse
Yep. I always do that. I hate that popup as much as I hate UAC or whatever it's called for Vista, Windows 7, and semi-XP. It just dawned on me that there are a lot things that need root versus a true linux distro lol.
It works on my phone, but my phone still has the stock battery, and the charge doesn't hold when it's getting hot for too long (I've had to put it in the freezer several times). So I wanted to make it so he can use his for his internet and mine for my internet.
As for theme - I thought I should have, but I guess I was lazy. It actually looks like the problem is more associated with the theme, because people on that thread are having that issue and have even done a full wipe. People are also having the issue with the theme not fully displaying properly, so I guess I'll take this issue into that thread later on.
Hi:
I have installed the JH7 update found here on xda. My phone is rooted with sideloading enabled. I will be honest, I have a ton of apps on my phone.
I have had SO many problems since the update. I had to re-install the update 3 times, because after HOURS of trying to enable sideloading it still wouldn't work. After the third install I was finally able to enable sideloading.
Now, my problem is, some apps are crashing as soon as I open them. The 2 biggest culprits are e-mail, and Shop Saavy. I click to open them, they open for between 1-5 seconds, then close.
Any thoughts? I am desperately trying to find an answer, I would hate to have to hard reset, since I have already spent in excess of 10 hours trying to get my phone to where it is now.
I did have task manager installed, but the problem persists even after uninstall. Also, I used task manager prior to the update with no problems.
Thanks so much!
PS: If I do have to hard reset, can I simply use Sprite backup to restore everything, or will there still be some things that need configuring (ie. home screen etc)?
Quick idea: Download ROM Manager from the Market and run "Fix Permissions." Sometimes that will clear up any force close issues.
a.n said:
Quick idea: Download ROM Manager from the Market and run "Fix Permissions." Sometimes that will clear up any force close issues.
Click to expand...
Click to collapse
Hi:
I tried your suggestion, but sadly, it didn't work
Thanks so much for your suggestion though!!
PS: The apps just close, I do not get an error message. I have found some posts with people with e-mail crashing issues, but it seems that they do get a force close message, and that it is Exchange related. I do not use exchange.
Now that you mention it, I have had the stock email client force close upon load a few times since the update, and it had never done that beforehand. Maybe try reflashing just the kernel?
swedishcancerboi said:
Now that you mention it, I have had the stock email client force close upon load a few times since the update, and it had never done that beforehand. Maybe try reflashing just the kernel?
Click to expand...
Click to collapse
Hi:
Sorry to be a dunce, but how do you reflash just the kernel, and will it delete everything (apps, data etc)?
Thanks so much!
My 2 cents:
I don't know why it took hours to enable sideloading, i spent only a few minutes - but that gives me the impression that something might seriously be broken.
I would back up everything you want to save and do a master reset - it will clear all data, but you hould be JH7 fresh. If you want to go further, you can reflash factory JF6 then update to JH7. Either way, make sure you check basic apps first before installing a bunch of stuff.
I don't subscribe to the blind grasping at straws method of fixing things. After to many hours it is just faster to rebuild. If you knew what was wrong, then fix it, but if you don't then rebuild.
I agree. If you are needing this to function properly now, then just reset back to factory and start over. But if you are like me and just have to know what is broken.....that could take a while. I always try to make sure I don't have anything on my phone I couldn't live without just for instances like this.
Flashing just the kernel can be done with Odin (search the forum). There is a "stock captivate kernel" floating around (I'd post it, but I'm sure we don't need files posted multiple times). Instructions are included in that post. Basically you need a computer, USB cable, drivers, and bollocks. However, as mentioned, this is a shot in the dark. Random force closes could be caused by a variety of issues ranging from corrupt software, file system inconsistencies, to hardware failure, phase of the moon, appetite level, etc....
The safest bet is to backup everything, flash stock (if needed) and take it back to AT&T for a replacement.
Good Luck!
Hi:
Thank you so much for the replies, and help.
I decided to go ahead and reflash JH7. This has fixed the entire problem. So, apparently it was software related.
I am now going to install all my apps one at a time, in order to find the culprit. Hopefully it is one I can live without lol.
Anyway, thanks again!
Did you ever figure out what app was causing this? I am starting to get annoyed with my force closes and was going to re-flash and re-add all apps.
Hi:
Well, I MAY have figured it out. I had a million programs installed, and it just seemed like too much work to try to figure it out.
So I just re-installed JH7, and started from scratch, so I'll never really know what the problem was.
However recently I started having the same problem again. Since I started from scratch I have been gradually installing programs, just in case one cased a problem.
Well, it seems my problem was Startup Manager. I did NOT disable any system programs etc..., but it was still causing apps to crash, as soon as I froze it with Titanium Backup Manager, the problem stopped.
So, if you happen to be using Startup Manager, I would try uninstalling/ disabling it. Or, if you use a task manager, try not using it, maybe it is stopping whatever Startup Manager was disabling on mine.
Anyway, I hope this was of some help.
Oops, sorry, the program causing my troubles is actually called Startup Auditor.
Sent from my SAMSUNG-SGH-I897 using XDA App
So I've not been a member here for very long but I've been following the nexus one, nexus s, and now the galaxy note forums since their inauguration. Up until now I've not had an issue with rooting, installing and tweaking roms etc. I've not made a post yet because I've felt it unnecessary to add to all the b.s. in these forums and if I have an issue I'll search and find an answer or figure it out myself.
I've run into a problem with Stunner 1.4.26 ..
yes. yes. yes. I have gone through the ringer - full wipe, properly done etc. etc.
On a fresh install I cannot access the internal sdcard. The rom does not see it.. I can't post the bug and whats happening in the dev forum as I haven't made enough posts yet, so now I'm getting started.
Hopefully someone else is experiencing this as I type and I'll be able to sort it out soon.
If I can figure out what is going on rest assured I won't keep it to myself. You'll be the first to know. Oh and I wont just say, 'Hey I fixed it!' I'll actually tell you how I did and what the problem was and why I think my fix is valid..
.damn forums.
Hello,
This is my first time posting here, and I would like to request anyone on here to please assist me with the problem I am currently facing. I bought an unlocked, rooted HTC One with stock Android 4.3 installed as it's sole, primary OS this past summer. The person I bought it from is the one who actually rooted the phone, as my knowledge of such processes is fairly limited. I understand there are plenty of complications that I may run into dealing with this problem on my own and technical references may be lost on me, but I'm fairly competent enough to follow instructions from someone who may be able to help.
Here's the problem: I received an Android 4.4 OS update yesterday, which downloaded automatically and asked me if I wanted to install it. I thought the process would be fairly simple and I would not encounter any problems. However, when I asked the update to register and install, first it went into boot (I'm not certain which software was used for root), then the process started and everything seemed to be going fine until 'Patching files onto the whatever' came up and then it appeared that I encountered an error and the phone automatically went into what I can only assume is the bootloader menu? There were big Stock Android looking buttons on it which said things like Install, Root, Settings and a few others I don't recall. I tried to hit Install to see what happened and it brought me back to the part where 4.4 was supposed to be installed and I could read the error message at the end of it which said something like 'Error in patching files to zip folder or something', and I went back to the supposed bootloader menu. Confused and afraid, I think I pressed a button which I felt would allow me to reboot my phone and bring me back to my original 4.3 OS and that I would still be able to use my phone. First it said something like 'You no longer have root permissions', and there was an option where I could slide to apparently 'fix this', but I selected the 'don't fix' option as I obviously had no idea what I was doing. After this, the phone attempted to reboot, and a turquoise blue screen with strange markings came up on it and my phone hung. I killed the phone with the master power button and held it to switch off the phone.
BUT now, even since that has happened, my phone appears to be dead. It isn't starting up. When I put it on charge, the red LED doesn't show up. I have tried to used several ways to turn on my phone but it just wouldn't work.
I would like some light to be shed on this particular problem, and if anyone has experienced something similar to this, PLEASE, help me in fixing this. I am an eager learner and despite my limited, close to non-existent knowledge about dealing with a phone's OS, I know I can learn fast and follow instructions cleanly.
Please help me. Thank you.
To the admins I apologize if this is in the wrong section if it is please move it accordingly.
Hello everyone, I have an issue, hopefully someone can hel me and it starts like this. I and everyone else have been waiting for months for a safe root method and a recovery system such as TWRP OR CWM just incase I fudge something up flashing custom roms so I can always go back to stock. I came across a safestrap article and decided it was something similar to what I was looking for. So I decided to root using the big K. I know not the best choice, you can boo me now.
After a successful root, I installed safestrap. Unfortunately safestrap kept crashing upon starting the app, I couldnt even get it to set up. thats fine, I was just going to unroot and keep on living life, but then I stumbled upon Xposed installer, that modified and tweaked like a custom rom but without all the risk according to a website. I said hey thats worth a try and I did. After the Xposed installer setup and a reboot, I wad looking for mods on the web and all of a sudden my apps and system files started crashing to the point that I could not use my phone. I immedeately uninstalled Xposed installer ss soon ad my phone stabalized and unrooted.
I thought everything was good, 4 hours later the apps and system files started crashing again, so I did a reboot and I noticed that custom with the lock came up on intial startup. though I was told I was unrooted by the K program and even double checked using a rootchecker app, which stated I had indeed an unrooted phone. I did another reboot and no custom or logo came out. At this point I just wanted a working phone and As much as I hated doing so I did a factory reset. This seemed to have fixed the problem, but 4 days later my phone randomly went into a bootloop. I couldnt get it to stop so I took out the battery and that did not fix it.It was strange becuase I thought it might have been unrelated since it wasnt doing this when I had the issue with Xposed installer.
After yet another factory reset my phone seems to be fine, its still too early to tell though since its only been about a day. I had the normal google playstore and gvoice app crashing...Sigh..the only thing different was that sometime yesterday after the second factory reset a notification popup of unfortunately a sytem file stopped working came up. I acknowledged it, but thankfully I havent gotten any problems. I forgot what the notification read. hopefully its not related to what happened the other day.I dont know if this is related to one another, but I did notice that before I rooted my android system had automatically upgraded. I looked for issues like this on the net and saw people where having random bootloops after system upgrades and that unchecking scanning for wifi fixed the problem. though I did this and it did not work, thats why I did the second factory reset.
Now Im asking for help if any further issues arise. I love my Note3 and at this point I just want a reliable working device. Im keeping my fingers crossed and hopefully that will be the end of it, but in case it started to act up again, what can I do? any information and help is greatly appreciated. thanks.
Never uninstall any Xposed app that changes system files without first reverting any changes you made with it. Some of them are permanent until they are turned off in the App. Then you can disable the module.
You may want to look into this http://forum.xda-developers.com/showthread.php?t=2559715
I cannot stress this enough.
READ READ READ.
Too many times have I seen someone read a line or 2 then rush right in ultimately turning their very nice phone into the most expensive paperweight one could own.
On that link I posted, read it until your eyes are bleeding if you truly need to start from scratch.
I am not joking here.
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
Thanks man. it makes sense. I will look into it. you mentioned read. I have read what I thought was plenty, but always ideas and opinions differ, sometimes knowing too much and causing what they say decision paralysis. Because I still read about the Xposed experiences and different people go about it in a different way. but what you mentioned about reverting back makes alot of sense.