yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] blively2:
For me, its like going from VHS tape directly to BluRay! Ace-I'm loving the 3.2 changes!!!! Thank you, thank you, THANK YOU!! :thumbup::thumbup::thumbup:

Sent from my JB-powered Cappy that Apple would LOVE to ban...
[Captivate Android Development] skomes:
Just installed the datadata version. So far it is nice and fast, quite stripped down compared to Helly Bean.

I think the speed is overblown, it feels snappy, but coming from Helly Bean it doesn't feel as amazing as people keep saying. I do notice on certain app launches though it does seem quite a bit faster, I don't get lag when launching the play store anymore.

Going to play with it for a while longer, seems nice, may go back to HB though.

The thing I miss the most is having the weather on the lockscreen, it beats any widget, I've had beautiful widgets, go widgets, HD widgets and the Jelly Bean lockscreen weather was the most reliable and best one of all.

But I am really enjoying the lag-free experience. The annoying things that caused slowdown are gone. Switching between apps, play store etc. No more lag on launching apps. The phone feels like it has more horsepower than it does. When installing apps in the play store, clicking the search bar to search for another app doesn't lag or slow down.
[Captivate Android Development] mdoctor:
+1... All datadata versions mess up my wifi... I'll wait for nodatadata too... :)
[Captivate Android Development] s0ul_ali:
Again stuck with same problem :( with 3.2 DATADATA, phone is again & again booting back to recovery. I tried

factory reset x 3 times

Wipe Cache

Wipe davrik cache

Wipe mount -> data/datadata/system/cache

wipe int'll

wipe Nstools setting

Install zip for SD -----> ( in mid recovery phone rebooted and back to main menu of recovery)

Again Installed zip from SD ---> ( zip installed smoothly)

reboot

since then phone is getting again & again to recover :(

2ndly I wipe boot in mount and phone got restarted now not even getting to recovery :( need help in both issues ..
[Captivate Android Development] skomes:
Yeah with 3.2 Datadata my WiFi no longer turns on. I don't mind too much because I have 6GB of data so I can use that.

That sucks.

My phone rebooted first install into recovery and 2nd install worked fine and it was all good. If you can't get to recovery, download Odin and flash back to stock ROM. You can also find Odin-1-Click where you just download the file and it does all the work, no downloading any extras.

You just need to get Odin, put your phone into download mode and then flash a new ROM.
[Captivate Android Development] s0ul_ali:
can i only flash CWM & kernal then boot in to recovery ? and recover fron nand?
[Captivate Android Development] skomes:
I have no idea.

I got stuck in a bootloop installing Helly Bean because the speedmod kernel in the forum flashing guide doesn't work with stock Gingerbread.

I downloaded an Odin-1-Click install, ran it and was back on stock and then tried again.

Odin can flash kernels though, through download mode without recovery, so it may work.
[Captivate Android Development] s0ul_ali:
Thanks but did flash only CWM Kernal and then formated SD card on laptop copied backup from PC and back again :)

But still y can't I install 3.2 on my phone :( thats a big issue, first edition & 2 data installed smoothly but 2 NODATADATA & 3.2 DATADATA are not installing ....
[Captivate Android Development] shariqm:
v2.0 NOdatadata is fully functional but has some issues:

Many times even though my screen is off my led buttons are lit, i.e. back menu, home, search and home button which doesn't help with the weak battery peformance of the rom (most likely cuz of Google now, a JB feature, cuz it keeps tabs on you so much),

2) Search button soft key only takes you to google now (I disabled google now but it still takes you to the google now homepage [without any cards cuz google now is disabled]

3) Voodoo sound (most likely NON-rom related issue, but if it isn't please look for fix) keeps resetting to default settings, particularly after reboot (even though "Restore at launch" is checked- which brings me to point 4:

4) SetCPU or other overcloking app always resets after boot so you wom't enjoy the 1400MHz Devil Kernel overclock

Like i said though, ROM is FULLY functional and very smooth
[Captivate Android Development] bik2000:
Install BLN Control to turn Backlight Notification off. https://play.google.com/store/apps/details?id=neldar.bln.control.free&hl=en

Or Devil Kernel Config. https://play.google.com/store/apps/details?id=de.hilbring.android.devilkernelconfig&hl=en
[Captivate Android Development] AceofSpades90:
This is because you get a notification. I think it's normal with BLN, no? Anyways, go to Settings -> Tv something -> Backlight time out -> tick never

EDIT: and to help your weak battery performance... change your modem. KC1 gives the best battery life to me

Dont change your build.prop

That's unfortunately what "search" is in JB roms... You can revert back to ICS googlesearch. Or delete google now from system/apps?

I'm using Voodoo sound without resetting to default settings, rebooting again to get back to you

Try NStools. This rom is stock, please don't expect that high of a value... Did you have this issue in HellyBean?(Since it shares the same kernel). I can't help you with overclocking to which i'm against... So don't expect much from my end. It's not a stability issue.
[Captivate Android Development] bdithug:
Is it safe to remove Google play music? Are any other apps dependant on play music to be installed?
[Captivate Android Development] AceofSpades90:
Yeah you can delete.
[Captivate Android Development] readitodie:
just want to thank the dev for this rom. I was thinking about going back to ICS after trying a couple of JB roms. But this rom is by far the best, snappest JB rom!

Thank you thank you!
[Captivate Android Development] shariqm:
Hi Ace, I love you dude, you are super helpful. This is my first and as far as I care, ONLY JB Rom cuz it's near perfect. I say near because I hear V3.0 NoDatadata is coming up soon, and I can only imagine it being even better!

As for modem, I am currently comparing JK4 to JK3 - KC1 didn't do too good for me.

I'll try the build.prop suggestion but I've never done that so might restrain from it.

Fair enough if you're not in favour of overclocking, makes sense.

Keep up the good/great/AWESOME work you're doing!
[Captivate Android Development] kevinseto:
Yep it's perfectly safe, I did it and installed Winamp. No Issues :):)
[Captivate Android Development] cvcduty:
So I have been using the v2 nodatadata for about a week or so and I have a couple comments to add.

As mentioned, this JB rom is very usable. I was a skeptic of nodatadata at first but I have come to realize that the hard work (and a trick?) the dev has developed is definitly working. :D

However, I do notice a few minor glitches... nothing I can't live with but maybe can be improved in the next release...

I have yet to notice anyone mentioning (maybe I missed it) this, but there is a glitch with a quick discolored lock screen when being unlocked. I had seen this on other ICS roms where the lock screen appears reversed for a brief second before it's back to normal. When it's in this state, the screen can't be unlocked. Like I said it usually lasts for a second or less so no big issues. There are times though, when if there is an operation in the background and the screen goes black, this reverse lockscreen stays longer and it is unresponsive until I press the power button again to cycle the screen.

I believe the nodatadata still does allow some slowdowns. It's nothing I haven't seen in even with other roms that do use datadata scheme, but I believe it's a tad bit worse here. I mean, when there is an operation running in the background (i.e. installing an app), the performance degrades drastically for a few seconds. Again, this happens in other roms, even datadata roms, but I think it's a tiny bit longer with this nodatadata rom.

The last thing is the fact that even with larger partition, you are still limited to how much app and data can be stored in this partition. It's something I have learned to live with owning a Cappy, so no biggie. It's just I was so excited that I would never have to deal with "low storage" warnings again but... that was not the case for me...

Anyway, I really am enjoying this rom as my daily driver. With only a very few minor issues, I would rank this as one of the best roms I have used on my Cappy. Thanks again and I look forward to your handy work with the v3 release... :good:
[Captivate Android Development] ChuckDaEngineer:
For the build.prop, you can use the OI File Manager or Root Explorer (need a root access file manager) and go to \System where the build.prop resides, rename the current build.prop to something other than build.prop and then copy over the new build.prop from your SD card to the \System location...reboot and profit.
[Captivate Android Development] takeoutttt:
You need to go to settings>performance>processor> set your desired clock > tick "set on boot"
[Captivate Android Development] MrSwiss876:
+1
[Captivate Android Development] shariqm:
EDIT: Just reinstalled the rom after wiping cache and Dalvik, and seems to be running fine. BUT just so I understand this, when I rename the build.prop file should I rename the extension? Like build.prop.old? WOuld that work better than build old.prop? thanks.

So i did what you said from Root Explorer. Changed the original build.prop to build old.prop and pasted the new one as build.prop under /system but when i rebooted I am now stuck in boot screen (15 minutes and nothing - it goes past the Devil Kernel page and is stuck on the red boot screen).

So I thought maybe reverting would help but when i went into Devil recovery and open file manager I dont see any files under /system. I've also checked show hidden files but to no avail. How can I go back to the original file?
[Captivate Android Development] AceofSpades90:
It's voodoo colors, go download voodoo sound or devil config and set all three Gamma to 0. It won't happen again (:
[Captivate Android Development] AceofSpades90:
You can't compare datadata with nodatadata in regards to write speed... Nodatadata wins that match hands down. Though, this rom somewhat blurrs the boundary between datadata and nodatadata but at a very small level. All in all it should be faster with write speed compared to new partition layout but not be as fast as datadata(it don't have that big of a partition to waste). But if you're talking about read speed, that's another story ;) nodatadata open apps faster and things such as that so unless you are downloading/installing something, you're doing everything else faster.

The rom is not datadata but it does act like one thus the low notification issue(although, you can get this in new partition layout too)... So it's because of the trick you were referring to. Compromise is crucial. You can't have good of everything, now can you? xDD

EDIT: Move some of your apps to sd card if you already hasn't
[Captivate Android Development] ChuckDaEngineer:
Hopefully you did a backup recently and you can restore to that. AFIK the ROM looks for the build.prop file on boot and will only run that file. If the build.old.prop confused the ROM that is a new one on me. You may have to reflash unfortunately. I have never had any luck with the Aroma file manager. Maybe someone knows the ADB commands to push the old build.prop from the LANIGHT zip file. Sorry for the trouble. I have been running that build.prop since Sunday without issue. BTW I renamed my old build.prop to build.prop.bak so maybe there is a script or xml that runs all the .prop files and is confused with the .prop extension on your backup. That is a really wild guess on my part.
[Captivate Android Development] s0ul_ali:
What kind of new partition layout do you use in 3.2? When I installed 2 DATADATA after wiping all the settings when I install zip from SD phone reboots and continue installation & 2 DATADATA is working fine. In the case of 3.2 DATADATA phone reboots and back to recovery menu doesn't continue installation. I tried every thing like

Factory resets x3

Wiping cache

wiping -> mount data/datadata/system/cache

clear dvrik cache

Wiping Volts of NS tools

Few time same process and fix permission after installing zip twice.

nothing seems to be working phone is rebooting in recovery again & again.

Can't understand why it's happening. I have been flashing phones for around 4 years.

Is there any other work around that shell I try? Or I'm missing some thing?
[Captivate Android Development] AceofSpades90:
Well the v2DATADATA has different partition to v3.2DATADATA(it uses HellyBean partition system). When it reboots you back in recovery, flash the zip again and wait. It flashes and repartition in the first recovery reboot.
[Captivate Android Development] shariqm:
no worries bud. I only wiped cache and Dalvik before reinstall so all my apps and data remained untouched anyhow so no need to worry about Nandroid restore. So what you're saying is you're using the build.prop Ace suggested to me with the V2 nodatadata? Cuz then that would just mean that if I change the extension i.e. change to build.prop.bak like you and paste in the new one it'll work. Most likely some script does run all .prop files on boot.
[Captivate Android Development] ChuckDaEngineer:
Yes, when I did the build.prop update I originally tested it on 3.2_DATADATA and sent it off to Ace to test and incorporate at his discretion. I then converted back to 2_NODATADATA since it is faster for me and I don't have any low memory issues and have been running it on V2 since Sunday.
[Captivate Android Development] Vo01985:
Would love to try this ROM over my current stable CM9.1 build, but I don't know which devil kernel to download/use. And not sure on how to use the difference in nodatadata and datadata version...
[Captivate Android Development] AceofSpades90:
My bad, i didn't see you were running v2NODATADATA... No wonder the reboots :P Incompatible build.prop :eek:

I'm not sure if it'll work for v2 but it was a tweaked build.prop for v3.2.
[Captivate Android Development] cvcduty:
Kernel is part of the rom...

And the difference between nodatadata and datadata are under the hood so to speak. They will function exactly the same for you for normal use... is this your concern?
[Captivate Android Development] Vo01985:
So I can just do a full backup, full wipe, and flash this ROM right over CM?
[Captivate Android Development] s0ul_ali:
That why new Helly Beans is also also acting same on my phone.

---------- Post added at 06:56 PM ---------- Previous post was at 06:52 PM ----------

I did flash it again once and twice also result is same getting back to recovery.
[Captivate Android Development] ChuckDaEngineer:
It works, I am running it now. The version number will be misleading though but I can change that. I have a couple more tweaks I am testing so I will PM you two versions when I am done with them so you can put them in each of the builds.
[Captivate Android Development] cvcduty:
So what is the trick with the Nandroid backup with this rom? Or it might be kernel issue...

Basically, I saw that there was now a CM10 M1 release out. Instead of a Nightly, they are now trying a Monthly drops which are supposed to be more stable. So I got tempted and decided to try my luck... I had tried the 9/3 build and could not deal with the lag... M1 build seems to be based on 9/10 build. It was good and smooth for about 45 mins... just about when I was done setting it back up, it started to really chug... not again...

Anyway, I had done a nandroid backup of LANight so no big deal... except, it kept failing trying to restore /system... tried about 5 times and gave up. I ended up doing advanced restore by doing /boot, /data & /cache separately. When done, I reflashed the LANight v2 on top just to be safe. So far, it seems ok. But anyway, what did I do wrong? I usually do not use nandroid but last couple times on my other devices it worked like a charm...

:confused:

---------- Post added at 02:49 PM ---------- Previous post was at 02:43 PM ----------

Yes That is what I did. I had CM9.1 and loaded v2 nodatadata without any issues. The first time you flash though, you might get what it would look like a boot loop... fear not, it wiil be fine. If it reboots and takes you to recovery again, just flash the rom again... matter of fact the OP states that you need to flash twice anyways...

Just follow the instructions in the OP.

Good luck.
[Captivate Android Development] johnnyrichter:
Just did the v2 nodatadata install coming from CM9.1 which suffered from lag and constant "can not install to internal storage or external SD" error. Installation steps weren't 100% compatible for my setup because I was running the Icy Glitch kernel but everything seems to have worked. I'm immediately noticing how smooth/fast the phone is before and after my usual 200/1200 overclock. Battery looks to be about the same or maybe a hair better.

I have some questions about this ROM...

-I went with the nodatadata build hoping to get away from all the captivate storage issues that came with ICS and JB. Was this the proper route to go? Do I have to do anything in particular now that I'm on a nodatadata build such as moving everything to externalSD after installing? If someone could explained the whole datadata/nodatata thing this would make a lot more sense to me.

-Is the baked-in devil kernel the most optimal kernel for this build or is there another I should try?

-What would be the best app to use for overclocking? I've been using Voltage Control for a while now and it's what I'm using on this ROM. Is this a good option?

-When I mount my phone via PC and the two folder windows pop up, what I believe use to be my internalSD is now empty except for two folders named /data/ and /LOST.DIR/. Is this normal? This is where I put kernels/roms/etc to flash in recovery and it use to have quite a few more folders in it.
[Captivate Android Development] Vo01985:
Hmmm alright I'll try flashing over it tomorrow then, will let you all know how it works out.

Sent from my ASUS Transformer Pad TF700T
[Captivate Android Development] AceofSpades90:
Ok once again, LANIGHT is incompatible with CM10 or any of it's deravatives(ALL JB roms I know has some sort of CM10 code in it, be it everything to big chunks. Heck, even SlimBean takes away its files from CM10/AOKP(CM10 again)). Unfortunately, Since we are incompatible with with CM10, we incompatible with ALL the JB roms. Even nodatadata doesn't use the same partition layout as CM10 though It claims to be compatible one way or the other. The only thing that is compatible I think of is v3.2 partition which ONLY use HellyBean(compiled from CM10 sources) datadata partition layout FOR it's kernel and that's it.

Ok I'm done raging, to the point now. You must be on nodatadata and I could only think of more problems for datadata folks with NANDroid backup. You only needed /boot and /system for nodatadata if it let's you choose? I never restored to LANIGHT since I never needed to, it's my daily driver. I did in past went to HellyBean to understand its new partition system for v3.2 but it's been like a week?
[Captivate Android Development] AceofSpades90:
Other then those 2 issues, whats your say on the build?

P.S: I will look into EXT SD issue in the next build since i know what to focus on.
[Captivate Android Development] swam1231:
Early results: Simple installation, Smooth & Fluid interface, WiFi working fine, No problem downloading paid apps(had this issue in a prev Rom), Both internal & external storage mounting

Not Tested: Calls & SMS (as I dont use my Cappy for phone needs anymore), Battery (but I believe it is very subjective), Bluetooth (searching for my headset, shouldn't be long), GPS

In One Word: Snappy
[Captivate Android Development] AceofSpades90:
What rom you are coming from?

So, external storage mounting working for you?

Been waiting for someone to flash and realize. FINALLY! :victory:

EDIT: Please pass on the word xD
[Captivate Android Development] swam1231:
SlimBean 2.1

Yes, but its bit of a hit or miss at the moment, which baffles me..Need to play with it more..

Thanks to you mate.. Keep up the great work. :good:
[Captivate Android Development] :
Fine with me, as long as it makes it better!
[Captivate Android Development] AceofSpades90:
Im kidding. I'll give proper credits.
[Captivate Android Development] Sword_of_a_1000_truths:
very smooth, smoother than CM10 and helly as far as my phone is concerned of course, and im liking it too
[Captivate Android Development] :
Give credits to st@matis for the original tweaks too!
[Captivate Android Development] hakim7489:
things that i like: very snappy, simplified, cool bootanimation.

wishlist for next release: clear button in notification drawer, centered clock and day option in notification, slider shortcuts in lockscreen, more free memory available.

nonetheless, well done!
[Captivate Android Development] cliftomr1082:
Running great, thanks.

One thing if possible, could you add virtual on screen buttons. I like to use them as much as possible, especially with certain cases on phone, sometimes hard to hit soft keys. Thanks for great rom so far.
[Captivate Android Development] Chuckd610:
Outstanding! This has to be the fastest ROM I have ever used. There is no lag whatsoever. I thought about implementing some of those build.prop tweaks, but I don't wanna mess up a good thing.
[Captivate Android Development] AceofSpades90:
I understand your concerns. Those are CM10 features and I'm aiming here for clean aosp experience. The problem isn't so much adding a certain feature it's more like maintaining and fixing bugs. You have to realize I'm the only person doing everything from building, maintaining to testing and uploading. This is not the only project and X-Bean team is pushing hard to release their own final build in coming days.

Anyways, I'm looking for a small team that could maintain this thread on weekdays and maybe test and hopefully tweak rom a little. Oh and someone that could come up with a logo.

EDIT: PM ME IF YOU WANNA HELP.
[Captivate Android Development] AceofSpades90:
Spread the word my friend. Thinking of a slogan, snappy ;D
[Captivate Android Development] Chuckd610:
I WILL spread the word ( changing my signature). Also, for someone who can get it done, a nice banner for this from would be great that would include the name of the rom and the developer's name. Sorry, but I'm not that advanced...lol
[Captivate Android Development] AceofSpades90:
You just said you are capable of tweaking build.prop, and I'm sure you could test new builds. Consider helping this rom grow :D
[Captivate Android Development] AceofSpades90:
If you're not busy you could help with your init.d tweaks, we need staff ;)
[Captivate Android Development] uncannyrt:
slogan: Motorhead Rom: well snap your neck! Just kidding, nice rom though. Very fast. coming from Helly bean, overclocked. i think i need to flash it again because I have no google talk.

good work!
[Captivate Android Development] AceofSpades90:
I don't remember adding Google talk .apk (:
[Captivate Android Development] uncannyrt:
Hence my confusion! , I guess I meant to say it won't give the option to install it

Solid and zippy from though

Any possibility of unlinking phone and notification volume in the next installment?

Thanks again
[Captivate Android Development] shariqm:
can i flash from ICS to this?

Hey, I'm running Team RemICS Android 4.0.4 right now with Kernel Semaphore.

Anyhow, I read you Ace suggesting someone needs to flash CM10 or AOKP prior to flashing this rom? Is this true, can I not simply upgrade from 4.0.4 to this rom by standard procedure, i.e. wipe data, dalvik cache, and flash?

thkx, super excited for this, review seem to be very positive, gj
[Captivate Android Development] AceofSpades90:
I'm planning on Odexing datadata. This might give it a tiny boost in speed so it can stay in league with nodatadata in future. This only applies to datadata. Let me hear your thoughts. We can keep it deodex but that might not help its future. Need more room in system and odex is an elegant choice.