Got it from the horse's mouth. Firmware update within three weeks. No more info as to version but comes from a very good source (or in this case, from a very good horse).
Let hope it is true and come down before we sell the damn phone......
Three weeks later ...
someone has already extended the time before the end of august
can not wait!
Now its the end of Sept... maybe
(^_^
Sent from my Dell Venue using XDA App
Guys... it's comming... ftp://ftp.dell.com/opensource/venue/
Samver said:
Guys... it's comming... ftp://ftp.dell.com/opensource/venue/
Click to expand...
Click to collapse
is this the long awaited 2.3.3 upgrade?
If click the 4.06 link, and then click how to built, these are the instructions and they clearly indicate gingerbread.
bluez
1) download source tree of android gingerbread from Google.
2) build android by
. build/envsetup.sh
choosecombo (all default option, Product choices are: 2. generic)
make -j4
3) replace external/bluez, and 'export BOARD_HAVE_BLUETOOTH=true'
4) mmm external/bluetooth/glib
mmm external/bluetooth/bluez
-------------------------------------------------------------------------------
jpeg
1) download source tree of android donut from Google.
2) build android by
. build/envsetup.sh
choosecombo (all default option, Product choices are: 2. generic)
make -j4
3) replace external/jpeg
4) mmm external/jpeg
-------------------------------------------------------------------------------
e2fsprogs
1) download source tree of android donut from Google.
2) build android by
. build/envsetup.sh
choosecombo (all default option, Product choices are: 2. generic)
make -j4
3) replace external/e2fsprogs
4) mmm external/e2fsprogs
-------------------------------------------------------------------------------
webkit
1) download source tree of android donut from Google.
2) build android by
. build/envsetup.sh
choosecombo (all default option, Product choices are: 2. generic)
make -j4
3) replace external/webkit
4) mmm external/webkit
-------------------------------------------------------------------------------
wpa_supplicant
1) download source tree of android froyo from Google.
2) build android by
. build/envsetup.sh
choosecombo (all default option, Product choices are: 2. generic)
make -j4
3) replace external/wpa_supplicant_6
4) mmm external/wpa_supplicant_6/wpa_supplicant
-------------------------------------------------------------------------------
kernel
1) download source tree of android froyo from Qualcomm.
2) replace kernel
3) build kernel by
. build/envsetup.sh
choosecombo
Build for the simulator or the device?
1. Device
2. Simulator
Which would you like? [1] 1
Build type choices are:
1. release
2. debug
Which would you like? [1] 1
Product choices are:
1. emulator
2. generic
3. sim
4. dream
5. passion
6. sapphire
7. msm7627_ffa
8. msm7627_surf
9. msm7630_surf
10. qsd8250_ffa
11. qsd8250_surf
You can also type the name of a product if you know it.
Which product would you like? [qsd8250_surf] 11
Variant choices are:
1. user
2. userdebug
3. eng
Which would you like? [eng] 3
5) make -j4 kernel
---------- Post added at 05:06 PM ---------- Previous post was at 05:04 PM ----------
All a foreign language to me unfortunately.
darn... it is 2.3.3! Devs! I got lost source tree!
why the kernel is from foryo?
only the bluetooth is from gingerbread.... main kernel is not gingerbread
If this is true, does anyone know when it will be available? Thanks
I'm cautiously optimistic that this is in fact an upcoming update (Gingerbread).
I highly doubt Dell is working on any update for Venue. Seems like Dell's focus has shifted to Windows 8. Per Michael Dell's message during Dell World 2011.
You're probably right. I am still hopeful though. They are still selling the Venue on the website so there may be a chance it will happen.
Yes, Venue will get 2.3. It is already out in Korea. Go to Dell support and type in Venue in the search bar. First 2 topics are of the Venue running 2.3.
Sent from my X10i using XDA App
Narvarr said:
Yes, Venue will get 2.3. It is already out in Korea. Go to Dell support and type in Venue in the search bar. First 2 topics are of the Venue running 2.3.
Sent from my X10i using XDA App
Click to expand...
Click to collapse
Link please....
Sent from my GT-S5570 using xda premium
http://search.dell.com/results.aspx...&~srd=False&ipsys=False&advsrch=False&~ck=tab
Sent from my X10i using XDA App
Thanks for the link, so can't we flash the Korean rom in our device?
Sent from my GT-S5570 using xda premium
Can someone upload build.prop file from korean olleh firmware? Version 3.19, and 3.03 if it possible...
Sent from my Dell Venue using XDA App
Samver said:
Can someone upload build.prop file from korean olleh firmware? Version 3.19, and 3.03 if it possible...
Sent from my Dell Venue using XDA App
Click to expand...
Click to collapse
See this thread and the wiki page. The roms are in zips in the thread which you can unzip to get any file you need. The 319 pkg is available on the wiki and also here as a zip.
Related
I've been digging through the Vibrant forums for a while now, and I would like to try my hand at building the Froyo release. I downloaded the source and can compile the kernel just fine, but the platform part I am in the dark. Could someone help me with how to build the platform part? Once I get that done, I'll dig around to see how to convert it over to a flashable zip. Thanks in advance.
Slashazard said:
I've been digging through the Vibrant forums for a while now, and I would like to try my hand at building the Froyo release. I downloaded the source and can compile the kernel just fine, but the platform part I am in the dark. Could someone help me with how to build the platform part? Once I get that done, I'll dig around to see how to convert it over to a flashable zip. Thanks in advance.
Click to expand...
Click to collapse
Hey. I myself learning to build my own custom rom too!
Sent from my SGH-T959 using XDA Premium App
The platform source has not been released (and never will be). Only kernel source is required to be released.
Sent from my SGH-T959 using XDA App
In the source package there is a platform tar file. Do I download the AOSP code and overwrite those folders with what was in the platform tar from Samsung? Then build like AOSP?
go into android developement section here on xda or Ask some of developers here, if u ask nicely i think they might help u.
Hello,
I've had some form of Android device for atleast a year. I've also moved on from Windows, now using Linux as my day-to-day operating system for 6+ months, having used it almost a year. I have a small bit of knowledge in both Java and C++.
That being said, I'm looking to start messing with the Linux (specifically Android) kernel. I'm hoping that, eventually, I'll be able to make my own kernel for my Thunderbolt. So, yeah, if anyone could post how they learned or recommend a book (or books),a website, etc. I'd very much appreciate it! I've been looking to get Developing the Linux kernel 3rd edition by Robert Love (I think that's the title/author, not 100% sure, though) but would like to see what anyone recommends. Also, I've seen a little bit of part 1 of OhHeyitslou's video regarding the Linux kernel, but would appreciate other resources.
Thanks,
Labsownyou
Sent from my Thunderbolt using Tapatalk.
hello labswanyou,
I'm also looking for learning how to develop android kernels. After flashing my phone with custom rom and kernel, it seems very interesting for me to develop android kernels.
It would be helpful for us if any of you describe how to create android kernels in simple steps or if you refer some websites where we can get simple tutorials for it.
I think the following link will help to understand the basics of android
developer.android.com/guide/basics/what-is-android.html
pratish7 said:
hello labswanyou,
I'm also looking for learning how to develop android kernels. After flashing my phone with custom rom and kernel, it seems very interesting for me to develop android kernels.
It would be helpful for us if any of you describe how to create android kernels in simple steps or if you refer some websites where we can get simple tutorials for it.
I think the following link will help to understand the basics of android
developer.android.com/guide/basics/what-is-android.html
Click to expand...
Click to collapse
Thanks for the link, though I kind of new most of it. It'll be interesting to see if people reply, and if/when they do, what they post!
I think it'd be great if one (or more...) of the kernel developers could point us in the right direction.
Hey guys, I'm not a kernel developer exactly(more of a tinkerer at this point--I'm learning), but I have a basic guide that I sent another XDA user that covers a very basic step by step guide that should work for most kernels. If you're interested I'd be glad to post it.
Sent from my ADR6300 using xda premium
swm5126 said:
Hey guys, I'm not a kernel developer exactly(more of a tinkerer at this point--I'm learning), but I have a basic guide that I sent another XDA user that covers a very basic step by step guide that should work for most kernels. If you're interested I'd be glad to post it.
Sent from my ADR6300 using xda premium
Click to expand...
Click to collapse
If you could, that be greatly appreciated!
Sent from my ADR6400L using Tapatalk
Since I don't know what kind of experience you have exactly (other than using Linux, which is good ) I'll just go all out. Don't be offended if it seems like I'm being too explicit, I'm just copying and pasting a couple things from guides I used when I was trying to figure this **** out a couple weeks ago. Most of this is assuming you have no build environment set up at all, and should work with any Linux builds of the Debian variant (Ubuntu...and thats all I can think of ).
Make sure you have the Android SDK tools installed so you have ADB and stuff. If you don't, Google it. The install steps from Google work fine.
Fire up a terminal. Add this first so you don't error out trying to install the jdk.
Code:
sudo add-apt-repository "deb http://archive.canonical.com/ maverick partner"
Assuming you're on an x86/32 bit version of linux, run:
Code:
sudo apt-get install git-core gnupg flex bison gperf libsdl1.2-dev libesd0-dev libwxgtk2.6-dev squashfs-tools build-essential zip curl libncurses5-dev zlib1g-dev sun-java6-jdk pngcrush schedtool
If using x64, run the above command as well as this one:
Code:
sudo apt-get install g++-multilib lib32z1-dev lib32ncurses5-dev lib32readline5-dev gcc-4.3-multilib g++-4.3-multilib
NOTE: gcc-4.3-multilib g++-4.3-multilib is no longer available for Ubuntu 11.04 64-bit, but should still build without issue.
Now you'll need to grab the ARM toolchain to be able to cross compile code for ARM devices.
Make a directory in your home folder (I just used android, so ~/android) and go into it on your terminal after all that **** up there is done.
Now do:
Code:
git clone git://github.com/CyanogenMod/android_prebuilt.git
or if you have a github account and to avoid a couple prompts:
Code:
git clone [email protected]:CyanogenMod/android_prebuilt.git
Assuming you did the first command, it'll ask for your name and email. You can give them, or just hit enter and ignore it. It'll take a while to download the whole package, and then a good amount of time to unpackage and check out the files. In reality, there's more there than you need for compiling a kernel, but as you do more you may find it helpful to already have some of the things in there.
Now you have the toolchain. The next thing to do is to add the ARM toolchain path to your .bashrc file so make can easily call it when you compile the kernel. Back on your terminal:
Code:
nano ~/.bashrc
Scroll alll the way down. On the end of the file, add:
Code:
export CCOMPILER=~/android/android_ prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/arm-eabi-
Where ~/android/ is the name of the folder you used git to clone the android_prebuilt repo from CM.
Then, to reload your .bashrc you just edited:
Code:
source ~/.bashrc
The last thing you need is the kernel source. I suggest using the kernel source that's used for CM7 for your device. If you don't which repo to use, you can go to [LINK]http://wiki.cyanogenmod.com/index.php[/LINK], find your device, and on the right hand side look who the maintainers are. Usually a quick google of their name + github on Google will land you in the right place.
Back on the terminal, go into your android folder you created, and run:
Code:
git clone git://[MAINTAINER USERNAME]/[whatever their kernel is called].git
Wait for it to finish. You should have a a kernel source folder with about a bazillion files in it now taking up way more space than it needs to to create a 2MB kernel
On your trusty terminal again (make sure you're in the kernel source folder you just cloned):
Code:
cp arch/arm/configs/[device name]_defconfig .
Don't forget the period at the end to copy it to the root of the source folder. I'm not sure what the device name will be, if its coming from a CM kernel, sometimes the maintainers put cyanogenmod_ in front. For example, for me its cyanogenmod_incrediblec_defconfig.
Finally.
The last part is easy(make sure you're still in the root of your source dir):
Code:
make ARCH=arm CROSS_COMPILE=$CCOMPILER
To run it with multiple threads (much faster on multicore setups) run this instead (the number after j is the number of threads that will run):
Code:
make -j4 ARCH=arm CROSS_COMPILE=$CCOMPILER
Then wait till it's done. If you did a multithread build and the compiler didn't like something, the error probably went by a while ago and you didn't catch it. The other threads run even after the error, until they can't run anymore without the missing peiece that errored out. If this happens, just hit the up key on your keyboard ans run the same make command again. The compiler will print the error right away since none of tgr threads can continue until the error is fixed. The last few lines of Make's output should tell you where its stashed the zImage file (your finished product!).
And there you have it. I think! Let me know how it goes.
Sent from my ADR6300 using xda premium
I say to use the CM7 kernel source since we were talking about it in a PM, but you can certainly grab a manufacturer's source tarball and use that instead. Just be careful, sometimes their defconfigs aren't always perfect. If this is the case,Make may ask you if it should enable certain features or drivers that it thinks are "new" and doesn't know what to do with.
Sent from my ADR6300 using xda premium
I surely suggest you to start compiling the linux kernel of your installed distribution. Just a simple copy of it, then, after playing on it tweaking around, move to android kernel. What posted by Swm5126 is actually the "state of the art how to do it".
P.S. googling AOSP (android open source project) you'll find lots of related resources.
GT-S5570 on Train
Please use the Q&A Forum for questions Thanks
Moving to Q&A
lufc said:
Please use the Q&A Forum for questions Thanks
Moving to Q&A
Click to expand...
Click to collapse
Thanks, and sorry about that. I'm newish to posting here...
Sent from my ADR6400L using Tapatalk
I am trying to build GB aosp from source on ubuntu for my phone samsung conquer 4G. I already have the source and in it there is a platform and in the text for it it says to put those files in the folders in the source than build. I am wondering if I would only replace files and not put in new ones? Or if I would even do this. If I shouldnt, how would I even port after its built and does anyone know what poison I should choose? Thanks a bunch
Any reason why GB? ICS or JB would be better wouldn't it? I'm not the best person to try to answer your question, but you will have to supply a little more info, I will help if I can.
onlychevys said:
Any reason why GB? ICS or JB would be better wouldn't it? I'm not the best person to try to answer your question, but you will have to supply a little more info, I will help if I can.
Click to expand...
Click to collapse
Thanks, i am building gb because my phone does not have any official roms like cm,aosp,etc. I am the only person with the device that is capable of building from source i have already built a kernel. Also i am doing gb because my phones version is 2.3.6 and it should be easier to port than ics or jb. If you need any more info i will be glad to give you it.
bump
itzdarockz said:
I am trying to build GB aosp from source on ubuntu for my phone samsung conquer 4G. I already have the source and in it there is a platform and in the text for it it says to put those files in the folders in the source than build. I am wondering if I would only replace files and not put in new ones? Or if I would even do this. If I shouldnt, how would I even port after its built and does anyone know what poison I should choose? Thanks a bunch
Click to expand...
Click to collapse
Could use some clarification
When you refer to the source are you talking aosp? Or your device source?
If your referring to the device source that goes in working/device/manufacturer/devicename/
Could you provide a screenshot of the device source? Wanna make sure it looks like a proper device tree
As for poison...you just add your device to the lunch menu and build it...create a file in your device tree called vendorsetup.sh (just right click and go to create new document and name it that) then open it with a text editor (gedit) and type this and save it :
Code:
add_lunch_combo full_devicename-eng
(replace "devicename" with your device
Then in the root of your working folder type
Code:
. build/envsetup.sh
lunch
Choose your device then type
Code:
make otapackage
or to fully utilize your CPU
Code:
make -j# otapackage
replacing "#" with the number of CPU cores your computer has plus 1 or 2...so for dual core I usually do male -j4 otapackage
Sent from my HTC PH39100 using Tapatalk 2
mg2195 said:
Could use some clarification
When you refer to the source are you talking aosp? Or your device source?
If your referring to the device source that goes in working/device/manufacturer/devicename/
Could you provide a screenshot of the device source? Wanna make sure it looks like a proper device tree
As for poison...you just add your device to the lunch menu and build it...create a file in your device tree called vendorsetup.sh (just right click and go to create new document and name it that) then open it with a text editor (gedit) and type this and save it :
Code:
add_lunch_combo full_devicename-eng
(replace "devicename" with your device
Then in the root of your working folder type
Code:
. build/envsetup.sh
lunch
Choose your device then type
Code:
make otapackage
or to fully utilize your CPU
Code:
make -j# otapackage
replacing "#" with the number of CPU cores your computer has plus 1 or 2...so for dual core I usually do male -j4 otapackage
Sent from my HTC PH39100 using Tapatalk 2
Click to expand...
Click to collapse
When i mean the source I meant my phones. It has two zips, kernel and platform. It has txt files on how to build the kernel and the update. And thanks man. The screen is attatched. The folders are build, extension, external, libcore, and vendor.
i was afraid of that...doesnt look like a device tree...and unfortunatly i have no expiernece creating a device tree from scratch/from manufacturer source...
anyways heres an example of two device tree i use...
mg2195 said:
i was afraid of that...doesnt look like a device tree...and unfortunatly i have no expiernece creating a device tree from scratch/from manufacturer source...
anyways heres an example of two device tree i use...
Click to expand...
Click to collapse
Thats why it says in a txt to replace files in the aosp source with the ones in the folder.
itzdarockz said:
Thats why it says in a txt to replace files in the aosp source with the ones in the folder.
Click to expand...
Click to collapse
Well do what it says then...it has .mk files and looks like that when placed in aosp?
Sent from my HTC PH39100 using Tapatalk 2
mg2195 said:
Well do what it says then...it has .mk files and looks like that when placed in aosp?
Sent from my HTC PH39100 using Tapatalk 2
Click to expand...
Click to collapse
Actually I think we do have a non manufacturer source does this look good? https://github.com/utkanos/android_device_samsung_SPHD600
itzdarockz said:
Actually I think we do have a non manufacturer source does this look good? https://github.com/utkanos/android_device_samsung_SPHD600
Click to expand...
Click to collapse
Yeah...looks small...but that's a device tree
Sent from my HTC PH39100 using Tapatalk 2
mg2195 said:
Yeah...looks small...but that's a device tree
Sent from my HTC PH39100 using Tapatalk 2
Click to expand...
Click to collapse
Doesn't building, I made the tree like you said with these files no luck.. I went to the Crespo 4gs and it has two folders.. But mine has 1. Also do u think I should port over some of the files i dont have from the crespo 4gs folder
itzdarockz said:
Doesn't building, I made the tree like you said with these files no luck.. I went to the Crespo 4gs and it has two folders.. But mine has 1. Also do u think I should port over some of the files i dont have from the crespo 4gs folder
Click to expand...
Click to collapse
Wouldnt hurt to try
Sent from my HTC PH39100 using Tapatalk 2
Hello !
In Tutorial about compile AOSP GB i see one think. When I write in terminal lunch i have list devices which i can compile. So I am in trouble becouse i don't know how can i add My device. I Download Source GB to my device but I have external folder, bionic and probably hardware (and kernel) So My Question is - How can I Add My phone to compile list, to compile flashable zip work?:fingers-crossed:
cheqolada said:
Hello !
In Tutorial about compile AOSP GB i see one think. When I write in terminal lunch i have list devices which i can compile. So I am in trouble becouse i don't know how can i add My device. I Download Source GB to my device but I have external folder, bionic and probably hardware (and kernel) So My Question is - How can I Add My phone to compile list, to compile flashable zip work?:fingers-crossed:
Click to expand...
Click to collapse
What is your device?
Sent from my GT-I9100 using xda app-developers app
xSkArx said:
What is your device?
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
Alcatel Ot - 908 / T-Mobile Move.
Hey guys i´m currently working on a AOSP-Theme and i want to include some APKs too.
So i´ve taken the cm7-launcher out of a cm7-rom.
Now i want the latest version of this launcher. Looked in the cyanogenmod-repositories and found the launcher.
The problem is, that when i download the pack its in sourcecode and not compiled. Well thats not the real problem..
I just want to know, is there a way to build a APK from Github in Windows?
I´ve searched now for 2 days and never found a right solution :/
Thanks instead
luxxx123 said:
Hey guys i´m currently working on a AOSP-Theme and i want to include some APKs too.
So i´ve taken the cm7-launcher out of a cm7-rom.
Now i want the latest version of this launcher. Looked in the cyanogenmod-repositories and found the launcher.
The problem is, that when i download the pack its in sourcecode and not compiled. Well thats not the real problem..
I just want to know, is there a way to build a APK from Github in Windows?
I´ve searched now for 2 days and never found a right solution :/
Thanks instead
Click to expand...
Click to collapse
Don't know about github but you can do it with eclipse
Sent from my A116 using Tapatalk 2
sak-venom1997 said:
Don't know about github but you can do it with eclipse
Sent from my A116 using Tapatalk 2
Click to expand...
Click to collapse
Thanks for your fast answer.
Already tried it.
1. Downloaded sourcecode as zip.
2. Extracted
3. File -> import -> Android (Existing Android Code into Workspace)
The problem is just that nearly all java-files are marked with exclamation marks and red crosses.
I attached a screenshot for you.
You have a suitable solution for this?
Thanks for your help
Before i forget it: i have ADT-Plugin, Android SDK and JDK installed
luxxx123 said:
Thanks for your fast answer.
Already tried it.
1. Downloaded sourcecode as zip.
2. Extracted
3. File -> import -> Android (Existing Android Code into Workspace)
The problem is just that nearly all java-files are marked with exclamation marks and red crosses.
I attached a screenshot for you.
You have a suitable solution for this?
Thanks for your help
Before i forget it: i have ADT-Plugin, Android SDK and JDK installed
Click to expand...
Click to collapse
They're showing errors could you post screens of each class
Try this
Make sure you set the same api version as is the source for launcher
Sent from my A116 using Tapatalk 2
sak-venom1997 said:
They're showing errors could you post screens of each class
Try this
Make sure you set the same api version as is the source for launcher
Sent from my A116 using Tapatalk 2
Click to expand...
Click to collapse
I´ve set the API version by clicking with "right click on project -> properties -> Android -> Android 2.3.3 (API10)" to API10 and the launcher
i want to compile is out of "gingerbread" branch from cyanogenmod-github-repo.
But nothing changed, because it already was set to API10.
I´ve attached a excel-sheet with discription, resource, path location, and so on.
Hope it helps
Thanks for your help
luxxx123 said:
I´ve set the API version by clicking with "right click on project -> properties -> Android -> Android 2.3.3 (API10)" to API10 and the launcher
i want to compile is out of "gingerbread" branch from cyanogenmod-github-repo.
But nothing changed, because it already was set to API10.
I´ve attached a excel-sheet with discription, resource, path location, and so on.
Hope it helps
Thanks for your help
Click to expand...
Click to collapse
It is using some cynanogen mod resources which are not there in android repository so it won't compile more over u can't use a cynanogen launcher with any rom if you whish to do so you would have to mod the code so that it can run with any Android
Search xda I think there may b some cynanogen launhers
Sent from my A116 using Tapatalk 2