yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] johnnyrichter:
Also just had another weird issue, but only once.

I noticed my phone had a sleep-death so I turned it on and threw it on the bed for a minute. When I checked back on it not a minute or two later it was at the ATT bootup screen again which means at some point in the bootup process it looped. On that second bootup it loaded the ROM just fine but it was a little laggy for a few minutes and Google Music kept crashing...not even sure what that is and honestly didn't know it was on the phone.
[Captivate Android Development] tonitron1:
Yup my media volume is definitely turned up, as I do hear the sound when i press the button for the microphone and when the search results come up, i just dont get the voice talking to me...
[Captivate Android Development] cvcduty:
I had this happen on v4.0 NDD also. Clearing media and rebooting seems to fix the problem.

---------- Post added at 09:44 AM ---------- Previous post was at 09:42 AM ----------

I got my first SOD on v4.0 NDD this morning. I pulled it off the charger and it was definitely on... When I checked my phone about 45 mins later (no use... in my pocket the whole time), it was frozen with black screen... could not power on. I pulled the battery to get it to boot... weird...
[Captivate Android Development] carlosgardel:
Me too, Because I read here check my ringtone and was changed to Unknown Ringtone. Im sure user Bozolini would say that we are inexperienced users and that happens to us because we dont know nothing.
[Captivate Android Development] 3men2:
I just tried that in my cappy running V2 NODATADATA and for me it is working correctly. I get the dialogue screen to cut/copy/paste and works good. I now have 120 hrs Up Time without a single FC, SOD. Not a single issue so far. :victory:
[Captivate Android Development] raenye:
I get this too whenever I have deep idle enabled; once the screen is off, it doesn't turn on.

Solution: disable deep idle (settings are in devil kernel config/devil kernel manager).

Speaking of bugs -- does anyone else get sometimes a green tint on screen unlock?
[Captivate Android Development] bdithug:
Not quite a tint, but a quick green flash on the screen. Its only a flash for a split second then it goes away
[Captivate Android Development] 3men2:
Its not a ROM bug... it's a Kernel bug.

Download Devil Kernel App from play store and set gamma offset color hack to "0" for all 3 colors.
[Captivate Android Development] illusoryphoenix:
Has anyone had any issues connecting to Google? I installed this ROM this past weekend and everything worked great (thanks Aces!), but for the past few hours, I've had spotty connection with Google's servers. I can connect to anything else, whether Wi-Fi or on the cell network.

Anybody have any ideas?
[Captivate Android Development] MrSwiss876:
yeah been having that same problem a few hours now....
[Captivate Android Development] gitah:
I have the same error :angel:
[Captivate Android Development] iregret:
Is ace still gonna update this?
[Captivate Android Development] AceofSpades90:
The thing is, this rom uses Galaxy Nexus apps. This is problem why? It confuses Google in believing YOU are running galaxy nexus. What you are running is the latest source code from Google. Heck even when you first time install LANIGHT it should have sent you an email like:

Coincidence? I think not! Google blocking LANIGHT from it's server...

Anyways... Settings -> Apps -> Google Account Manager -> Clear data and force stop then reboot.

EDIT: Though it still gives an error... Flash gapps from goo.im

EDIT: My bad, well known JB issue..
[Captivate Android Development] :
Only thing I have to say is linkception is not cool. Linking to a download is great. Linking to a post that links to another post that links to a download is just... weird.

Good rom.
[Captivate Android Development] AceofSpades90:
I'm not too sure. I have college and exams... I'll see what i can do. Might only focus on major updates like v5.0 and whole numbers. Will keep a close eye on the thread but i do like people helping each other out. It's more natural that way. Don't get me wrong, this is a development thread after all. You learn from your experience or someone else's. Me fixing problems doesn't always give you a learning curve is all im saying.

Feel free to flash any other rom if you may wanting to.

EDIT: Let me know if you guys like CM10/AOKP or any other rom of that matter you want to see LANIGHT using it as a base. Compiling and updating repo is a pain. No one seems to like AOSP anyway... (:

EDIT EDIT: Most of the bugs reported are either repeated for thousand times or either irrelevant. Some asked if Datadata and nodatadata has the same partition layout even though it has been discussed in great details several times... Other issues are solvable like ext-sd can be mount from recovery... others can be as simple as not overclocking/idle or flashing a kernel or going under settings -> tv out -> and turning off backlight. The only legitimate issue i see is with the ringtones and that im working on to fix whenever i get done with my exams...

Yes, i do realize what a bug is when i see it. Famous WiFi bug in the initial states of the rom was the only bug that i had to turn my brain off and start from scratch even though i had no problem nor most captivate users. Please search the forum for help and it may very well already been answered.
[Captivate Android Development] MrSwiss876:
I already have the latest gapps from goo.im .....
[Captivate Android Development] bdithug:
My gf's stock galaxy nexus can't connect to google now either. It can sync the account contacts, email etc fine but can't connect to Google Now. Probably a Google issue
[Captivate Android Development] AceofSpades90:
It's the same issue here...

EDIT: its working again xD
[Captivate Android Development] illusoryphoenix:
The fix is to clear cache in your browser. Just did it and now Google Now works happily :).
[Captivate Android Development] Monfro:
I would suggest AOKP as a base: it is really snappy and smooth.
[Captivate Android Development] johnnyrichter:
I was using CM9 ICS for a long time on my cappy and loved it. I've had AOKP ICS on my GF's fassy and we both love it. Your ROM is the first JB ROM I've tried on my phone, and I don't feel that any of the current fassy JB roms are stable enough for my GF(noob) to use.

My problem is I have a cappy so I get the "can't install to X or Y" and/or "not enough space on X or Y" errors thanks to how samsung designed this phone. This is why I am currently running your v2 nodatadata because it seems to be the only ROM I like that doesn't give me those issues.

With that said, I like both CM and AOKP but wouldn't be able to use them if they cause those errors for me like official CM and AOKP do.
[Captivate Android Development] nadaltennis77:
I don't have a solution for you, but what I can say is that I've been using cm10 (Cbalts hellybean) for at least one or two months now and I have never gotten either of those errors. I am thinking about trying out this rom as it looks very promising, but don't expect it to give me those errors either.

When exactly are you getting those errors? Within clockwork mod recovery? Or after your initial boot up of the rom? When you install apps? A bit more info might help us

---------- Post added at 06:32 AM ---------- Previous post was at 06:24 AM ----------

+1
[Captivate Android Development] johnnyrichter:
I get them while trying to install a new app, or even update an existing app, usually just the "can not install to internal storage or sd card." I think after X amount of space is taken up in /datadata/ the phone stops letting me install anything to internal or external SD, and even gives me that same error when I try to move an app to SD to make room on internal. When this happens I can usually delete an app to make room for a new app. I only have a few apps, a few games, a small contact list, never use video recorder, rarely use camera, etc. Nothing that would take up too much space.

It is my understanding that this is the fault of the phone and certain ROMs make the problem appear. It could also be another issue with these first-gen captivates, like the sleep-deaths my phone also suffers from.

So far I think CM9 was the only ROM that gave me the problem. Any other ROMs I've tried weren't on my phone long enough to see if they had the same issue. I heard nodatadata ROMs bypass the storage problem which is why I tried OP's v2 nodatadata and so far it runs great.
[Captivate Android Development] AceofSpades90:
OK here are few things... your first issue can be solved by any CM10/AOKP or its derivative rooms that don't use data data. Nodsyadata in theory gives the same partition layout as recent CM10. CM9 uses old data data.

About your sleep death issue. I have no sleep deaths the whole time I'm running La night. I don't know where you bought your phone but I'm sure its not the phone. Why phone goes into sleep death? Several reasons ranging from overclockong to enabling idle. Some kernels/rom seem to set too aggressive of a LMK(low memory killer) that kills off any task running in background and thus sending your phone in a low power state. Sometimes you have an Ill choice of your governor which doesn't play well with all power saving frenzy and leaves your phone unusable while its snoozing. In simple words, your phone may not be the culprit.

Edit: wipe your init.d settings and flash another kernel if issue stays. Yes there are 2 more kernel choices with NODATADATA.. semaphore and CM10 kernel... if you don't know about them... I say you do research other then coming with such a bogus conclusion.
[Captivate Android Development] raenye:
Any idea if these are compatible with datadata?
[Captivate Android Development] AceofSpades90:
Not compatible with datadata. Since only JB kernel that supports new datadata partition is devil.
[Captivate Android Development] AceofSpades90:
The problem is stability...
[Captivate Android Development] Monfro:
Build 2 is stable.

Now code is mature (even if some features are not yet ready, most of all arw there and works )

Sent from my Captivate
[Captivate Android Development] ChuckDaEngineer:
My Opinion

Ace, you should do what you enjoy. My two cents is you are a talented AOSP developer like krarvind and I would hate to see you move to AOKP or CM10 as a base. Hell, I can build those. Your AOSP is fast and stable and I would miss it. I would survive just fine, though, so build what you enjoy and share as you see fit.

Thanks for your work.
[Captivate Android Development] mbonus:
Plus a million!!!!!

The only minor annoyance has been the ringtone issue, and even that, for reasons unknown, has stabilized on my device. 4.2 dd daily driver
[Captivate Android Development] TheGrub:
Ace, I've been a huge fan of your work and 4.2Datadata has been my daily driver since I installed it !

I hope you continue your amazing work so we can enjoy our Captivate for a little while longer :) :) :)

Thanks
[Captivate Android Development] kedster:
High there, I would usually try to read all of the thread or at least skim it, but im a student and i know its an excuse but its just not my priority right now. So I was wondering whats the advantages and disadvantage and purpose of Datadata and then the same for nodatadata
[Captivate Android Development] blively2:
Being a busy student is the dumbest reason I've ever heard of as an excuse for not wanting to read. Stop being lazy and read!!!

Can you imagine trying to get by in school by just asking the professor to regurgitate all the info in your text book because you didn't feel like reading???? Amazing!
[Captivate Android Development] Monfro:
I have tryed LANIGHT nodatadata 4.0 and i have to agree.

Rom is really smooth and snappy.

Probably the smoothest rom around.

Congratulations AceofSpades90!!

Going AOSP means less built in feature, but really more speed.

I am also thinking that going AOSP is a great choice (with both partition layouts).
[Captivate Android Development] cvcduty:
I would agree... AOSP keeps things simple. I came from using another AOSP rom (TeamNyx) for a long time so I personally prefer AOSP based roms.
[Captivate Android Development] ChuckDaEngineer:
If you don't have time to read, you don't have time to be goofing around with your phone. Stay stock and stay in school.
[Captivate Android Development] Snow_fox:
I just want to second a lot of what was said here.

I moved *FROM* CM10 to LANIGHT.

I haven't regretted it yet.

I've found while there are still a few hangs here and there.. generally speaking LANIGHT is a much, much, smoother experience than CM10.

With all of that said, we are the end users and you don't owe us jack. If you want to move on to other projects then, I'll just stick with V2 nodatadata since it's stable for me.

CM10 is nice and I appreciate the effort they put in but, if I wanted CM10, I'd use CM10. I tried it, found it to be less and less appealing since CM7 for a variety of reasons.
[Captivate Android Development] kedster:
I do almost take offence to this, it is is a simple question, and actually it is becire u am already reading 4 books and have papers to write, as well as try to get some of my joy reading in. In addition I do try to have a soacial life.

Now i do have time to read, I read the first page, and i have read many other materials on flashing, i have flashed many phones and helped others, but i have never really understood the datadata thing, so i thought i would as. Also, I dont have time to read, because its 67 pages, and they are not just problems and answers they are also random discusions. My phone is running helly bean 14 right now and i wanted soemthing a little smoother, and i know i have had issues with datadata before, but no one ever seems to want to answer or even link to an answer. I know how to fix it but i dont know what im fixing because there wenrt anwers
[Captivate Android Development] johnnyrichter:
The first generation captivates had a sleep-death issue that was known by ATT and Samsung. There was this whole phone-exchange program they offered to customers that owned the first-gen captivate which allowed them to exchange the phone for a revised captivate that had the sleep-death problem fixed. Some of those first-gen cappies had the issue constantly even with stock software, some only had it on third-party ROMs, some only had it with certain kernels, some only had it when overclocked, some only had it when certain apps were installed, etc. When I have some time later today I can link to you the "official" XDA thread that documented all this information and also gave a list of the model numbers affected...every cappy up to a certain model number had this defect but not all suffered from it the same amount or under the same circumstances.

Some apps are claimed to make sleep-deaths happen more often, deep idle being enabled has also been blamed. Some say you can reduce the sleep-deaths by increasing your idle clock or increasing the voltage for your idle clock. Some say you can reduce the sleep-deaths by disabling deep idle although this is usually disabled by default on most of the popular kernels/roms(in my experience) so deep idle may be completely irrelevant to the problem.

I have found that my phone suffers sleep-deaths the least on stock software. On third party kernels/roms I can reduce the amount of sleep-deaths per day by increasing my idle voltage which reduces them to 1-2 a day, sometimes less than that.

So put simply...I did do my research. :)

---------- Post added at 05:42 PM ---------- Previous post was at 05:35 PM ----------

As for what base you want to stick with, AOSP has been treating your end-users properly so perhaps you should stick with that? It's smooth, it's fast, and it's what you're use to at this point. Sure some of us like to have things like a ROM settings menu but this is AOSP and we knew what we would/wouldn't get when we came to this thread.

I'm still on v2 nodatadata and I have no plans to change to anything else unless a new version of nodatadata comes out and it's just as stable/bug-free as v2. I do miss some of the things that came with having CM or AOKP, but I'll gladly trade those perks for stability, speed, and no storage problems.
[Captivate Android Development] bdithug:
I won't bust ur chops because I am a student as well and know that the effort that some people put into ripping on u, they could have very well answered ur question.

The main difference I believe is nodatadata is one big partition to work around the low storage warnings. It uses storage space more efficiently.

Datadata has 2 partitions (one being data and the other datadata) which results in some people running out space on one partition which forces them to move things to the SD card.

That's my take on it. Not sure if its 100% accurate but that's what I think the difference is
[Captivate Android Development] kedster:
Thank you very much, I believe that it makes it much simpler now.
[Captivate Android Development] nadaltennis77:
What is the advantage to using the datadata version then?
[Captivate Android Development] AceofSpades90:
Keep an eye on thread. Will post v5.0 test just for the hell of it.

EDIT: It's Uploading... Give it 20 minutes. You know where to find it ;)
[Captivate Android Development] iregret:
Nice been waiting for this. :D

Edit: Does it have nodatadata version?
[Captivate Android Development] AceofSpades90:
It's a secret. You'll know ;)

EDIT: Upload complete xD
[Captivate Android Development] Snow_fox:
Well, I'll be sure to check it out. :D

Edit: dling now.

Edit #2: I'm just getting a black screen.. It never really loads past the devil kernel screen. For some reason the screen goes black and if I touch the capacitive buttons they light up but, the screen itself remains black never loading. I'm attempting to load this from V2 nodatadata.

going to experiment around and see if I can get it to load maybe.

Edit #3: Tried installing it straight on top of V2 nodatadata, then tried wiping user settings 3x + cache partition, then tried installing it. Yet again, I only got a black screen where the capacitive buttons would light up but, not actually doing anything.

Restoring V2 now and going to bed.

Hope others have more luck than me.
[Captivate Android Development] bigtree_zhang:
How to process it? I met same problem.
[Captivate Android Development] johnnyrichter:
This has been answered numerous times on the last few pages.
[Captivate Android Development] blively2:
I'm not seeing v5...where might I locate it?

Sent from my JB-powered Cappy that Apple would LOVE to ban...
[Captivate Android Development] ChuckDaEngineer:
Follow the OP link to 4.2.1_NODATADATA and that takes you to the XDA hosting site where Ace has his latest releases. There is a test folder that holds V5.0 but I have not been able to get it to install. I got the black screen of death when I dirty flashed it over my V4.0_NODATADATA daily driver so I restored the nandroid I made and switched it to my development Cappy. Since then I haven't been able to get it to boot but I am going through a methodical "kernel change/reflash V5.0 clean" process. Next I will install V2_NODATADATA and go from there. So far I have tried the latest Devil kernel and the latest stock CM10 with a virgin flash from stock GB KK4 with no luck. I might try flashing CM10 if I can't get V2 to install. It is fun to goof around with.
[Captivate Android Development] treau:
I tried everything in my bag of tricks too. Dirty flash over v2,v4.0, v4.2, then tried a clean flash. Then flashed semaphore 2.0.3c and the new one. Nothing seemed to work. I even changed out the bootani in the flashable rom hoping it was just a bad file. Still can't get past the kernel screen. I don't have a secondary cappy , so I'm am done trying things before I brick, until someone else has a breakthrough.
[Captivate Android Development] oriveradel:
I had the same issue..I formated SD card completely clean up after I backed efs folder..the started off with data data v2 beta..did not install any APpS and flashed

4.2...data data
[Captivate Android Development] treau:
I made some progress on v5. I got it to boot into a boot loop. What i did was change out the boot animation in the original zip, then i flashed it on top v2 no datadata. Once it got done, i went back into recovery and flashed devil 1.4.2 kernel. at least it is booting past the black screen.
[Captivate Android Development] MrSwiss876:
seems like too much work to move from V2 to 4.2 or 5 NODATA -_-......
[Captivate Android Development] AceofSpades90:
Yeah nodatadata just hates to get updated for some reason while data data on the other hand...
[Captivate Android Development] AceofSpades90:
Good News: Will upload Stable release for 5.2_nodatadata in morning (Problem was incompatibility with the newer Devil Kernel... CM10 influence will force us if we move to newer kernel to use CM10 drivers...)

Bad News: Complete AOSP experience ;)
[Captivate Android Development] johnnyrichter:
Stable meaning it will be free of the flash issues that 4.0/4.2 had? That's the only thing keeping me on v2 nodatadata.
[Captivate Android Development] AceofSpades90:
Yes. You can flash it directly with a complete wipe.
[Captivate Android Development] treau:
I'm all charged up and ready to flash...
[Captivate Android Development] TheGrub:
Ohhhh yeeeahhh ... A NoDatadata comeback !!!!

I'm ready.... Hitting Refresh every 30sec :P
[Captivate Android Development] blively2:
Ace, when you say "morning", what time zone are you in? ;)

Sent from my JB-powered Cappy that Apple would LOVE to ban...
[Captivate Android Development] AceofSpades90:
Changelog: v5.2_NODATADATA

- Most recent syned sources from Google

- Stripped down version and "pure" AOSP (yes, no notification toggles or anything. It was causing problems)

- Took out bunch of scripts that weren't working

- No need to flash gapps anymore

- Ringtone issue solved (Been running for 2 days without any issue)

- Revert back to the 1.4.1 kernel

- Many more things

- Flash it and you'll know the rest of the changelog

Download: HERE xD
[Captivate Android Development] Snow_fox:
Tried v5.2

I had no wifi with it.

Reverting back to V2.
[Captivate Android Development] s0ul_ali:
Google play is not working app and from browser as well since few days I'm on DATA DATA 2. Any suggestion?
[Captivate Android Development] :
Flashing now.
[Captivate Android Development] blively2:
Flashed, installed perfectly first time:thumbup:and everything checks out and working properly as should. Great work on this one, Ace thanks for the tireless efforts on your part!! Without your hard work and dedication to this rom, we'd all be just settling with sub-optimal jb flavored roms.

Sent from my JB-powered Cappy that Apple would LOVE to ban...
[Captivate Android Development] Snow_fox:
You're not having wifi issues?
[Captivate Android Development] xisque:
Installed v4.2_Datadata, very responsive snappy, etc.

It killed my efs folder and replaced my IMEI number for some wierd number. Ill restore it later.

Still no clue the difference between Nodatadata and Datadata.
[Captivate Android Development] blively2:
No...none whatsoever.

Sent from my JB-powered Cappy that Apple would LOVE to ban...
[Captivate Android Development] tkjeeper:
All good here too. Wi-Fi fine. Only issue I just found is it seems the lock screen is transparent, other than that, lightening fast!
[Captivate Android Development] Snow_fox:
Peculiar, I'm glad others aren't having the same issue but, I wonder if I did something wrong.
[Captivate Android Development] blively2:
Just rewipe, reflash, etc...wouldn't hurt...

Sent from my JB-powered Cappy that Apple would LOVE to ban...
[Captivate Android Development] Organized_Chaos:
This is a great ROM. So far, I've only had one force close. Other than that, it's been lightening fast.

I chose this ROM so I can add ONLY the things I want. My question is... does anyone know of a thread or repository that has a list of common addons that I can flash? Things like lockscreens (like the ones found in CM), battery bar, toggles, etc? Or are there just apps that I need to download to get this functionality?