yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] Lancered:
I had been running Apex 5.3, trying to get to 7.1 now but Odin tells me

Any ideas? This is after flashing back to stock/masterclearing. I placed the galaxys-bootloader-JVB.tar.md5 file in PDA and had re-partition and autostart checked.
[Captivate Android Development] watsa:
bad download, download the file again and you will be fine
[Captivate Android Development] Lancered:
I've tried redownloading, just did again just in case but same message.

I'm probably screwing up someplace since I've never flashed GB before. Do the other options (Bootloader, PIT, Phone, CSC) stay empty?
[Captivate Android Development] Reynaldinho111:
Some phones just cant handle it. Im one of the lucky ones who can oc and uv like crazy. Others cant even get past 1.2. Just depends on your hardware

Sent from my beloved Cappy!!
[Captivate Android Development] watsa:
yep.. the bootloader.tar goes into PDA and then connect ur phone to pc in download mode. Once ODIN recognizes the phone hit start.

(This is the most risky step in upgrading to GB)

Edit: Dont tick repartition
[Captivate Android Development] dizx:
For those with Swype 3 problems, I can't imagine how our systems differ as I have been installing and uninstalling Swype over 15 times today and haven't had issues being able to choose it or another keyboard.

The only thing I can think of, when flashing a theme with swype already included is to uninstall the current swype that is loaded and then flash the theme. Of course, it will not be Swype 3, so then you will have to uninstall the themed swype and then install Swype 3.

Or...before flashing the themed zip, take out the Swype.apk and libSwypeCore.so file in the zip so that it doesn't conflict with an already loaded Swype.
[Captivate Android Development] dizx:
Consider yourself lucky. Mine goes nuts if running higher than 1.2. :-)
[Captivate Android Development] mirrored:
Ok if I were to do this, which it sounds simple enough, how can I right now rid my entire system of anything Swype related so I can have a clean install for swype 3?
[Captivate Android Development] Lancered:
Ah hell, soft bricked. Cellphone-exclamation-computer. :s I wonder what I did incorrectly...as that's exactly how what I did.

This happened to me once but now I can't remember what I did. Lol. Thanks anyway.
[Captivate Android Development] watsa:
did u read my post about not checking repartition? Open Odin and just select PDA, dont set anything else
[Captivate Android Development] Lancered:
Will try it again, ODINed back to stock and I'm good to go.

Thanks!
[Captivate Android Development] leoriver42:
Get rid via Root Explorer of system/app/Swype.apk and of system/lib/libSwypeCore.so after that, clear the dalvik cache (I use titanium backup, but I believe you can also do it with cwm) and reboot.
[Captivate Android Development] pwnerman:
dude you might not have soft bricked that happened to me when a kernel flash failed for some reason in odin all i did to fix was reflash the kernel
[Captivate Android Development] Lancered:
Thanks, all went smoothly.

At least I think. It's taking an awful long time to boot up, but I'm patient, lol. Thanks again.
[Captivate Android Development] dizx:
Well, I've always just uninstalled Swype with TiBu.

If there is a libSwypeCore.so file in the /system/lib folder, then I delete that too.

Then I reboot into Recovery and wipe cache and dalvik-cache, and reboot.

Run Swype Installer and take it from there.
[Captivate Android Development] sinichi21:
hmmm i dont know whats causing mine im doing it apex fresh install what i do is play a music from the default samsung player then press the power to lock it then press the power again to see the playing song on the lock screen and press the power again to lock it and it will reboot sometimes i hangs up, did it with wifi on and wifi off still rebooting
[Captivate Android Development] pwnerman:
Could fix your problem

Must do after flash else u may get reboot on miui lockscreen

go to settings --> device customization --> lockscreen --> custom app --> select a custom app
[Captivate Android Development] zerkai:
Can we get the four tab unlock added? I liked that one. I could care less for the star wars one.

Swiped from my SGH-I897 using Tapatalk
[Captivate Android Development] mirrored:
So I uninstalled Swype and Swype installer with TB. Then used root explorer to delete the swype file in system/lib (swype.apk was not in system/app). Then went into recovery and wiped dalvik cache (couldnt find wipe cache except for wipe cache partition and format cache so I didnt choose either). Then I rebooted and double checked Swype was gone in Root Explorer (it was).

Then I went to settings and tried to choose something besides swiftkey and ran into the same problem of it automatically switching back to swiftkey no matter what keyboard I chose. So now I uninstalled swiftkey via TB. I went back into settings and now it will only let me choose samsung keyboard. Perfect keyboard box is checked but I cant use it because it switches me back to samsung automatically.

I think my phones settings to allow me to switch keyboards got screwed up when I installed the matted blues theme.

So whats the next step?
[Captivate Android Development] pwnerman:
i flashed matterblues and i have had no such problems and the simpliest fix i can see is starting completely over. An issue like that is prob really rare and it will take you way longer to find an answer then just doing a reflash in recovery and if that doesnt work return to stock, master clear then reflash the bootloaders. Also this is completly optional but its just what i did out of chance that might help you. After you flash to stock and master clear jump over to the serendipity thread and follow mikey's instructions for flashing the bootloaders his way then coming to apex from there. Thats just what i did because i was on serendipity before this rom and i have never had a problem that didnt go away after like one time

TO AVOID ISSUES ITS ALWAYS ALWAYS BEST TO FLASH A THEME RIGHT AFTER YOU FLASH A ROM.
[Captivate Android Development] mirrored:
That's what I was unfortunately thinking. I'll do that tomorrow around 9pst if no one else has any other ideas before then.
[Captivate Android Development] pwnerman:
the thanks button needs attention =]
[Captivate Android Development] Chuckd610:
I was one of those who were unable to get out of the endless boot loop. Thanks for the info and posting the new kernel. Everything is looking good! Watsaa, if you're familiar with the DSP Manager app (from CM7), do you know if it can be modified to work with Apex? Thanks
[Captivate Android Development] mirrored:
Attention has been paid :)

On a successful note, after reinstalling SwiftKey and then Swype, every keyboard can be chosen without hassle or issue and all work perfectly! Yay
[Captivate Android Development] watsa:
U mean this??? you will lose samsung music player though. will be replaced by CM7 one
[Captivate Android Development] Chuckd610:
Thanks for the post. Hmmmmmmm, guess I will have to compare the two players.
[Captivate Android Development] Lancered:
Me again :( I went to sleep last night and the Cappy never dig get out of the flashing "Android" stage. Did again now but it's been there again 20 minutes.

1. I flashed back to stock using ODIN 1-click (old ODIN, not v1.82 as I'm not as familiar with that one) then I mastercleared

2. Followed steps 7 and 8. Nothing is checked (no autoboot or F. Reset time). Pulled out battery once I got the green light in Odin for the bootloader, and again for the kernel.

3. Clicked my ROM using Clockwork

Am I missing a step?
[Captivate Android Development] watsa:
whats the name of kernel file?
[Captivate Android Development] Lancered:
TalonDEV-0.1.6.tar

The one in the OP. I'm not that saavy with kernels and such, I just went for what was advised.
[Captivate Android Development] watsa:
Thats the problem buddy, download the kernel again from OP and i bet it will work.

Edit: I have switched to 0.2.2 to get Apex 7.1 working couple of days back.

Edit Edit: No need to go back to JF6 now, flash 0.2.2 using ODIN and then from CWM flash Apex
[Captivate Android Development] Chuckd610:
Is there a TW4 launcher floating around somewhere that will work with 7.1?
[Captivate Android Development] Chuckd610:
I am a witness that 0.2.2 worked and 0.1.6 did not.
[Captivate Android Development] Lancered:
Heeell I did not notice that?!

I'm IN at last! Sweet!
[Captivate Android Development] airtower:
How is everyone getting 1.6 OC? The max I can set is 1.2.

Also, the talon page says to manage settings under CWM (went there looking for extended OC speeds). Neither the app nor CWM recovery allow me to change anything like that.
[Captivate Android Development] froli13:
Get a gf if you need attention...
[Captivate Android Development] watsa:
TW4 has been causing random reboots recently. If you look at Talon' thread everybody seems to have that problem. This is the reason i am holding off on TW4
[Captivate Android Development] eep2378:
Try the Arc launcher that comes with 7.1. No reboot issues, very smooth. I'm really impressed with it so far. :)
[Captivate Android Development] jsmith8858:
Light Sensor Working?

I'm running v7-update-1 and it seems the light sensor does not work; auto-brightness never changes anything despite the phone being in total darkness or bright daylight.

Is it just me or is anyone else having a problem with this? Can anyone confirm for sure that it works fine in version 7.1 ? Any tweaks or work-arounds or tests I can run to fix this that anyone knows of?

I'm currently running the xcalibur kernel as in general I prefer the stablest kernels I can find and don't really overclock.

Thanks!
[Captivate Android Development] purav17:
I am a bit confused. On the first page it says 7.1 wipe package and under that it says that too many changes so no wipe package not avaiable. But than few lines under i see a 7 - 7.1 update non wipe package....Can someone please explain?

Thanks
[Captivate Android Development] ctleng76:
This happened to me as well. First, I updated TiBu to the latest version (not sure if this was required), then I uninstalled an app that was FC'ing. I then restored the app with the data and it worked. I have been doing this to any apps that FC. I do them one at a time. I am not sure if more than one can be done at a time. This was my experience, there is probably a good explanation for it with a better solution than this, but this worked for me.
[Captivate Android Development] eep2378:
7.1 is a wipe package(as it was a pretty substantial update) under changelog it states there were eight(8) changes/upgrades over previous version.

7.0 update 1 is a non-wipe for those already on Apex 7.0. this was a minor update(hence the non wipe moniker).

If you're on update 1 then you need to flash 7.1 wipe package to have the latest Apex.

The wording is a little confusing. Maybe Watsaa can streamline the OP a bit ;)
[Captivate Android Development] watsa:
if u read the OP carefully it says No non wipe - Sorry but too many changes
[Captivate Android Development] ctleng76:
I am having the same problem and I am running 7.1.
[Captivate Android Development] watsa:
The whole OP will soon move to a website :)
[Captivate Android Development] tjarrard:
I'm seeing the same thing. Saw a post in Talon thread about it too. Not sure where the problem lies.

Sent from my Captivate running Apex 7.1 / Talon 0.2.2
[Captivate Android Development] dizx:
+1 on what pwnerman just mentioned. Worse case is to reflash, like I did when my phone freaked out in ways I've never experienced before a few weeks ago (in a bad way).

Let us know how it goes and hope you can get all the keyboards working again.
[Captivate Android Development] dizx:
That doesn't always work. LOL.
[Captivate Android Development] cbasse:
Curious to know the Apex team's thoughts on the new AT&T bootloaders - is this something that Captivate GB users in general should consider using, or is it too early to tell if there's any benefit/need to do so?

Thanks!
[Captivate Android Development] matrix4nov:
Please help me, I cant install Touchwiz 4.0 with this ROM ? whats problem ?
[Captivate Android Development] Sgt_Bilbo:
TW4 currently isn't compatible w/ Apex 7.1. I was running it on 7.0-Update 1, but Watsaa changed a lot with 7.1 and TW4 isn't happy with the changes. Your best bet is to switch to the SE Arc Launcher Watsaa included w/ Apex 7.1. its about as close as you'll find to TW4, less lag, better sorting options, and better animation. It won't hurt to switch...I swear. ;)
[Captivate Android Development] watsa:
If you read Talon' thread TW4 is causing reboots for many, thats y m holding off on it
[Captivate Android Development] Uncle Irish:
What kills me is that everyone wanted TW3 off their phones. Now that TW4 is out, everyone wants it. There are many other launchers out there that are better than what Samsung offers.
[Captivate Android Development] tjarrard:
Here is a post from the TalonDev thread about the auto brightness.

Sent from my Captivate running Apex 7.1 / Talon 0.2.2
[Captivate Android Development] Lancered:
Same. Force closes after restoring. I did another clean install of the ROM and have not touched TiBu for now, but I'm drawing a blank on how to get all my apps without random restarts every time I go to use one.

Would it be because some of the apps may not be GB compatible?
[Captivate Android Development] Uncle Irish:
There is a setting in TiBu to force original location or something like that. Tick that box when you do the restore. Not sure if it will fix the issue, but it may. Some apps might be getting restored to SD (internal) versus internal storage.
[Captivate Android Development] jonnyg1097:
I am not getting my data to work properly with 7.1 is anybody else having this issue? It was fine with 7 update 1
[Captivate Android Development] froli13:
Okay guys, please stop posting about TW4 and tibu restore issues. It doesn't concern the rom so it shouldn't be discussed here. There have been more post about these two than about the rom itself lately.

Thanks for understanding.
[Captivate Android Development] watsa:
There is no change in 7.1 that could affect data, trying switching modem maybe :confused::confused:
[Captivate Android Development] rogersa2k:
Here's what I did to get it to work. This has worked for me with ApeX 6.5, 6.6 and 7. I have no idea if it's useful to anyone else.

1) Restored to stock GB (the one in the GR-12 instructions)

2) Used ODIN to apply TalonDEV 2.2R2

3) Installed ApeX 7.1 (cleared cached and dalvik cache just in case)

4) Booted up ApeX, removed TiBu 3.8.1.1 and installed 3.8.6 (current)

5) Installed Handcent and ADW, rebooted

6) Installed all the rest of my apps

For some reason it seems like restoring all of my apps at once, or including Handcent with a bunch of others, causes the FC issues. This is just an observation though.

- Aaron
[Captivate Android Development] rogersa2k:
FYI, I get these TiBu restore issue *only* with ApeX roms. I have no idea why this is the case. I really like ApeX though so I deal with it.

- Aaron
[Captivate Android Development] froli13:
FYI, you can't really rely on tibu. Sometimes it works, sometimes it doesn't. Use it at your own risk. I had no issues myself with tibu and apex so far...
[Captivate Android Development] watsa:
Many have had problems with TiBU specially when upgrading from froyo to gingerbread across all ROMs, TiBU has worked fine for many on Apex.. There is no specefic code which is against TiBU in Apex, its just a matter of whats being restored
[Captivate Android Development] Barsky:
I haven't installed 7.1 yet. Has anyone who has experienced the Home button insanity issue noticed if it is gone in this version? Love the rom, but that was driving me nuts :-)
[Captivate Android Development] rogersa2k:
Well, in this case I was restoring my apps that were backed up in ApeX 7 Update 1. I agree it doesn't make sense that it only happens with ApeX. Anyway, I won't bring this up again.

Keep up the great work! I'm loving 7.1 so far.

- Aaron
[Captivate Android Development] jonnyg1097:
Which one would you recommend? Or perhaps you could tell me the one you are using.
[Captivate Android Development] jonnyg1097:
For restoring I use Mybackup Root which seems to do a good job at restoring everything just fine.
[Captivate Android Development] watsa:
It really depends on your area, I use KC1 which is included in the ROM. Maybe you can start with reliable JK4?
[Captivate Android Development] watsa:
Can you PM me the list of apps & data that you backup? Thanks for understanding buddy
[Captivate Android Development] mrhaley30705:
+1. I've even restored system settings without problems using it. I actually use both. One is a backup to the other.
[Captivate Android Development] dc5ftw:
hey watsaa,

I cooked the font from UOT kitchen and then when i flashed it, nothing change. I already tried to mount system, mount data and flash too and still nothing change. Any idea??
[Captivate Android Development] jonnyg1097:
Well from the looks of things (based on the info on the left side) we are in the same area (Toronto lol). I am trying an older backup and maybe that will give me the data. But if it doesnt work I shall KC1 and then JK4 if it doesnt work.
[Captivate Android Development] froli13:
PM the file you cooked, I'll fix it.
[Captivate Android Development] dc5ftw:
too late. I just got it to work. stupid me didnt see the part where it say that i didnt have to upload any file.:o I just went back to the kitchen and cooked another one font only and flashed with mount system/data and now its on the phone.:D Next up is searching for battery mod with percentage. For some reason i dont like the big number inside the battery from UOT kitchen lol.

Thank though! :D
[Captivate Android Development] 168us:
cant update apps from market

After install the Apex 7.1, and restored my backup from Titianium Backup. When I try to use market to update those apps - google maps, youtube. I got error. "Download was unsuccessful. please try again."

Any idea?

Thanks.
[Captivate Android Development] froli13:
Never restore system apps and/or data
[Captivate Android Development] watsa:
Clear data/cache for market, and then try again. i bet it will work
[Captivate Android Development] jonnyg1097:
So it seems that it was my fault I must of unchecked "use packet data" when I installed the update initially. Although new problem has occurred and it seems that Touchwiz is crashing whenever I try to open up a program with it. Although the SE launcher doesn't crash the programs except for Memo.

I don't mind though because I like the SE launcher better and I use ADW launcher too sometimes and I am sure I can find another memo taking app in the market that would end up working just fine. But I thought I should let you know.
[Captivate Android Development] tkjeeper:
Hey watsaa, I'm really drawn to this rom, I want to try again. What method do you suggest for converting back to rfs? When I was on it last time, I went into voodoo and couldn't find the "convert to rfs" spot I'm used to seeing. I guess my phone doesn't like ext4. Any ideas?

Sent from the frozen tundra known as Canada.
[Captivate Android Development] froli13:
Did you restore system apps and/or data? TW works fine here.
[Captivate Android Development] jonnyg1097:
No I didn't I just did a reinstall of the rom so its the " fresh out of the box " feel. I just started clicking on the internet browser and then it didnt boot up it actually restarted my phone. I tried other apps and it again would restart my phone. Then I tried the SE launcher and then tried some apps and those were opening up fully. But then Memo kept on crashing and restarting my phone.
[Captivate Android Development] froli13:
Did you apply any mods, tweaks or theme?
[Captivate Android Development] -Perp-:
in CWM, it should say something like: voodoo lagfix enabled / voodoo lagfix disable.

You want to disable the lagfix to convert back to RFS
[Captivate Android Development] jonnyg1097:
Nope not yet but I may be adding your matted blue theme later on.
[Captivate Android Development] froli13:
Then I have no ideas about whats wrong... :confused:

Wait for a couple of minutes before flashing MattedBlues, new update coming SOON. Uploading and updating OP right now!! :D
[Captivate Android Development] watsa:
Its next to impossible that TW3 is crashing out of the box. what actually happens?
[Captivate Android Development] froli13:
New update for MattedBlues for ApeX !!

I am proud of this release, I hope will enjoy it as much as I do! :D

I hope this will fix your 1% battery indicator crave lol

Changelog:
[Captivate Android Development] watsa:
i just tried memo and it works with SE launcher
[Captivate Android Development] jonnyg1097:
Well i dont know what I am doing then... lol it still restarts my phone * shrug *
[Captivate Android Development] jonnyg1097:
Ok here is what happens, when I hit on an app the screen goes black, the notification bar is still visible, and then the screen pops back up and I get a notification on screen that the app failed. There was also times when the screen goes completely black when I hit an app and then the whole phone restarts on me.
[Captivate Android Development] watsa:
and this is on fresh apex out of the box with instructions followed as present in OP? No TiBU nothing
[Captivate Android Development] jonnyg1097:
Yup fresh out of the box with nothing added onto it. And the instructions on the OP was how I installed it.
[Captivate Android Development] watsa:
well i give up then because only u r the one having this issue
[Captivate Android Development] georgem106:
Can I PM you my attempt UOT Kitchen file trying to change the Battery to show large number?
[Captivate Android Development] jonnyg1097:
Yea its sounding like I am. Thanks though for trying.
[Captivate Android Development] froli13:
There's two possibilities:

1- you made something to make it crash

2- everybody has the same problem

Seems like it's number 1...
[Captivate Android Development] watsa:
Try this.. reboot into recovery.. mounts & storage --> mount system --> Back --> Install zip from SD card --> choose UOT cooked zip and flash
[Captivate Android Development] froli13:
Yep, no problem, PM me and explain me the problem too.
[Captivate Android Development] georgem106:
That did it...your'e okay in my book....no matter what everyone else says about you. LOL
[Captivate Android Development] -Perp-:
If you are getting problems no one else is, flash back to stock, download rom again and try to flash.

If you already did this, then your phone just hates this rom lol
[Captivate Android Development] georgem106:
Thanks but watsaa gave me the work around. Thank you again.
[Captivate Android Development] watsa:
:confused::confused:
[Captivate Android Development] georgem106:
Thank you watsaa.
[Captivate Android Development] jonnyg1097:
Haha I am starting to think my phone doesnt like this update for whatever reason since 7 update 1 had no issues at all.

But at the same time I wouldnt be shocked if watsaa somehow looked at my phone and saw an error on my part.
[Captivate Android Development] watsa:
I guess he is right, try downloading rom again and flash it on top of what u have now
[Captivate Android Development] Lancered:
I can second jonnyg1097issues. I had only noticed memo crashing (I'm on SE) but didn't mind as I could use another. But since he mentioned apps crashing on TW, I've tried a few and they have indeed restarted the phone. No TiBu.

I do love this ROM (have since 5.3) but I'm going to try another GB one to see if I have similar issues...to narrow down if it's my phone or me. The latter most likely. Lol.
[Captivate Android Development] watsa:
I can understand apps crashing but not launcher itself. as for apps which ones are problem?
[Captivate Android Development] Lancered:
On SE launcher, just Memo as far I've noticed.

On TW, so far which have been Maps, Allshare and Desktop Home (something like that), and all three have restarted it.

Edit: The apps have crashed, not the launcher itself.