yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] Phoenix-Lead:
I need to do that as well. It is very hard to dev without a phone. I bricked mine last week and I have been creating new stuff and having testers run it. So far so good, only minor changes needed.:D
[Captivate Android Development] Phoenix-Lead:
For some reason this is happening on certain devices. I know it works fine on my wife's phone. (Axura 2.4).

If it causing reboots, you could just install manually through tibu, although it sucks, you will not lose any of your apps and data and the phone will not turn off.
[Captivate Android Development] Pheno.menon:
One request: please add linking of notification and voice call ring volume in the next release! This is an essential feature :eek:
[Captivate Android Development] newter55:
Volume master....free from the market...will do this. I prefer not to have them linked but this app will do it for you and allows easy changing of all volume levels in one place
[Captivate Android Development] Phoenix-Lead:
I will not be linking them. I like to fulfill the requests of the users, but not this one. Sorry.
[Captivate Android Development] Pheno.menon:
Thanks. This is good enough :)

No worries, a workaround was all I needed.

I found a bug: when selecting "Folder View" in its options, Messaging application force closes.

I have Red Soul theme and NakedRed Swype installed, so it might be from one of these.. might be not.
[Captivate Android Development] blperks2:
Adam - sent you a PM :)
[Captivate Android Development] dizx:
Take your time with 2.5 for sure. I know ETA is tomorrow, but at least I have been able to put 2.3 through its paces.

Thanks to all the testers during this time that Adam awaits his own replacement unit.
[Captivate Android Development] 88EVGAFTW:
cant wait for 2.5
[Captivate Android Development] Boobie Watcher:
i didnt back up my nv_data...........so when i flash back to stock on the next release can i then back it up and make a nandroid backup of my stock....then just flash back to stock that way, or am i screwed for not backing it up in the first place
[Captivate Android Development] dredge999:
I just reflashed after odin/clear and it still happens. I think I am going to manually reinstall everything and then try some other backup program like My Backup Pro.

If I am going to be flashing this one as much as I did my Nexus One I need to be able to quickly restore apps+settings.

Rick
[Captivate Android Development] Pheno.menon:
Yup. Follow the instructions here for a faster flash process.
[Captivate Android Development] sabesh:
Adam, thx for making this a great place for newbies like myself. It really is a useful and friendly place here. Cheers.

Rogers users> I now use the voicemail-to-text feature to inform me of any new VMs. Works quite well.
[Captivate Android Development] gin032:
CIFS in AXURA

Ive just switched to Axura from stock and am impressed with it over many other ROMs. I personally went back to stock because I needed tun VPN and CIFS support.

I don't see any CIFS modules in AXURA, though I did see mention of "enabling it with cwm-tweaks" in a setiron kernel discussion, though I have no idea what that means.

Has anyone got cifs.ko or working cifs in AUXURA?
[Captivate Android Development] Maliberti:
OK,

So I know 2.5 will be coming out later and I have the next week off from work and don't need exchange working. I am playing with the SGS too and upgraded to Galaxy Tab email.

Everything installed correctly and my exchange server info was accepted.

But it does not not sync. Anyone else having this problem?
[Captivate Android Development] dp1mat:
Backing Up your NV_data

The reason its important to back up your NV_data (Non-volitile) is this has your imei, product code, unlock codes and model. This informatioin is not recreated with a JF6 OCD (One click downloader)

Certain Roms write data to your NV_data

(i think it was JPC leak from I9000 that was the first one. it changed everyones product code to I897ZKAKOR)

Axura changes the product code to I959ZKATMB or something like that

The Correct Product code for our Captivate is I897ZKAATT.

If your IMEI says 004999010640000 this is incorrect also and you may find your phone to stop making calls as this is like a debugging or prototype imei

Finally, if your unlock code is FFFFFFFF, you need this repair in order to unlock your code

All of these can be fixed with Helroz's Repair_nv_data.zip Found Here: http://perso.numericable.fr/helroz/P...ir_nv_data.zip

I did not create the software or any of the instructions, THis is credited to Helroz in the vibrant forum (please thank and donate to him) he came up with all of this, Im just sharing knowlage.

this can be found here: Unlocking Tmo Vibrant

http://xdaforums.com/show...&postcount=103

Just read the read me first. then the .Doc Make sure you are at Stock JH7 (I didnt try jf6) and root with busy Box (Super One click by CLShort Fuse worked for me)

Then Step 2,3 and 4. Monitor your phone for SU access attempts, it has several and be patient and read what its asking you to look for,

Now if you havent Backed up your NV_data then now is the time. I Use root explorer and just copy the /efs folder to a safe place (I have a copy on my ext. sd card and a backup hard drive)

You can also Use SGS tools (not SGS tool Box) to do a product code check. This also copies all of the pertenant NV_Data files to a folder on your internal SD card. you can use these also if you want.​

Thanks will be added soon as well

Master™

hansmrtn

shiftystylee

adamholden85

justflorin

mattbeau[/QUOTE]

followed this to a t. I still cant get my product code to change to I897ZKAATT it stays at I959ZKATMB I had mine messed up as I never made a backup untill to late.
[Captivate Android Development] ThisWasATriumph:
I just checked all that using SGS Toolbox and everything is how it should be. It even automatically backed up my Nv_data to the sd card for me :D
[Captivate Android Development] xidcat:
Assuming you flashed back to stock and did a Master Clear (if not, you need to go back to square one.)

You're not trying to restore system data are you? If not, pick the apps that you absolutely need to recover (because of the data), and recover one at a time with Titanium, then download the rest. Could be a bad flash or one app is hosing up the system. If you came from 2.1, you may an app that was not updated for Froyo.
[Captivate Android Development] mcord11758:
How does one find out what their product code is
[Captivate Android Development] blperks2:
I also have the same issue. I changed versions of Tibu and tried the same file and got a parsing error. Somewhere along the line it didn't save all the files right. Don't think its anything to do with the rom but Tibu.
[Captivate Android Development] hansonmi:
read post 1307 or the part at the beginning of the thread where it talks about the nv_data.bin file... captivates have a product code ending in ZKAATT... you can also look it up on Samsungs Website under their cellular phone categories.
[Captivate Android Development] mcord11758:
Here is my product code. I apparently have two at the moment. One is correct, the other not. I am not having any issues at the moment, but should I be concerned
[Captivate Android Development] hansonmi:
You have to make the backup of you nv_data.bin file before you flash any custom rom... you should do this when you first take the phone out of the box and root it and install busybox or some file manager that allows root access to copy things from your /efs/ folder.

you really should back up your entire /efs/ folder to a safe location instead of just your nv_data.* files just in case.

If you didn't and you don't have an unlocked captivate, PM me and i will get back to you as soon as I can to tell you how to get it back to stock as much as possible" to get you to be able to use Kies again with your stock phone.
[Captivate Android Development] hansonmi:
You should be fine... product codes are used by a couple of things including Kies to see if your phone is a at&t captivate or not... if not, you cannot use Kies when you flash back to stock... your code that ends in AATT is the correct product code for the captivate.
[Captivate Android Development] rwj5279955:
Mine is just wrong, I897ZKATMB
[Captivate Android Development] tehillim:
I have the reverse of this screenshot. My correct product code (I897ZKAATT) is in backup.nv_data.bak, and the product code in nv_database.bin is I897ZKATMB (I assume TMB is TMobile). What does this mean for me?

Info retrieved via SGS Toolbox
[Captivate Android Development] LightningGA:
I have the same thing here.
[Captivate Android Development] techniq35:
Battery

Which errors specifically (#3, #4, and #5)?

Btw, I did a little more testing today, at one point disabling all the notification quick settings (Wifi, BT, GPS, Sound, Rotation). The only one I saw much improvement with was disabling Wifi. The burn rate still seemed more than it should be (probably around 5%/hr, but only kept it that way for about 3 hours), and not sure why with Wifi on it would burn at like 10-15%/hr.

I'm currently charging my phone and going to flash a different rom to see if the problem still exists (leaning towards Assonance, especially since Perception is having all types of problems from its base rom and B9 was pulled). I've noticed some battery issue reports in all roms, and even in Axura before I started to see them. Maybe my battery is going bad (although doubtful)

I'm sure I'll be back (unless a Gingerbread rom drops soon, which looks to be a few weeks out, with Christmas/New Years coming and all).
[Captivate Android Development] Eibon:
I know its probably been mentioned many times in this thread, but what is the average battery life for moderate and light usage for this ROM?
[Captivate Android Development] dp1mat:
same thing to and I been working on this for 4 hrs all i get is I897ZKATMB I been trying to get this ironed out all day to no avail. I did have some weird jacked up ID but got it to I897ZKATMB
[Captivate Android Development] hansonmi:
NV_DATA.BIN

There seems to be a lot of confusion about product codes and how to restore them and what it means if your product code is wrong... (not ending with ZKAATT)... if you have the correct information in the back-up files which can be seen in the SGS Toolbox, just copy those to your sd card, and to your computer and rename them to be nv_data.bin and nv_data.bin.md5 then store them in a safe place since those are the correct nv_data files.

I am going to create a thread on what to do to get your phone back to stock with the correct product code... like it says in many other threads about the nv_data.bin stuff, if you never plan on returning to stock and using Kies to get updates, you don't need to worry about your product codes... I will update this post with the location of the thread for those that are interested... I have no idea when i will be able to get it done though since i use adb, busybox, and hexeditor programs an i need to account for the people that don't know how to use any of those programs or even know what adb (android debugging bridge) is or what it does.

Update: will hopefully have the new thread done tomorrow evening (12/20/10)

Update: new thread created... http://xdaforums.com/showthread.php?p=9946574#post9946574

Please note that the alternative to using ADB for everything would be to root and use root explorer or super explorer or something... however, there are a few commands that you really have no choice but to use adb shell to chown the edited nv_data.bin file.
[Captivate Android Development] dp1mat:
Thanks Hansonmi
[Captivate Android Development] kytrauma:
To those of you having device id issues, do you have the restore id script saved on your sd card? Ever since I put it on mine I haven't had to change my id once it always does it for me.

Sent from my happy cappy
[Captivate Android Development] hansonmi:
all of the above, sorry, i was more or less talking about the one where it was mentioned about the rogue sensor for the vibrant but not on the captivate... keep in mind my 100% stock captivate had a huge log file of warnings and errors just from being on for a few hours and it the same **stuff** over and over again...
[Captivate Android Development] ThisWasATriumph:
Wow I forgot the lagfix on 2.4 wasn't enabled by default. Been running it all this time and didn't even notice. Lagged once in a while but not enough to make me second guess. Nice work :cool:
[Captivate Android Development] holeshot77:
:) Love this ROM!
[Captivate Android Development] Spidious:
If lagfix on 2.4 wasn't enabled by default, and if it won't be on v2.5.

How do you enable it ?
[Captivate Android Development] gin032:
I loaded the setiron 1.4.7 kernel over the Axura 1.4.6 version, as there was a CIFS fix in it. You can do this with Odin or Heimdall. No need for a CIFS module because it's provided with the kernel each boot. The boot process will however delete it if it is not used (or "enable"), so you must activate it:

Enter recovery mode (hold power button while running until power options menu, select recovery)

select advanced speedMod ULK Features

select TWEAK options

select enable CIFS

enabling CIFS adds an entry to tweaks.conf which is read by the post-init.sh script. This script will cause the module to be loaded or it will be deleted. I would have preferred it if the files were just not loaded rather than deleted so I could have opted to insmod them later should I need it. Anyway, once enabled you can then use something like cifsmanager to mount CIFS filesystems...including watching movies streamed on your home network !
[Captivate Android Development] rawb123456:
Auxura gingerbread theme with black status bar and greeen icons? Thanks for the reply
[Captivate Android Development] ThisWasATriumph:
Recovery>Advanced speedmod ULK features>lagfix>ext4 all. then reboot and select "yes, backup and restore" and wait.
[Captivate Android Development] holeshot77:
Same. How do I/We fix this? Is there a way to alternate these?
[Captivate Android Development] dpmurphy81:
I know this is a question but i think it is more dev oriented can the jl3 modem be used in place of the ji6 kernal modem with ucji6 2.2 froyo.
[Captivate Android Development] Boobie Watcher:
if your familiar with adb commands and what not it might not be that hard for you to fix, i never got around to fooling with adb so im going to have to study a little before i start the process.....they are posting a full thread dedicated on how to fix this, should be out in the next day or 2 so it should be all good man!
[Captivate Android Development] holeshot77:
i hope they post a link here for it. So for the time being, I won't have to worry about not making phone calls or anything will I?
[Captivate Android Development] rootnik:
New install here.

I was more nervous about this rom than others because of all the warnings about bricking, but the only problem I had was having no service after restarting the phone with the sim card post install. I rebooted a few times and it still didn't have service. Finally I powered down, removed the battery and the sim card for about a minute, replaced them and booted up with service.

I was using bouncing between Cognition and Doc's "Less is More" rom. What really turned me on to this rom were the people who are posting in this thread... there is just a different atmosphere here.
[Captivate Android Development] hansonmi:
New Thread up and runnign for repairing your productcode

I have gotten the new thread up for the steps of repaining your captivate's productcode in the nv_data.bin file so you can go to 100% stock and use kies again...

i have been up staring at this computer for hours and so there may be grammer issues and what-not, so please exuse me. I also know the list of steps looks kind of funky... i was fighting with M$ Word to get my document to copy over properly and I didn't win.. i will correct tomorrow... sleep is more important at this point.

Also note, that you DO NOT NEED to use abd for everything... as i noted in the thread, you can do all the copying and moving of files with root explorer or something similar as long as you have root permissions, but adb is a good thing to learn. I have provided locations in the thread to where you can find everything you need... adb commands do need to be issued at one point though in the process (i mention where that point is in the thread).

Here is the thread...

http://xdaforums.com/showthread.php?p=9946574#post9946574

enjoy and good night everyone.
[Captivate Android Development] gin032:
Voicemail notification appears to work OK for me on Rogers, though I did replace my product code from my /efs backup of stock.
[Captivate Android Development] 88EVGAFTW:
Nevermind, a little googling fixed that :D

I am thoroughly LOVING this rom over the Design Gears ones, i like the way the animations are, the colors, and the keyboard themes and font it comes with :D :D

props :D ;)

edit: I try to install the music player apk but it just says "Application not Installed" :confused: :confused: :confused: but I installed Root Explorer just fine.
[Captivate Android Development] rawb123456:
Place musicplayer.apk in systems/apps via root explorer
[Captivate Android Development] kangi26:
What I do is first is make sure you have stopped the app in task manager(or something similar) I use SystemPanel Lite. Then using Root Explorer; go to system/apps and delete the music.apk. I'll then copy/paste the new music.apk into system/apps. You should be good to go
[Captivate Android Development] Chargerdude70:
Do we know if 2.5 will be full data wipe?
[Captivate Android Development] rockettman:
Yes it will as there are going to be some specific changes to the framework as well as to launcher2.
[Captivate Android Development] Phoenix-Lead:
Yes, it will wipe. Too many problems if not.:)
[Captivate Android Development] Phoenix-Lead:
Woo hoo

I stole my wife's phone for the day and I am loving 2.5!! It just feels smoother to me and the framework tweaks are killer!! Thanks rockett!
[Captivate Android Development] Mkarin:
Patiently waiting for 2.5... Hurry up! :D
[Captivate Android Development] Phoenix-Lead:
I am shooting for tonight. We shall see though. This is based off of me being able to finish the framework tweaks with rockett and being able to put it through the ringer.
[Captivate Android Development] mcord11758:
Screen shots of the tweaks?
[Captivate Android Development] rockettman:
They aren't quite all finished yet...working on them now as well as trying to work so hopefully we can get it all finished for you. Just trying to make it look cleaner and a little more Axura specific!
[Captivate Android Development] Phoenix-Lead:
Confidential until release. There are too many "can you do this" or "I want that". So, screenshots come with the release.
[Captivate Android Development] sabesh:
Thx, good to know!
[Captivate Android Development] Phoenix-Lead:
Update

I am expecting better battery life for you all. It seems as though memory use is much lower on 2.5 than any other build.

Edit:

I am talking using 178Mb as compared to the average 250 I was using!!
[Captivate Android Development] Chargerdude70:
Thanks for that gents...can you answer this please...whos and what version kernel are we getting this release?
[Captivate Android Development] Phoenix-Lead:
SetiroN's 1.4.7. Works well and seems to manage memory better IMO.
[Captivate Android Development] PRTEQ:
Very nice... did you fix the

voice mail notification? Because that is a deal breaker flr me.

Hope to use it soon.
[Captivate Android Development] Phoenix-Lead:
Not yet, sorry. Too much going on right now. Are you located outside of the US?
[Captivate Android Development] Chargerdude70:
Sorry Adam for so many questions. I am still on 2.3 and liking it. No force closes and no randon shut downs(so far..crossing fingers and toes)...I like the fact that I have ear phones during call...do you know if that has been fixed in SetrioN's 1.4.7 kernel?...if not, I may sit back and observe for a while....
[Captivate Android Development] smokestack76:
Also check out the heap size in build.prop, Thats off the charts and has been ;)

Its one thing to free some megs. But remember we are not on WinMo so free mem doesnt mean alot. More apps thrown into mem that we use means faster. Just because its in the mem does not mean it uses CPU. Thats why task killers and what not are a bad idea. Only areas i look at are the Heap and cache area.
[Captivate Android Development] NOSintake:
Oh yay! I'm messing with Darky's ROM right now (testing for a friend), but I'm looking forward to coming back to Axura and better battery life!

EDIT - btw, does anyon UV? If so, what are some settings to try out? Or is it just trial and error? Any big benefits on battery life performance?
[Captivate Android Development] inneyeseakay:
Okay... Issue is really starting to annoy me.

I'm using Handcent and have standard messaging app notifications turned off. Whenever I get a text message, I get my Handcent notification icon + the icon pointed out below. The icon pictured below doesn't go away when I read the message either, I have to manually clear it.

Any ideas where this icon is coming from so I can turn it off?
[Captivate Android Development] soypoi:
That looks like one of the handcent notification things. double check your handcent settings for notifications and disable it.

Sent from John May's V communication device
[Captivate Android Development] Sgt_Bilbo:
If you have Beautiful Widgets pack 2 installed, that's probably the culprit. Uninstall it and your problem should be solved.
[Captivate Android Development] Phoenix-Lead:
That happens on a few roms. my wife gets that too even before axura. Thats why I don't use out.
[Captivate Android Development] Felklaw:
What is that widget you are using which displays the system information like that?

Looks pretty sweet.
[Captivate Android Development] inneyeseakay:
Thanks guys for quick responses... It was, indeed, BW2! All fixed now! :)
[Captivate Android Development] inneyeseakay:
Perfect System Monitor... For some reason Voltage doesn't work with the captivate though. There are quite a few other items you can choose to display as well.
[Captivate Android Development] rootnik:
Is there anyway to make the Voicemail button on the dialer open Google Voice?
[Captivate Android Development] Keland44:
lookin forward for that
[Captivate Android Development] philly fan:
2.5?

I see mention of 2.5 when will it be out?
[Captivate Android Development] LightningGA:
Adam is hoping to release it later today/tonight
[Captivate Android Development] inneyeseakay:
Adam... will 2.5 be using Xcali's or SetiroN's kernel?
[Captivate Android Development] rockettman:
SetiroN's 1.4.7 Seems to handle everything better!
[Captivate Android Development] bowtieguy:
Adam,

I have sent you a couple emails

Are they going to /dev/null?

Cheers
[Captivate Android Development] Phoenix-Lead:
I haven't gotten any emails from you as of yet..I know my email is ok bc rockettman is conversing with me daily on it. Try again. If you forgot it just pm me.
[Captivate Android Development] JPxM0Dz:
Me wants it Now!! ;)
[Captivate Android Development] BoostedSR20:
This (2.3) is the best my phone has run since RC1. Thanks for the continuing work on this, can't wait for new releases.

On another note, why doesn't anyone in the Cappy community use ROM Manager? I recently helped a friend with an Evo root/start flashing, and good lord they have a HUGE selection on there, and its so easy to flash multiple ROMS all day long using Rom Manager. Same with my GF's Nexus. Did I miss something somewhere?
[Captivate Android Development] Phoenix-Lead:
Fine, you twisted my arm. It is included in 2.5. I didn't want to spoil any of the secrets
[Captivate Android Development] BoostedSR20:
lol.... awesome. Sorry to spoil the fun. ;)

Also, you are the quickest responding guy here... I hadn't even left this thread before you responded. :eek:
[Captivate Android Development] comdei:
So we will be able to flash new updates without going back to stock!

:D?
[Captivate Android Development] Phoenix-Lead:
Not bad for also being at work, huh?