yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] nasif619:
sorry i am not a kernel dev. but what change need to after doing unpack boot.img?
[Galaxy S I9000 Android Development] capez:
Search for randomblame in xda (iconia a500 forum)...he wrote a post where he told which files change...like init.rc or other .rcs
[Galaxy S I9000 Android Development] nasif619:
ok. i am trying to do that, already done unpacking

where you are stucked?
[Galaxy S I9000 Android Development] ST3MC:
First of all i want to thank you and everyone working on this for keeping this device alive :)

Now for the Questions lolz

1.with the way it runs on nexus s do you think it will run better then ics on this device?

2.have you managed to boot it yet?

Thanks agine m8
[Galaxy S I9000 Android Development] DarknessWarrior:
1: yes, according to Google, JB is much more optimized in terms of rendering the menus etc, so it will be more fluid and faster than ICS

2: my guess is just as good as yours but i don't think so or they would have posted something or some download link.

as i stated before as soon as it is bootable i don't mind installing it on my SGS for error reporting/beta testing purposes.
[Galaxy S I9000 Android Development] capez:
In repaking boot.img and making everything boot
[Galaxy S I9000 Android Development] bravoleader:
Good luck guys. I'm sure you will do a great job.

Inviato dal mio GT-I9000 con Tapatalk 2
[Galaxy S I9000 Android Development] aopvet:
Hope July brings JB to our phone. Have a nice month to all of you.
[Galaxy S I9000 Android Development] Abyv:
May be u can check with pawitp ..he may be able to help you
[Galaxy S I9000 Android Development] bhu1:
Better u tweet to galnet or lttldvl . I don't think pawitp will help, but galnet did it for ICS. He can help.
[Galaxy S I9000 Android Development] RDilus:
if you need beta testers let me know im ready to screw up my galaxy s for this :P
[Galaxy S I9000 Android Development] pdppdp:
Lol. Me too.
[Galaxy S I9000 Android Development] DarknessWarrior:
stratosk from semaphore also posted a couple pages ago, he can probably help too
[Galaxy S I9000 Android Development] capez:
In the meantime, you can watch this video to see the butter running on our little brother Nexus S, which shares with us the same hardware :)

[YOUTUBE]_od9kVXLS3Y[/YOUTUBE]
[Galaxy S I9000 Android Development] dadebue:
Any news? ;)
[Galaxy S I9000 Android Development] strickyy:
Yeah, apparently it was booting yesterday at around 8-9 pm, but will not be posted here, before he gets thanked 289381 times.
[Galaxy S I9000 Android Development] BlackAngel1971:
I would like to apply for a job as a beta tester;)
[Galaxy S I9000 Android Development] capez:
It didn't boot neither yesterday nor today...As said before, the only problem is boot.img, and DerTeufel is working on the new kernel.

If you don't want to thank me now (and you aren't obliged to thank me), you can do it when we'll post the booting rom.

This thread is made mainly for grouping developers who can help porting Android 4.1.

Thank me or not thank me, it's not a problem, because the only thing i want now is Jelly Bean running in my phone and yours, and i'm trying to figure out every single method to solve this problem ;)
[Galaxy S I9000 Android Development] topfreitas:
capez, Thank you very much ;D We'll be here waiting for this rom :):good:
[Galaxy S I9000 Android Development] Pjuuder:
You go girl!
[Galaxy S I9000 Android Development] TFDRA:
Lets hope we're gonna get JB today, i'm willing to test it for you, if you need some people :rolleyes:
[Galaxy S I9000 Android Development] TnK8iD:
The boot-time will come for sure :D

and with the DerTeufel' s kernel our SGS will be faster than never

Thanks guys for doing this portig
[Galaxy S I9000 Android Development] dhiru1602:
I don't think any kernel changes are required. Maybe there are some changes to be made in the init scripts.
[Galaxy S I9000 Android Development] mkalter:
DerTeufel1980 is now helping us with kernel. Hopefully we have a working kernel this time. Thanks to Stratosk for his time. Please be patient and wait untill we have a working Jelly Bean.

Cheers,

MKalter
[Galaxy S I9000 Android Development] capez:
I'm not a girl
[Galaxy S I9000 Android Development] mkalter:
[YOUTUBE]pa14VNsdSYM[/YOUTUBE]

DON'T FORGET TO HIT THE LIKE BUTTON!!!
[Galaxy S I9000 Android Development] capez:
hahaha...Keep the thread clean please XD
[Galaxy S I9000 Android Development] kfheaven:
The whole world waiting our lovely sgs running jb....but I know v have the best dev team....sure will get it in this few day..
[Galaxy S I9000 Android Development] RolluS:
Hi,

I'm the lead dev of MyUI rom. MyUI Team is cooking and porting MIUIv4, TouchWizz, and ICS roms for the I9000, fascinate or vibrant. Really skilled on shell, I may help with debugging as soon as logcat is running.

I also know the use of make and g++ and so on, already compiled on i586 or crosscompiled to win32 and know how to handle returns (errors/warnings) . Never on android indeed,but already on Parrot's ARDrone using a toolchain..

If you think I can help, please F***** me on twitter: @Ro11u5 ;)

Cheers,

RolluS
[Galaxy S I9000 Android Development] 6i9:
Without being too technical, how far away are we from flashing a JB ROM onto our device? Estimated time?

I'm just curious :) Keep up the great work devs!
[Galaxy S I9000 Android Development] capez:
Thanks.

When it will be bootable we'll notify you. Your help is needed.

Cheers,

capez
[Galaxy S I9000 Android Development] mkalter:
We're getting closer and closer, DaXmax, who has ported JB had the same problem we have now. I've pm't him and I hope he'll pm me back soon. So hopefully today. Thanks to DerTeufel who made a good kernel...

Cheer

MKalter
[Galaxy S I9000 Android Development] kfheaven:
Dun ask about estimated time.....is worth to wait.:)
[Galaxy S I9000 Android Development] Besthiroeu:
Even if it boots there will be a lot of bugs.

For daily usable ROM you'll probably need to wait official Nexus S ROM and its sources.
[Galaxy S I9000 Android Development] 6i9:
And this is why Android >> iOS :D
[Galaxy S I9000 Android Development] ballsofsteel:
Well the first ICS Rom that resembles something that is usable came out in early December 2011 (~a month and a half after the announcement). However, most early builds were rigged with issues like performance and hardware (camera, BT, wifi etc.). I guess we could expect one by september/october at the fastest, with solid, bug free ones in dec 2012/early 2013.
[Galaxy S I9000 Android Development] TotallydubbedHD:
I love how follow me was censored :p!

I ABSOLUTELY love the fact that all you devs are getting together to try and solve this - this is what android is all about!
[Galaxy S I9000 Android Development] Num_Lock:
True
[Galaxy S I9000 Android Development] kfheaven:
Ya..all Android Dev team is work together to make it happen....u can't get it at any other places....
[Galaxy S I9000 Android Development] 6i9:
This is true.

However, the activity and hunger on the forum as of late in comparison to then seems a lot stronger and determined to have this JB port - because it's the missing piece of the puzzle to ICS.

I'm not sure when the ICS code leaked though? Was it as early as JB to its revealing at I/O?
[Galaxy S I9000 Android Development] capez:
We are proud to announce the new team of Galaxy S ROM developers:

TAJB​

Team Android Jelly Beam​

Members

for now

:

- Capez

- Mkalter

Thanks to:

- DerTeufel1980

- Stratosk
[Galaxy S I9000 Android Development] RolluS:
I think that I can help as soon as kernel is booting ;)

Glad to help
[Galaxy S I9000 Android Development] UltrasFrankfurt:
Great team, but I'd call it duo:p:D

Gesendet von meinem GT-I9000 mit Tapatalk 2
[Galaxy S I9000 Android Development] mkalter:
Lol, It's says member FOR NOW, so maybe there are coming more in!
[Galaxy S III Themes and Apps] focamonca:
Really simple. Can some1 drop the apk for the JellyBean VoiceSearch and any other apks directly related to it functioning properly? Thanks much in advance.

I found this in the Gnex section, let's try.
[Galaxy S III Themes and Apps] mc-paulo:
What is Velvet.apk for?
[Galaxy S III Themes and Apps] focamonca:
Is the name of the app extracted from the nexus, the voice recognition
[Galaxy S III Themes and Apps] ermacwins:
Does it work?
[Galaxy S III Themes and Apps] wackyD:
Yeah have you tried it?
[Galaxy S III Themes and Apps] Cleothaj32:
I downloaded it but wasn't able to install it, says a problem with the parsing.
[Galaxy S III Themes and Apps] focamonca:
No, it says error.. but in the gnex section it works for them.. :/ test yourself...
[Galaxy S III Themes and Apps] focamonca:
Up
[Galaxy S III Themes and Apps] TMaLuST:
I just tried to install it on foxhound 0.6 and siyah. It's not working either.

I'm going to try to push it as a system app in the jelly bean port rom.

Will update shortly after the flash
[Galaxy S III Themes and Apps] TMaLuST:
Update: with its normal apk, it didn't work yesterday.

I changed the original apk with the one you posted here, and then it worked.

We don't have connections, radio or wifi, on that port, so I couldn't test if it really worked, but atleast we know that it's opening without force closes.

I think it has something to do with the new APIs, but I really hope I'm wrong ;)
[Galaxy S III Themes and Apps] focamonca:
I don't have an apk called velvet in sys/app..
[Galaxy S III Themes and Apps] rajarshi10:
How the hell did u install it? Its still aborted :rolleyes:
[Galaxy S III Themes and Apps] Rocklee99:
how do u install this? its not working
[Galaxy S III Themes and Apps] TMaLuST:
Let me explain myself better:

Yesterday night I installed the 4.1 ported rom but the voice search was force closing.

I came back to ics, and tried to install the app. As you also saw by yourselves, it's not working on ics.

I then decided to try again on jelly bean, but before flashing I changed the original voice search apk with this one. Then I flashed the rom and whilst the engine keep force closing as soon as you try the speech test, the application itself is able to launch without force closing.

Long story short: on ics it's not working for me either; on jelly bean it does, but the ported rom has no connectivity so I couldn't test it.
[Galaxy S III Themes and Apps] cnonline:
I downloaded the .apk file and tried to install it. Its says Parse error: There is a problem parsing the package. :(
[Galaxy S III Themes and Apps] mp2ning:
The apk's from the Galaxy Nexus are odexed in stock form. There is a velvet.apk and a velvet.odex file along with it! The velvet.apk only will not do the trick; it has to be a de-odexed version of it to begin with!

Is the file from the OP a de-odexed version?

I would love this working my Galaxy SIII!
[Galaxy S III Themes and Apps] sublimejosh2000:
Uhm.. me too. I have a friend with a Gnex. I will see if i can grab thus and do some magic with it.
[Galaxy S III Themes and Apps] MiG123:
can i haz projectbutter.apk pleeze...
[Galaxy S III Themes and Apps] focamonca:
Quote!
[Galaxy S III Themes and Apps] h20wakebum:
Does this help?

I found the de-odexed version of this.

http://xdaforums.com/showthread.php?p=28034994

I am not a developer, but I really want the google now functionality!!

If anyone is willing to assist me as I try that would be great!!!! I'm willing to learn and would love to learn.
[Galaxy S III Themes and Apps] focamonca:
It says for me the same error..
[Galaxy S III Themes and Apps] abo azzam:
It says for me the same error..
[Galaxy S III Themes and Apps] vinnypel2ella:
Would it help if I uploaded a titanium backup file of my Velvet.apk? Have you changed your build.prop ro.build.version.sdk= value from 15 to 16, go into system/app and change GoogleQuickSearchBox.apk to GoogleQuickSearchBox.apk1 (Instead of backing up/uninstalling). Then reboot. Then install the Velvet.apk. Then change the version.sdk= value back to 15 and reboot. I believe if you use my titanium backup file all you'd have to do is restore the backup from TB.
[Galaxy S III Themes and Apps] MilkChan:
really 4.1?? amazing!! Let me try it:silly:
[Galaxy S III Themes and Apps] jonefuroy:
This metode should sort of work with most asop based devices. The problem is (as I've learned) that the voice part of now is build in to the kernel.

I have Google now running and working 80% of the time without Voice. Still its useful and a great little bit of what's to come!

http://xdaforums.com/showthread.php?t=1749045
[Transformer TF300T Q&A, Help & Troubleshooting] ralph075:
As a fresh TF300-owner I was wondering if it is possible to create a nandroid backup (and restore oc) without unlocking my device.

I have rooted my device, but don't need unlocking (no intentions to flash roms). However, a full backup gives me some peace of mind. Is there any way to achieve this without unlocking? (I think I know the answer, but I hope I missed a way to achieve this...)

Aside, as I am asking already, do you have advice to maximize root-advantage? I have rooted specifically for the Switch Me-app (purchased, it is so good!) and for AdFree.

As I have root now, do you guys have any suggestions for "must-have" apps or tweaks that require root?

Any help is appreciated, thanks in advance!
[Transformer TF300T Q&A, Help & Troubleshooting] ralph075:
Ok, have been reading further and what I already thought seems to be true: Without unlocking no nandroid backup...

Well, good to know and to keep in mind. Of course, if I missed something, I love to hear :fingers-crossed: And if anyone has suggestions for root-dependend apps or tweaks, I'm still interested ;)

Thus far I found the following suggestion myself:

Minor tweaks and speed increase , specific post 261 as I am on WW fw .30

Some app suggestions from the Prime topic

Needless to say more suggestions are always welcome ;)
[Transformer TF300T Q&A, Help & Troubleshooting] cavsoldier19d:
Simply put..nandroid backup is a function of cwm recovery. To get cwm recovery installed, the boot loader must be unlocked. So therefore, no nandroid backup can occur without an unlocked boot loader. I've seen a windows root program with other Android devices that roots, unlocks the boot loader, installs cwm recovery and offers its own internal backup feature. But again, that's only possible with an unlocked boot loader
[Transformer TF300T Q&A, Help & Troubleshooting] ralph075:
Yes, after searching, reading, re-reading, more searching, reading again, another google attempt (at that time I wasn't searching for the answer, but for my desired answer (to find out that the desired answer doesn't exist) ;) ) I finally came to this conclusion too.

Well, no nandroid backup then for me, cause don't want to unlock bootloader, except the backup there is no need for me (at least not yet, future experience might change my opinion).

Thanks for explaining anyway!
[Transformer TF300T Q&A, Help & Troubleshooting] 3ddyz:
Isn't there another way of installing CWM tho? Defy's can install it with a locked bootloader (2ndinit).
[Transformer TF300T Q&A, Help & Troubleshooting] cavsoldier19d:
There may be other methods to installing cwm recovery, however no matter which method u use, it will still require unlocking the boot loader. Unlocking the boot loader and flashing a custom recovery are two seperate processes
[Transformer TF300T Q&A, Help & Troubleshooting] 3ddyz:
That's what I mean tho, the Defy didn't have an unlocked bootloader but still had CWM...
[Transformer TF300T Q&A, Help & Troubleshooting] ch3mn3y:
Yes u are right. There is an app (i dont remember the name), which let u to install cwm on locked bootloader. However it needs to have possibility to flash cwm port for specific phone/tablet and now it can only flash port for tf300 - it is flashing this for tf101 and it can brick our tf300.

Sent using r800i with DoomKernel v14 (460mHz/1.21gHz)
[Transformer TF300T Q&A, Help & Troubleshooting] cavsoldier19d:
Every Android device is different when it comes to rooting, flashing roms and flashing recoveries. Its the same reason why we can't just use one root program for all Android devices unlike jail breaking an iPhone. Every Android manufacturer and model will vary with boot loaders, partitions, root exploits and everything else. What may work for one Android device will not work for another. And at this time, on the tf300, there is no other way to install a custom recovery without unlocking the boot loader...unless we just had a breakthrough that I'm not aware of. We are all hoping for that breakthrough to come.
[Transformer TF300T Q&A, Help & Troubleshooting] ameer1234567890:
If you are able to root the device and install busybox, there is a method!
[Transformer TF300T Q&A, Help & Troubleshooting] EndlessDissent:
Actually, nandroid backups aren't limited to recovery. You could nandroid using fastboot if you like. Recovery just makes it easier. In fact, pretty much every function of recovery can be performed using fastboot. You need to unlock the bootloader to access fastboot, though, so that doesn't really help here. Just thought I'd point that out.
[Samsung Galaxy Nexus] epicrevolt:
Solution:

If you were like me, you couldn't get ADB working no matter what you did with the drivers. As it turns out, I was plugging it into a USB 3 port on my motherboard. I have the USB 3 drivers installed, but there seems to be an adb issue with USB 3 ports. be warned, my issue is now fixed (I probably don't even need them bootleg drivers either). Thank You XDA.

Alright, so I just picked up a Galaxy Nexus (coming from Thunderbolt) today only to find out that my sdk will not detect my phone in adb devices. Now, I have the Thunderbolt and Eris working fine with it, but the NExus seems a little stubborn. Here are the steps I have taken:

1. Plug in phone, wait for win7 (x64) to install all the drivers... Success

1a. MTP and PTP both installed, using MTP for the rest.

2. Turn on debugging on my phone one more driver... Success

3. Went to the GNex Samsung support page to download and install that driver... Success

4. Go into Device Manager, everything is A-OK, drivers all happy

5. Open up my sdk prompt and type adb devices and 1 device is found, offline

6. Type it in again, nothing, maybe a glitch?

So there is nothing wrong in Device Manager, no Windows Updates, SDK works fine, but no device under adb devices. This is honestly the strangest thing ever.

If you have any special instructions regarding drivers, please be specific, stating "update your driver" doesn't really help.

Oh, and this is my first post I believe.
[Samsung Galaxy Nexus] Jubakuba:
Update your drivers :laugh:

Right Click the "Android" option and select Update Driver. Choose to "Browse My Computer" and "Let Me Pick From A List." Pick the Samsung driver with the newest date and install it.

Srsly though...

If that doesn't work...try the PDAnet option.

My sig has a link.

Install PADnet and plug your phone in.

Then check that the new driver is the one in use.
[Samsung Galaxy Nexus] efrant:
@ OP, did you restart your PC after installing the drivers? If not, that may cause an issue. As well, you could always restart the ADB daemon. Type:

adb kill-server

adb start-server

As for drivers, I personally would not recommend using any package that installs crapware other software along with the driver (such as the PDA drivers). Chance are if the package comes with an .exe extension, it contains other software. 1wayjonny has packaged the driver by itself here. Those are clean drivers with nothing extra to cause any issues. I recommend those, but (as with anything that works well) you need to manually install it, i.e., right-click on the device listed in Device Manager and select update, and browse to the location where you unzipped the driver. This needs to be done TWICE: once when your device is booted in fastboot mode, and once when booted normally.
[Samsung Galaxy Nexus] epicrevolt:
Noob question, but how do I install those drivers?
[Samsung Galaxy Nexus] epicrevolt:
Alright, so I have done the following:

Uninstalled all Samsung Drivers through Device Manager

Unplugged phone

uninstalled those official Samsung drivers for the GNex (available for download on their site)

Plug phone back in, both MTP and Nexus unknown

install the 1wayjonny driver... Success (It's now under Android Device in Device Manager)

adb still doesn't work... f*ck

reboot phone into fastboot (vol +/- & power)

install 1wayjonny driver... success

fastboot device recognized by 'fastboot devices' and commads work.

I believe the issue is with the MTP device as it is not recognized so therefore I can't access the phone storage. So far the only way I can get MTP working is by using the official Samsung driver, but that overrides the ADB driver by 1wayjonny (no way around it, even through uninstallation and choosing the 1wayjonny driver, Samsung one is more 'recent').

In the attachment you can see that the MTP device has no driver and therefore is unavailable.

Thank you so much for the help so far.

UPDATE: MTP Driver downloaded through Windows Update, divice still not showing up in adb. Actually when I first run adb devices after kill-server it finds the device as offline, but as soon as I type 'adb devices' again, it's gone. poof.
[HTC Aria Q&A, Help & Troubleshooting] RealPsygnosis:
Hi to all, my gf wats to buy an HTC Gratia...

I'd like to know if it's the same of HTC Aria and the same of the ROM Mod of Cyanogen that I found in the section HTC Liberty...

If So what is the lastest official rom and what's the last mod?

thanks a lot
[HTC Aria Q&A, Help & Troubleshooting] dutchmkl:
Yes Aria is US version and Gratia is EU version both fall under the HTC Liberty section

Last official rom of HTC is Android 2.2. But we have also CM7 and CM9
[HTC Aria Q&A, Help & Troubleshooting] molecula364:
and CM10, don't forget ;)

but CM9&10 haven't full worked features, like videocam recorder, HW acceleration video...
[Verizon Droid Charge] slane35:
I was running the latest tweaked ROM yesterday when it rebooted itself into a boot loop. Iets stuck at "Samsung"

I attempted to restore using Odin following the instructions in the how to fix your phone thread. Though i've been successful with that in the past, this time it didn't fix the phone. Its still stuck on Samsung, but will randomly display the stock boot ani with sound, or even get to the lock screen, but then immediately go back to displaying Samsung.

Any ideas would be greatly appreciated, and yes, i've followed all instructions correctly with wipes and loading things in Odin, etc.

Thanks!
[Verizon Droid Charge] dwitherell:
Hmm... was there anything going on at the time of reboot? Very curious.

Beyond that - assuming all went as it should with ODIN, if you are still having issues then the problem is a bit beyond the rom. It seems a scapegoat but perhaps a hardware error is underlying things...?

Anyhoo - what file (or files) have you tried to ODIN? There are a few to choose from, and they all can be found

here

(just be sure to only DL and use the charge-specific ones of course). I would try each one and hope at some point something sticks to where the phone is usable again. Sorry for the troubles!
[Verizon Droid Charge] slane35:
Thanks for your reply! Phone was just sitting on my desk, I was text messaging...it may have been plugged into a non Samsung charger. I doubt its the fault of your ROM tho, as it had been running great since I installed 2.1 a few weeks ago. Its always run hot so that might have just caught up with it.

I'll try all those files this time on fresh downloads, might have been something corrupted.

thanks again!

UPDATE: Successfully loaded ED1 on, and it boots. I can unlock the phone, begin the setup process, but then it reboots. I'm so confused...
[Verizon Droid Charge] kvswim:
Find the most current OTA file and flash it instead of working your way all the way from Froyo to Gingerbread.