Hi All
Now for the last 2 weeks I have been looking at the Original development thread and the more you look at it the more you see Android 4.0.4 versions pop up.
Could someone please define for me what makes it version 4.0.4 as when iI rip the roms apart all of them in the log files of the Roms say XWLPS or something with a clear Android 4.0.3 next to it.
What confuse me about this is what makes it 4.0.4 when the internals of the DEODEX'ed files all say its 4.0.3?
I pulled all these roms apart because I wanted to see where the 4.0.4 comes from but ... ye
What?
4.0.4 roms are AOKP/CM9/AOSP roms
All ssung roms are 4.0.3 based till now
You may google are the changes between 4.0.3 and 4.0.4
Sent from my GT-I9100 using Tapatalk 2
sahibunlimited said:
What?
4.0.4 roms are AOKP/CM9/AOSP roms
All ssung roms are 4.0.3 based till now
You may google are the changes between 4.0.3 and 4.0.4
Sent from my GT-I9100 using Tapatalk 2
Click to expand...
Click to collapse
Ok so that being said it would mean that the 4.0.4 is a made up version they gave their roms to be and not a true 4.0.4?
I'm trying to understand this as there will be a official 4.0.4 for the SGS2 and what then? Will they call their roms 4.0.5?
Cause their 4.0.4 wont be anything close to the official 4.0.4 ...
PS... Thanks for the person giving the tread a 1 star rating ... You really take trolling to a new level. Really epic work on you for being a coward rating the topic and not posting who you are.
toxicdust said:
Ok so that being said it would mean that the 4.0.4 is a made up version they gave their roms to be and not a true 4.0.4?
I'm trying to understand this as there will be a official 4.0.4 for the SGS2 and what then? Will they call their roms 4.0.5?
Cause their 4.0.4 wont be anything close to the official 4.0.4 ...
PS... Thanks for the person giving the tread a 1 star rating ... You really take trolling to a new level. Really epic work on you for being a coward rating the topic and not posting who you are.
Click to expand...
Click to collapse
4.0.4 has some fixes. The reason AOSP/AOKP/CM9 have version 4.0.4 is because they are built from sources directly from Google.
Samsung has yet to release an ICS version with 4.0.4 sources integrated into their version of ICS yet, thus they are still on 4.0.3. I presume once they integrate the 4.0.4 sources, they will also increment their versioning.
http://en.wikipedia.org/wiki/Android_version_history#Ice_Cream_Sandwich_4.0.x
ctomgee said:
4.0.4 has some fixes. The reason AOSP/AOKP/CM9 have version 4.0.4 is because they are built from sources directly from Google.
Samsung has yet to release an ICS version with 4.0.4 sources integrated into their version of ICS yet, thus they are still on 4.0.3. I presume once they integrate the 4.0.4 sources, they will also increment their versioning.
http://en.wikipedia.org/wiki/Android_version_history#Ice_Cream_Sandwich_4.0.x
Click to expand...
Click to collapse
Thanks. That clarifies it a bit. Was it sourced from the Nexus? Because I know the Nexus is currently on 4.0.4 and has been for a while from what I could tell.
Why I'm asking and there was a good reason was that I was looking for the source code to build a rom from it but seeing as there are no available Default roms out there I was wondering where it got ported from and who dump the source code on 4.0.3 base versions.
toxicdust said:
Thanks. That clarifies it a bit. Was it sourced from the Nexus? Because I know the Nexus is currently on 4.0.4 and has been for a while from what I could tell.
Why I'm asking and there was a good reason was that I was looking for the source code to build a rom from it but seeing as there are no available Default roms out there I was wondering where it got ported from and who dump the source code on 4.0.3 base versions.
Click to expand...
Click to collapse
If you want to make a new rom you will have to choose which base you want
Samsung
Samsung apps
4.0.3 for now
Good camera
Samsung apps like wifi direct
Touchwiz
CM9
Build from source
Daily updates (no ****, they update every day)
Some buggs like not so good camera and slow sdcard speed
No samsung apps
ability to switch to 2g only
4.0.4
AOKP
This is basicly CM9 with the rom control app which gives alot of customization
This is my knowledge, everyone can correct me if im wrong
They both have advantages and disadvantages...
manmad said:
If you want to make a new rom you will have to choose which base you want
Samsung
Samsung apps
4.0.3 for now
Good camera
Samsung apps like wifi direct
Touchwiz
CM9
Build from source
Daily updates (no ****, they update every day)
Some buggs like not so good camera and slow sdcard speed
No samsung apps
ability to switch to 2g only
4.0.4
AOKP
This is basicly CM9 with the rom control app which gives alot of customization
This is my knowledge, everyone can correct me if im wrong
They both have advantages and disadvantages...
Click to expand...
Click to collapse
I was looking to build a Samsung 4.0.4 rom. Thats why I wanted to look into the Source to update the relevant 4.0.3 framework or lib to make it work. But might just wait then for JB 4.1 to be released in the next month or 2
toxicdust said:
some muddled up spam about looking at source code without any clue what source code is
Click to expand...
Click to collapse
I've got no idea what you're going on about, so I'm just going to stick this here in the hope you can learn and understand yourself.
http://source.android.com/
http://en.wikipedia.org/wiki/Android_(operating_system)#Android_Open_Source_Project
oinkylicious said:
Replaced with a random trolling trololololol as I want to be cool and think I am so epic
Click to expand...
Click to collapse
Wow thanks... You were probably also born knowing everything. You aspire ppl to kill themselves. Hope you are proud of yourself
Could a mod please delete this tread as clearly trying to do something for the community is only left for the elite and those born knowing everything.
Seriously so over this BS with ppl giving crap comments when something is begin asked. If you didn't want to help then don't post its really not that hard to understand is it.
toxicdust said:
Wow thanks.
Click to expand...
Click to collapse
You're welcome, looking forward to your ROM.
Your info is all wrong, instead of getting angry on comments who are iterated by your wrong assumptions, try to learn with open head and delete your wrong info from your head first.
Sent from my GT-I9100 using Tapatalk 2
Samsung only released 4.03
Google released the source of 4.04 so oems or whoever can make the rom out of it for their devices.
Thus AOSP rom's are the only ones for S2 that are on 4.04.
Sent from my GT-I9100 using Tapatalk 2
Ok ... So pulling the latest CM9 apart I found this and this is why I posed the question cause clearly calling me noob like you do in the tags is completely underestimating my skill level.
Lookin at the buildinfo and this dont lie and isnt noob like you guys call it. please explain the bold parts marked in the extraction.
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=IMM76D <- Seen in the menu
ro.build.display.id=IMM76D <- Seen in the menu
ro.build.version.incremental=eng.codeworkx.20120420.182038
ro.build.version.sdk=15
ro.build.version.codename=REL
ro.build.version.release=4.0.4 <- What is seen in the menu
ro.build.date=Fr 20. Apr 18:20:53 CEST 2012
ro.build.date.utc=1334938853
ro.build.type=userdebug
ro.build.user=codeworkx
ro.build.host=cyanogenmod
ro.build.tags=test-keys
ro.product.model=GT-I9100
ro.product.brand=Samsung
ro.product.name=GT-I9100
ro.product.device=galaxys2
ro.product.board=smdk4210
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=samsung
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=exynos4
# ro.build.product is obsolete; use ro.product.device
ro.build.product=galaxys2
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=GT-I9100-user 4.0.3 IML74K XXLPQ release-keys <- Not seen and in the background
ro.build.fingerprint=samsung/GT-I9100/GT-I9100:4.0.3/IML74K/XXLPQ:user/release-keys <- Not seen and in the background
ro.build.characteristics=default
ro.cm.device=galaxys2
# end build properties
#
# system.prop for galaxys2
#
Click to expand...
Click to collapse
Now clearly I'm the noob here but what I have pulled OUT of the latest 4.0.4 build shows something different. So please explain this
And then again I ask the noob question again
Define Android 4.0.4 ???
Ok I can do a build.prop for your placebo
ro.build.description=GT-I9100-user 4.0.4 IMM76D XXLPQ release-keys
ro.build.fingerprint=samsung/GT-I9100/GT-I9100:4.0.4/IMM76D/XXLPQ:user/release-keys
Click to expand...
Click to collapse
Here you go, try it, and get some compatibility issues on market, and perhaps some other apps
You can get android 4.0.4 changelog here
http://forum.xda-developers.com/showthread.php?t=1481044
Remind that build.prop is just a .txt renamed to .prop, used to define some properties needed for device. Android 4.0.4 content is built on sources, frameworks, all the apps inside, from google source trees, directly forked to CyanogenMod sources.
If you dont believe, just get a fresh CyanogenMod source, and get a fresh AOSP source, and do some diff patchs . Or just look at android/default.xml, and you will see.
Hope this answer your question.
D4rKn3sSyS said:
Ok I can do a build.prop for your placebo
Here you go, try it, and get some compatibility issues on market, and perhaps some other apps
You can get android 4.0.4 changelog here
http://forum.xda-developers.com/showthread.php?t=1481044
Remind that build.prop is just a .txt renamed to .prop, used to define some properties needed for device. Android 4.0.4 content is built on sources, frameworks, all the apps inside, from google source trees, directly forked to CyanogenMod sources.
If you dont believe, just get a fresh CyanogenMod source, and get a fresh AOSP source, and do some diff patchs . Or just look at android/default.xml, and you will see.
Hope this answer your question.
Click to expand...
Click to collapse
Finally a answer. Thanks. Reason I was asking is what I was seeing and what was shouted at me didn't make sense at all.
Now clearly I'm the noob here but what I have pulled OUT of the latest 4.0.4 build shows something different. So please explain this
And then again I ask the noob question again
Define Android 4.0.4 ???
Click to expand...
Click to collapse
Yes you are a noob, and getting angry over it is wrong.
You already got the answer, just let me add this, as I already told you source is from google but if you are not a manufacturer of a phone you need model specific codes for it to work. So you need Samsung specific codes/drivers.
That's why you see some 4.03 codes.
I give you a very good example that anyone can understand.
i9100G didn't had cm9 until Samsung released ICS for it, and right after that you get cm9 for it.
Related
I've been following the development of so-called ROMs for the Vibrant (and other SGS devices), but I have yet to see a single AOSP ROM. Even when Samsung released the original kernel sources for 2.1, there were no AOSP 2.1 ROMs. Why not? Is it because they don't know which BLOBs to pull for insertion or the proper vendor overlays?
Some developers have done great work with SGS kernels (especially supercurio and his Voodoo kernels ... eugene373's tend to always wipe the internal SD card unnecessarily ...). But, a kernel does not a ROM make ... therefore I ask, what is truly missing to build an AOSP ROM. I've gone through the sources, but I don't follow makefiles too well.
I know we have another month or so before Samsung is obligated to release their 2.2 kernel sources, but that should have no impact on 2.1 AOSP ROMs. Therefore, I ask "what is the hold up?" What is missing, and what might I contribute ...
Need 2.2 source code...
2.1 is a dead horse--why bother when 2.2/2.3 are out?
The reason to bother is to at least get AOSP running. Once its on 2.1, it'll be easier to get 2.2 AOSP running on it. But claiming 2.1 is a "dead horse" is the wrong path ... the real question still stands: after 9 months on the market their still are no AOSP ROMs.
MIUI
Now that vibrant 2.2 source is released ... we finally have a REAL AOSP port and my all time favorite from my old HD2 the MIUI.... so keep your heads up and wait for it to get finished.
Get a custom rom. There are so many good devs doing them don't waste your time on AOSP....... until they release the actual source code...... on April 22
sarim.ali said:
Now that vibrant 2.2 source is released ... we finally have a REAL AOSP port and my all time favorite from my old HD2 the MIUI.... so keep your heads up and wait for it to get finished.
Click to expand...
Click to collapse
Except, the 2.2 source for the Vibrant has not been released. The SGH-T959D that shows Froyo sources on Samsung's site is for the Canadian Fascinate, not the US T-Mobile Vibrant. Samsung has yet to release the 2.2 sources.
oka1 said:
Get a custom rom. There are so many good devs doing them don't waste your time on AOSP....... until they release the actual source code...... on April 22
Click to expand...
Click to collapse
Except the so-called "custom ROMs" are just modifications on the stock theme, a replacement kernel and a change of some of the supplied applications.
There is nothing close to a full "custom ROM" such as CyanogenMod or MIUI because we don't have Samsung's sources. What is passing for a "custom ROM" for the Vibrant are just repackaged files. It is akin to the "ROM cooking" that took place for the WinMo phones, not a truly ground-up build from source that is possible with Android.
EDT/Devs4Android has the MIUI build. From Source.
TW has a 2.2.1 in testing.
EDT has a 2.2.1 Beta released.
TW has a 2.3 AOSP in testing. From Source.
EDT has 2.2 AOSP in testing. From Source.
What you want is out there for you.
Watch the forums and reply when a call for Alpha testers is posted.
Hopefully it won't be long before you see a full TW/EDT/Devs4Android collaboration!
I think what the original poster is trying to ask (and I have the same question) is why were there never any real 2.1 AOSP, cyanogen5 for the vibrant. The source for 2.1 has been around for many months. Were some other proprietary bits missing, was the released source code such a mess that it was unbuildable, something else? With those questions in mind, why will things be any different when the 2.2 source comes out?
mattb3 said:
I think what the original poster is trying to ask (and I have the same question) is why were there never any real 2.1 AOSP, cyanogen5 for the vibrant. The source for 2.1 has been around for many months. Were some other proprietary bits missing, was the released source code such a mess that it was unbuildable, something else? With those questions in mind, why will things be any different when the 2.2 source comes out?
Click to expand...
Click to collapse
Yes, this is more towards what I was getting at. We do not have Samsung's kernel sources for 2.2. And, we do not have a Samsung provided vendor overlay.
When we receive these two pieces, then a true AOSP build will be possible. However, we do have the 2.1 kernel sources, so why wasn't a true AOSP build possible then? What was missing, and can we actually expect Samsung to release the overlay that's needed?
Actually, that's true. I know it was old but why didn't anyone build a 2.1 cyanogen or aosp rom? (Not to say its easy.)
Sent from my SGH-T959 using XDA App
A noob question, kindly can someone explain what is the vendor overlay stuff?
Many thanks!
Where have you been?
rpcameron said:
I've been following the development of so-called ROMs for the Vibrant (and other SGS devices), but I have yet to see a single AOSP ROM. Even when Samsung released the original kernel sources for 2.1, there were no AOSP 2.1 ROMs. Why not? Is it because they don't know which BLOBs to pull for insertion or the proper vendor overlays?
Some developers have done great work with SGS kernels (especially supercurio and his Voodoo kernels ... eugene373's tend to always wipe the internal SD card unnecessarily ...). But, a kernel does not a ROM make ... therefore I ask, what is truly missing to build an AOSP ROM. I've gone through the sources, but I don't follow makefiles too well.
I know we have another month or so before Samsung is obligated to release their 2.2 kernel sources, but that should have no impact on 2.1 AOSP ROMs. Therefore, I ask "what is the hold up?" What is missing, and what might I contribute ...
Click to expand...
Click to collapse
Dude theres been a true AOSP ROM for the Vibrant since like december and thats CM 6.1
Im running it now
rpcameron said:
I've been following the development of so-called ROMs for the Vibrant (and other SGS devices), but I have yet to see a single AOSP ROM. Even when Samsung released the original kernel sources for 2.1, there were no AOSP 2.1 ROMs. Why not? Is it because they don't know which BLOBs to pull for insertion or the proper vendor overlays?
Some developers have done great work with SGS kernels (especially supercurio and his Voodoo kernels ... eugene373's tend to always wipe the internal SD card unnecessarily ...). But, a kernel does not a ROM make ... therefore I ask, what is truly missing to build an AOSP ROM. I've gone through the sources, but I don't follow makefiles too well.
I know we have another month or so before Samsung is obligated to release their 2.2 kernel sources, but that should have no impact on 2.1 AOSP ROMs. Therefore, I ask "what is the hold up?" What is missing, and what might I contribute ...
Click to expand...
Click to collapse
For probably the same reason that many phones with non AOSP firmware running 1.5/1.6 did not bother with AOSP 1.5/1.6 when they were released around the time 2.1 source hit. Why bother developing at all for what is essentially an "out of date" OS.
The only people it seems who actively continue to develop for existing (as opposed to new) firmware are manufacturers and carriers. This stupidity should be left to the manufacturers who still do this.
One of the larger snags way back then (sits in his rocking chair on the porch) was a lack of understanding of the phones proprietary aspects and how to work around them. But we have a fairly clear understanding of Samsung's boot process now, and RFS can now easily be turned into a distant memory.
I would wager a guess that the apathy towards 2.1 will not repeat itself once we have 2.2 source widely available and the low level similarities between 2.2 and 2.3 should have Gingerbread being more than the experiment it currently is. It's been barely more than a week since Eugene's little present manifested and there are already proper and stable kernels available.
Keep in mind that the devs we do have, have done a phenomenal job of cleaning up, speeding up, and drastically enhancing our existing 2.2 release. And perhaps to the point where many will not really care, though I know many would still like to see CyanogenMod6/7 properly on this phone.
Master&Slave™ said:
Dude theres been a true AOSP ROM for the Vibrant since like december and thats CM 6.1
Im running it now
Click to expand...
Click to collapse
Um, that's not quite true. The CyanogenMod.com website lists 0 files available for download for either experimental or stable files. The CM6.1 you must be running is not a true CM build.
Also, CM is not AOSP, but rather AOSP with modifications.
phrozenflame said:
A noob question, kindly can someone explain what is the vendor overlay stuff?
Many thanks!
Click to expand...
Click to collapse
The vendor overlay tells the AOSP build system which proprietary files are needed from the device that are not available in source form. This includes things like GPS and video drivers, baseband firmware for wireless radios, &c.
hi everybody !
a month age i decided to compile a new rom for my Galaxy S absolutely from AOSP source ( branch 2.2.1_r1 ) after some compile-time problem and many painful steps to resolve ,eventually the rom successfully built and can boot it up flawlessly on emulator.
i create a nandroid backup of current rom and installed the compiled one. but i am facing new problem :
1- the phone successfully boots but after short while screen began
flicking several time and the phone go in deep sleep and never wakeup
( power button or menu button does not do any thing )
2- touch screen works only for some second that I can unlock the
phone
3- there is no network available
4- I have downloaded samsung opesource package for GT-I9000. it
contains a folder named 'platform' but when i merge these files to
AOSP , the compile process stops and fails again. if there any one can
help me which files from samsung source should i merge and how ? if
you now the answer and dont have spare time then some internet link or
online document is really useful .i have no problem studding and
reading and searching . reaching to target is my only hope .
I am really disappointed why there is not a good and complete step2step tutorial to compile an AOSP rom for galaxy s (GT-I9000) !!
such docs is available for phones like dell streak , desire , dream , magic , .... . i really want to to active these aspect on XDA forum and with help of all you ( mods and masters ) try to create such tutorial that any one in world can use to refer . i think XDA is the only reference on net to collect and create such help and document. please help me and leave PM or comment to agree ot disagree and from where can i start ?!! thank in advanced .
edit :
there is a google groups post that i send my question in Android-platform . if you prefer please join this group and active that post to ask any question related to 'galaxy s compile from source ' .
post located at http://groups.google.com/group/android-platform/browse_thread/thread/da5d6f18f3bd3c9b
hi guys i was looking around and saw a galnetmiui ICS build
it states " to mark our success at merging ICS with MIUI frameworks we have officially taking it on board to support all 17 official MIUI China Roms. We will be supporting all 17 roms from now on, and better still our stable builds will now include the ICS framework as standard."
after flashing is says i have 4.0.1
so does that mean i "have" ICS ?
so far its the smoothest thing that has ever been in my phone better that cm7 or official miui builds
thanks
good question, i was also a bit confused by this statement
i also want to know this
It's how the frames make it all work, bro.
LMGTFY:
frame·work/ˈfrāmˌwərk/
Noun:
An essential supporting structure of a building, vehicle, or object.
A basic structure underlying a system, concept, or text: "the theoretical framework of political sociology".3
It's like the house's foundations. It's what everything else is based upon.
So do you have ICS? In terms of content, no, you don't. You don't have ICS launcher, apps, etc. What you have is the ICS framework, the base.
and what's all included in this framework?
kernel, baseband, modem, ...
do i have the new functions of ICS?
thanks for answers
thanks 10 char
There's a link to Galnet website+forums in my signature. You might want to ask there, since XDA doesn't want to let Galnet make a ROM thread.
In this forum i can see two threads:
"Galaxy S II Original Android Development"
and
"Galaxy S II Android Development"
What's the difference?
Thanks!
Brgds,
M.
Bad move. Anyway, read this http://forum.xda-developers.com/showthread.php?t=1219612
Original Android = Stock Roms
Android Development = Custom Roms
custm_made said:
Original Android = Stock Roms
Android Development = Custom Roms
Click to expand...
Click to collapse
WRONG WRONG WRONG .
jje
seriously I always wonder about the right answer even I read the original post of the difference, I am not very good in english maybe thats why I didn't fully undertand the main difference, but I guess the below:
Original android: after sometime the ROM is being stable so it goes to that forum
Android: still under development and not proved to be usable as stable version
NOTE: I am not sure at all, and please if any one knows the right answer to confirm it ... we are not all good english speakers
In all honesty, why does it matter ? It's not important. However...Original Android development is exactly that, a forum for stuff that is original. Whereas Android development has pretty much 'everything else' development-wise & stuff that is often based on/contains parts of someone else's work.
I still don't get why knowing this is so important to you ? Besides, if you'd read & followed the link you were given (which lead to other links and an eventual answer), you would have got the answer I just gave you.
ahm_salloum said:
seriously I always wonder about the right answer even I read the original post of the difference, I am not very good in english maybe thats why I didn't fully undertand the main difference, but I guess the below:
Original android: after sometime the ROM is being stable so it goes to that forum
Android: still under development and not proved to be usable as stable version
NOTE: I am not sure at all, and please if any one knows the right answer to confirm it ... we are not all good english speakers
Click to expand...
Click to collapse
Enter on both sections an see it yourself.
Sent from my GT-I9100 using Tapatalk
parazitul80 said:
Enter on both sections an see it yourself.
Sent from my GT-I9100 using Tapatalk
Click to expand...
Click to collapse
I must be stupid but...
If we look at Original ROM index we've got Sammy, AOKP & AOSP based ROMs for both ICS & GB.
If we then take a look at Android ROM index we have Sammy, AOKP, AOSP & MIUI ROMs, also for ICS & GB.. and a new one for JB
Plus custom kernels in both sections aswell.
If by original we're talking about pure original as in not a modified/port of an already existing ROM then shouldn't it only be official Cyanogen, Kang, MIUI ROMS and maybe official Sammy releases in Original section?
Always Original Android best google experience
Hi guys.
While surfing the Internet I found the open source page Samsung (do not know if you already knew about it.). In it, is the official source code for Stock ROM of all editions of the GT-S5830 (L / I / M ...)
And there is something curious, there is a source code for of a S5830V ROM. I do not know that phone is, but this is not code for Android 2.3 is for Android 4.0. To know where I'm going.
Useful?. I hope so. :fingers-crossed:
If the code is to be useful, it will be possible to develop Custom ROM more stable and fully functional. :victory: Just need a good developer invest some of your time to take a look at, something that would be greatly appreciated and if I can with a good donation.
http://opensource.samsung.com/reception/receptionSub.do?method=search&searchValue=S5830
There's also many other models like the SIII / II / I, Y, S5550, etc, etc, etc
PS: Excuse my English, Google Translate I speak Spanish
Yeah, but most of Galaxy Ace here are the pure GT-S5830
I think he means that since the hardware is about the same we may able able to use some of the source code and code from the drivers to make a fully working CM9 for the GTS5830
Sent from my GT-S5830 using xda app-developers app
Yes. in fact, I think the only difference between an edition and another is just the modem, the bands used for mobile network.
Not sure, but seriously believe that these sources will serve to create fully functional CM9.
Please share
Ok, I don't know if this is important, but I found it on the README_Kernel file:
$ cd kernel/common/
$ make ARCH=arm bcm21553_cooperve_defconfig
$ make ARCH=arm CROSS_COMPILE=../../prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/arm-eabi- modules zImage -j`grep processor /proc/cpuinfo | wc -l`
Click to expand...
Click to collapse
BCM21553_Cooperve is the chipset of those C, M and I models, a.k.a Cooperve
I have this phone i bought it in australia lockd to vodafone network i manged to unlock it through them i posted here http://forum.xda-developers.com/showthread.php?t=1902313
I spoke to the samsung customer service rep who put me on hold to speak to the tech department he got back to me and said the V has the same chipset as the 5830i different only in the band
Im trying to flash the 5830i stock firmware throught odin and havnt done it yet
Definitely looks promising!
Downloading the code, i'll try to inspect it. ForceF said it had kernel version 140, afaik 5830is only have kernel 126
I downloaded it time ago,the kernel is for Gingerbread 2.6.35.7
The config is CooperVe for Galaxy Ace V
The config for Galaxy Ace I is totoro (Galaxy Y)
Why would they call it ICS if it's a GB build, wtf samsung :\
ZakooZ said:
Why would they call it ICS if it's a GB build, wtf samsung :\
Click to expand...
Click to collapse
Could have been a mistake...
POTATO!!!!
Hello i am new on this site on android & on forum. kindly can any one help me? i need BBM for android 2.3.6 i tryed to install BBM from this link
http://forum.xda-developers.com/showthread.php?t=2496483
but its not working & pop up window open saying Sorry! The application BBM (process com.bbm) has stopped unexpectedly. Please try again. Fore close.
Can any one help me please.
No, you need to ask the developers, but I highly doubt they will listen
All force-closes create a logcat entry. It would be nice if people would provide the extra information found therein more often...
Ok, reading the post provided, the op sais you need to extract some libs and push them to /system/lib. did you pushed them?
andresrivas said:
Ok, reading the post provided, the op sais you need to extract some libs and push them to /system/lib. did you pushed them?
Click to expand...
Click to collapse
I've tried that and it didn't work. It needs more development or wait until we have a complete functional Kernel and update to the latest Android version available.
douglasroos said:
I've tried that and it didn't work. It needs more development or wait until we have a complete functional Kernel and update to the latest Android version available.
Click to expand...
Click to collapse
"wait until we have a complete functional kernel"....so we don't have a complete functional kernel for GB (2.3.6, like your thread states you have and are looking for help with)? i'm sorry, but you have no idea what you're talking about and clearly haven't read anything. a 30 page thread and countless complaints about fc, no activity since October. go post something like this over in that thread or contact the dev directly. on top of that, the dev's account has been disabled, which pretty much means drop it and move on.
"latest Android version available" - officially for us 2.3.6 rev 145, unofficially 4.2.2 (stable)/4.3 (semi-stable), 4.4 in idk what early stage of dev (contact epinter for update, but not an eta)
I have no idea what i'm talking about? Excuse me ohh allmighty lord who knows everything. I have a question for you. What is the minimum android version required to run BBM? 4.0 right? Do we have that officially? No, so we have to flash custom roms. Maybe he didnt because he wants everything working at 100% and sticks with GB. The dev of BBM for 2.3.6 isnt developing the app anymore so we need yo wait until that app gets to work on GB or wait for a complete and functional kernel for the devs bring to us a fully functional Android ROM based on 4.3-4.4. LEARN to read before treat someone like a stupid 5years old kid.
Enviado desde mi MB860 mediante Tapatalk