yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] rmntruexjr:
I had this on several flashes and never pinpointed the cause. Had status bar issues and settings issues as well on some flashes. This last time I formatted everything flashed stock with recovery, then flashed cm10.1 and let it load. Then I factory reset and formatted system and then flashed M2 once and let it load.......no problems so far.

You know, maybe sephhi can answer this one, but as I wrote this a variable occurred to me.....Could I be messing it up by rebooting to recovery?...for example: This good flash, after I installed cm10.1, I factory reset and formatted system. Then flashed M2 without rebooting to recovery first. On at least some of my bad flashes, I had rebooted to recovery after the wipe/format before I flashed M2. Might be nothing, just grasping at straws as to why it's so easy for my flash to go wrong in the sense that random things are buggy that shouldn't be depending on the flash.
[Captivate Android Development] Mortal Eternity:
its normal, press ok and proceed further... you won't be having any problem afterwards... :)
[Captivate Android Development] anwarkhan25:
Re: [ROM][4.2.2]Captivating(Xperia Themed)[Milestone 2]

Can you post some more settings like semaphore manager, cm settings, nstools... would be greatly appreciated :D
[Captivate Android Development] Mortal Eternity:
captivating users were super man n now they are "SUPER BATMAN" lolz thanks to sephhie :D
[Captivate Android Development] Tsaukpaetra:
:( So sad, somehow my wifi broke, coming from SlimBean 4.2.1... I'll try reflashing or something...
[Captivate Android Development] sephhi:
Re: [ROM][4.2.2]Captivating(Xperia Themed)[Milestone 2]

You'll have to do a full wipe for sure. Completely different base, etc
[Captivate Android Development] iosmonster:
Re: [ROM][4.2.2]Captivating(Xperia Themed)[Milestone 2]

For some reason it won't pet me put a pattern for my lockscreen
[Captivate Android Development] Darkangels6sic6:
Re: [ROM][4.2.2]Captivating(Xperia Themed)[Milestone 2]

Did something happen to the download or is mine being picking. When I go to download 4.2.2 it finishes immediately at about 312bytes. Not fails, but says complete
[Captivate Android Development] Mortal Eternity:
it downloads fine... i just did... its about 290 mb... i may be somthing wrong with you download manager or ur isp! :rolleyes:
[Captivate Android Development] Darkangels6sic6:
Re: [ROM][4.2.2]Captivating(Xperia Themed)[Milestone 2]

No clue, but it's working fine through goo manager
[Captivate Android Development] mcyorian:
Check This bug list

great rom but

1- on power widget data button doesnt turns dark when you turn off data

2- on system settings some options and configuration dont change untill you reboot phone

3- try to change xperia keyboard to another keyboard is a hell, xperia keyboard resist to be changed and you must disable or unnistall it from app manager

4- pressing back button on system configurationmenu cause FC and every chang you did,return to last config.

i hope this help to improve this great rom, meanwhile ill back to AOKP

Congrats!
[Captivate Android Development] RichMD:
I decided to factory reset, wipe cache/dalvik, nstools settings, etc and flashed it again. I did verify the MD5 is good. Last time I had the cobalt 9/10 blue theme. This time I didn't even load that. I don't have the process system error anymore. However, I was finding that I would set "unknown sources" and usb debugging would not "appear" to stick after setting them. I would go in right after setting them and they wouldn't show as set. I then decided to set them and choose reboot while still on that screen. On reboot, the setting is correct.

Regarding performance, I used semaphore to enable bigmem (changed camera to 480p first) and also I set liveoc to 115%. I see a big improvement in nenamark2 (>30fps). I didn't change anything else (voltage, etc). Stability and speed are most important followed by battery life. Are there any other suggested settings? The captivate used to be mine but I have a Note2 now so I can't keep up with XDA for both devices... :D

I also still have an issue where the statusbar will only show the clock until I go and change something like wifi, etc and then everything else shows up. Is that normal? I will try another launcher (go ex).
[Captivate Android Development] sephhi:
Re: [ROM][4.2.2]Captivating(Xperia Themed)[Milestone 2]

None of the issues you mention are in the Rom. You have a bad flash. There was another user with the exact same issues due to a bad flash. Don't you think other users would have reported the same if there were such issues? Here's what you do:

Do a full wipe and format system as well. Flash stock cm10.1 and then flash the Rom on top of it. Report back after you've done this and if you still have those issues I will gladly assist you.
[Captivate Android Development] mcyorian:
My flash was after Data factoryreset / full wipe / dalvik chache / format system / and clean any script from another kernel o r rom....

all twice!

maybe i must try to flash from a stock cm10.1

thanks

but at least be sure the data button on power widget works on yours! ;)
[Captivate Android Development] RichMD:
Hi Sepphi,

If we have a few issues like settings don't "appear" to stick until you reboot and then show correct and the statusbar doesn't initially show WIFI, etc would you suggest flashing CM 10.1 and then this ROM again? I've already flashed this multiple times but after coming from CM10.0

Edit: I will try it and report back. It can't hurt to try.
[Captivate Android Development] sephhi:
Re: [ROM][4.2.2]Captivating(Xperia Themed)[Milestone 2]

Yep, it works.
[Captivate Android Development] sephhi:
Re: [ROM][4.2.2]Captivating(Xperia Themed)[Milestone 2]

Yes try that and report back. This Rom seems to be very sensitive for a couple users for some odd reason.
[Captivate Android Development] RichMD:
I was wondering if the difference is for people that didn't have M1 previously? Is there any initialization (new fs format for 4.2.x, etc) that M1 does that isn't in M2?
[Captivate Android Development] Mortal Eternity:
didn't see any of the above mentioned issues... :eek:

1. mobile data on and off toggling fine.

2. every setting change taking place instantly (some semaphore settings required reboot - and its mentioned in front of the option)

3. using swiftkey 3 as a keyboard and i changed it just fine without any problem and long processes...

4. no FCs as yet.

I guess you had a bad flash mate, please do a full wipe and flash this rom 3 times, it may help!

i just found one little thing (which i can't call a problem) in my ring tune and notification tune list, almost every tune is appearing twice (1st is not playing and 2nd plays when clicked) i guess its just because i cleared cache and delvik only and flashed M2 over 10.2 (didn't do a full wipe)

please can any one else confirm it so i could do a full wipe to fix this!?

p.s. i m scoring 3621 on M2 - Antutu bench marks without a single tweak and oc settings applied :D thanks sephhi :)
[Captivate Android Development] sephhi:
Yep, you have the bad flash issue. solution is to flash cm10.1 first then flash the rom over it.
[Captivate Android Development] danigrad:
+1

The rest is perfect! Love the battery bar and center clock, I missed those before :good:
[Captivate Android Development] Darkangels6sic6:
Re: [ROM][4.2.2]Captivating(Xperia Themed)[Milestone 2]

Luckily only for a few and for some of us few those issues are gone so we can love this Rom with everyone!
[Captivate Android Development] 3men2:
That is the only issue I've seen so far but I was having that even with 10.2 :eek:

Not a clue why is that.
[Captivate Android Development] rmntruexjr:
Still having the same issues as RichMD.....all the same ones. Sometimes right out of the gate, sometimes after I start installing apps....And if I change anything system app related like uninstalling system apps, or disabling them it goes nuts....Happening on both of my cappys.

I still think it's funny that whenever this "bad flash" or whatever it is happens, besides all the things mentioned so far like the settings not sticking till reboot and all that, I also get a third toggle on my gps in settings......gps is off, I tap once the indicator turns blue for a sec then turns back off. I tap a second time and then the indicator turns blue and stays blue. I tap again and it turns off....3 toggles lol....still when I tap twice and the indicator stays on, if I back out and return, it is back off again. Until I reboot then the gps is really on.......

I'm just glad I'm not the only one.

With that said, I've never been more into a rom than I am this one and for me it's worth figuring out how to make it work on my phone (it's half the fun isn't it).:good:
[Captivate Android Development] sephhi:
For those with the statusbar issue, try flashing the official semaphore kernel.
[Captivate Android Development] sephhi:
Did you let cm10.1 boot to check if settings stick? try doing that before flashing the rom over it.

There is so much tweaking I think it pushes some cappys to their limits and the ones with the not so great chipsets are having problems. Way back when glitch kernel was being used there was a lot of info about why some of our phones are more overclockable than others and the fact of the matter is that Samsung's quality control was not so great with the first round of galaxy s devices(their first android attempt). Some have slow nand, remember the whole no datadata vs datadata fiasco? The deep idle issues, and variations in undervolting and overclocking are all caused by this. Also everyone knows about out gpsgate, lol. Now, clearly samsung have learned from the galaxy s launch and the galaxy s2 was way better in this regard and so on.
[Captivate Android Development] rmntruexjr:
Yes I did, and sometimes even after I'm on M2 everything can work as it should but then somewhere down the line of setting up and installing apps and rebooting, it can start in......Tried to narrow it down to an app or particular setting, but haven't found it yet....One time it was all good until I switched to my zeam launcher so I thought it might be that, but other times I see the same issues with the stock launcher before I even switch.

....I have had zero luck with the unofficial kernel so I am back to the official 2.9.8. Still not seeing my status bar after boot until I swipe it.....I did however, according to benchmarks, increase performance by doing so....lol:confused::D
[Captivate Android Development] ge77af:
Re: [ROM][4.2.2]Captivating(Xperia Themed)[Milestone 2]

In games touch screen is not responsive. I downloaded sgs touch booster but nothing plz help
[Captivate Android Development] rmntruexjr:
Exactly why I don't give up lol...zram + my cappy = sloooow....just gotta find what works.
[Captivate Android Development] RichMD:
I tried full wipes and flashed 10.1. After rebooting, I did the full wipes and installed M2 (just once - no reboot to recovery, etc). After booting up everything was working great - settings would stick, etc. I then used Semaphore Mgr to enable Bibmem (after setting 480p) and rebooted and then settings wouldn't stick anymore. At some point I also enabled dev options but I can't remember exactly when. I have tried rebooting to recovery and using clear semaphore mgr settings, and even uninstalled the app but settings still don't "appear" to stick. They actually do but you don't see it until a reboot. I have turned off Dev settings, bigmem is off, no liveOC, etc but I can't get the settings to stick again.

Could I get a link to the M1 release? I installed that on my daughter's phone and everything worked great. I wonder if installing that first and setting everything up and then wiping cache/dalvik and flashing M2 over it would work.

---------- Post added at 01:08 PM ---------- Previous post was at 12:54 PM ----------

Edit: I found the M1 link on Goo.im - http://goo.im/devs/sephhi/captivating/captivatingM1.zip. MD5 - http://goo.im/devs/sephhi/captivating/captivatingM1.md5

I decided to reboot to recovery, go to advanced and did the 3 wipes of semaphore mgr, nstools, and init.d. I then wiped cache and dalvik. I then installed M2 again without a factory reset or system wipe. After booting up, settings stick again. It's not a solution but narrowing it down. After a few reboots to ensure settings stick, I will install semaphore mgr, reboot, check, enable bigmem, reboot, check, enable liveoc 110%, reboot, check, and lastly enable dev options, reboot, check.

Edit: Sorry for the long post but hopefully troubleshooting will help others. I tried rebooting without changing anything and settings would not stick anymore. I tried recovery, wipe cache/dalvik and fix permissions. Settings still wouldn't stick. Trying wipe dalvik/cache, fix permissions, and reinstalling M2.
[Captivate Android Development] rmntruexjr:
Re: [ROM][4.2.2]Captivating(Xperia Themed)[Milestone 2]

Ok, so while having these issues, and had flashed the official kernel, I booted to recovery and without any wipe or format I reflashed m2 and then let it load.....of coarse it changed the kernel back so for the heck of it I checked settings and all was good again.....I overclocked the kernel even though in the past it had no effect or even gave lower scores.....then I benched....um.... I don't know what happened but I don't dare to reboot......ran 2 times cause I didn't believe the first one.....stable so far....
[Captivate Android Development] rmntruexjr:
Re: [ROM][4.2.2]Captivating(Xperia Themed)[Milestone 2]

This looks good too....now I'm going to reboot.....wish me luck :thumbup::D

Edit: I rebooted and settings still stick(only 2 toggles for gps) and even better, my oc voltage settings stuck in nstools......Note: I have not nor do I dare to open the semaphore app yet....seems that after dirty reflashing M2 over the M2 that was on the official 2.9.8sc, my issues are gone again except one...I still have to swipe the status bar for it to appear after the reboot.

Edit 2: Holy crap...even after a reboot my test scores are crazy!! 5400 to 5500 in antutu and 7200-7300 in an3d.... going to setup my settings and install apps from the markets one by one to see if anything messes this up.
[Captivate Android Development] Mortal Eternity:
Seriously...

How can i have one of those for my cappy?! :silly:
[Captivate Android Development] BigBozolini:
Re: [ROM][4.2.2]Captivating(Xperia Themed)[Milestone 2]

That explains what I'm experiencing. I got the capdaddy day one nigga and some of these builds run flawlessly while others do not-- unfortunately. Forgot about those dam chips. Thanks for the ROM sephi.
[Captivate Android Development] sleeper994:
Re: [ROM][4.2.2]Captivating(Xperia Themed)[Milestone 2]

Since I cant get this ROM to work for me, I was wondering if Sepphhi could make a flashable .zip of a inverted Facebook app so we could use it on other ROMs like CM??
[Captivate Android Development] Darkangels6sic6:
Re: [ROM][4.2.2]Captivating(Xperia Themed)[Milestone 2]

Ps. I miss the glitch days when we 25% oc'd buss speed while having 1.5ghz cpu. My only issue I discovered was second boot gets stuck on boot animation. I waited about 20 minutes and no luck. I had reinstalled my apps so that sucked. Tried again and same thing. Second boot gets stuck. Even tried wiping cache. Haven't tried flashing the kernel itself so we will see.

And absolutely yes full wipes. A dirty flash is exceptionally rare for me even when allowed.
[Captivate Android Development] era246:
AW: [ROM][4.2.2]Captivating(Xperia Themed)[Milestone 2]

For me everything except the lockscreen patternn works!!! Great work :)
[Captivate Android Development] sephhi:
Did you oc?
[Captivate Android Development] Darkangels6sic6:
Re: [ROM][4.2.2]Captivating(Xperia Themed)[Milestone 2]

The first time, but returned back to normal before hand and I didn't oc the second time.
[Captivate Android Development] rmntruexjr:
2 times during installing apps rebooting and testing the settings messed up like before. Each time I just dirty reflashed M2 again and all was well again.....The system seems to be very picky....I have in the past deleted system apps I didn't need and even added my own by just using an explorer with root and setting permissions on the app after pasting but no go now lol...messing with anything system related including settings in the semaphore app sometimes, seems to make it do funny things. I was just going to add xperia wallpapers but got system process errors and the usual settings mess up on reboot.

The dirty flash fixes what ever I'm doing to mess it up though....it even keeps my nstools(minus voltage) and semaphore settings how I have them set.

...now if I can just get my voltage to stick through a reboot...In nstools if I check "set on boot" my cpu settings stick on reboot but my voltage doesn't...If I also check "use init.d script" then my voltage does stick but my cpu settings don't:laugh::eek:

Almost done downloading asphalt 6 again to test it out, but I'm still benching those high numbers, and still no crashes from the oc. Even when I forget to fix my voltage on a reboot lol....
[Captivate Android Development] Darkangels6sic6:
Re: [ROM][4.2.2]Captivating(Xperia Themed)[Milestone 2]

Can't solve the problem but you can savevthe voltage settings and load them
[Captivate Android Development] rmntruexjr:
yeah, that is the quickest way I've found so far to get back to good after a reboot......

semaphore and nstools (and maybe even that performance tab in settings) are conflicting...I can make nstools settings default just by making sure semaphore app was the last app of the 2 loaded before a reboot. It makes it so when the os loads apps on reboot, it loads semaphore settings after it loads nstools. I literally see my cpu speed start at 1440 and then reset to 1000 during the startup process. As long as I make sure nstools is the last of the 2 I opened, everthing in nstools but voltage sticks because the os loads the nstools settings last on the reboot.
[Captivate Android Development] slytidar:
if i am using sephhi's nstools settings do i have to change the oc value ?

if so to which amount ?
[Captivate Android Development] 3men2:
No matter what I do voltage settings in nstools are not sticking after reboot. its creating conflicts with semaphore manager and causing reboots to recovery. I can't have stable overclock past 1200. If I try 1440 ir reboots during Antutu benchmarks. With 1320 it reboots while adjusting voltage. In few words...its a mess.

SOOOOO.. I decided to stay with just changing settings in semaphore manager. I get stable 1200 and score between 5000 to 5300 in Antutu. :)

Better safe than nothing. LOL :eek:
[Captivate Android Development] slytidar:
thats so nice

with the curent settings from sephhi, i get to 4589

and my oc sticks .. i think thats because i dont have semaphore manager

so i guess i should use your settings, can you help me with it ?
[Captivate Android Development] Darkangels6sic6:
Re: [ROM][4.2.2]Captivating(Xperia Themed)[Milestone 2]

I only got 38ish with the 20% live oc. Something sounds wrong with that
[Captivate Android Development] 3men2:
I dont do any special changes to semaphore manager.

I just put LiveOC to 120%

Turn ON Bigmem

And activate custom voltages but don't change anything in there. Reboot and thats all.
[Captivate Android Development] slytidar:
i also get 38 .. what are you doing something else too ??
[Captivate Android Development] 3men2:
No..nothing more. But I do the benchmark after a clean reboot and give ROM a couple minutes to settle.
[Captivate Android Development] slytidar:
do yo uthink it is safe for using sephhi's nstool settings with live oc 120 % ??
[Captivate Android Development] 3men2:
I tried with no luck. settings were not sticking for me. I had unstable overclock and rebooting to recovery. But you can give it a try.

Just found out a bug. Screen security seems to be broken. I use pattern and when I have to pick size of pattern, it keeps loading again no matter what pattern size I choos. 3x3 4x4 5x5 6x6.

Didnt notice this before cuz I dirty flashed over 10.2 and It was working fine. I wiped everything and Installed a fresh M2 and found the problem when tried to change the setting.
[Captivate Android Development] slytidar:
not stable :/

guess i have to ask sephhi about his live oc

and yes that is a bug but someone already posted it so i didnt mind
[Captivate Android Development] desilla:
Hey guys i remember reading in stratosk semaphore kernel thread not to use nstools as it causes conflicts with semaphore manager.

Maybe this is the cause of your problems?
[Captivate Android Development] slytidar:
so do you have the settings for semaphore manager ?
[Captivate Android Development] kinggame992000:
Re: [ROM][4.2.2]Captivating(Xperia Themed)[Milestone 2]

Just flash m2. And I notice no semaphore manager app in the Rom, so I just try overclocking with setcpu for now.. So far the Rom feel snappier even though quadrant score lower. This is the 1st time after flashing I notice it faster lol. Thank shephi
[Captivate Android Development] rmntruexjr:
Found a trick....If you use semaphore app for voltage it doesn't show the extra step so I never tried it...turns out it is what is resetting the voltage...

In the semaphore app, the L0 setting is actually the 1200 step not the 1000 step.....so when I set nstools to 1350 for the 1200 step it was going back to 1325 because of the semaphore default L0 voltage .....so disabling nstools voltage and using semaphore voltage you can set all but the 100 step if you have it enabled..then reboot.... The voltage stayed for me then but I had no control over the 100 step or the int voltage.lol so here is what I did....in this order....

I used setcpu just for monitoring purposes, nothing was set in it........In nstools I enable the 1200mhz step and that's it. Then In semaphore, I set the voltage....this is mine: L0-1350, L1-1325, L2-1275, L3-1100, L4-975....That takes care of the 1200 step down to the 200 step. Then in my case, I set the live oc to 120%, and also set bigmem, bln, and I used the 3072KB sd read ahead. Then reboot.

At this point I was at 1440 for the cpu and the voltage stuck....setcpu showed the voltage and cpu settings had stuck through a reboot....But what to do about the 100 step and the int voltage???......

I loaded nstools and went to the voltage tab and unclicked the default voltage setting....then, only touching the 100 step and int voltage I set them as I wanted. In my case....100 step-975....int voltage 1200mhz-1150mv, 1000mhz-1125mv, 800mhz-1125...and 1100mv for the rest...

Then I backed out and rebooted......after the os loaded I used set cpu to check and sure enough, the voltages set in semophore app stuck and the voltage I changed in nstools stuck. I am sure of it because the 100 step was 950 before i changed it in nstools and now in setcpu it said 975, so I can only guess that the int voltages stuck too since setcpu doesn't show those.....

one thing to note though...after I did all this, if I look in nstools it says the voltage for the steps I set in semaphore are reset but it is wrong. when I look with setcpu the voltage is as it should be.....

I know what I wrote is a mess, but It worked for me and I'm scoring 7300 in an3d and 5500 in antutu.

Edit: I just did the same thing on my second cappy and had the same results.......although I did notice if you open up nstools it does try to default my first four steps but after I get out of nstools I can either reboot or click apply again in semaphore voltage to get them back....lol

Edit2: still running great and I even found that I can load nstools to go higher than 120% live oc and as long as I dont go to voltages, It doesn't mess em up....I am running 1488 using 124% live oc...don't know if it will be stable but it ran through antutu bench and scored in the 5500 range.