yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] RichMD:
Thanks. It's good to know that is a thing of the past. It's bad because I have no idea what happened then. He said he hasn't loaded anything new in several days.
[Captivate Android Development] sephhi:
That's an odd one. If it got stuck on android is updating then an app got corrupted somehow and startup is hanging on that particular application.
[Captivate Android Development] sephhi:
Re: [ROM][4.2.2]Captivating(Xperia Themed)[X5](More Unbelievable performance!)

The new walkman notification controls
[Captivate Android Development] sephhi:
Dev-host mirrors added to OP!!!
[Captivate Android Development] RichMD:
MD5 verification issue

FYI that I tried verifying MD5 of the download against the MD5 listed in the MD5 file you listed. They don't match. The MD5 you listed on the ROM download page does match what I downloaded. It is just the text in the MD5 check-file is wrong.
[Captivate Android Development] rmntruexjr:
What the........I decide out of boredom to check the thread when I got home....Now I know what I might be doing next :good:.....as long as I can focus on the screen anyway:silly:......

Guess I need to go back a page or 2 and use up my thanks!!.......As long as the checksum matches up :laugh: j/k

Edit...md5 was good here.
[Captivate Android Development] Shortelz:
So uh, I have been looking for the past 30 minutes to try and find instructions on this thread, I can't seem to find any.

I am coming from SlimICS 3.1.0 - Android 4.1.2 and using the Semaphore 2.6.1 kernel. I would like to switch to this, and probably with the devil kernel since it feels smoother to me, what do I need to do to accomplish this, due to the lack of instructions.

Thanks
[Captivate Android Development] merikgvr4:
Upgrading from x4, do I just flash over the new rom without any wipes? Thanks
[Captivate Android Development] rmntruexjr:
I was on X4.....I just wiped cache and dalvik...no problems so far....:good:
[Captivate Android Development] sephhi:
Backup your apps

wipe data

advanced>clear semaphore settings

format /system

flash rom

reboot
[Captivate Android Development] cliftomr1082:
And those of us on X4, do we wipe or hot flash?
[Captivate Android Development] sephhi:
Hot Flash?xD

Yep wipe cache and dalvik then flash
[Captivate Android Development] RichMD:
I did a full clean flash loading X5. I went into devil kernel mgr to set liveOC to 110% and went to memory to set Bigmem and accidentally changed fudgeswap and I'm not certain what the default value is. I looked for a "reset to default" within the configuration utility but didn't see one. I know I could probably reset it by going into recovery and choosing the devil option but I don't know if the installation sets certain "tweaks" that would then be lost.

What should the configuration be and I assume from previous posts that it doesn't make a difference if I use NSTools or devil kernel mgr for setting OC, liveOC, and bigmem. Those are the only options I want to configure because I don't understand the others well enough to change any defauts.
[Captivate Android Development] rmntruexjr:
The fudge swap if I'm not mistaken has no effect unless swap is already enabled...I have moved that slider by mistake before and it had no effect............

Others might and probably will tell you different, but for me, I only use devil app and performance section of settings. For voltage either voltagecontrol or setcpu......I have nothing but trouble when I try to use nstools, so after I flash, I always disable nstools right off the bat.

Again, maybe just me, but I'm overclocking the snot out of my phone and it takes it all, but when I used nstools I got reboots using the same settings.
[Captivate Android Development] RichMD:
Thanks,

I didn't change anything else so it is probably fine. I must have missed it but I didn't see setting max cpu in devil kernel mgr so I set 1200 in nstools but did not change any voltage settings. I went into Devil kernel mgr and set liveOC to 110% (so max is now 1320). The only other change I made was bigmem. I am currently running stability test - cpu and gpu test and I haven't had any reboots but will continue to test with these settings.

The only strange thing I have seen is the battery. After flashing it said full charge but 91% and wasn't charging. I kept playing around and it would charge briefly but stop well before 100%. I tried charging to max and wiped the stats and it was discharging REALLY fast. After a reboot, it showed about 30% lower and quickly drained from there. I've read that battery can take a few cycles to stabilize but I've never seenbt act so wacky but will see if it straightens out. The CPU/GPU with full brightness should drain it quick so I can go through some cycles.

Another quick question: What is considered "too hot" for the battery in celcius. It is currently 50 which would be 122 fahrenheit. that's with it charging and running cpu/gpu testing at 1320 though.
[Captivate Android Development] kevnuke:
Anyone else getting a "Server not found" when they try to download from Goo?
[Captivate Android Development] sephhi:
Use the dev-host mirrors in the OP.

Devil kernel update added to goo. Link
[Captivate Android Development] RichMD:
Just out of curiosity I tried loading antutu to see what kind of score I would get with 1200 and 110% liveOC and bigmem. I didn't change anything else and Antutu showed 3648 which I know probably seems low. What do others get on X5 and is there any options I should consider changing (governors, etc) that would optimize it for general use and smooth response (not for gaming)?
[Captivate Android Development] sephhi:
antutu isn't reliable on the x series. Entropy and other tweaks lower the scores even though performance increase is obvious. You're better off using an3d or glbench(sp?) etc for benchmarks. You can also do browser benchmarks with other apps.
[Captivate Android Development] RichMD:
Thanks, I know benchmarks can be an unreliable way to gauge performance. I was figuring that someone running the same benchmark app used on the same build, then maybe that would be a fair way to judge how each phone is tweaked. I'll try an3d but I'm curious what a "decent" score should be on X5 (I'm not looking to tweak to the max) and also would that score only be meaningful for 3d games but not a good way to score overall responsiveness? It's not my phone so I won't spend a lot of time testing various configs and am just looking for what a reasonably good config/performance would be and how will I know if I am "there" without playing for a while.

Also, is antutu battery tester at all reliable to know how well the battery life is? My son said he would only get 3-4 hours of screen time while at the dimmest setting (on X1) which sounds low since I remember about 4 hours at the brightest setting. I know there is a lot more that affects battery (poor signal, etc) and have loaded GSAM battery monitor to check how it is doing on X5.

Sorry for all the questions but I don't think I will find any decent answers for the above if they are for a different build/phone.
[Captivate Android Development] rmntruexjr:
Re: [ROM][4.2.2]Captivating(Xperia Themed)[X5](More Unbelievable performance!)

The antutu and the first an3d is with my oc.... The last an3d is stock speed.

Hmm..guess I'm not able to post pics atm....hanging on waiting for response......anyway, about 5700 in antutu and 7200+ in an3d at 1464mhz......at stock an3d score was 6800+.

As far as temps go....my battery runs between 28c and 42c over 50 sounds high...but I remember a few gb roms that would cook it at almost 130f or 54.5c
[Captivate Android Development] Darkangels6sic6:
Re: [ROM][4.2.2]Captivating(Xperia Themed)[X5](More Unbelievable performance!)

Haha. That's cause Amara is a he'll of an artist
[Captivate Android Development] RichMD:
OK. I loaded an3dbench and the result was 6854. However, that was with OC set to 1200, liveOC to 110% and bigmem. Shouldn't it be better and does it indicate maybe something isn't set right? Did you change any governors, etc?
[Captivate Android Development] Bane99:
Anyone have a suggestion for a kernel that plays nice with this ROM that isn't Devil Kernel?
[Captivate Android Development] sephhi:
Look up at the poll :fingers-crossed:
[Captivate Android Development] sephhi:
unstable oc. I can tell because at anything above 1200 you should get 7000 in an3d.
[Captivate Android Development] rmntruexjr:
Yup, I second that......

---------- Post added at 08:37 PM ---------- Previous post was at 08:35 PM ----------

.For testing and gaming I've been using min/max for a gov and noop for scheduler, but for everyday use I usually leave it on interactive/ sio/
[Captivate Android Development] RichMD:
Thanks, I didn't know you could have unstable oc without the phone rebooting. I figured if it passed a stability test for a while then it was OK. I didn't change any voltages. How do I know if I have a stable OC if the phone doesn't reboot during a prolonged stability test? :confused:
[Captivate Android Development] rmntruexjr:
The only good stability test is real world everyday use...games, mp3's, videos, downloads and so on......I could run stability tests of my choice all day and think I'm good till I watch a movie or listen to mp3's and bang it reboots or just locks up........If you hadn't changed voltage, that could have been the issue....the device can stutter and lag without rebooting if the voltage is a bit too low for the oc......

Yeah I run 1464 but my voltages are high as well...1464(1350mv) 1220(1325mv) 976(1275mv) 400(1050mv) and 200/100(950mv)....I didn't have to touch the int voltage at all, the stock int. voltage for this kernel seems good for what I'm running.....I also disabled 16 bit transparency in performance, but that's just my personal preference, not sure how much it helps or hurts.

I still think one of the biggest differences in how this rom works for people is how much stuff people run in the background...Auto updates, sync and any monitoring apps........I see a HUGE difference between test scores depending on whether or not I'm using greenify to hibernate my apps.
[Captivate Android Development] RichMD:
Thanks for the reply. I checked nstools (not sure where else to check voltages) and the default voltages is selected. However, that is 1350mv for 1200 which is the max frequency I have set. I tried adding more apps to greenify but there is hardly anything running on the phone so far.

Edit: Well, I removed the 1320 max frequency so 1100 is max (110% liveOC) and my and3d score went up to 6935 so you guys were right on. Nenamark increased as well.

Edit: I increased liveOC to 120% and and3d went up to 7072. I will just leave the settings like that and ensure it is stable. Thanks for the feedback.
[Captivate Android Development] treau:
Re: [ROM][4.2.2]Captivating(Xperia Themed)[X5](More Unbelievable performance!)

I have 2 spare cappys that my toddler uses to play all kinds of performance demanding games (also learning games ) and I run both of them with stock settings. Both phones run just fine, and the speed playing temple run 2 and OZ is the same as it runs on my s3.

Have you tried to run without messing with kernel settings? I honestly do not see a reason to OC unless you are truly trying to show off benchmarks scores that don't mean squat.
[Captivate Android Development] rmntruexjr:
That's cool I'm glad it's working better.......Another thing I'll throw out there in my experience, and I've messed with it for hours on end, I swear these phones like even numbers, but not all even numbers when it comes to cpu and bus frequency......

If I set a live oc from 111 to 119 it's unstable and I even get sd corruption sometimes.... 110, 120 and even numbers after that is what will work for me, 122, 124.....I can also set a step oc to 1200 no problem after that......But.... Only when using devil or the first unofficial semaphore(without the extra 1100 and 1300 steps)....

When we used the first unofficial semaphore kernel for a build or two I could oc no prob. Then for a few builds after that I couldn't oc as good because the kernel also enabled an 1100 and 1300 step in between and my phone didn't like it one bit.......since devil, I'm back at 1464:good:

Now, I don't claim to be an expert on any of it, but I've spent many years building, tweaking, and overclocking computers and other electronics and I've seen similar and crazier things than what I just wrote lol:rolleyes:

Edit: I can see from the post above me that I was a little late with my reply,...and it didn't mean squat lol...I personally see a great improvement in my day to day use...but guess it might be just me......and yes it does run good for an old phone with stock settings. This rom is great!!...Haven't had any issues after flashing X5...Thanks again sephhi!!
[Captivate Android Development] RichMD:
I started trying to OC because I flashed X5 and it still seemed kind of laggy without loading any apps. I thought maybe OC would help.
[Captivate Android Development] treau:
Re: [ROM][4.2.2]Captivating(Xperia Themed)[X5](More Unbelievable performance!)

Did you let the ROM settle first. Before any tweaks I have always gave the phone a few + hrs to settle. I have noticed with x4 and x5 that it is laggy until I reboot the phone for the first time. Which I do after reinstall all the apps.

The cappy is a great phone and ever better now that sepphi has tweaked it.
[Captivate Android Development] sephhi:
With regards to letting the phone settle, I have noticed this behavior as well. On a side note, this might be the most uneventful release ever xD
[Captivate Android Development] RichMD:
I've seen many posts about "letting the phone settle" after flashing for 10 minutes or even hours mentioned above. I have always wondered what supposedly had to happen. Obviously, there are syncs for contacts, apps, etc that takes place for a while. However, if you reboot or use the phone "too soon" then those activities would continue later, etc.

My question is if you don't "let the phone settle" right after flashing, is there any initial setup activity that could get interrupted that would cause the phone to not work as well. I know that sounds like an odd question but I don't remember if I let it settle after flashing. Would that only mean it would be laggy initially but eventually it doesn't make a difference?

On a side note - Do you mean nobody had any problems or you didn't get much feedback?
[Captivate Android Development] Darian71:
I too have read to let the phone settle for at least 10 minutes. I have been doing this every since the X series releases even before I hit the start setup after a full wipe. And continue to do so with only cache and dalvik wipe. I do notice a better response especially after the first reboot.

P. S. I downloaded Temple Run Oz and finally experienced some lag after 6 or 7 runs but haven't experimented with greenify yet. Otherwise X5 is continuing to launch my Cappy into the stratosphere. THANK YOU SEPPHI! :good:
[Captivate Android Development] treau:
Re: [ROM][4.2.2]Captivating(Xperia Themed)[X5](More Unbelievable performance!)

I don't think it will have ill effect on the phone if you don't wait.

From what I have read in the past is hat every time you flash a new ROM your phone re communicates with Samsung and or your provided to perform a (lack of a better phrase) new phone set up. It is something that is built into the code. Some devs in the sgs3 forum found that line of code and was able to bypass it. I think the devs name was TrevE.
[Captivate Android Development] RichMD:
You mentioned not even going through the initial setup for 10 minutes. I've seen people say "IMPORTANT - do not touch for 10 minutes", etc, etc. I'd really like to know if there is any logic (as in why...) behind such strong statements. I think sometimes people read things and don't ask "why" and just start saying to do it as well. I'm not saying there isn't a good reason. It's just there are a lot of "best practices" about calibrating your battery, etc. One of my "favorites" is "FACTORY RESET 3X, WIPE cache 3x, etc, etc.". It's "possible" it could make a difference but I HIGHLY doubt it makes a difference after the first FORMAT - it either works or you would see a failure, etc.

Sorry to highjack the thread Sephhi :o Initially I was just wondering if I should wipe my son's phone again and "let it settle" before touching it to make sure it would work best going forward. I can do that even that if you think it would make a difference after the first reboot - it just doesn't make any sense to me based on my limited knowledge. I know there could be a good reason though.
[Captivate Android Development] treau:
I believe the wipe 3x is more of a OCD thing, but it also helps guarantee that the phone has been truly wiped. For the amount of time it takes to wipe the 2 extra times i feel it is worth it.

I found the posted i was speaking of in my last post

Click Here

I do not know if what is stated in this post was in affect when the cappy came out, but it is in NEW devices now.
[Captivate Android Development] kevnuke:
Re: [ROM][4.2.2]Captivating(Xperia Themed)[X5](More Unbelievable performance!)

Who knows what ghosts lie within the code..
[Captivate Android Development] kevnuke:
Re: [ROM][4.2.2]Captivating(Xperia Themed)[X5](More Unbelievable performance!)

Well I was ABOUT to say I'm having no issues on X5 but my phone is still randomly turning itself off after the backlight timer turns the screen off. Strange because I accidentally left it on, unplugged last night for 6 hours while I slept and it didn't do that. The Wi-Fi was even on all night.

Hope this problem gets tracked down soon.

---------- Post added at 10:56 AM ---------- Previous post was at 10:36 AM ----------

Mine got stuck on the "starting apps" part of that after fixing permissions, wiping cache, and wiping dalvik in recovery before I Odin flashed stock and went back up to X5.
[Captivate Android Development] sephhi:
Simple answer. Media scanner. It runs for a while depending on how much media you have on the device. It slows down everything else.

If you interrupt the initial scan, it can lead to missing media in your library(photos even ringtones etc) until you trigger it again.
[Captivate Android Development] sephhi:
Hmm...have you tried changing kernels?
[Captivate Android Development] RichMD:
Thanks - that would not be anything that would cause the phone to be laggy, etc after it finishes. I can just connect usb to a pc and unplug and that will trigger media scanner (unless a simple reboot does as well).

It sounds like there is no lasting problem caused if you don't let it settle if that is the only thing that anyone can think of.
[Captivate Android Development] kinggame992000:
Re: [ROM][4.2.2]Captivating(Xperia Themed)[X5](More Unbelievable performance!)

Once again I successful dirty wipe with no problems. So far nothing out of place.I will try out game later

. I thought x4 was a perfect release already.... What special about x5 she phi?
[Captivate Android Development] sephhi:
I've seen my name misspelled before but I don't think anyone's ever turned it into 2 words before xD

X5

-launcher bugfixes

-launcher added options(margins)

-same, possibly better performance than x4

-less aggressive killing of certain app types e.g words with friends

-superuser integrated with settings again

-better multitasking

-walkman player can now create playlists

-walkman player has updated notification controls
[Captivate Android Development] sephhi:
It should only apply to clean flashes. If you do a clean flash in the future you can see this effect by quickly opening the gallery and seeing how long it takes to populate the thumbnails. It can take a while for the music to populate after that. Sometimes it's quick other times it doesn't seem to kick in till many minutes after boot.
[Captivate Android Development] Darkangels6sic6:
Re: [ROM][4.2.2]Captivating(Xperia Themed)[X5](More Unbelievable performance!)

I only got 4 something with 1100mhz plus 20% oc. That's was on all builds before x5
[Captivate Android Development] kevnuke:
Re: [ROM][4.2.2]Captivating(Xperia Themed)[X5](More Unbelievable performance!)

Have been considering it but I forget by the time I get home XD

EDIT: Can you provide a link to kernels I can use so I'll be less likely to forget?
[Captivate Android Development] RichMD:
Strange battery behavior

Since flashing X5 on my son's phone, the one strange thing has been the battery has acted "wacky" on more than one occasion. I've attached a screenshot showing battery. He told me he was using an app (a game - magnus ignis?) and all of a sudden it shut off. He turned it on and within a few seconds it said shutting off and the battery showed 0%. He then plugged it in to charge and told me about it. I checked the phone within a couple of minutes and it showed 71% as shown in the picture. Any ideas? :confused:
[Captivate Android Development] RichMD:
You obviously must have had unstable OC like they told me if that was for and3d. My score went up when I removed the 1200 frequency. With no OC - just 116% liveOC, I got 7025 (just barely over 7 - can't remember now). I brought liveOC down to 110% to make sure it is stable.
[Captivate Android Development] kevnuke:
Re: [ROM][4.2.2]Captivating(Xperia Themed)[X5](More Unbelievable performance!)

I've had this problem before. The battery isn't calibrated.

1. Download the Battery Calibration app from the play store

2. Run the battery out completely with the phone on, until it shuts off.

3. Put the phone into Download mode and then disconnect the cord if that's the way you did it. Let the battery run all the way down while in Download mode.

4. After the battery drains completely (you may want to try to power it on to make sure), plug it in and immediately boot directly into recovery. WITHOUT BOOTING INTO THE ROM FIRST

5. Wipe battery stats from recovery.

6. Turn off the phone from recovery.

7. Charge to 100% with the phone off.

8. Start the phone and run the Battery Calibration app. If the battery meter in the status bar shows less than 100% let it continue to charge.

If it seems like it's staying stuck on the same percentage, unplug the phone for a few seconds and plug it back in. This seems to unstick whatever is doing it.

If it continues to stay at the same percentage or gets stuck at less than 100% again, uncheck the " wait until 100%" option and calibrate immediately.

9. Run the battery all the way down to 0% again, using Download mode if necessary.

You might have to go through a few cycles of charging/discharging to get it right.

Also, do you use more than one battery in that phone?

EDIT: Typos
[Captivate Android Development] Darkangels6sic6:
Re: [ROM][4.2.2]Captivating(Xperia Themed)[X5](More Unbelievable performance!)

Wow. My scores never go that Hi. Even with only oc or only live oc
[Captivate Android Development] RichMD:
Thanks, I will try what you said. I did question if it was a battery calibration problem and downloaded the app and had to play with it to get it to 100% and then let it discharge. However, I wasn't sure if the whole battery calibration process was still considered valuable. I thought I read that every time your battery hits 100% it resets the stats that you wipe anyway. Also, I've never seen a process where you have to leave it in download mode but I will give it a try. I've seen various methods of full charge, wipe, drain until it shuts off, turn on and then quickly plug in and leave it charging to full and then full discharge again. Lots of methods but I will give yours a try.

We only have one battery for the phone.

---------- Post added at 08:00 PM ---------- Previous post was at 07:57 PM ----------

I just tried it again to make sure I wasn't mistaken. I have the phone set to 110% liveOC, bigmem, and no OC (1000 top frequency). I got 6817 on and3d. If you aren't getting scores in that range, try removing any OC settings and test again to see if it improves. It did for me.

Edit: I used greenify to pause lookout as well and got 6853