Develop Bugs

[Q] why does my n64oid keep crashing?

Upon loading any ROM, the app crashes. I'm using the newest version, 2.5

I remember reading that people were having issues with emulators crashing on this phone. I remember someone saying that if you disable the sound it won't crash. When I say that I mean disable it from within the emulator settings.
Sent from my SPH-D710 using xda premium

I have the same update, though i don't have any crashes, just some lag.
Oh i Get you now, its when Upon clicking a rom to load is when it crashes?
Try to clear any Data from the App, and try again, if not check your settings.
I haven't ran into this problems myself, the roms can be either .zip or v64 "if i remember correctly their unzipped form" .rar or anything else won't work i believe.
make sure the Rom works in a PC emulator, because if not, then thats probably the problem you have.

Already several threads actively open about this subject...just do a search.

Hmm... I was having an issue like that with Yoshi Story too. My fix was to download another ROM.
I'm not having any issues like that. (Running Rooted Stock).
The games should be running smoothly. I have the latest 64oid as well. Like I stated earlier, only my Yoshi Story ROM was messing up. It could be you've downloaded a whole lot of bad ROMs. Probably unlikely but could happen.
If you download the ROM again, try and make sure it's from a different source. Just a thought.

I can run it fine on the stock rom but it appears the app doesnt work well with Calkulin's rom

Need build.prop from recent stock

So... I have been on a custom ROM for a while now. The ROM I have been using is great... unfortunately... I have been having constant problems on the market. Currently, I can go to the market on the web and it still lists my device from when it had the latest stock version. My issue is that now it is showing a TON of apps that are incompatible which is complete BS. I was able to get some of the APKs and had some from a titanium backup I had done previously... and they all work perfectly fine.
I did a wipe of market data and removed my account on my phone. I then rebooted, added my account, and started up the market. This fixed about half of the apps... but I still have a ton of apps showing incompatible.
To try and track down this issue... can someone post a build.prop from the latest stock build? I want to try some modifications to my build.prop to try and fix the issue. Currently, I am on the King Kang ROM (AOKP+Paranoid)
EDIT: Was able to restore my device ID from a backup from when I was running stock. I am now able to install things... though it worries me that the problem could re-occur as with its normal configuration it would prevent installation of some applications.

Goblinlord said:
So... I have been on a custom ROM for a while now. The ROM I have been using is great... unfortunately... I have been having constant problems on the market. Currently, I can go to the market on the web and it still lists my device from when it had the latest stock version. My issue is that now it is showing a TON of apps that are incompatible which is complete BS. I was able to get some of the APKs and had some from a titanium backup I had done previously... and they all work perfectly fine.
I did a wipe of market data and removed my account on my phone. I then rebooted, added my account, and started up the market. This fixed about half of the apps... but I still have a ton of apps showing incompatible.
To try and track down this issue... can someone post a build.prop from the latest stock build? I want to try some modifications to my build.prop to try and fix the issue. Currently, I am on the King Kang ROM (AOKP+Paranoid)
EDIT: Was able to restore my device ID from a backup from when I was running stock. I am now able to install things... though it worries me that the problem could re-occur as with its normal configuration it would prevent installation of some applications.
Click to expand...
Click to collapse
Did you ever change the DPI on your phone? That will make installing things from the market impossible unless you have a modded market.
Sent from my SPH-D710 using xda app-developers app

however it was set on this ROM is where it was initially and had problems. I changed with Paranoid but other than that no. After changing with Paranoid I can still DL most apps. Though... the DPI is pretty jacked immediately after flashing... its all set at like 320 default which is too large for almost anything. I have set it down to 200. Even though I still have it at 200 after restoring a device ID I can now install stuff again for now though.

Cyanogenmod help

I've looked through the forums for hours now and according to the noob video made by xda. I'm asking for help. I have an at&t Samsung galaxy s3 with the CyanogenMod installed (as the title implies) and to be honest its not worth the hastle. I'm having problems left and right. First off, the camera app that comes with the phone is missing. Or if theres a custom one. Its not included. I'm aware that I can find and install an external apk but I'll get to the problem with that in a bit. I followed very detailed instructions on installing the cyanogenmod and gapps and everything was fine (stable version) but the notifications suggested I update the mod so I did. Now I have the camera but my play store will not work. It opens for a split second then closes. Also, the file manager is gone. So I downloaded multiple file managers and it seems after first use that they can no longer open anything. I can't even access the files. I checked the superuser allowed and disallowed apps and everything seems fine. Now with the apk problem. Almost any apk I download will not install on my phone. Sorry for the erratic problems just jumbled everywhere in this post but I'm using my phone to write this so its a bit difficult to organize. Any feedback would greatly be appreciated. A link to a post already like this (which I couldn't find) or a link to a tutorial maybe or troubleshooting these problems. I will delete this post as soon as I find a solution so I don't use up space on the forums with a somewhat personal problem. Thanks in advance!
Using AT&T SAMSUNG Galaxy S3-SGH-I747

GoLordNibbler said:
I've looked through the forums for hours now and according to the noob video made by xda. I'm asking for help. I have an at&t Samsung galaxy s3 with the CyanogenMod installed (as the title implies) and to be honest its not worth the hastle. I'm having problems left and right. First off, the camera app that comes with the phone is missing. Or if theres a custom one. Its not included. I'm aware that I can find and install an external apk but I'll get to the problem with that in a bit. I followed very detailed instructions on installing the cyanogenmod and gapps and everything was fine (stable version) but the notifications suggested I update the mod so I did. Now I have the camera but my play store will not work. It opens for a split second then closes. Also, the file manager is gone. So I downloaded multiple file managers and it seems after first use that they can no longer open anything. I can't even access the files. I checked the superuser allowed and disallowed apps and everything seems fine. Now with the apk problem. Almost any apk I download will not install on my phone. Sorry for the erratic problems just jumbled everywhere in this post but I'm using my phone to write this so its a bit difficult to organize. Any feedback would greatly be appreciated. A link to a post already like this (which I couldn't find) or a link to a tutorial maybe or troubleshooting these problems. I will delete this post as soon as I find a solution so I don't use up space on the forums with a somewhat personal problem. Thanks in advance!
Using AT&T SAMSUNG Galaxy S3-SGH-I747
Click to expand...
Click to collapse
Go in application settings and delete your play store's data/cache. That should fix it.
Without it, it's kinda hard to install apps unless you sideload. If you do sideload, you need to allow it in your settings (security I believe).

if you're using the stable version of CM
you might have to go to Date & Time setting
and fix the date on there in order to make play store works
and everything you say about camera, it is weird indeed because not only CM, every rom out there should include a camera app
if that problem still exists for you, you might want to clean/wipe everything, from cache to system and then flash the rom again

Thank you guys. I tried wiping the cache and it still didn't work. I don't mind side loading which is what I've been doing but its not ideal. I can only search for the exact app(s) I want rather than exploring via play store. Also, you guys didn't mention the problem with the file managers not working after first try. If you have any feedback it'd be great. I would like to keep the cyanogenmod but its just not worth the time and effort (opinion). If I can't fix the problem or find a solution I'll just go back to my phones stock UI because even though I think flashing ROMs is awesome. It really isn't worth frustrating myself with something that's an option and not a necessity. Thanks in advance for feedback.
Sent from my SAMSUNG-SGH-I747

Have you tried a factory reset?

GoLordNibbler said:
Thank you guys. I tried wiping the cache and it still didn't work. I don't mind side loading which is what I've been doing but its not ideal. I can only search for the exact app(s) I want rather than exploring via play store. Also, you guys didn't mention the problem with the file managers not working after first try. If you have any feedback it'd be great. I would like to keep the cyanogenmod but its just not worth the time and effort (opinion). If I can't fix the problem or find a solution I'll just go back to my phones stock UI because even though I think flashing ROMs is awesome. It really isn't worth frustrating myself with something that's an option and not a necessity. Thanks in advance for feedback.
Sent from my SAMSUNG-SGH-I747
Click to expand...
Click to collapse
the file manager part is really weird.
if you clean install, especially the stable version, everything should works just fine
however, it sounds like bad install though
how about this this
Download Titanium Backup and wipe data + cache for file manager only and see if it works
if not, try the longer way
download stock att rom(4.1.1)
go to recovery, wipe everything
go to download mode
flash stock rom with odin
restart to recovery, wipe dalvik and cache
root the phone
Re-Download CM10 stable
go to recovery, wipe everything, including System
flash cm10
reboot and see if everything works

Yeah I've tried a factory reset. It only deleted my user data not really resetting the phone. Thank you pcchano (sorry if I got name wrong) I'll try and erase everything and reinstall from scratch but its not my first time using custom ROMs so I'm sure I did it right but I'll give it a go. Also, someone told me that I need to completely wipe any data associated with Google wallet before I root or else play store will not work. Has anyone tried out this theory or know anything about it? It doesn't make sense to me seeing as wallet is saved server side beside the basic user data stored on the phone. But please let me know. You guys are all very helpful thanks for the feedback.
Sent from my SAMSUNG-SGH-I747

Also, I've never had to wipe dalvik before? Could that be my problem? I also noticed that when I updated cm the info panel said 'experimental' even though I chose the stable version to start with? Could some of these problems be associated with cm rather than blaming it on my phone? Thanks in advance for any feedback.
Sent from my SAMSUNG-SGH-I747

GoLordNibbler said:
Also, I've never had to wipe dalvik before? Could that be my problem? I also noticed that when I updated cm the info panel said 'experimental' even though I chose the stable version to start with? Could some of these problems be associated with cm rather than blaming it on my phone? Thanks in advance for any feedback.
Sent from my SAMSUNG-SGH-I747
Click to expand...
Click to collapse
i have like 2 s3 using CM10 stable version and no problem with it (other than the play store wouldn't connect due to the date in setting wasn't correct) while I myself am using CM10.1 and other than the bugs that come with CM10.1 or google source code, it is a functional rom
so i would rather say, it is your phone
and you should always wipe dalvik cache along with cache partition before flashing new rom.

OK pcshano thanks very much. I'll just erase everything and start from scratch. Thanks everyone who helped me. This forum and you people are awesome. I'll delete this post as soon as I reinstall the ROM to make sure it worked. Thanks again!
Sent from my SAMSUNG-SGH-I747

The stable cm is of the 10 variety. The experimental builds are 10.1 if I'm not mistaken. In which case you should only need to flash the appropriate gapps package to get the play store functioning and camera as well. The file manager issue I don't know beyond the external sd card being a bit sketchy on 4.2 builds. Are you using an external sd card? Start with a fresh flash of 10.1 if you want to go with that, flash a 4.2 gapps zip and see what happens from there.
Sent from my SAMSUNG-SGH-I747 using xda premium

[Q] Bluetooth and external SD issues platform.xml

I have the Samsung Galaxy S3 with Wind Mobile. Recently Updated to 4.4.2 and rooted with Towel Root. Everything was good until TitaniumBu couldn't access the externalSD card.
I tried using a couple of xposed modules (Handle External Storage & then KitKat SD Card Full Access), but they didn't allow Titanium to access the SD card either.
So I tried the manual method of modifying platform.xml (also changed permissions on the modified file) but I have the same issue as some other people I've read about (bluetooth stopped working, whatsapp crashed, maps, youtube, play store, titanium backup, touchpal keyboard, web browsing all stopped working). Also when I connect my phone to my PC, the phone and the sd are shown as empty.
I tried copying back the original platform.xml that I had saved and still no luck.
I'm not worried about the titanium accessing the sd card right now. I'm just trying to get the apps and bluetooth working. Anybody have any other ideas?

Try ktoonsez' kt747 kernel.

Thanks
DocHoliday77 said:
Try ktoonsez' kt747 kernel.
Click to expand...
Click to collapse
Thanks for the info Doc, but I'm not too confident flashing kernels (never done it) so I ended up wiping everything and starting from scratch. I installed? kitkat 4.2.2 and then rooted again with towelroot.
I then installed SD fix and TWRP, but the funny thing is that when I restarted my phone, I no longer had wifi.I tried a few things that I found in XDA and on other websites, but I couldn't get wifi back.
So then I redid everything again. Kit Kit & towel root, but no TWRP, no external sd fixes, and I am able to use my phone. The problem for me is that my apps have no access to the extSD and I can't do a back up without that access. I'm thinking that the extsd fixes that i have tried over the last few days mess something up with my phone. Or maybe towel root & the fixes are not good together? Maybe I should have used Root 66 like I used before?
I don't want to risk messing anything up right now, so I'm just going to wait around, and see if anyone else runs into my problems.
Thanks again.

Towelroot, or any other root method shouldn't have any effect on the actual operation of the device. What is happening is there are new seLinux security enhancements built in to kk. Apps can now only read/write to folders they create/own. If another app created the folder, or if it was created by the owning app before the new security was implemented, seLinux will not allow that app to use it. More and more people are having problems even after the platform.xml edit which makes me believe its got to be done before flashing, or a factory reset may be needed. Im not sure on that right now.
The platform.xml edit is only for the external sdcard btw. You have to disable seLinux to solve this on the internal one. (Looks like this may also be true for external now, but like I said, im not sure about that yet)
There's an app in the store, I think its called sdfix, or sdfixer or something similar (search seLinux mode changer) that people have had some success with, so try that first.
Alternatively, I can mod the stock kernel to disable seLinux there. (May do this today anyway).
It's perfectly fine if you're not comfortable flashing kernels, but its really nothing to be too worried over. A custom one like ktoonsez kt747, will flash and run normally, and you have the option to learn more if you like so you can configure it how you want.
If you have any specific concerns about it, feel free to ask us. But in the end its up to you if you still want to refrain from flashing one.
Another thing you can try is to rename the apps folders, then reinstall it and let it recreate them. Then copy the contents of the old into the new. Not totally sure it would work as I expect, but in theory it should.
Anyway, if nothing else, try that app I mentioned. And let us know how ut goes!

Thanks Again
DocHoliday77 said:
Towelroot, or any other root method shouldn't have any effect on the actual operation of the device. What is happening is there are new seLinux security enhancements built in to kk. Apps can now only read/write to folders they create/own. If another app created the folder, or if it was created by the owning app before the new security was implemented, seLinux will not allow that app to use it. More and more people are having problems even after the platform.xml edit which makes me believe its got to be done before flashing, or a factory reset may be needed. Im not sure on that right now.
The platform.xml edit is only for the external sdcard btw. You have to disable seLinux to solve this on the internal one. (Looks like this may also be true for external now, but like I said, im not sure about that yet)
There's an app in the store, I think its called sdfix, or sdfixer or something similar (search seLinux mode changer) that people have had some success with, so try that first.
Alternatively, I can mod the stock kernel to disable seLinux there. (May do this today anyway).
It's perfectly fine if you're not comfortable flashing kernels, but its really nothing to be too worried over. A custom one like ktoonsez kt747, will flash and run normally, and you have the option to learn more if you like so you can configure it how you want.
If you have any specific concerns about it, feel free to ask us. But in the end its up to you if you still want to refrain from flashing one.
Another thing you can try is to rename the apps folders, then reinstall it and let it recreate them. Then copy the contents of the old into the new. Not totally sure it would work as I expect, but in theory it should.
Anyway, if nothing else, try that app I mentioned. And let us know how ut goes!
Click to expand...
Click to collapse
Thanks again for your response.
I tried sdfix and thats when my wifi got messed up.
I've spent 2 days getting my phone almost back to where it was before, so I think I'll wait a few days/weeks before I mess with it again.
Thanks for the explanation, but sooner or later I think I will try the ktoonsez kt747.
I'll update here whenever I try something.
Thanks again. Your help is appreciated.

DocHoliday77 said:
Towelroot, or any other root method shouldn't have any effect on the actual operation of the device. What is happening is there are new seLinux security enhancements built in to kk. Apps can now only read/write to folders they create/own. If another app created the folder, or if it was created by the owning app before the new security was implemented, seLinux will not allow that app to use it. More and more people are having problems even after the platform.xml edit which makes me believe its got to be done before flashing, or a factory reset may be needed. Im not sure on that right now.
The platform.xml edit is only for the external sdcard btw. You have to disable seLinux to solve this on the internal one. (Looks like this may also be true for external now, but like I said, im not sure about that yet)
There's an app in the store, I think its called sdfix, or sdfixer or something similar (search seLinux mode changer) that people have had some success with, so try that first.
Alternatively, I can mod the stock kernel to disable seLinux there. (May do this today anyway).
It's perfectly fine if you're not comfortable flashing kernels, but its really nothing to be too worried over. A custom one like ktoonsez kt747, will flash and run normally, and you have the option to learn more if you like so you can configure it how you want.
If you have any specific concerns about it, feel free to ask us. But in the end its up to you if you still want to refrain from flashing one.
Another thing you can try is to rename the apps folders, then reinstall it and let it recreate them. Then copy the contents of the old into the new. Not totally sure it would work as I expect, but in theory it should.
Anyway, if nothing else, try that app I mentioned. And let us know how ut goes!
Click to expand...
Click to collapse
FYI Doc. I tried the updated KitKat SD Card Full Access (version 1.2) Xposed module that came out today. It worked, and now Titanium can back up to my external SD card. Finally.

Thanks for letting us know! I don't use xposed so wouldn't have known about it otherwise. Still, I am sorry you had so much trouble with all of this and that I couldn't help you better. Glad to hear you finally got it sorted out though!

Thanks Doc
DocHoliday77 said:
Thanks for letting us know! I don't use xposed so wouldn't have known about it otherwise. Still, I am sorry you had so much trouble with all of this and that I couldn't help you better. Glad to hear you finally got it sorted out though!
Click to expand...
Click to collapse
No worries. I browse XDA a lot, and I see your answers, and they're always helpful. I appreciate all your help.

[Q] reboot manager

Hi all, I am certain others are having this problem, but I couldn't find any threads about it.
Does anyone know how to get a reboot widget to work? I used to keep Quick Reboot on my home screen just to have easy access to recovery and other stuff. Since the Lollipop update, none of the reboot managers on the play store work.
Anyone know of a work around or alternative?

Is your phone rooted, from what i understand the app you're referring to or any like it requires it. If you are rooted most any custom rom will have the boot menu your looking for just not as a widget.

Holo Reboot works for me on OB7.
https://play.google.com/store/apps/details?id=com.scartech.holoreboot
It has a dark and bright widget.
Sent from my SM-N910P using Tapatalk

samep said:
Holo Reboot works for me on OB7.
https://play.google.com/store/apps/details?id=com.scartech.holoreboot
It has a dark and bright widget.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Dang, it doesn't work for me. It asks for root privileges and I grant them, then says your phone will reboot....but never does. It behaves the same way all reboot managers do, just bombs out.
It has been like this on every ROM I've used (Noterized, Alliance), including stock. WTF?? Are you certain it is rebooting your Note when you ask it to?
Even apps Like Synapse that came with my ROM cannot reboot. The Xposed module reboot function fails too. Like I said, it isn't specific to this ROM, it has always been like this for me on the NOTE 4.

pinetreehater said:
Dang, it doesn't work for me. It asks for root privileges and I grant them, then says your phone will reboot....but never does. It behaves the same way all reboot managers do, just bombs out.
It has been like this on every ROM I've used (Noterized, Alliance), including stock. WTF?? Are you certain it is rebooting your Note when you ask it to?
Even apps Like Synapse that came with my ROM cannot reboot. The Xposed module reboot function fails too. Like I said, it isn't specific to this ROM, it has always been like this for me on the NOTE 4.
Click to expand...
Click to collapse
I was using it with rooted OB7 stock using beta 2.49 SuperSU apk. Just flashed a custom ROM that uses 2.46 and does just as you say.
Try the beta 2.49. It was made for the lollipop kernel enforcing vs permissive mode issue.
http://forum.xda-developers.com/showpost.php?p=55256620&postcount=1 Shouldn't be beta, IMO.
Edit: that didn't fix it on custom ROM for me either. I'll look deeper into this.
Sent from my SM-N910P using Tapatalk

samep said:
I was using it with rooted OB7 stock using beta 2.49 SuperSU apk. Just flashed a custom ROM that uses 2.46 and does just as you say.
Try the beta 2.49. It was made for the lollipop kernel enforcing vs permissive mode issue.
http://forum.xda-developers.com/showpost.php?p=55256620&postcount=1 Shouldn't be beta, IMO.
Edit: that didn't fix it on custom ROM for me either. I'll look deeper into this.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
I have found that applications that issue a reboot command(like xposed), also fail to result in a reboot. However, interestingly enough, I just noticed that the reboot command from within Titanium works (it is inside the menu list).
Sometimes I notice when I try to reboot with a app, a toast message comes on a says "Reboot:Null" or "that function doesn't exist (or something like that)" as if that command functionality doesn't exist on the Note 4. I know it isn't a Lollipop issue, because my wife's G2 has Lollipop and Quickboot works flawlessly.
When Titanium successfully rebooted, it flashed a toast message (the first time). I didn't have a chance to read it all, it was long. But it seems to be using another method to initiate a reboot. Dunno, I am stumped.

pinetreehater said:
I have found that applications that issue a reboot command(like xposed), also fail to result in a reboot. However, interestingly enough, I just noticed that the reboot command from within Titanium works (it is inside the menu list).
Sometimes I notice when I try to reboot with a app, a toast message comes on a says "Reboot:Null" or "that function doesn't exist (or something like that)" as if that command functionality doesn't exist on the Note 4. I know it isn't a Lollipop issue, because my wife's G2 has Lollipop and Quickboot works flawlessly.
When Titanium successfully rebooted, it flashed a toast message (the first time). I didn't have a chance to read it all, it was long. But it seems to be using another method to initiate a reboot. Dunno, I am stumped.
Click to expand...
Click to collapse
I got some ideas just slow going setting up a fresh ROM. For stock, I had a highly customized setup, look and feel but everyone's preferences are not alike so I can't complain. Even with Titanium and TWRP tar to pull from, I had system customized too. I've got apps and lib folder to edit; some to copy over and some to delete. Keyboards have got to go; back to custom Swype with top number row and directional left right arrows. There's always the nandroid to restore but I'll try to set this up for a backup.
I'll chime in if I figure it out. Maybe just a matter of time. Not out of ideas yet. If someone has a solution, chime in.
Sent from my SM-N910P using Tapatalk