Related
I have an old Fascinate that is no longer in service that I'd like to give to my kids for games and geocaching.
Is there any way to permanently disable the phone/3G data features, or is there a custom ROM with these features removed?
I've tried googling around and found some ROMs for this, but nothing specifically for the Fascinate.
mbellot said:
I have an old Fascinate that is no longer in service that I'd like to give to my kids for games and geocaching.
Is there any way to permanently disable the phone/3G data features, or is there a custom ROM with these features removed?
I've tried googling around and found some ROMs for this, but nothing specifically for the Fascinate.
Click to expand...
Click to collapse
Id say start with THS Build 14, and delete Phone.apk, TelephonyProvider.apk, MMS.apk, and Contacts.apk. Id say that's it if its deactivated, because then they cant call and accidentally activate it somehow.
Take a look at the GeeWiz thread in the development section. DJP has a version of the ROM specifically designed for what you are trying to do.
Good luck.
Sent from my TeamDRH ICS for GTablet using XDA
Thanks to both of you.
I'll give GeeWiz a look, it's cool that someone is actually developing a ROM to utilize unused but otherwise great phones.
Short term I may try a variation on Cookiemonster's suggestion since the phone has CM7.2 on it now and removing those apks might be simpler than a complete wipe and rebuild.
:good:
Using Samsung Galaxy Note from Tmobile, the SGH-T879, a.k.a SGH-i717, Android version 4.0.4, Rooted
About me: I am not a developer or programmer; but, I am savvy enough to manipulate/configure Windows computers, remove malicious software and generally troubleshoot many common problems on a PC.
What I need to do: I need to record cell phone conversations at the line level (not speakerphone) and am beginning to believe that isn't possible on Android 4.0.4. Someone told me I might need a custom ROM that allows line recording. I don't understand ROM and its relation to the phone as well as I do Windows OS and its relation to the Computer; but, I want to learn so I can solve this call recording problem.
Can someone point me in the right direction for learning about this?
Sir, there are apps free from the GPlay Market for this...take a look, although you have to be rooted for some apps but you stated you are rooted.
A custom ROM is not needed.
Again, do a search via mighty Google and see any thing points you to the Market GPlay.
google voice has this built in. just press 4 while in call.
bigjoe2675 said:
Sir, there are apps free from the GPlay Market for this...take a look, although you have to be rooted for some apps but you stated you are rooted.
A custom ROM is not needed.
Again, do a search via mighty Google and see any thing points you to the Market GPlay.
Click to expand...
Click to collapse
Thanks for the reply.
I have been working on this problem for two weeks+, have tried many call recording programs and had exchanges with their tech support. NONE will record from line on this phone. Their final answer is to just use speakerphone. I have had exchanges with others and found that not one has reported a successful LINE level recording with stock Android versions above 2.3.5. I have also read in forums where some were able to record but it broke when their Android versions were upgraded or they got a newer phone with a later Android version.
The recording programs offered on Google are, in my opinion, misnamed voice recorders as they record only when the phone is on speaker.
Please, is there a good place on the 'net where I can learn about ROMs?.
google voice has this built in. just press 4 while in call.
Click to expand...
Click to collapse
Thanks, but I don't use Google. I want something that runs entirely within the phone.
Alex Ethridge said:
Thanks for the reply.
I have been working on this problem for two weeks+, have tried many call recording programs and had exchanges with their tech support. NONE will record from line on this phone. Their final answer is to just use speakerphone. I have had exchanges with others and found that not one has reported a successful LINE level recording with stock Android versions above 2.3.5. I have also read in forums where some were able to record but it broke when their Android versions were upgraded or they got a newer phone with a later Android version.
The recording programs offered on Google are, in my opinion, misnamed voice recorders as they record only when the phone is on speaker.
Please, is there a good place on the 'net where I can learn about ROMs?.Thanks, but I don't use Google. I want something that runs entirely within the phone.
Click to expand...
Click to collapse
First read the thread linked below at least twice for help on understanding how to flash custom ROM builds etc.. Reading it twice will help make sure you grasp everything well prior to flashing your Note.
[Road & Ref Map]: Galaxy Note Super Everything Thread (I717) 9/11/2012: http://forum.xda-developers.com/showthread.php?t=1740367
Moreover, once you understand the steps needed in order to load different ROM builds etc.., below is a link to an excellent Gingerbread 2.3.6 XLA2 ROM by DAGr8 that has the line recording built in. That said, I still use it as my "go to" ROM when not trying out ICS & JB builds, due to the built in line recording, as well as the ability to enable Ad-Hoc WiFi support by switching out the wpa_supplicant file.
[ROM]XLA2[04/02] SAUROM Projekt 'One Rom to Rule Them All: http://forum.xda-developers.com/showthread.php?t=1522942
Also, if you do load SAUROM RC7 + RC7.1, search this thread link below for support in order to fix the alarm force close issue, and to add "Equalizer" from the play store to increase volume.
http://forum.xda-developers.com/showthread.php?t=1525341
On a final note, deploy the xda search feature to find more tips & info...
Hope this helps a little...
Best to all,
R
Thanks so very much for the reply. This will get me started.
Alex Ethridge said:
Thanks so very much for the reply. This will get me started.
Click to expand...
Click to collapse
Hey Alex, don't thank me, d'oh! I somehow skipped right past your first OP post. If you have a Samsung Galaxy Note from T-Mobile, "the SGH-T879 model", and not the SGH-I717 model from At&t, SAUROM may not work as intended, and you should post in T-Mobile Galaxy Note section, not here. That said, I'm not sure what would be best for the T-Mobile Note as far as line recording, but you should post and search in that specific sub-forum for help.
Best to all,
R
Yes, it is the T879 and thanks for the heads-up.
I don't see a T879 or T-mobile Galaxy Note section here. Where is it?
Thanks.
It isn't here - its an altogether different forum. Just go to the main list of supported phones and find it there.
Hello, I have been a member for a while, but mostly read, do not post on this site so I cant post in the development section yet. I have an EVO3d I am trying new JB Roms on to find a new cool rom , but every one I find I am having an issue here and there. I recently updated my Kernel to a different kernel, and that fixed some of the issues.
I am trying Paranoid Andriod JB and got everything to work, but receiving SMS messages. I cant find the setting for changing the Proxy like suggested in one post I read. Could someone point me in the right direction? Sorry if this is posted, I searched but was unable to find it for the Sprint Evo 3d. I found something for Cricket, Called APN manager. Would the settings be the same except for the mycricket inputs be sprint instead?
Any one know any other ROMs to try that are cool and customizable for JB?
Thanks for all you developers do, Love ALL of the work!
Chris
Hello, first and foremost I know where you are coming from. I've been playing around with jb ROMs for weeks now. You are using paranoid jb correct? The problem you are having is the developer ported this ROM over from another device meant for another carrier and thus the APN settings are not coded for sprint correctly. Generally, ROMs built from source typically have MMS and texting working specifically for that device. While no ROM is best and due to moderator preference we cannot have opinion threads on which is best. However I can point your to a few ROMs that have those things working. You can try gangnam style, king kang, unofficial jb aokp. Hope this helps.
Looks like CM11 is having APN issues related to MMS after the 3/3 nightly build. I am unable to send MMS with the stock messenger. 8sms does send MMS but returns the error: "No APN specified on the device"
Has anyone found a work around for this?
abunchofidiots said:
Looks like CM11 is having APN issues related to MMS after the 3/3 nightly build. I am unable to send MMS with the stock messenger. 8sms does send MMS but returns the error: "No APN specified on the device"
Has anyone found a work around for this?
Click to expand...
Click to collapse
Yeah my fix was to go back to a Samsung build. I'm tired of this crap.
Sent from my SCH-I605 using Tapatalk
abunchofidiots said:
Looks like CM11 is having APN issues related to MMS after the 3/3 nightly build. I am unable to send MMS with the stock messenger. 8sms does send MMS but returns the error: "No APN specified on the device"
Has anyone found a work around for this?
Click to expand...
Click to collapse
You are experiencing what appears to be a rather widespread issue with the newly released AOSP roms. Apparantly there is an issue with SMS not sending for some users and MMS not sending for many users. I posted the following in the Pac-Rom thread in an attempt to aggregate the information I gathered in one location:
fujimoh said:
I posted previously that I was having an issue with SMS messages not sending. I can usually send one or two messages when I first boot up the phone, but after that the message just hangs on "SENDING..." and then gives an error that it was not sent. I posted this problem in the general troubleshooting section http://forum.xda-developers.com/showthread.php?t=2672724 and received the following response: "Known Verizon issue. Call them or hang tight. This is not a rom issue. If you need texting until it's fixed go back to TW."
Additionally, many people with this problem seem to be located in the Central PA area, as is indicated in this thread http://forum.xda-developers.com/showthread.php?t=2662658 and discussed on the Verizon Community Support forums. I am not located in PA but my area code is central PA since I never changed it when I moved.
I spoke with a Verizon rep via their Live Chat feature and the rep stated the following:
Verizon Rep: Interesting, ok thank you for that information [SMS not sending]. I checked with Sasmung [sic] and confirmed it's not a known issue but we definitely want your phone to work as it should.
Verizon Rep: Ok, I did see that report [issues with SMS in Central PA area] on the forum as well. With Samsung not reporting it all it means is it's not a widespread issue. Nonetheless, with you doing the reset already we'll want to look at replacing the unit.
I am not really interested in purchasing a new phone, so I politely declined that alternative. However it would appear that the Verizon network is working normally, and the responses show that this issue is isolated to AOSP roms as the above user stated they had no issue on a TW rom. The SMS/MMS issue is also discussed in the CM11 nighly thread, with people stating they are having similar problems. I am not really interested in flashing a TW rom and going through the set-up process just to flash back to PAC and redo the setup process once this issue is corrected. So, I'll just be monitoring this and other threads for a new nightlie or a fix.
Click to expand...
Click to collapse
I received this rather snarky reply from another user who claims to know what is going on.
DreamFX said:
It is a known Verizon network issue. There is people way above the front line staff working on it. They don't tell the front line staff this because since it's just limited to aosp and they only support stock, unrooted phones they tell people there is no issue. They could send you ten replacements phones and they all will do the same thing. It's not the phone, it's not the AOSP rom, and it's not your sim card. It's a bizzare issue that makes all aosp roms ever made not work in certain areas, mostly central pa but others as well. There is no need to post on multiple threads about an issue that you had already been given an answer for. It's being worked on. There is nothing the pac team can do for this. There is another xda user working directly with the engineers providing me updates. I will let you know when we find out a resolution.
Click to expand...
Click to collapse
It's likely not the answer your looking for, but hopefully it provides some insight for you into the issue and saves you time having to pour through search results. It appears that TW roms are not having any issues, so for now the 'fix' would appear to be using one of them.
fujimoh said:
You are experiencing what appears to be a rather widespread issue with the newly released AOSP roms. Apparantly there is an issue with SMS not sending for some users and MMS not sending for many users. I posted the following in the Pac-Rom thread in an attempt to aggregate the information I gathered in one location:
I received this rather snarky reply from another user who claims to know what is going on.
It's likely not the answer your looking for, but hopefully it provides some insight for you into the issue and saves you time having to pour through search results. It appears that TW roms are not having any issues, so for now the 'fix' would appear to be using one of them.
Click to expand...
Click to collapse
I just use the 3-2-14 build myself. I have had a lot of problems from all of the other CM11 builds.
Flipapotimus said:
I just use the 3-2-14 build myself. I have had a lot of problems from all of the other CM11 builds.
Click to expand...
Click to collapse
The 3/3 build still worked for me. Also 8SMS is a workaround for the APN issue for the time being.
I have considered going back to a TW rom in order to get MHL_or_ Miracast / Wi-Fi Direct working. These just don't seem to work in CM11.
abunchofidiots said:
The 3/3 build still worked for me. Also 8SMS is a workaround for the APN issue for the time being.
I have considered going back to a TW rom in order to get MHL_or_ Miracast / Wi-Fi Direct working. These just don't seem to work in CM11.
Click to expand...
Click to collapse
I will definitely try some TW 4.4 ROM's. I don't know that I will try any until then. I definitely will not move off of this 3-2 build until this mess is fixed.
The latest nightly seems to have fixed the APN issue. No to wait for the Wi-Fi Direct and Miracast to get fixed.
Everytime im using a custom rom, i cant use spotify properly. It crashes randomly, playback stops etc.
tried cyanogenmod, slimbean and slimkat.
Or is there an fix for this issue?
thanks
Run stock (dual boot ??)/
why would i use dual boot if i want a clean rom an use spotify as one of my main apps?
Because fu*king app developers (regular ones, like the ones who develop apps like Spotify) don't have fu*king users of custom roms on their radar. They're only fu*king interested in the 99.99% of phone users who use their phone in a fu*king 'regular' manner. They don't fu*king care whether their apps work with custom roms or not. It doesn't make one fu*king iota of difference to their business whether their app works for you with your fu*king custom rom setup or not.
Now...
You can either fu*king accept that, or you can gnash your teeth & cry about it. I gave you a suggestion based on similar frustrations I have experienced with many apps over the past couple of yrs when I've been running custom roms.
The bottom line is, if you want every app to work guaranteed, run a fu*king stock rom or custom rom that is Samsung-based with minimal deviations from stock. If you want to run fu*king AOSP roms, expect many 'vanilla' apps not to work
If this app is that important to you, you know what to do. Also, did it not fu*king occur to you to ask the developers of the fu*king roms in question whether there is any chance of them implementing something on the rom side which may make the app in question work, or even ask the fu*king users of the fu*king roms in question (in the rom threads) whether any of them have been able to figure out a fu*king workaround ?
Given the minimal fu*king traffic we get in Q&A these days, asking a specific question like that you've got f*ck all chance of getting an answer which might help you get a solution. You're far more likely to get that (if a solution is possible, that is) by going 'straight to the source' (I.E the fu*king rom thread), as it were.
See ? I can use fu*king/f*ck/etc in my post too. Thing is, it makes me look just as big an idiot as you looked using it in your post
Edit - Also, did it not occur to you that perhaps a simple build.prop edit might be a way around this, assuming the issue is simply a case of the app reading the build.prop, seeing it's not stock & barfing (it may not be this also, but it's worth trying or finding out if the app checks this) ? If you don't know how/what to edit, that info is easily found by searching here/elsewhere.