yashsingh1/xdaforums huggingface dataset:
[Desire Themes and Apps] salvi1379:
Hello everybody, I'm not sure if this is the right place to post my thread, if it's not I'm sorry ;) I'm not a developer so i would like to know if it's possible to set a transparent background in android settings menu instead of the black one. Thank You !
[Defy Android Development] peetr_:
Sometimes someone forgets to backup something, so this is a solution for this case.

1. Download this http://modmymobile.com/forums/402-g...81-sbf-mbn-depacker-alpha-3-05-13-2010-a.html

2. Open the Motorola depacker, then click on Open from file, find your .sbf firmware and open. Then click on split to folder.

3. Download explore2fs - http://www.chrysocome.net/explore2fs

4. Open explore2fs, click on open image file, click on file type and choose all files, find in the splitted .sbf folder CG39.smg file and open it.

Now you have all stock system files, right before your eyes :)
[Nook Color General] GuestD2201:
Hi there,

I just flashed phiremod v4 on my nook color and I absolutely love it, except for 2 things:

1) How can I change font to the default one? This custom font makes my eyes bleed when reading twitter

2) I tried to play some m4v files with movies, that were playing normally on froyo, and got "Sorry, this video cannot be played" message. What should I do to make it play?

Thanks a lot!
[Nook Color General] lschroeder:
Been debating between phiremod v4 Gingerbread 2.3.2, phiremod BETA 2 Froyo 2.2.1. Currently 2.1 overclocked at 1.1. One of the main issues for me is video playback. When I use Movies or RockPlayer Lite with hardware acceleration everything is great. If I turn off hardware acceleration RockPlayer Lite sync is terrible. I have read the for phiremod v3 that RockPlayer Lite worked but because of the lack of hardware acceleration had the sync issues. Guess only way to get proper video playback with phiremod v4 or higher is to wait until the developers add it to the nightly. Does the phiremod BETA 2 allow hardware acceleration since they were playing normally in Froyo?
[Nook Color General] hongkongdisney:
phiremod v4 Gingerbread 2.3.2 is not support video playback...

I hope the developer will get this work soon..
[Nook Color General] GuestD2201:
Guys, any clues about changing the font to the default Android font?

Also, I would be grateful if somebody'll mention these 2 problems in phiremod topic in Developers branch(here), since I don't have enough posts to write there.

lschroeder

,

sorry, don't have an answer about BETA2, I will probably try it tomorrow and write the results here.
[Nook Color General] lschroeder:
I went over to androidtablets.net and to this thread [ROM][Feb. 15 2011] >> phiremod nook BETA 2 << Themed Froyo 2.2.1

There are several reports of video not playing correctly in BETA 2.
[Nook Color General] dvrdwn:
I just burnt the image to my 8gb sd card and installed it in the NC. then I rebooted the NC and all is well. do I now turn off my NC and take the sd card out or just run the NC off the sd card all the time?
[Nook Color General] GuestD2201:
You can remove the SD card and boot from nook. But be sure to format your SD from computer, not from the nook, before you will start using it as usual storage.
[HD2 Android Themes and Apps] rasumia:
Dear i have been searching desire HD theme for HD2 but what i found is that i like ROM from one Chef and Theme from another Chef. but couldnt find standalone theme for DHD. i hope one of our expert friend would start work for theme for DHD. Chef might choose a base like 1.72 or 1.84... cause most Chef are trying to get as stock possible...

for me i like the Glass Theme very much but i want it in Rafdroid/imilka DHD Rom.

thanks a lot! :D

Edit: I got Skins here but full theme would be much better. I am not sure if i will get response but i will wait...

Edit: We have UOT Kitchen where we can make our own theme if we like that can be found here
[Touch HD Themes and Apps] hwarang:
Hello, how to change the call screen windows on my blackstone because i dont like it?
[Touch HD Themes and Apps] lumisab:
Hi

show me a picture from your call screen that I know what you mean,maby I can show you how to change
[Touch HD Themes and Apps] hwarang:
I am fine. Installed Iconsoft phonex 2.1 :p
[Captivate Android Development] atinm:
For developers only!! We are not supporting users yet

The instructions to build Gingerbread are on http://cmsgs.com

If you intend to develop for Captivate, you are welcome to use the instructions to build from source and test/debug/fix. This is not for the average user right now and we ask that you do not post binaries for users because things are unstable and we'd really rather not be dealing with users who've managed to screw up their phones.

There are two steps initially - first is to flash and convert filesystems, update recovery, kernel and CM7, but after that you can just install the CM7 zip if you have done another rebuild as you do development.

There is no easy way of going back to froyo - you would have to flash to stock via Odin one-click and let it blow away the filesystem etc. This is why it is for developers only - it is very alpha and you will find yourself going back and forth a lot.

Warning - this will eat your kitties and possibly your doggies and goldfish too!

-Atin
[Captivate Android Development] davwman:
I dont mean to ruin the thead but, just want to say thanks to all devs working on cm7! And look foward to running cyanogen again after using on my htc magic a couple years ago!
[Captivate Android Development] geokhentix:
Building right now...I am the excite.
[Captivate Android Development] nissy86:
good stuff.

can't wait to see the first gingerbread rom on captivate.
[Captivate Android Development] shawn122:
Why the hate? Take a chill pill.....
[Captivate Android Development] vunuts:
Because he likes to act like a little kid in just about any thread that he can.

There's always gotta be one douchebag.

Anyways, let's keep this thread clean.
[Captivate Android Development] ih4ckback:
That **** isn't needed here. Building now and pretty stoked. Thanks!
[Captivate Android Development] Neckrobeard:
I am the excite.
[Captivate Android Development] bamonkey:
Im interested in trying to impliment voodoo sound. Ive been following this http://code.google.com/p/cyanogenmod7-for-samsung-galaxys/issues/detail?id=16 and it looks like it wouldnt be too hard. Any ideas on how easy or hard this really is or what i could try to do on my end to try to add from supercurio's repo? *see his nexus S thead from the link above*
[Captivate Android Development] gandalf21502:
Thanks in advance for all those who cook up some GREAT ROMS!!!
[Captivate Android Development] cchant:
Getting errors on sync. 'Bad head' not at my computer so can't get exact error
[Captivate Android Development] atinm:
Try again - seems to be working here.
[Captivate Android Development] atinm:
Since all the code is on github, both for voodoo sound and for CM7, you just need kernel/android smarts to pull in the changes. Clone the repos, take what you need . . . sorry I can't help more, I haven't looked at voodoo sound but there are others who have that could help I'm sure.
[Captivate Android Development] ballz0iron:
Error in line 1380 of project.py, in GetHead fd = open(path, 'rb')
[Captivate Android Development] ih4ckback:
I got this error.

error: revision refs/heads/master in manifests not found
[Captivate Android Development] cchant:
I got both of those. Clean repo
[Captivate Android Development] Kaik541:
this is an error with repo/your machine, not CM7. try syncing again after a while (possibly after a reboot) or clearing out the folder (including your .repo folder) and trying again
[Captivate Android Development] ih4ckback:
Actually I should clarify, I got that error trying to init the GB initial flash repo. Any assistance? I need to start there since I don't have it or do I not really need it?
[Captivate Android Development] atinm:
Sorry guys - there should be a -b gingerbread on the repo init -u git://github.com/teamhacksung/android.git -b gingerbread, I've fixed the wiki page with the instructions for the initial flash.
[Captivate Android Development] ih4ckback:
I seeeeeee. Syncing now lol.
[Captivate Android Development] smithisize:
I'm getting a lot of errors syncing, following latest instructions here.

More info in my other thread here: http://xdaforums.com/showthread.php?p=11693061#post11693061

Basically, not being able to fetch A LOT of packages...

Regards

Smith

EDIT: I went ahead and let it finish syncing with errors, and attempted to continue with the process. Synced google apps and rom manager stuff fine. But, I can't even build the kernel because the contents of ~/android/system/ never populated, and I mean no files nor subdirectories, therefore nothing to build with :(

Ideas on how to solve this? I tried syncing the repo again and it updated a few things, but still didn't manage to download any kernel stuff...
[Captivate Android Development] atinm:
The errors look like they're networking related on your end.
[Captivate Android Development] smithisize:
Hmm, I don't know how though :/ My connection is pretty good here... do I need to use a different DNS server than the Qwest default??
[Captivate Android Development] Kaik541:
just keep repo syncing until the work tree is 100% in sync. everything will get populated then and it'll remember what it does and doesn't have every time you try to sync again.
[Captivate Android Development] smithisize:
Ok, well I synced until it said:

Fetching projects: 100% (230/230), done.

Yet, ~/android/system/kernel still doesn't exist :/
[Captivate Android Development] .Candy:
Clean out everything. Go to ~ (your home directory) and press CTRL+H, assuming you're using Ubuntu. This will show all hidden files. Delete anything with the name repo in it. Also delete the bin folder and android folder. Then follow the instructions again that're on the website from the very beginning (except for aptitude stuff). My issue was because atinm forgot to put the -b parameter in the instructions :mad: (jk, it's all good). So I'm syncing again, and not getting any errors like before. Hopefully this'll work for you too :p

Edit: @atinm: why do you have us reboot our computer after we install repo? Simply closing and re-opening the terminal will allow the bashrc file to load without having to do a full reboot. Just wondering... I feel it's impractical and wastes time to reboot your computer.
[Captivate Android Development] Kaik541:
these are just instructions to guarantee it works across every platform. hell a simple "reload" or "bash" will achieve the same thing on most distros... this is just a stronger guarantee.
[Captivate Android Development] smithisize:
I'm at a loss. I'd love to help with all of this, but I guess too bad.

Deleted all repo data, and re synced.

"Fetching projects: 100% (230/230), done.

Syncing work tree: 100% (230/230), done.

"

"marcus@marcus-GT5662:~/vendor/cyanogen$ cd ~/android/system/kernel

bash: cd: /home/marcus/android/system/kernel: No such file or directory

marcus@marcus-GT5662:~/vendor/cyanogen$

"

Well, idk what's wrong, but I guess I'm out of the running on this project.

Good luck to those who can download everything.

Regards

Smith
[Captivate Android Development] .Candy:
The kernel folder you're looking for is found in ~/kernel.

I can tell this because from your prompt, I see that you're in a "~/vendor/cyanogen" directory. For some reason, you synced your repo to your home folder instead of the ~/android/system folder, so anything that would normally be in ~/android/system is now just in ~.
[Captivate Android Development] smithisize:
Well ****... makes me look retarded haha

Thanks!
[Captivate Android Development] .Candy:
Lol no problem :p sorry I took a while to respond; I was out at dinner.

Anyway, I finished building my CM before I left, but something's wrong... I'm flashing over Serendipity, but it gets to the Galaxy S cyanogenmod splash screen, but sits there. I'm able to reboot into recovery and flash the stuff that needs flashing, and the last step I'm able to complete is flashing cm7-captivate-initial-xxxxxxxx.zip.
[Captivate Android Development] AJerman:
I think the issue is a missing step in the instructions. It tells you to reboot your system, then you sync your repo, but it never tells you to cd ~/android/system before you do the sync.
[Captivate Android Development] Kaik541:
well I guess the expectation is that because you switched to that directory (and then did nothing there) that you would assume you should continue from that directory. otherwise the "cd ~/android/system" would literally mean/do nothing :)
[Captivate Android Development] AJerman:
Not if you rebooted though. I think a lot of developer type people would understand, but I can still see where the confusion is. If you reboot then open a new terminal, you're going to be in your home directory, as I expect was the issue for smithisize.

Edit: I see the wiki is already fixed, so it shouldn't be an issue for anyone now.
[Captivate Android Development] Kaik541:
I'm pretty sure the title points to this being intended for devs not for everyday users :) so you're supposed to have the capability of understanding what it is you are doing.
[Captivate Android Development] .Candy:
1. Kaik541 is correct. I did personally understand to continue in the ~/android/system directory after the reboot. If you don't understand that, then I believe you shouldn't be building CM7 and should wait for an official release.

2. That is not the issue. For some reason, even though I had cd'd to the ~/android/system directory, it would still initialize the repo in ~, but the -b parameter fixed that. This still doesn't help why my phone isn't booting.
[Captivate Android Development] AJerman:
Haha, very true, but I'll admit, even I had to take a second to see where I needed to sync to. Anyway, I wish my sync would stop going 50 KBps so I could compile this. 94% dammit! :mad:
[Captivate Android Development] Billabong81:
Same problem here. Tried also last night and had same problem. Not sure what I'm doing wrong here :(
[Captivate Android Development] tonyc0642:
When a non-developer posts in this thread, just report it by clicking the /!\ button in the top right corner of the post. Then people don't have to post about how you're not supposed to post in this thread if you're not a developer, further exacerbating the issue. Problem solved.
[Captivate Android Development] slifer315:
how big is the initial zip you made?

Sent from a phone, playing a phone, disguised as another phone.
[Captivate Android Development] Billabong81:
Mine was just under 12mb if I remember right... will go check and report back.

EDIT: FYI, I'm getting same error as .Candy if not noticed earlier.

EDIT2: Yep, it's just over 7mb. Definitely the problem for me! Now to figure out how to fix it.
[Captivate Android Development] AJerman:
Oh, I wasn't saying that would fix the issue with it not booting, just thought that might have been why it pulled to your home directory. If you had followed the directions word for word, a lot of people may have that issue, but it's fixed now either way.

As for not booting, can you adb in and dmesg and see where it's hanging? I can't help much yet since I'm still waiting for this repo sync to finish.
[Captivate Android Development] .Candy:
Oh lol I know your suggestion wasn't for me, I was just stating that my phone wouldn't boot in hope that more people would see that I was having an issue :p but thanks for actually helping now!

Uhm no, I can't... I actually got frustrated and re-flashed Serendipity (my main ROM) and am going to leave it for now, because I'm going to bed soon, and have to go to school tomorrow. I need my phone to be functional for school, you know ;)

Could you explain what you mean by dmesg? What command is that?

And could you link me to the Nexus S drivers for ADB? I looked for a few minutes in the Nexus S forums and couldn't find them... thanks (: I'll post my results tomorrow after school.

I'll probably re-sync my repo before I try this anyway, and maybe something'll be fixed, or it might've just been that my build this time was messed up. Anyway, thanks (:

Edit: Oh sorry... didn't see the post asking for the size of my initial. I hadn't noticed this before, but it's only 8.3 MB.

That's an issue... in fact, that's definitely an issue. I just unzipped it and the only thing in /system is build.prop. Probably a re-sync and build would be best, but I'll do that tomorrow. Thanks for pointing this out (:

PS: I noticed that the build file said I was on a 32 bit OS and it required 64, though it continued building anyway. Would that be the issue?
[Captivate Android Development] Billabong81:
I've been able to get my initial zip up to ~24mb, but no higher. I'm getting a few errors at this step:

make -j`grep 'processor' /proc/cpuinfo | wc -l` otapackage

Think my problems are related to this somehow.
[Captivate Android Development] Kaik541:
your initial packages should be somewhere in the ~130 MB range. any OTA's produced should be about 85 MB. zImage about 4 mB.
[Captivate Android Development] Billabong81:
I think I might have found the problem. I had not downloaded GAPPS or ROM Manager. .Candy, try adding these commands, then recompiling:

cd vendor/cyanogen
./get-rommanager
./get-google-files
[Captivate Android Development] bubbinator91:
Yeah i had to do that to get it to compile. Also, since the the initial and ota zips convert all partitions (including the efs partition) to yaffs2, what's the appropriate way to go back to stock?
[Captivate Android Development] Kaik541:
yeah of course you need those, that's why it's included in the instructions? (right after repo init/sync)

edit: forgot to add, to get back to stock you should just use either odin one-click or (supposedly) an ODIN with repartition checked with a pit file.
[Captivate Android Development] Billabong81:
Kaik, that part of the instructions is not listed on the initial flash page. I found it by comparing the initial flash page to the other page.
[Captivate Android Development] bubbinator91:
Yep. I had to do that too.
[Captivate Android Development] AJerman:
Finally got it up and running. It's running very well too. I really need one of the new MacBook Pros. My old MacBook just can't handle compiling chores like this. I didn't seem to have any issues as long as I followed the instructions. I have to go to sleep though. I'm going to hate myself for spending this much time on this in the morning!
[Captivate Android Development] ih4ckback:
well I followed the instructions and my initial is only 27.7mbs? what am I doing wrong?
[Captivate Android Development] smokestack76:
Have you tried since the OP updated the instructions? If so did you get any errors?
[Captivate Android Development] ih4ckback:
Yeah I did it after it was updated. I'll just post my output. Everything was fine until

Install: out/target/product/captivate/system/app/DownloadProviderUi.apk
target Java: DrmProvider (out/target/common/obj/APPS/DrmProvider_intermediates/classes)
packages/providers/DrmProvider/src/com/android/providers/drm/DrmProvider.java:227: package Manifest does not exist
if (getContext().checkCallingOrSelfPermission(Manifest.permission.INSTALL_DRM)
^
packages/providers/DrmProvider/src/com/android/providers/drm/DrmProvider.java:343: package Manifest does not exist
if (getContext().checkCallingOrSelfPermission(Manifest.permission.ACCESS_DRM)
^
packages/providers/DrmProvider/src/com/android/providers/drm/DrmProvider.java:369: package Manifest does not exist
if (getContext().checkCallingOrSelfPermission(Manifest.permission.ACCESS_DRM)
^
packages/providers/DrmProvider/src/com/android/providers/drm/DrmProvider.java:396: package Manifest does not exist
Manifest.permission.INSTALL_DRM : Manifest.permission.ACCESS_DRM;
^
packages/providers/DrmProvider/src/com/android/providers/drm/DrmProvider.java:396: package Manifest does not exist
Manifest.permission.INSTALL_DRM : Manifest.permission.ACCESS_DRM;
^
Note: packages/providers/DrmProvider/src/com/android/providers/drm/DrmPushReceiver.java uses or overrides a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
5 errors
make: *** [out/target/common/obj/APPS/DrmProvider_intermediates/classes-full-debug.jar] Error 41

what does

-Xlint do and how do I use it? just at the beginning of the code?
[Captivate Android Development] smokestack76:
Xlint displays warnings for java. Looks to me like you either dont have java installed or not correctly. So start there.
[Captivate Android Development] smokestack76:
The last lines there have me puzzled. I havent had a error like that lol. So either java or issues with your drm folder missing items. Im at work so wont be much help until i get home and check what i have on my machine.

And with Xlint there is a way to add it to your compiler. So google the one you use to find out how to add it.
[Captivate Android Development] ih4ckback:
well you were right about Java its installing and I will retry and see what happens next. thanks for the help :)

Installing Java did nothing.

I'm also getting this at the beginning of running the same code.

find: `out/target/common/docs/gen': No such file or directory
[Captivate Android Development] .Candy:
Blind faith; I'm going to take my morning shower, compile with Gapps (I should've thought of that :p), and if the file size looks promising (~130MB), I'll post my results saying how much I love you guys :D

And if it bricks my phone, I guess I'll have to live one day without a phone (although that's very hard for me :o).

Yeah, this really is blind faith as I now only have one hour before I have to leave for school lol.
[Captivate Android Development] atinm:
Ignore that warning. Also, people who are developers that will be actively working on CM7 should be the only ones trying this out - this really is not ready for primetime.
[Captivate Android Development] ih4ckback:
I would be if i could get the damn thing built lol.
[Captivate Android Development] .Candy:
I/(hopefully we) realize that. I personally have experience with android enough to fix certain issues, though I doubt there's going to be anything I can fix myself, seeing as there are certain people using this as a daily driver and most of the bugs are deep in the build.

Anyway, if anyone was having the issue that I was having before, just be sure to get ROM Manager and Gapps... that fixed it for me.
[Captivate Android Development] atinm:
Odin one-click is the only safe way I know and what I use.
[Captivate Android Development] atinm:
I added the ROM Manager and Gapps download to the initial instructions - sorry about that (easy to forget because those two steps are automatic for me after a new sync ;) )

Also, I tend to flash back to Firebird when I have to use my phone for work, but keep it in CM7 for normal use. The biggest crash for me is on wifi sleep and I'm working on that bug now (its in the kernel).
[Captivate Android Development] atinm:
Try a resync, and get the ROMManager and Gapps and try to build again. We're not having problems now but I've had your exact error before and I had to make sure everything was sync'ed correctly (including using the correct branch). I might even have had to blow my repo away and do a clean sync, I forget now..,
[Captivate Android Development] .Candy:
Hmm... Firebird kernel?

Why was I under the impression that only the Nexus S kernel would work?

And I'm assuming the FB kernel doesn't have the wifi sleep? But yeah, I was aware that the wifi sleep issue was still there, and was willing to live with it ;) But if FB fixes that, then that's awesome :p
[Captivate Android Development] atinm:
I meant flashing back to stock and then Firebird when I want my phone to be reliable (or more reliable than CM7 is right now). For normal use I stay in CM7. And yes, the froyo kernel (.32) in Firebird doesn't have the sleep problem.