Call Recording works on NEW phone. - Vibrant Q&A, Help & Troubleshooting

So I bricked my Vibrant and just got a new one as a warranty exchange, yay, good for me. I've gone about the whole rooting and flashing to Simply Honey that I ported over from I9000. In doing so I found that call recording works perfectly whereas it did not on my old phone. Others are not having success getting it to work either. My question is are there certain things on our phones, in all the lines of script and programming, that remain even after using Odin or flashing different roms? If so would it be possible to find the differences between the stock KA6 that my new phone came with and the KA6 that came as an update.
I only ask because I am not a developer, merely a guy who swapped a few files around to get a working I9000 rom that I liked and I'm not deeply familiar with all the files in Android like some of you are. Anyone wants to chime in maybe we as a community can figure this out for those that want that feature.

interesting, I ll look at mine as well never looked at that

Related

Work Phone - Should I Install a Rom?

Well my work just got a bunch of iPhones and the CEO got one of the. He had the Samsung before so I got it as an upgrade over my crackberry.
Now I really want to install a custom rom/kernel on the phone but I am hesitating because its really not my phone and my work owns it.
What do you guys think should I stick with stock or should I root the phone and install a rom?
Stock. There's nothing like explaining to the boss how you f'd up company equipment.
I dont know if one should/should not install custom roms on a work phone, as I don't have one. But I can tell you that if you do decide to root and install one of the custom roms, it's not that hard to unroot and go back to stock later on when you need to return the phone. There are several threads here that will guide you through the process too.
jenisiz said:
Stock. There's nothing like explaining to the boss how you f'd up company equipment.
Click to expand...
Click to collapse
I guess your right I just hate being stuck on 2.1 when I know I can have a nice Froyo install. It's just so hard not to do because I have done it with all my other devices.
dsf767 said:
I guess your right I just hate being stuck on 2.1 when I know I can have a nice Froyo install. It's just so hard not to do because I have done it with all my other devices.
Click to expand...
Click to collapse
I hear you...but who's to say he won't ask for it out the blue someday?
Idk, at this point, the fascinate is practically impossible to brick. You also say you have experience rooting and customizing other phones, correct? I say go for it. The only reason I could see not to is due to security issues. Work passwords and etc.. I really don't know too much about all of that tho.
Sent from my SCH-I500 using XDA Premium App
I have a rooted android work phone. All you have to do is read what ppl are saying about the roms and FOLLOW DIRECTIONS and youll be fine.
dsf767 said:
Well my work just got a bunch of iPhones and the CEO got one of the. He had the Samsung before so I got it as an upgrade over my crackberry.
Now I really want to install a custom rom/kernel on the phone but I am hesitating because its really not my phone and my work owns it.
What do you guys think should I stick with stock or should I root the phone and install a rom?
Click to expand...
Click to collapse
Used my fascinating voodoo powers
I seriously discourage doing anything to it. It's not yours for one, and (no disrespect to the devs ofcourse, their work is amazing) there really isnt anything spectacular for this phone at the moment due to samsung's failure to provide any source code. To be more specific... our kernels suck.
And oh yea this shouldve been in the Q&A section so be ready for ashasaur to move this thread. (hes really good at doing that )
Depends on your comfort level, and of course, your corporate policies.
Sent from my SCH-I500 using XDA Premium App
I would say root your phone at the most. It's fairly easy to recover from just rooting, but flashing roms/kernels/modems is much more risky. At least with rooting, you could fairly easily freeze the bloat with TiBu and have a more functional phone. Thawing everything and un-rooting would have you a stock phone back fairly quickly, and you could also still receive OTA updates as well.
I say go for it if anything goes wrong all you have to do is odin back to stock it removes everything its as simple as plugging the phone in load the stock file and click start I've done this countless times
We pick our work cell phones specifically because of the potential customization we can do. I hate being stuck with some company's version of what they think will be useful to me in my job. I can Odin this phone back to stock/factory defaults in less than 5 minutes if need be, so customizing this phone and expanding its abilities, and recovering from those customizations quickly, were what attracted me to it.
Android is Android, whether it's Samsung's stock version or one of the dev's version of it. Your phone is still going to perform the same tasks you need it to for your job. As long as you are both competent with the technologies involved and confident in your ability to restore to stock, I don't see why you should hesitate from exploring the options that are out there, especially when Froyo source drops and we see an explosion of dev-created customizations/enhancements.
Really? If your asking for advice on whether to mess with a business owned phone, it makes me wonder are you the ceo's mail clerk?
SuperClean2.9.1vNitroDark
Personally for a work phone, I'd update it for better usage in my work.
Increasing battery life usage duration.
Less irritating buggy glitches.
Removing the idiotic TW/BING/VZW craps. (too many add-on hacks from google default causing reliability and dependability problems)
Adding Backup and Restore nandroid for possible failures and migrations.
I suggest DJ05 + SuperClean + Blaze v2.3.1R2.

[Q] Official Gingerbread ROM?

Hi,
I just bought a vibrant from ebay and waiting anxiously for it to arrive.
Meanwhile I would like to check if the official GB rom is coming soon?
If not, I will like to seek your advice a good ROM that you will recommend newbies to flash.
Thanks!
CyanogenMod 7 is pretty amazing if you are looking for a good gingerbread ROM
Sent from my SGH-T959 using XDA Premium App
MIUI or CM 7 but it still in Beta some bugs and no GPS
But there a lots of Great 2.2 Froyo Roms for vibrant
Hope that Helps
If you're a true noob who's not flashed a lot before I would suggest any of the 2.2.1 roms. They are all functional and a bit better than 2.2. The only thing you'll lose is wifi calling which is a huge battery drain anyway.
Right now the gingerbread roms don't have working GPS and require a little bit more experience with flashing.
My teammate and I have the Simply Galaxy/Honey series. 2.8 is very fast and stable and its 2.2.1. Team EDT also puts out quality work and you can always count on their roms to be fast and stable as well.
Sent from my GT-I9000 using XDA Premium App
yah stick with 2.2 or 2.2.1 until u get experienced enough for cm7 or other gb roms! So id listen to explodingboy70
Thanks for all the advice! You are wonderful guys!
One more thing, will Samsung update the vibrant with an official GB rom?
I read that some said it could be done through Kies?
nhc said:
Hi,
I just bought a vibrant from ebay and waiting anxiously for it to arrive.
Meanwhile I would like to check if the official GB rom is coming soon?
If not, I will like to seek your advice a good ROM that you will recommend newbies to flash.
Thanks!
Click to expand...
Click to collapse
Simply honey 2.3.3 gb.By far the best gb for the vibrant.flawless, and easy install.
Sent from my GT-I9000 using XDA App
At this point we don't know when and if we're getting an official gingerbread from T-mobile. Samsung released gingerbread for the international version only - the GT-I9000. It is not completely identical to the Vibrant. It's up to the carriers when and if they release it and put their touches on it. Once Samsung releases some source code for Gingerbread, you'll see a huge jump in gingerbread development and improvements in those roms. Until then, stick to 2.2.1 like the others have said. I stick to team whiskey's roms, and every month or so I flash to a gingerbread rom for like a week to get a feel for it, then go back to 2.2.1 since I can't deal with the bugs in our GB roms for too long at once
Hi,
Finally my phone has arrived. Its already on Official 2.2 (I guessed) with Kernel Version 2.6.32.9 with build number FROYO.UVKA6.
If I want to remain like this for now (awaiting the official GB), what are the improvement that I can or should make to the phone with the current config?
eg. Voodoo , Other kernel, modem, rom?
I would give it a few days before you starting flashing etc etc. Get used to the phone with froyo, learns the ins and out of all the settings and stuff, will come in handy when you are ready to start playing.
If you haven't already, you should read the myriad of info in the vibrant bible, focusing on rooting, flashing and the things needed. I def would get a good handle on understanding programs like titanium, busy box and rom manager as all will eventually need to be used in one way shape or form.
To be honest, after my few days of learning the ropes, you should consider after learning the phones ins and outs, using ODIN to get back to 2.1 that normally comes with the vibrant (I am not 100% sure that all vibrants came with 2.1 stock, not sure if yours is the new model or outgoing model), rooting, installing titanium backup, busybox and rom manager and make a NANDROID backup of a nice clean OS so that should you run into issues flashing, you have an emergency back up to fall back on. I just did this over the past 2 days and it was a great learning experience.
I did my first rom flash today and was pretty cool, not as hard as I thought but really teaches you the ins and outs of all this cool stuff.
The ppl here were great in helping me and answering my questions, truly a great community.
My phone came with 2.1, then upgraded to 2.2, rooted and removed all the bloatware and never backed anything up. I then realized after help here, it was better to go back to 2.1, do all the right steps to root, install the right apps above, then make a nice clean emergency backup. It def will save your ass sooner or later.
With regards to changes, with my phone when it was at 2.2, I did alot to help improve battery life, I use a black wallpaper, I only turn on wifi when needed, I don't enable GPS at all. I set brightest via power widget to lowest unless in bright sun at which time, you can easily brighten it, you can change how quickly the screen goes dark, etc etc. There's alot of things you can do but since you just got the phone, you need to see how you're going to use it, in order to customize it.
Just my 2 from a beginner
Samsung won't say when or if a release of gb will actually come to US variants. I emailed them just the other day.
If you can live without GPS, then go with cyanogen mod
Sent from my badass Vibrant
I have been looking for a while and as usual with Samsung/T-Mobile the official word on GB is very deliberately vague.
I've been trying different ROMs and between my wife's Vibrant and mine, I have tried 5 ROMs so far.
Flashing some of the simpler Froyo ROMs is definitely easier and safer then jumping straight to CM7 or MIUI.
I would go with the earlier advice of getting familiar with your phone first and making sure you are comfortable with rebooting in recovery, wipe cache, etc.
One click root, back-up and re-install some apps so you are comfortable with all that.
Once you feel good, then try the simpler ROMs. TeamWhiskey - Nero is the first one I tried and it was easy to install and quite fast.
After that, went with Bionix.
Now I'm running SimpleHoney and on my wife's phone we are running DarkyRom 9.5.
All of these can be flashed through CWM which makes them simpler and safer.
Hope this helps! Enjoy your phone.
Sav
Thank you all for the replies. The advice and guidance are really much appreciated.
After one whole day fooling around, I finally managed to Root it and to install Simple Galaxy 2.8. I had some problems initially with the new 3e recovery from froyo causing unable to root problem. But I googled it and managed to workaround it.
I will play with the phone for a few more days before I decide if I want to go for the next level, GB
Go check out EDT's Asgard rom. Pretty slick.

[Q] Custom ROM

Hi All,
My wife is finally fed up being stuck on 2.1 and is looking for me to update her phone. I'm pretty familiar with the process on my phone (Droid X), but I know absolutely nothing about rooting and installing ROMs on this phone.
The instructions thread sticky'd here looks pretty self explanatory, but I imagine I might have some questions during it... but there is nothing I can do about that just yet.
A couple of questions.
1) Is there anything I should know that's not in that thread. A link to ODIN would be pretty nice since I have no clue what that is (guessing it's something like RDSLite).
2) What's the current favorite GB ROM? I'm thinking about putting her on something TW based, simply because of the amount of changes that could make it a harder transition for her. I figure I can pop Launcher Pro on and let her use the TW Dialer and other menus she's used to.
3) I know I'm going to sound crazy for contradicting myself above, but what's not working in CM7? I haven't put my X on CM7 because there are some things not working entirely, but I'd consider it depending on what's missing.
4) Since the X's bootloader is still locked, I have no experience flashing radios and kernels. I'm assuming these should be outlined pretty closely in whatever ROM I choose to install.
Any other general advice would be appreciated, I'd like to get this done either tonight or tomorrow.
Kind of on a random note, I thought she was supposed to be on at least 2.2 stock. She's still on 2.1 for some reason, and I could swear I read about a 2.2 update a while ago, which gave me a bit of a surprise when I read 2.1-update1 in the Firmware version.
Thanks for your help!
Read this link... It has everything you need to get started
http://forum.xda-developers.com/showthread.php?t=1238070
If you went to settings/about phone/updates? There will be an option to check for system updates. It's been a while since I've looked at that setup, but it's in that general area. I would definitely recommend Vanilla GB for your wife if you're looking for simple but intense performance. I switch between all the MTD GB roms, I love all of em.
Sent telepathically.
Thanks guys.
She's looking for stability more than anything, but I want her to be familiar and not lost.
If she decides she wants TW later, can it be put on later or is it completely ripped? I just don't want to need to flash this multiple times.
I'm leaning towards PowerWash GB now; can't tell if GB is still in dev. Thinking maybe I should just use one of the Froyo ones.
Thoughts?
Check out the "stickies" section in development. There are multiple official restore packages in case you mess up. Look in the "Going from Vanilla GB/etc etc to any other ROM" thread. You can move mountains with that one.
Sent telepathically.
EtherBoo said:
Thanks guys.
She's looking for stability more than anything, but I want her to be familiar and not lost.
If she decides she wants TW later, can it be put on later or is it completely ripped? I just don't want to need to flash this multiple times.
I'm leaning towards PowerWash GB now; can't tell if GB is still in dev. Thinking maybe I should just use one of the Froyo ones.
Thoughts?
Click to expand...
Click to collapse
Until powerwashed gingerbread gets a kernal, the pw 1.2 ed05 is faster since it has the otb-fusion 1.6 kernal. Also if your phone can handle the undervolt, the 0808 pbj kernal works nice to. Again everything you need is in the link I posted. Even includes a going back to stock tutorial, with vzw official 2.2.2 ed05 package from pentafive.
Just got it working on CM7. Woooo.
I had her playing with Vanilla and she seems to not like it.
I tried to get her onto PowerWash and it was not very happy. Odin kept crapping out.
Any suggestions as to how I could get a TW ROM on via CWM? Most of them seem to require Odin, and I don't see too many tutorials around (unless I'm missing something). I'd rather make her use vanilla than put her back on Froyo though...

[Q] New to Rezound, have a few questions

I recently switched from a Droid X (running CM9) to the Rezound, and I am loving it so far. I have read all the stickies on unlocking, rooting, and installing ROMs, and it is very different on this device. I understand the general idea, but I have a few questions...
For one, I am accustomed to being able to SBF back to factory if anything went wrong with my DX. I realize that there is no SBF process for a "bricked" Rezound, and that there are ways to fix your device if something goes wrong. I am wondering if there is a way to actually brick a Rezound beyond repair by just flashing ROMs and kernels. And if this does happen, has anyone had trouble getting a new device from Verizon after using HTCdev to unlock their device? I realize that it may void parts of the warranty, but I was just wondering if anyone has actually been denied a replacement device because of this.
My last question is, does Chrome work on ICS ROMs on the Rezound? I've looked through a lot of threads for the different ROMs in the development section, but I have not even seen it mentioned. On my Tab 10.1 (also CM9) and some other devices I have played with, you could just change the build number in the build.prop to fix Chrome if it didn't work with a ROM. Does this work for the Rezound?
Troider said:
I recently switched from a Droid X (running CM9) to the Rezound, and I am loving it so far. I have read all the stickies on unlocking, rooting, and installing ROMs, and it is very different on this device. I understand the general idea, but I have a few questions...
For one, I am accustomed to being able to SBF back to factory if anything went wrong with my DX. I realize that there is no SBF process for a "bricked" Rezound, and that there are ways to fix your device if something goes wrong. I am wondering if there is a way to actually brick a Rezound beyond repair by just flashing ROMs and kernels. And if this does happen, has anyone had trouble getting a new device from Verizon after using HTCdev to unlock their device? I realize that it may void parts of the warranty, but I was just wondering if anyone has actually been denied a replacement device because of this.
My last question is, does Chrome work on ICS ROMs on the Rezound? I've looked through a lot of threads for the different ROMs in the development section, but I have not even seen it mentioned. On my Tab 10.1 (also CM9) and some other devices I have played with, you could just change the build number in the build.prop to fix Chrome if it didn't work with a ROM. Does this work for the Rezound?
Click to expand...
Click to collapse
Bricking is pretty tough on this phone. I haven't heard of full on bricking yet.
Also haven't heard of a warranty being voided just for flashing ROM's, at least for HTC.
There is a Chrome APK in the Themes forum. Sideload it as the very first thing you do once you flash an ICS rom. After that you are golden.
Good Luck.
Anyone know when ICS is out for Motorola Razr?
What? You aren't going to find to many people in this forum that actually care about an ICS release for the Razr.
http://lmgtfy.com/?q=motorola+razr+ics+release
Kalger said:
Anyone know when ICS is out for Motorola Razr?
Click to expand...
Click to collapse
Try here... http://forum.xda-developers.com/forumdisplay.php?f=1361
Troider said:
I recently switched from a Droid X (running CM9) to the Rezound, and I am loving it so far. I have read all the stickies on unlocking, rooting, and installing ROMs, and it is very different on this device. I understand the general idea, but I have a few questions...
For one, I am accustomed to being able to SBF back to factory if anything went wrong with my DX. I realize that there is no SBF process for a "bricked" Rezound, and that there are ways to fix your device if something goes wrong. I am wondering if there is a way to actually brick a Rezound beyond repair by just flashing ROMs and kernels. And if this does happen, has anyone had trouble getting a new device from Verizon after using HTCdev to unlock their device? I realize that it may void parts of the warranty, but I was just wondering if anyone has actually been denied a replacement device because of this.
My last question is, does Chrome work on ICS ROMs on the Rezound? I've looked through a lot of threads for the different ROMs in the development section, but I have not even seen it mentioned. On my Tab 10.1 (also CM9) and some other devices I have played with, you could just change the build number in the build.prop to fix Chrome if it didn't work with a ROM. Does this work for the Rezound?
Click to expand...
Click to collapse
I am a almost 3 year Motorola user using that root/flashing/sbf process. I haven't went back to unrooting yet on my Rezound, but I can tell you it's a little more difficult to get rooted than the original Motorola Droid and the Motorola Droid X2 (which is what i upgraded from).
First you have unlock the bootloader. I did it the slow way step-by-step through HTCDev.com becuase the noob method wasn't working for me. After you get the files you need from the SDK Android app it's pretty much easy from there to unlock the bastard.
Flashing new roms is pretty similiar, but there's a hitch. Usually when you flash a ROM you have to flash a kernal that is compabitable with the ROM. Which means you have to do it in the bootloader instead of in Recovery. The only time you don't have to do this is when the ROM has a built in kernal (boot.img) and it almost flashes it for you automatically.
I'm very happy with my upgrade from the X2, but then again the original X had a lot more variety as far as development. The X2 wasn't very popular even though for a short while it was the best specced pure 3G device on Verizon when 4G LTE came out.
I've tried a couple ICS ROMs and for the most part they're pretty damn stable with a few bugs in them. Personally I like ROMs very polished with literally almost no bugs so I'm sticking with GB ROMs until something pretty polished comes out. I will be totally happy with my Rezound if we get a full or pretty close to a full AOSP ROM released under Ice Cream Sandwich.
If you have any other questions private message me. I've owned the Rezound for about a week now and have been happy with it.
Chrome shows in the market for ics running rezounds, no need to side load.
Sent from my Rezound using Tapatalk

What roms can be used with the i605 ND7 4.4.2 with safestrap and locked bootloader?

i was told that only touchwiz roms will work with this phone but ive been looking all over and everything i find is old and for 4.3. the note 2 forums seem to be dead but if anyone is still on here and sees this please let me know
so far it looks like these are my choices.
alliance, n3bula, trents.
Just be aware, Alliance has this terrible picture for phone calls of people who aren't in your contact list. It's an image of some girl in her bra.
This would be passable (still dumb) in my teens, but having to constantly hide my phone in public because I'm worried that a random phone number will call me and project some half-nude girl on the entire screen of my phone is incredibly frustrating. I've tried using the xposed framework to change this picture, but haven't had any success. Another way (according to other threads in XDA) is to unpack the ROM and change it yourself. If I'm doing this, however, I might as well change ROMs. Just why, dev? Why?
With that said, anyone have recommendations for N3bula or Trents?
Also, can this thread please be moved to the proper location? It feels weird to have it here, lol.

Categories

Resources