yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] NiXXeD:
Looks like the new build is out. Gonna try and see if there were kernel updates, if not I imagine we could swap in this kernel and it should work, yes?
[Captivate Android Development] Squeak22:
Looks like there were, so we must wait patiently.
[Captivate Android Development] wmwilker:
I'm about to try :p

--EDIT--

Looks good so far. I had to redo the reorient but that only takes a minute.

Good to go!!!!

YMMV
[Captivate Android Development] Squeak22:
There were kernel changes from the 11/16 version, so there are some fixes you don't have using this old version.
[Captivate Android Development] wmwilker:
I'm not sure what you mean.

The download I had was xxx17A and this was xxx20
[Captivate Android Development] NiXXeD:
Which process did you use to flash this? Did you just drop the captivate kernel on top of the zip? Or flash separately?
[Captivate Android Development] wmwilker:
I flashed through Odin and CWM as stated in the i9000 thread. I used di11igaf's rom to start and went from there.

I just threw this on top of my current install with CWM
[Captivate Android Development] Squeak22:
What I mean is that the reorient kernel you used is based on the 11/16 drop and not updated to the 11/20 release.
[Captivate Android Development] wmwilker:
I didn't think that would matter.

In the past I would use xcaliburinhand's kernel on several different i9000 roms and it worked on all of those roms.

I assumed this would work similarly.
[Captivate Android Development] cruiserbax:
with the cognition ROMs and all similar ROMs for our Captivates, the updates are almost always strictly changes to the actual ROM and not the Kernel and when it is a Kernel change it's normally just switching to another version of a custom Kernel. With this SGS CM build they had to insert the CM initramfs into the Kernel. most of the bugs that are being worked on right now need to be fixed in the Kernel so if you're using the current re-oriented version and if there were no major updates to the ROM then you have in-fact not updated much of anything.
[Captivate Android Development] aqtrans:
Yeah we definitely need a new kernel. One of the SD card mountpoints changed, and isn't being recognized without those certain changes. Other than that, it boots and works.
[Captivate Android Development] Smallsmx3:
Are we going to get updated kernels to keep up with the i9000 beta updates?
[Captivate Android Development] Squeak22:
I'm sure we will once Glitter gets it done. Have some patience, he's doing this for fun/free (especially since he doesn't have a donate button!).
[Captivate Android Development] wmwilker:
Still working with no issues but I'm not sure if anything was added ;)
[Captivate Android Development] ademejia:
the only issue i had when i installed the captivate kernel is the internal sd card is missing. i coundn't restore my titanium back up
[Captivate Android Development] Sebring5:
Thanks to all the people who contributed to making 6.1 CyanogenMod happen. I installed with di11igaf's instructions. You can find instructions here: http://xdaforums.com/showpost.php?p=9289273&postcount=51. One key point is missing. After installing initial kernal you do not reboot. You go to recovery to flash 6.1 rom instead.

6.1 is fast and functional. Really drains the battery quick so I do not know how long I can work with it. So far so great.
[Captivate Android Development] dalingrin:
Glitterballs,

Any chance that you will post the source code on github or the like?
[Captivate Android Development] di11igaf:
your phone is automatically gonna reboot after you flash the initial kernel in odin unless you do a battery pull(not needed). when the phone automatically reboots after flashing, reboot the phone into recovery and flash 6.1

edit-and try the voltage control app to make the battery a little better if your OCed. i had pretty decent battery life with that rom.
[Captivate Android Development] Sebring5:
Thanks for your help.
[Captivate Android Development] MikeyMike01:
You can uncheck Reboot.
[Captivate Android Development] DOAlaboratories:
Any chance on incorporating raspdeep's 1.4ghz OC into this when it gets out of alpha?

Sent from my Cappy using mental telepathy, *****ezz.
[Captivate Android Development] glitterballs:
Well...two things. The source is changing very rapidly, any time I go to make a build, I'm just pulling it from Aery's git. So, it kinda seems pointless for me to make a git which would constantly be out of date. The other sources I've used are already out there as well, raspdeep posts code in his thread, xcaliburinhad has a git I used to kang the orientation, headphone, and keyboard fixes. He deserves all the credit for that. In the spirit of openness, if you're having trouble building the kernel, I'll do what I can to help you. PM me, ok? There are only about ten lines of code of difference between three or four files between stock I-9000 and 're-oriented'.

Eh....that's the first I've heard of it. I may, but even 1.2GHz seems like overkill for most things. In any event, it won't be my first priority. I actually planned on trying to get the Brain **** scheduler working before the first CM releases came out, so if I get a stable build with the newer ramdisks, and I can get BFS working, and raspdeep releases a source which everyone finds stable enough I might.

What happened to you though man, when I first started reading Captivate forums, I thought you were the next rising star in Captivate ROM development. Man, I can't wait for this fn Captivate froyo source to get released. We have half-brained hacks like myself trying to do this stuff when there are people who really know what they're doing probably *coughunhelpfulcough* apparently sitting on the sidelines until the source gets released. This phone is gonna insane once we get the source and those guys step up.
[Captivate Android Development] tiger4j:
I read up on raspdeeps 1.4 oc today. I think he pulled that one but the thread seems to indicate that the 1.3 is pretty stable. I think its really something like 1280. I believe they were getting 17 to 18 mflops pretty consistently with it. That on top of cm would be pretty nice.

*sorry* didnt see "out of alpha"
[Captivate Android Development] DOAlaboratories:
Real life hit :( school, meetings,, relationships, and the like.

I'm studying into kernel compiling more now, along with theming.

but If you would could you send me a PM about this kernel? there are some things i'd like to work on with you on this.
[Captivate Android Development] NiXXeD:
Reverted my vold.fstab and flashed the new update. Appears to be working as indicated in the CM6 threads.

Thanks for the work on this =)
[Captivate Android Development] gtg465x:
Wifi for you?
[Captivate Android Development] biggem001:
my speakerphone isn't working on calls?
[Captivate Android Development] NiXXeD:
1120A build these are broken. So no. The ROM is working as expected (IE look at the issues log before you post about issues).
[Captivate Android Development] biggem001:
Do NOT update to latest

-bugs i've got so far-

camera doesn't work (unless you store to external sd)

mounting sdcards to pc caused problems where they wouldn't remount back, had to restart or manually mount them

i kind of have a reboot issue on mine, it gets MUCH worse on cyanogen, at full charge it shuts off. no other rom does this.
[Captivate Android Development] gtg465x:
I know it's in the issue log, but there was some talk in another thread that made me wonder if the wifi issue is only affecting glitterball's kernel.
[Captivate Android Development] Squeak22:
Nah, it looks like they tried to fix tethering, but broke wifi. I think I might skip 11/20 and wait for the next one.
[Captivate Android Development] gtg465x:
I'm getting kernel panics at full charge with this latest kernel and I've never even had a reboot issue.
[Captivate Android Development] glitterballs:
Camera is a known issue. This is also a beta build and we aren't on a fully supported device, so keep that in mind.

I had wifi working on the 1120A build with an intermediate kernel I didn't post. Try either of the first two kernels posts, turn off data, then turn on wifi. If that doesn't work, let me know, and I can post the kernel where wifi was working. (But again, you won't have both SD cards) edit - it may show that tethering is active, even though it isn't. With data on, the phone will show wifi connected, so it's necessary to turn data off, then turn on wifi.

Flash stock 1120A kernel or either of the first two kernels I have posted here and let me know if it happens. May be upstream problem. Logcat?
[Vibrant Themes and Apps] smackdown85146:
Anybody have it/anybody can port it? I love that keyboard, but can't find one compatible with JK2.

Any help is appreciated! :D
[Windows Mobile Development and Hacking General] Edwardo:
Hi!

Searched through the forum and couldn' find anything conserning my problem:

These days I'm using Android and my old WinMobile HTC Diamond has been out of use for ages. Can't remember my device password anymore. Damn.. Yep, stupid question maybe but; is thr any way to force open the lock? I've been thinking of reseting the whole device also, but because I can't remember what's in the built in memory, still hesitating...
[Windows Mobile Development and Hacking General] brandi:
If you hard reset your device, the password will be gone ;)
[Windows Mobile Development and Hacking General] ahsiang888:
if you can't remember what is in the built in memory, probably it is not important. :)
[Epic 4G General] sersdf2:
i understand this might be a known issue (radio crash after froyo update). anybody know what to do?

rooted my phone awhile ago... upgraded to Froyo a couple days ago (leaked FROYO.DJ29) and things were moving along pretty well. today while the phone was sitting inactive, it decided to go into airplane mode.

the last thing it did was try to download a google maps update.

i'm completely unable to get out of airplane mode. if i unselect it, it says "turning on wireless connections..." but never finishes that. resetting doesn't help. taking the battery out doesn't help.

in fact, the date on the phone reset to December 31, 2004.... any help would be super appreciated!!
[Epic 4G General] Deleted member 2173701:
try flashing the di18 modem file. i fixed a couple of my buddys friends epics like this.
[Epic 4G General] sersdf2:
UPDATE: i turned off my phone for an hour and when i turned it back on it was working fine.

add it to the bug list i guess if others report similar findings
[Epic 4G General] suzook:
This happens a few times a day on my epic....I went back to 2.1....ill wait for the official froyo release
[Epic 4G General] onilink67:
Happened to me once over a week ago was a bad flash wiped everything again and reinstalled been running this verson since with absolutly no issues actually I find it better then 2.1 as I don't hang up on people anymore when talking on the phone.
[Vibrant Q&A, Help & Troubleshooting] htown978:
After flashing Unofficial TMO 2.2 Froyo ODIN *2E Recovery +SD Fixed not my vibrate won't work. anyone have a solution?
[Vibrant Q&A, Help & Troubleshooting] roguly:
youre going to have to be more specific buddy. the phone wont turn on at all? can you get into recovery? are you hardware locked? etc. without info its going to be hard to help you. :)
[Vibrant Q&A, Help & Troubleshooting] Blkegk:
Wrong forum
[Vibrant Q&A, Help & Troubleshooting] htown978:
the phone is on and has been updated but the vibrate feature doesn't work when receives calls or texts
[Vibrant Q&A, Help & Troubleshooting] htown978:
Unfortunately I didn't notice a rom help forum.
[Vibrant Q&A, Help & Troubleshooting] Insomaniac10:
Hes not a moderator, you dont have to answer to him
[Vibrant Q&A, Help & Troubleshooting] htown978:
I know just being sarcastic but now for the resolution to the problem
[Vibrant Q&A, Help & Troubleshooting] jayzusfk:
Did you turn on vibrate in the sound options in settings? It's a little different than previous versions.
[Vibrant Q&A, Help & Troubleshooting] htown978:
yep vibrate set to always and still nothing
[Vibrant Q&A, Help & Troubleshooting] stefan.buddle:
Quick question:

Is English your first language?

If yes go to part 1, if not go to part 2

Part 1:

you Solution is in this link *Here*

Part 2:

click this---> *Here*
[Vibrant Q&A, Help & Troubleshooting] htown978:
Thanks for the help. If someone knows the real solution it would be greatly appreciated. Also it seems like english isn't your first language "you solution" don't you mean"YOUR SOLUTION". Maybe if you stop hiding in your moms basement on the computer English might be your first language
[Vibrant Q&A, Help & Troubleshooting] princearic:
Try this.

- take out your battery

- plug in phone via usb (computer on)

- hold both vol up and down buttons together simultaneously

- reinsert your battery while still maintaining your button pressing magic

With any luck, download mode should pop up and you can odin back to stock. Hope it works out for you
[Vibrant Q&A, Help & Troubleshooting] stefan.buddle:
Yes I make spelling mistakes, granted, like any other person, but unlike you I can realize I made a mistake... Post in the correct place next time, stop being a tool

ALL of these solutions have be stated before dozens of times in multiple places...
[Android Software Development] Technecium:
With FroYo comes the ability to set Voice Recognition to many different languages. If I choose "English (US)" under "Language", where is that setting stored on the OS? Is it in a db, an xml file, or some other configuration file?

Thanks
[Galaxy Tab Q&A, Help & Troubleshooting] teeskay:
Greetings,

I recently got a Galaxy TAB in Malaysia with the DXJJ1 firmware. There were issues connecting to my Exchange server, so I decided to download a new firmware from www.samfirmwares.com. I chose the latest Asia Firmware and downloaded the P1 PIT file - P1_add_hidden.pit.

I have tried using Odin 1.31 and Odin 1.7 both with no success. I always get a failure on the second try with factoryfs.rfs:

<ID:0/003> Odin v.3 engine (ID:3)..

<ID:0/003> File analysis..

<ID:0/003> SetupConnection..

<ID:0/003> Initialzation..

<ID:0/003> Get PIT for mapping..

<ID:0/003> Firmware update start..

<ID:0/003> param.lfs

<ID:0/003> zImage

<ID:0/003> cache.rfs

<ID:0/003> factoryfs.rfs

<ID:0/003> modem.bin

<ID:0/003> param.lfs

<ID:0/003> zImage

<ID:0/003> cache.rfs

<ID:0/003> factoryfs.rfs

<ID:0/003>

<ID:0/003> Complete(Write) operation failed.

<OSM> All threads completed. (succeed 0 / failed 1)

I've tried the DDJJ5 firmware and the latest ZHJK1 firmware, both don't work - after browsing around I'm thinking this might be a PIT file issue, but I'm not sure... now I can't use my tablet at all. Luckily it doesn't seem bricked, but I need to figure out a way to flash back either the original firmware or preferably a new firmware.

Any help would be most appreciated. Thank you.
[Galaxy Tab Q&A, Help & Troubleshooting] deafjam:
Did you also add the modem/phone csc and pda files? You probably need to apply a full firmware then an update.
[Galaxy Tab Q&A, Help & Troubleshooting] teeskay:
Hi, I clicked on PHONE/CSC also. Which is a full firmware that I should use? If I just click on "PDA" and update with the .tar file, it will flash but then I get a:

update media, please wait

E:Can't mount /dev/block/stl10

(invalid argument)

etc. error

:S
[Galaxy Tab Q&A, Help & Troubleshooting] Justin^Tan:
i dont think its the PIT file considering its the same P1 PIT

different from those EUR JJ4 and JK1 which have different PIT

my 1st logic is only flashing the PDS without repartition, but i never get the chance to do that

mine is also DXJJ1, indonesia here

if anybody manage to get through flashing, please post here, i'm desperately seeking guidance too hehe

when u try only the PDA files, did u tick the repartition?

and the pit files u use, is it the one that came with odin 1.7?
[Galaxy Tab Q&A, Help & Troubleshooting] shollywood:
Flash with the JJ4, as it is a full flash. Use ALL the files in it and make sure you select repartition, auto reboot and reset time.

Then if you wish you can flash JK1 over that, without repartition.
[Galaxy Tab Q&A, Help & Troubleshooting] Justin^Tan:
ur solution works on eur firmware, r u sure that would works with asian firmware? considering ur method is to get the 1st with PIT.1 which is jj4 meanwhile all asia's firmware already PIT.1 in the 1st place
[Galaxy Tab Q&A, Help & Troubleshooting] leekslk:
May I know if JJ5 is a full flash as well? If thats is so, I assume you could.flash JJ5 then do JK1?
[Galaxy Tab Q&A, Help & Troubleshooting] shollywood:
You will know if it is a FULL flash as it will contain all parts, Phone, PDA, CSC, and the PIT file. The non Full contain only *.tar file...

To the best of my knowledge JJ4 was the last FULL flash...
[Galaxy Tab Q&A, Help & Troubleshooting] shollywood:
If that is the case you do not require the full flash....
[Galaxy Tab Q&A, Help & Troubleshooting] Justin^Tan:
and there you go, DXJK2 is already out, to the Thread Starter, would you mind trying that one?

considering DX is the code for south east asia anyway, that would be the best suited for us
[Galaxy Tab Q&A, Help & Troubleshooting] leekslk:
Just downloaded P1000ZUJJ4 but it does not seem to contain modem/phone csc. all there is after an unzip is a single .tar file which I assume is the pda file.

Is it not possible to update the pda file only and not touch the CSC and modem files?

Sorry if I do not make sense.
[Galaxy Tab Q&A, Help & Troubleshooting] Justin^Tan:
it is possible thats what JK5 on eur firmware is for

its only flashing for PDA

u can search on thread how to flash from jj4 to jk5

to my extent, jj4 is the 1st file on eur that has P1 PIT, thats why its full flash

thats why u dont need a full flash again to jk5

if its the same case here, u should try from jj1 to jk5 by just flashing PDA without ticking repartition

i still didnt dare to do it myself though

but looking on samfirmware, all asia firmware is already P1 PIT by default
[Galaxy Tab Q&A, Help & Troubleshooting] ledyoung:
Have the same problem...
[Galaxy Tab Q&A, Help & Troubleshooting] zenkinz:
If you can put your tab into download mode, then just flash your stock fw over.
[Galaxy Tab Q&A, Help & Troubleshooting] TheATHEiST:
Topic reported.

This is not a development project.
[G2 and Desire Z Android Development] fastludeh22:
before you post with problems make sure you have read this at least 2 times. have this info in you post:

what was the last running rom/kernel combo you had?

list EVERYTHING you have done since that point

which recovery is installed?

what happens in recovery when you type

adb devices?

adb remount?

adb shell?

does it try to boot? is it stuck on splash screen, or does it make it to boot animation? 1 min after you turn it on, what happens when you type:

adb devices?

adb remount?

adb shell?
[G2 and Desire Z Android Development] funkeee:
Thank you, really, for taking the time to write this guide. I shared that dreadful feeling of a brick a little while ago, but made it out alive. I know this will help a lot of people.
[G2 and Desire Z Android Development] gilnino:
I'm not bricked, semi bricked or none of that. Rootrd and running BB 0.3

This is the best guide to everything you would need. Too bad you can't post this at the beginning of every thread or some kind of link on every page. This would answer a lot of question if some people would look hard enough. I'm not some smart phone guy by no means. I just read a lot before I ask. In my further reading I can direct people.with further problems here.

Thanks for all your work and giving me another fun hobby

Peace
[G2 and Desire Z Android Development] renn9420:
Question why is it that you have "dd if....../mmcblk0p21" in one area and towards the bottom you have "May brick phone ...dd if...../mmcblk0p18." Thought it should always be .../mmcblk0p18?

Phone: T-Mobile G2/Vision Rooted

Rom: Latest Cyanogen

Recovery: CWM waiting for Amon_RA
[G2 and Desire Z Android Development] gilnino:
Good point . Not sure on that one
[G2 and Desire Z Android Development] fastludeh22:
if you look where im saying /mmcblk0p21 we are replacing RECOVERY with CWM. i do that because i just dont like the idea of trying to replace hboot from a looping system. worst case something goes wrong, you still have hboot and you can try again. screw up hboot, game over! then once android is back up and running we worry about hboot on mmcblk0p18.
[G2 and Desire Z Android Development] g_grey:
you should not state that steps can be changed if people are brave, someone is going to sip parts and cry that their hboot is boned and now they have a BRICK, this is the best post i have seen in the G2 section thus far and i have been through almost every thread(with any kind of importance) in the dev section and 90% of them in general and Q&A. thank you for this post and let's hope people READ at least 5 times before even starting on this.
[G2 and Desire Z Android Development] renn9420:
Gotcha

Phone: T-Mobile G2/Vision Rooted

Rom: Latest Cyanogen

Recovery: CWM waiting for Amon_RA
[G2 and Desire Z Android Development] reycat:
Amazing guide, thanks a lot.

I have a full, honest-to-god brick in my drawer (executed dd if=/sdcard/hbooteng.img of=/dev/block/mmcblk0p18 with a wrong "hbooteng.img file).

I'm really, really interested in some guide or info about how to try and recover the brick. I don't mind if I have to open the case, there's not going down from where I am right now.

By the way, my second DZ just arrived, tomorrow I'll try to S-OFF it again... I will have nightmares tonight. :)
[G2 and Desire Z Android Development] fastludeh22:
Well it will take a jtag and a lot of research, since it hasn't been done to a g2 yet. Search g1 development forum dor debricking if u want an idea of what's involved.

I remember talking to gtrab a little about your problem. So did you use the wrong file, or did you type an address wrong? What file or typo was it exactly?

What happens when u try to boot into fastboot, or anything else?
[G2 and Desire Z Android Development] DJ ELITE:
{golf clap} on the post.

you sir, have incredible patience... and it's truly appreciated.
[G2 and Desire Z Android Development] reycat:
Mmm... It seems all of it is quite a bit over my head.

Don't ask me how I did it, but I actually downloaded a web page instead of the actual hboot file I should have used :D. I did it from the phone and didn't notice. Since I was supposed to rename it to make the typing easier, I didn't notice it was the wrong file.

Anyway, right now the phone is a complete brick. It doesn't respond to any button presses, the LED doesn't do anything when you plug in the charger... A complete brick.
[G2 and Desire Z Android Development] marley097:
Device offline?

Never used ADB before, followed [forum wont let me post outside links] to set it up. when typing adb devices while in recovery mode, get "list of devices attached

HT09PR204734

offline."

here is a screen shot : [forum wont let me post)

running windows 7 64bit...device not recognized by ADB at alll when stuck on splash screen....did some research couldnt find a real solution...soooo what do you recommend trying?
[G2 and Desire Z Android Development] -FuRBz-:
im stuck on the splash screen.. and i cant get adb to work either.. is missing a driver but i cant for the life of me find one ...
[G2 and Desire Z Android Development] marley097:
Download and instal PDANet, that gave me the drivers i needed for adb, now if only i could figure out how to get my device to register online through the ADB command interface.....
[G2 and Desire Z Android Development] -FuRBz-:
^^ you my friend are awesome! dl pdanet, was able to get the drivers.. was able to go into bootloader and did a recovery from there.. im up and running again!!