yashsingh1/xdaforums huggingface dataset:
[General Topics] Joe Pinball:
I upgraded my Alpine Radio stack from the stock O2's version of 1.00 to the recommended one of 1.04, and it outperforms my mobile (Sony-Ericsson t68i) in terms of reception strength and voice clarity & quality (both ways)

So I'd say, go ahead and flash your radio: I am sure there are links to find out how to make a complete backup of your existing ROMS onto an SD card, so you could always 'revert to original' if for some reason the upgrade failed or the radio got worse.

Joe

P.S. as far as I know, if you wish you can just reflash the radio stack on it's own, leaving the extended & WM roms intact.
[Android Q&A, Help & Troubleshooting] Anre9:
So here's the story : as my E-boda Impresspeed e1 tab has only 512 mb ram i tried to use switchme app to create a second account and use titanium backup to block some apps as it uses 300 mb of that ram. So i got the app and created two accounts as described here http://xdaforums.com/showthread.php?t=2463270 . I switched to the second account but it has no internary memory to install other apps and the switchme app isn't there and now i can't go back. I tried flashing the nandroid backup i have but the my recovery is stock and i can't flash it. There is no recovery for my tab . I also tried formating from the stock recovery and settings but it just starts in an account like this with 34 mb internal memory all used. So i can't install anything and i am stuck in this account.Help me pls :(
[Verizon Samsung Galaxy S 4] Tada10:
Took OTA from MJ7. Lost root and re rooted with Vroot. :)

I know some don't like it. Just saying it works.

Sent from my Galaxy S4
[Verizon Samsung Galaxy S 4] tech_head:
The people that make that software claim to be a real company.

The website points to other ROM and unlock related services.

Still don't know how much I trust the method.

One thing remains though, if you don't tell what the hole is, they can't plug it.

So far, they haven't disclosed the hole and Samsung and VZW, at least didn't plug it with this latest release.

I'm still not upgrading to MJ7 so for me this isn't an issue.
[Verizon Samsung Galaxy S 4] trook:
I trust it, I used it a while back and the Chinese haven't taken over my phone yet...
[Verizon Samsung Galaxy S 4] GHMTQD:
I hate to say "what are they hiding" but how much extra time could it take Samsung to reverse-engineer Vroot? A whole workday? I'm sure it's a genuine part of the Vroot's team's ethos, I just don't think it holds that much water.
[Verizon Samsung Galaxy S 4] DRELUXOID:
There's a better root method that works for MJ7 and MK2.

http://xdaforums.com/showthread.php?t=2565758
[Verizon Samsung Galaxy S 4] Sir_Eagle:
Not really better just another method. And most around here will say safer.
[Verizon Samsung Galaxy S 4] tech_head:
But now, I can move to MJ7 if I like.

I refused to use *Root.
[Verizon Samsung Galaxy S 4] dougeefresh:
Thanks.
[Verizon Samsung Galaxy S 4] ddemlong:
I just updated by OTA, kept root, I am happy.
[Verizon Samsung Galaxy S 4] technich:
You didn't use root keeper or anything? You were successfully able to keep root just by taking ota?
[Verizon Samsung Galaxy S 4] Jaeson2308:
Did you use rootkeeper or anything other then just taking the ota?

using my GS4 MJ7 Vroot
[Verizon Samsung Galaxy S 4] xxxtncxxx:
I am going to say he is talking about the OTA from MJ7 > MK2, not from Mxx > MJ7 and yes this root method works for MK2 also:

http://xdaforums.com/showthread.php?t=2565758

I also prefer this method, props to the dev for a job well done.

---------- Post added at 07:04 AM ---------- Previous post was at 06:59 AM ----------

If I was in your shoes I would odin flash MJ7, take the OTA, then use the root method previously stated. But I am not you, I also hate vroot so...
[Verizon Samsung Galaxy S 4] ddemlong:
Actually I have kept root since the begining taking OTAs. I use both SU Pro and Voodoo Root Keeper. I have only rooted the phone once and it was when I first got it.
[Verizon Samsung Galaxy S 4] Tada10:
Finally in the app store glad I stuck with Vroot. :)

Sent from my Galaxy S4
[Verizon Samsung Galaxy S 4] tech_head:
Glad it worked for you.

I waited and am plenty happy with the people here and used the 1 click "saferoot".

Saferoot Rocks!!!
[Verizon Samsung Galaxy S 4] k1mu:
That's great! Where's the source code for their technique? Does it now work with the network turned off? If not, why not?
[Verizon Samsung Galaxy S 4] technich:
Is it possible to Odin back versions? I have been under the impression, especially with mk2, that if you do so it hard bricks the device?
[Verizon Samsung Galaxy S 4] thunderbls:
Once you go forward or if you are already there Odin will not work backwards.
[Verizon Samsung Galaxy S 4] richii0207:
Their site explains why they don't post the source
[Verizon Samsung Galaxy S 4] technich:
Thanks, that's what I thought. And, since it's not unlocking the bootloader, safe strap will only be able to boot roms on the same kernel - in my case, mk2, right?
[Verizon Samsung Galaxy S 4] k1mu:
No, their site provides invalid excuses for why they don't post the source. They're using the same rooting technique from cubeundcube that Saferoot uses. It's known, it's in the wild, and it's being patched, so why not publish?

If a simple developer like me can figure out what they're doing, do you really think that Samsung can't?
[Verizon Samsung Galaxy S 4] SwiftLeeO:
I personally use Saferoot and I'd say that if what your saying about their company is true, that everyone might as well just use Saferoot because for one thing it's really simple, and another reason is that it doesn't set off the KNOX fuse that I've been reading about. Don't get me wrong, I've only had my phone for a little over a week, but I do my homework before I root a phone that has this high of a price tag. My opinion would be for everyone to use Saferoot&Disable_Knox and freeze the OTA updater until/if there is a method to unlock the bootloader for mk2 base. I'm not even a developer, that's just my opinion from what I've read.
[Galaxy S III Q&A, Help & Troubleshooting] anpho:
I have a problem. My volume up was not working very well for a while but it worked if you pressed it hard enough so I didn't go on about fixing it, because I was controlling volume within the settings. The problem got worse all the time and now it isn't working at all. And on top of that now my phone can't boot probably cause of some bad zip I was flashing while trying some mods for my rom (I am using Omega v51), and the phone stays on the omega droid walking screen and doesn't boot. Usually this would not be a problem because I would boot into recovery and reflash the rom, or wipe davlik and cache or fix permissions or whatever. But now with the volume up not working I can't go into recovery. I can't go into download mode either, to flash rom via odin, because, despite volume down button works ok, when you go into download mode you still have to press volume up to "continue".

Any other way to get into recovery or download mode without the use of volume rockers?

I even try with adb commands but they don't seem to work when the rom is booting...

PS. I don't think it's a problem of the volume rocker, rather it's a problem of the volume switch on the cable, because i removed the back panel and removed the volume button, and pressed the switch manually and it doesn't work either. I can order another cable from e-bay but it will take a while to arrive and in the meantime, I am stuck without a phone, so any help on getting in the recovery or download mode is appreciated.
[Galaxy S III Q&A, Help & Troubleshooting] JJEgan:
USB recovery jig for download mode . See multiple posts .
[Galaxy S III Q&A, Help & Troubleshooting] anpho:
Thanks for the answer. I thought of that but I don't have one and if i order one from e-bay it will take a while to arrive also. I am hoping for a solution that doesn't involve waiting that long
[Galaxy S III Q&A, Help & Troubleshooting] anpho:
Just un update. Finally i got into download mode and stayed in the screen where you need to press volume up to go into download mode, removed the volume up button and pressed the up switch with a screwdriver hoping that at least one time it will be pressed and go into download mode and finally i was able to do that. So i reflashed the rom via odin and it booted into the rom. now volume up still not working, but at least I have a working phone until the parts from e-bay arrive to replace the faulty button and/or switch :)

Thanks for the help.
[Galaxy S III Q&A, Help & Troubleshooting] limnaln:
I'm facing the same problem now. Thank you :)
[One (M7) Q&A, Help & Troubleshooting] S0wL:
I tried to root my htc one, i followed correctly all the steps , after I installed twrp 2.6.3.3 I reboot it and it got stucked in the boot screen.

I had stock rom on the phone.

How can I fix this problem. I already tried the trick with the flashlight and it did not work.
[One (M7) Q&A, Help & Troubleshooting] scifitrekkie:
What method did you use to root?
[One (M7) Q&A, Help & Troubleshooting] S0wL:
I used One_All-In-One_Kit_v
[One (M7) Q&A, Help & Troubleshooting] Guich:
Try another time the trick with the light, should work.

However, when your phone can boot in bootloader, reflash the recovery and do an erase cache :)
[One (M7) Q&A, Help & Troubleshooting] S0wL:
I left the phone like this until the battery drain and then I let it to charge a bit. Now i managed to get into bootloader
[One (M7) Q&A, Help & Troubleshooting] Guich:
Good, now you've only to re-flash the recovery, do an erase cache and you're done!
[One (M7) Q&A, Help & Troubleshooting] S0wL:
Yes I did it. Thank you. I dont know what;s wrong but TWRP 2.6.3.3 is a pain in the ass it doesnt work properly all the time
[One (M7) Q&A, Help & Troubleshooting] scifitrekkie:
try CWM 6.0.4.5 works well for me, glad to hear you got back in to phone.
[Galaxy Note 3 Q&A, Help & Troubleshooting] lhikari:
why! Just whym

EVERYTHING is turned off ughhh and battery savibg is on

still google plus preventing my phone to have any kind of battery

wakelock shows it as the top with x35 next to it

help plz :(
[Galaxy Note 3 Q&A, Help & Troubleshooting] Killberty:
Deactivate it in application manager

hit 'thanks' if i helped you

SM-N9005 DBT-DMJ7 0x0

XDA Developers 4 premium app
[Galaxy Note 3 Q&A, Help & Troubleshooting] lhikari:
my phone freeze grrrr
[Galaxy Note 3 Q&A, Help & Troubleshooting] Killberty:
Reboot ;)

hit 'thanks' if i helped you

SM-N9005 DBT-DMJ7 0x0

XDA Developers 4 premium app
[Galaxy Note 3 Q&A, Help & Troubleshooting] lhikari:
Phone turned off so i will see today
[AT&T, Rogers HTC One X, Telstra One XL] craig@xatik:
Does anyone play Samurai Siege? I'm on the 12/12 nightly of CM 11 and I'm not able to get Samurai Siege to boot. I click on it and it just pulls up a black screen.

Has anyone experienced this issue?

I was going to post this in the CM11 thread, but it doesn't seem like it's been created yet.
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
There is a CM11 thread here:

http://xdaforums.com/showthread.php?t=2382933

I suggest you post in there but make sure you provide a logcat for the developer, without a logcat it'll be an almost pointless post.

Sent from my Evita.
[Nexus 7 (2013) LTE Android Development] DivinityCycle:
Forgot to mention, since this makes your device think its a "phone", if you install Dialer.apk, you can have access to the normal "Phone" app in your Apps drawer, and mess with SIP goodness :P
[Nexus 7 (2013) LTE Android Development] DivinityCycle:
Also, for CyanogenMod users, your ROM probably did not come with some APKs that will make this more useful.

You CAN just use Google Hangouts as your SMS/MMS app, but some people may prefer to use the native CM app instead (it has those nice pop-up messages!). For that you need MMS.apk.

If you want to mess with the "Phone" functionality, you'll need Dialer.apk.

And finally, if you want to receive emergency notifications from the government (for like natural disasters and Independence Day-style alien invasions and stuff :P) you'll need CellBroadcastReceiver.apk. Please note that none of these are needed for SMS functionality and all these APKs are from CyanogenMod and will not work on stock or other ROMs.

For CM10 Stable, I grabbed these APKs out of the Nexus 4 (mako) ROM, stuck them in a zip and uploaded them here.

On CM11-M1. same deal but I used the Nexus 5 (hammerhead) ROM as my source. Those are here.

These files just need to be placed into the appropriate folder(s) on your device and then you'll need to set the file ownership & permissions the same as the rest of the the stuff in there (owned by root:root, -rw-r--r-).

They all go in /system/app, except for MMS and Dialer on CM11. On KitKat they have introduce the new /system/priv-app folder. My ZIPs contain those directories to remind you where to put the stuff.
[Nexus 7 (2013) LTE Android Development] sbiriguda:
I'm not a Windows user and I'd love to modify my own (stock) framework-res.apk to re-enable SMS support. Do you know what tools FrameWork Flasher uses "behind the scenes" to decompile and recompile the apk?

I don't like the idea of tampering with framework-res.apk using apktool unless somebody can confirm that this is the right direction.
[Nexus 7 (2013) LTE Android Development] DivinityCycle:
APK Tool is indeed the right direction to take.

I actually had to update the binary of APK tool that Framework Flasher uses, since the one included in the original isn't new enough to know what JellyBean and KitKat are :P Since FrameWork Flasher is a Windows Batch Script, I'm certain its just automatically doing stuff in the command line you could be doing by hand.

Looking at the source, I think the deompilation is done with this command:

java -Xmx%heapn%m -jar apktool.jar d "../place-framework-res-here/framework-res.apk" "../files-to-edit/framework-res.apk"

"%heapn%" is a variable, which appears to default to the value of 64.

So the command

"java -Xmx64m -jar apktool.jar d "/path/toframework-res.apk" "/path/to/extract/to"

should work on Linux or Mac, provided you've got Java installed and the jar in the current working directory. Obviously change the paths to match your local stuff. Post how it works if you'd like, I'love to update the guide to include Mac / Linux instructions, and Framework Flasher is the only "Windows" part about it.
[Nexus 7 (2013) LTE Android Development] sbiriguda:
Obviously I messed up the resulting framework-res.apk because it got stuck in a Zygote startup loop. It's worth noting that I built apktool from the latest git sources, so there might be some bugs lurking in the shadows.

Oh well, I'll just wait for somebody else to do the dirty work :)
[Nexus 7 (2013) LTE Android Development] DivinityCycle:
Well, if you send me your framework-res.apk I can mod it for you. Takes like 2 seconds :P

The Framework Flasher source code shows the following for the actual "do the work" steps:

To decompile the original APK-

java -Xmx%heapn%m -jar apktool.jar d "../place-framework-res-here/framework-res.apk" "../files-to-edit/framework-res.apk"

To compile the new APK-

java -Xmx%heapn%m -jar apktool.jar b %~dp0files-to-edit\framework-res.apk %~dp0place-framework-res-here\unsignedframework-res.apk

To sign the APK-

java -Xmx%heapn%m -jar signapk.jar -w testkey.x509.pem testkey.pk8 ../place-framework-res-here/unsignedframework-res.apk ../place-framework-res-here/signedframework-res.apk

To build the unsigned ZIP-

7za a -tzip %~dp0place-framework-res-here\unsignedframework-res.apk %~dp0temp-files\* -mx%usrc% -r

And finally, to sign the ZIP-

java -Xmx%heapn%m -jar signapk.jar -w testkey.x509.pem testkey.pk8 ../final-zip-file/update_unsigned.zip ../final-zip-file/update.zip

note: you do not actually need to sign the ZIP. You CAN flash a zip without a signature on it, its just that with signature you get verification that the file is intact, which isn't a bad idea.

In Batch's screwy syntax, %heapn% is the variable that contains the heap size, and it looks like the default heap size the script uses is 64 unless otherwise specified by the end-user.

Also, %~dp0 is just a path expansion expression used to give the full path to the target files where its used.

I'm pretty sure you can make use of the jar and key files inside the FrameWork Flasher zip file I attached to this thread. You can find them in the resources folder. Both apktool.ar and signapk.jar are necessary, and I'm pretty sure the testkey files are needed to do the digital signatures and make this stuff work. Hope that stuff helps :P
[Nexus 7 (2013) LTE Android Development] deyanimay:
Your mediafire link is just another link to download 7zip, could you update it. Thanks.
[Nexus 7 (2013) LTE Android Development] DivinityCycle:
Damn you multi-tasking!!! sorry about that. Fixing it nao.

The link should be http://www.mediafire.com/download/jozlg1xy4vxiegb/FrameworkFlasher-MOD.zip
[Nexus 7 (2013) LTE Android Development] JoeBruin32:
when I tried to use framework flasher option 1 it said

I attached the log. I'm trying to do this with CM 11 M1 on my deb, windows 8. Any ideas?

edit: framework-res.apk i'm trying to decompile: https://www.dropbox.com/s/iqc3eniv0u51ytg/framework-res.apk

seems like this is a common problem (googled it echo off) but I havent found a solution that works

edit 2: just tried it on my windows 7 laptop with the same result :(

edit 3: tried doing this with the cm 10.2 framework-res.apk with the same result. :(
[Nexus 7 (2013) LTE Android Development] Paten:
About the voice mail message. Have you tried to install T-mobile Visual Voicemail to see if it could download then delete the message? I don't know how this app works, it's just the first thing I thought of when I read your post.
[Nexus 7 (2013) LTE Android Development] nsmart:
Thanks for creating this quide. I tried the single steps of the guide two weeks ago (I described it here: http://xdaforums.com/showpost.php?p=47928887&postcount=167), but always got a bootloop. (De-)compiling the framework succeeded without errors and I tried it with and without changing the build.prop. By now I have no clue what went wrong. Mabye you need a special version of apktool fitting the rom you want to patch ?
[Nexus 7 (2013) LTE Android Development] deyanimay:
I've tried this and it doesn't work. I guess the app can't properly add the visual voicemail service to that line. I've also asked T-mobile about it and they said that I don't even have a voicemail box to store messages so there is nothing they can do about it.
[Nexus 7 (2013) LTE Android Development] sbiriguda:
Same here, it appears that setting config_voice_capable to true triggers an NPE inside the Keyguard class (i.e. the system PIN entry dialog) which then in turn causes SystemUI to restart over and over.

Perhaps the answer lies somewhere in the changes between 4.4 and 4.4.2 inside the AOSP device tree for deb, but I don't have the time to do an extensive diff of everything that has changed between those two releases.

Has anybody succeded in modding the stock KOT49H build without side effects?

---EDIT---

Apparently [MENTION=517854]GuyAdams[/MENTION] managed to do it. Question is, how :)
[Nexus 7 (2013) LTE Android Development] burpitt:
cheers mate, nice post etc, been trying to get this going the last few days (and trying the other posts I've seen you talking on) but so far no luck. I'm getting the same log error as the previous poster too.

cheers :)

running nexus 7 with cm11 latest nightly.
[Nexus 7 (2013) LTE Android Development] DivinityCycle:
Well that sucks! It looks like APKtool doesn't work on anything newer than 4.4. I was able to reproduce the errors by trying to decompile / recompile the framework-res.apk from stock 4.4.2. The current release of APKtool from Slimbean I found here on XDA Devs appears to not be new enough. The main attraction of FrameWork Flasher over other solutions was the extremely easy & rapid download & use (as opposed to the end user having to like go download and install the entire Android dev kit), and Virtuous Ten Studio can definitely do this job, but again it looks to be an order of magnitude more complex for the average user to use. I'm going to be a little busy today doing actual work, but I should be able to find the time to work on this other stuff as well. Frustrating!
[Nexus 7 (2013) LTE Android Development] curtdragon:
Is this working for the rom here: http://xdaforums.com/showthread.php?t=2545628

And what about the carrier dont they see you now making calls and texts on a line that is set to be a tablet?
[Nexus 7 (2013) LTE Android Development] DivinityCycle:
Did you even read my post? At no point did I say anything about "making calls", and as stated in the OP, this simply turns on the software on the tablet that allows you to send & receive SMS/MMS messages. You have to have to actually have SMS service to send / received SMS messages.

Also as carefully stated in OP, using CM10 or CM11 means you can use Voice+ to make Google Voice messages act like regular SMS.

Last but not least, the most recent builds of Bruce's CM11 ROM (the one you linked to) already have this modification applied (as he explained in the most recent few posts).
[Nexus 7 (2013) LTE Android Development] curtdragon:
Hey thanks for coming off as a douchbag. Do I even read? No, perhaps you've edited your post several times since i did. Not to mention the fact that your title reads "Enable SMS on any ROM" then you go on to say that it will also enable the voice portion of the phone. Finally I asked a legitimate question it he texts why? because with ATT i have a share plan. While the plan says it's unlimited talk and text then the data is shared each device is different on the account and priced differently as well.

Also if I wanted to use Google Voice to send text messages i would just do that. Voice+ sends

But as you said this is enabled in the ROm i am using so I will exit this thread now.

You really need work on your people skills.
[Nexus 7 (2013) LTE Android Development] SuperVito:
I do not run framework flasher is not possible to have a zip ready to be flash? I have a nexus 7 2013 LTE with cm 11 kot49h.... Thanks

Inviato dal mio Nexus 7 utilizzando Tapatalk
[Nexus 7 (2013) LTE Android Development] DivinityCycle:
Just a quick update to this thread. I've updated the FrameWork Flasher to include the latest aapt.exe, which makes it work with the latest stock firmware.

The updated Framework Flasher is here: http://www.mediafire.com/download/7v6d88650o6cbjy/FrameworkFlasher-MOD.zip

Also, here's the latest stock Google Dialer in case you want it: http://www.mediafire.com/download/llzq1u26mnvcivy/GoogleDialer.zip
[Nexus 7 (2013) LTE Android Development] Garoto1973:
I have the same problem with the newest mod zip. Did you ever get a solution?
[Nexus 7 (2013) LTE Android Development] DivinityCycle:
I am unable to reproduce the problem. What do your logs say? Also, make sure you're using the newly-updated FrameWork Flasher I just posted about.
[Nexus 7 (2013) LTE Android Development] mus1mus:
echo is off??

might need some java compilers? not sure though
[Nexus 7 (2013) LTE Android Development] User_99:
I've the same problem. patching works fine. No errors, but ROM do not boot up. Only bootloops.

In my case I exchanged the framework in the ROM zip file before flashing and got always bootloops. With untouched - original framework - flash and booting up was fine...

Yes, I use the latest avaialble FrameWork Flasher mod ;)
[Nexus 7 (2013) LTE Android Development] DivinityCycle:
Just a quick update, I was able to use my updated Firmware Flasher to apply the "voiceenable" mod to both the current stock firmware, and now the most recent nightly CM 11.I am running it now with no issues. I'm guessing that since the Flasher utilities (aapt.exe, apktool.jar) are fully up to date on the systems that are having issues compiling the modified framework, maybe it's the Java version?
[Nexus 7 (2013) LTE Android Development] User_99:
Thy very much for the files. I use currently a Stock KK with the SMS path from GuyAdams and it works fine. Will test the tool when I change the Rom again. Currently on vacation an no PC available ;)

Will test it on CM11 and SlimKat...