Database Info

[Q] flash a galaxy s rom on sns?

Hey is it possible to flash a galaxy s rom on the sns ? I think it could be very cool to run a tw rom.
Have a nice weekend
Sent from my Nexus S using Tapatalk

hoseth0711 said:
Hey is it possible to flash a galaxy s rom on the sns ? I think it could be very cool to run a tw rom.
Have a nice weekend
Sent from my Nexus S using Tapatalk
Click to expand...
Click to collapse
I don't think you could take a current SGS ROM and flash it on the SNS without tweaks and mods to it. Hardware drivers are probably different, so that's the first issue you'd have. Also, depending on the version of the SGS you have, even the physical buttons are off.
Some people were able to run i9000 ROMs on the Vibrant with only minimal issues, but folks on the Captivate had screen orientation issues and other stuff. We know for a fact that the radios in the SNS are different than the other models (low power chips).

distortedloop said:
I don't think you could take a current SGS ROM and flash it on the SNS without tweaks and mods to it. Hardware drivers are probably different, so that's the first issue you'd have. Also, depending on the version of the SGS you have, even the physical buttons are off.
Some people were able to run i9000 ROMs on the Vibrant with only minimal issues, but folks on the Captivate had screen orientation issues and other stuff. We know for a fact that the radios in the SNS are different than the other models (low power chips).
Click to expand...
Click to collapse
Hmm ok, thank you. I just think it's sad that the rom development for sns is nearly totaly dead
Sent from my Nexus S using Tapatalk

hoseth0711 said:
Hmm ok, thank you. I just think it's sad that the rom development for sns is nearly totaly dead
Sent from my Nexus S using Tapatalk
Click to expand...
Click to collapse
Give it a little time, the phone's only been out 5 weeks. The Galaxy S variants, even the i9000, which came out globally and first (last May), didn't have many custom roms until at least a month (I think MCR was first in June), and the action really didn't get heavy until August/September (so 3-4 months).
We'll hit critical mass soon enough with the devs.
Cyanogen's almost ready for "beta" or "release candidate status", and MCR is looking pretty stable, and you've got Team Whisky/Bionix that many are praising. I think we're off to a good start, even if it's not a fast-running one!

distortedloop said:
Give it a little time, the phone's only been out 5 weeks. The Galaxy S variants, even the i9000, which came out globally and first (last May), didn't have many custom roms until at least a month (I think MCR was first in June), and the action really didn't get heavy until August/September (so 3-4 months).
We'll hit critical mass soon enough with the devs.
Cyanogen's almost ready for "beta" or "release candidate status", and MCR is looking pretty stable, and you've got Team Whisky/Bionix that many are praising. I think we're off to a good start, even if it's not a fast-running one!
Click to expand...
Click to collapse
Actually I believe we're on CM7rc9. Don't think they count as beta anymore given how stable it is. I use rc7 as my daily driver and I haven't had a single random reboot (even running an OC kernel). Honestly, yes our rom development isn't huge yet but morfic (think thats his name, the guy who makes the trinity kernel) is f***ing awesome. The guy really listens to the input of his users and just makes quality s***. He really is impressive.

kenvan19 said:
Actually I believe we're on CM7rc9. Don't think they count as beta anymore given how stable it is. I use rc7 as my daily driver and I haven't had a single random reboot (even running an OC kernel). Honestly, yes our rom development isn't huge yet but morfic (think thats his name, the guy who makes the trinity kernel) is f***ing awesome. The guy really listens to the input of his users and just makes quality s***. He really is impressive.
Click to expand...
Click to collapse
Agreed 100% about morfic. I remember him in the early days of the Galaxy S i9000.
I didn't know Cyanogen was at rc7 already. Good to know, and time for me to consider actually using it as my daily driver. I'm actually pretty happy with stock Gingerbread, but CM has always rocked my phones that it's out for.

hoseth0711 said:
Hmm ok, thank you. I just think it's sad that the rom development for sns is nearly totaly dead
Sent from my Nexus S using Tapatalk
Click to expand...
Click to collapse
umm... no it isn't
a lot of 'developers' don't compile from AOSP source; instead they base their ROMs off CM7 or GRH78.. so they're probably waiting for that as a start (not meant to disrespect anyone)
I consider CM7 to be a significant point in NS (i hate saying SNS) development. The Galaxy S series have been wanting CM support for a long time and the NS is the first to get it. At this point, I wouldn't even know if the Galaxy S would get CM support or not, it might but given the difficulties with Samsung releasing the source for drivers; it'll certainly be difficult as well as the Galaxy S diversity (I9000, Captivate, Epic 4G, Fascinate, Vibrant) whereas the Nexus S is just the Nexus S worldwide.

Seriously,
I don't know how you think development is dead. If anything, it's just getting started. And there's 3 great roms to choose from so far. Many phone users are grateful for having even 1 modded rom to use. And, as mentioned above, CM7 was first working on NS's instead of the Galaxy S.
I see a long future for the Nexus S in terms of rom development. I'm sorry you feel that way. May I ask, what phone are you referring to that has "alive" development, as compared to our "dead" development?

nickmv said:
Seriously,
I don't know how you think development is dead. If anything, it's just getting started. And there's 3 great roms to choose from so far. Many phone users are grateful for having even 1 modded rom to use. And, as mentioned above, CM7 was first working on NS's instead of the Galaxy S.
I see a long future for the Nexus S in terms of rom development. I'm sorry you feel that way. May I ask, what phone are you referring to that has "alive" development, as compared to our "dead" development?
Click to expand...
Click to collapse
What he said. That's one thing I highly miss about the G1. It was the first Android phone and thats where it all started. ROMs were all booming and now the community is all split apart.
It's not dead at all, it's just getting warmed up Once CM7's official RC or Stable is released (I personally consider the nightly to be a daily driver/stable), it'll be a gateway to many other great ROMs that is based off CM7.

[ROM] CyanogenMod 7 b2 for vega (04/03/2011)

I know all you guys have been waiting for 2.3 on the vega well here it is its very raw and probably not good enough for every day use.The build is at the same stage as the gtab so it has all the same bugs and so on as the gtab plus a few more just for us lol :-D(as we don't have kernel source yet :-( ).
There will be little support if any for this build as i am currently working on a LOT of stuff. But when we get kernel source i can work some more on this
Please have the stock rom and nvflash ready in-case u have to recover from this :-D
Nither me or the cyanogenmod team are responsible for any damage caused by this rom weather that is bricking your device, eating babies, global warming or your house burning down !
ChangeLog[/B
B1
- Status Bar Buttons
- Newer CM src (due to issues with 2.3.3 not latest)
(WIPE DATA IF COMING FROM STOCK ROM)
B1
- Fixed Camera
- Fixed Rotation
- Latest CM source
[What Doesnt Work]
- Some GPS apps will FC (maps works but it needs to be version 5.0) the gtab has these same issues when they have a fix so will we
[What Does Work]
- Everything Else !
[Requirements]
- Advent Vega (ovb)
- ClockworkMod 2.x.x
[Install]
the normal way in clockworkmod :-D
[Download]
B2 HERE !
To enable camera
in adb shell / terminal app / gscript
ON = "echo 'set28h' > /proc/gpio"
OFF = "echo 'set28l' > /proc/gpio"
I suggest having the camera off when not in use as i haven't tested the affects of having it on for long periods of time are
[Credits]
- Bekit + sceptrr for the original gtab vendor setup
- CyanogenMod team for there awesome src
- Anyone else i missed

im so gona flash this. if its only camera, rotation and video decoding not working it seams usable to me. I just have to wait to friday maybe monday when my POV Mobii arrives. I got CM7 on my DHD. I also have an Archos70IT but no roms for that and a Toshiba Folio wich really is quiet nice. But it dosent have that strong community and rom devs around it. Then i saw that You had jumped on AdventVega and was going to make a CM7 build for it+ it has several other roms and rom builders working for it. So i orderd one. I really miss having an active community around the devices i got. Well the Desire HD is good, but the plates i got, when i check there forums almost never any activity. I hope people will tturn to Xda for the Vega not just Modaco.
I just your kernels for the DHD. Always good qquality work, thats promising for the CM7 for Vega.
PS. Download link for CM6 dont work, i only get error 404. Could you please upload a working link

I really need rotation to work before I can stick on one of these CM roms
However good news, kernel sources should be out today or tomorrow and Paul at modaco may already have it.

Nice one, I thought you'd abandoned this.

What is the point of releasing cm7 when you get cm6 to work properly for day to day use. I say waste of time.

Whats the point on working on 2.2 when 2.3 runs with the same buggs?

Apache14 said:
Whats the point on working on 2.2 when 2.3 runs with the same buggs?
Click to expand...
Click to collapse
I concur, plus CM7 has better features for our tablets than CM6.1 i.e. how to move apps2sd

It still doesn't make sense as both of them still buggy and not good for daily use.

lol the issue is the fix for sensors on 2.2 would fix 2.3 soo really 2.3 is thing to work at ... that and getting a solid vendor base so when 3.0 hits aosp we will be able to make best use of it .....
the main issue is nither 2.2 or 2.3 aosp have any real support for tegra 2 chips (hw decoding and other features) .... 3.0 aosp will do as there main device will be tegra based im hoping it wont be too much trouble getting 3.0 on this device

Apache14 said:
lol the issue is the fix for sensors on 2.2 would fix 2.3 soo really 2.3 is thing to work at ... that and getting a solid vendor base so when 3.0 hits aosp we will be able to make best use of it .....
the main issue is nither 2.2 or 2.3 aosp have any real support for tegra 2 chips (hw decoding and other features) .... 3.0 aosp will do as there main device will be tegra based im hoping it wont be too much trouble getting 3.0 on this device
Click to expand...
Click to collapse
Shouldn't be, and of course I will do all I can to help you or whoever decides to build it.

Fair enough. @apache14 I pm u some days ago did you get it.

Lennyuk said:
Shouldn't be, and of course I will do all I can to help you or whoever decides to build it.
Click to expand...
Click to collapse
nice :-D I will be .... im hoping to become the maintainer for vega on CM git (also need to get the vega into RaiderX's hands )
alphaola said:
Fair enough. @apache14 I pm u some days ago did you get it.
Click to expand...
Click to collapse
Oh did u ? i didnt see ill look for it in a bit mate

Apache14 said:
nice :-D I will be .... im hoping to become the maintainer for vega on CM git (also need to get the vega into RaiderX's hands )
Oh did u ? i didnt see ill look for it in a bit mate
Click to expand...
Click to collapse
Well if enough people donate to Raider he will soon have enough ££ to get one.

Nice work, Apache14!
Also, the kernel source is being released by Advent tomorrow.
http://twitter.com/adventvega

This rom is working awesome for me so far.
Installed the gapps from here http://goo-inside.me/google-apps/
Thanks bumbledroid.

Is this useful? -> http://forum.xda-developers.com/showthread.php?t=912197

@apache14, you didn't get back to me about the pm.I guess you choosed to ignore me. Cheers

alphaola said:
@apache14, you didn't get back to me about the pm.I guess you choosed to ignore me. Cheers
Click to expand...
Click to collapse
If apache14 didn't reply to you about the pm, then why would apache14 reply to you about this?
Also, apache14 will now probably ignore you, because you are too impatient, and don't realise that he/she may have other, more important things to do...

HunteronX said:
If apache14 didn't reply to you about the pm, then why would apache14 reply to you about this?
Also, apache14 will now probably ignore you, because you are too impatient, and don't realise that he/she may have other, more important things to do...
Click to expand...
Click to collapse
Or maybe his just arrogant ass that thinks he knows it all and can't acknowledge just a question. And its quite nosey to respond to someone's question especially when it specifically directed to someone [email protected], you don't know what the pm is about.so y unsolicited response.
I know you go on about its a forum and blah blah,am sure etiquette ring a bell to you.

Source code released - http://androidcommunity.com/advent-vega-source-code-v1-08-released-20110128/
This is good news, no?

[ROM] Showcase AOSP Froyo V0.9.1, Voodoo AOSP kernel, and GAPPS 3/20/2011

I AM IN NO WAY RESPONSIBLE FOR ANY DIRECTIONS YOU FOLLOW HERE NOR AM I RESPONSIBLE FOR THE PROBLEMS ANYTHING I HAVE CREATED MAY CAUSE YOU. YOU ASSUME ALL RESPONSIBILITY AND DISCLAIM THE RIGHTS TO SUE ME.
NEW RELEASE 3/28/2011
OK, time for a simultaneous release of AOSP Showcase and Mesmerize, with AOSP voodoo kernels and a set of GAPPS that jt1134 has built for us.
First of all lets give thanks to those that helped me out and made this happen. Phidelt82, thanks for testing and hosting the downloads. Elijahblake, thanks for testing and sticking to it even through your phone troubles that the inbetween releases and original (yet buggy) release called. Thanks dfgas for testing as well, and getting me important Mesmerize files. Baked_Tator, thanks for testing it, you provided great help. MrHanMan, thanks for testing, you provided great help as well. Thanks to all other testers who I can not remember their names at this moment (PM me and you'll get put in this list). Thanks jt1134 for all the work you put in on the fascinate rom lately, you've had me playing catch up, because though I strive, I can't be as fast as you. Thanks to lmartin92, for dedicating time, energy, and learning through the entire experience and making these builds happen (that's me)
Now to the order of business, announcing this release. You showcase users who have endured previous releases are now ready for a stable release and here it is. Yes some things are not working, but these are the things most folk can get along without.
What's working?
Bluetooth (though headsets, and keyboards may not work), file sending has been tested by many and is claimed to be working.
SMS is now working fully.
3g is working.
GPS is working.
Wifi is working.
Google contacts/gmail syncing is working (may require reboot or a bit of patience on your part).
In call sound volume setting is working thanks to jt1134.
It shows the proper company as to who is providing you services now.
Much more is probably working, but I can't identify them all nor make claims as of yet.
What isn't working?
Bluetooth headset.
MMS.
Video Camera.
Camera does not work at 5mp and it uses black and white previews.
Probably some other things, if you find them, let me know and I'll get to work fixing them.
Where can I get this?
The Showcase AOSP V0.9 rom release is here
mirror
and a torrent magnet link is magnet:?xt=urn:btih:7f1f77e7e9e9cd29cdf19b8eff9daa0ddaf8f9cf&dn=showcase-aosp-latest.zip&tr=http%3A%2F%2Fopenbittorent.com%2Fannounce.
The EC10 AOSP voodoo kernel is here.
The AOSP Gapps are here.
Use CWM Red to flash these in this order, kernel, rom, gapps. Anytime you flash the rom reflash gapps because the rom breaks gapps after reinstallation. Be sure to wipe data and cache before you reboot.
What happened to the kernel being inside of the rom? I've decided to seperate them out, if someone wants a non-voodoo kernel, they can make one and use it. It does have to be customized for AOSP. I just don't know yet how to do this, but it shouldn't be too hard.
In other words, I'm allowing folk to use different kernels than mine own if they care to put the work into it to make it happen.
WHATEVER YOU DO DO NOT *228 unless you wish to possibly lose your phone!
I would like to donate to the cause.
Glad to help you do that. I'm specifically looking to beef up my dev machine to a six core 16 GB ram beast. Of course, if anyone wants to participate in building, I'll actually donate some of my machine torwards a build server. These are the parts I would like to have, and I'm probably upgrading from 8GB 3core machine to a 12GB 3core machine next month (just modifying this sucker here).
I need 2 sets of this memory to make my dream happen. It's a Mushkin 2x4 GB ddr3 1333 (10666) MHZ). The cpu I would like to see is a six core AMD Phenom II x6 1100T. No I don't expect anyone to provide me with this, but this is what I'm going to upgrade to eventually and try to donate back to the community with a Samsung galaxy s i500 build server. By the way, when making donations I'm not the only one to consider. All those fine folk listed above deserve it just as much or more so than me. Now enough with my dreams.
Enjoy AOSP.
Changes in 0.9.1
Streaming issues kind of fixed (no hd youtube, but the rest seems to work).
New GAPPS.
New Kernel (EC10 from jt1134 which is a generic (works on all i500 devices to date) kernel)
GMAIL/contacts sync is fixed
For any questions, comments please join the IRC on #samsung-mesmerize on irc.freenode.net.

Fix for MY PROBLEM please READ FULLY!!!!
New Version is working GREAT!!!!! Thanks again Lmartin92 Thanks to JT1134 and thanks to everyone involved

Awwwwwwwwwww yeah!!!... Thanks to everyone involved!!!

Go go gadget Batesville. Thanks again for the goodies!

Now for some help on getting fixes
all i need fixed is sms and 3g.. I can work with that

Excellent job! I'm looking forward to seeing how this progresses.

Good work man, would you be so kind as to keep the title of this like the rest and add [ROM] and EB11?
I'm also interested in seeing some screenshots .

No problem, changed. That's good info right there, makes this as easily searchable as the rest. Thanks.

lmartin92 said:
No problem, changed. That's good info right there, makes this as easily searchable as the rest. Thanks.
Click to expand...
Click to collapse
No prob, plus this should save you from answering some dumb questions . Glad to see the showcase getting some Dev love!

I'll add some sms debug to the framework tonight. Shouldn't be hard to fix.
Sent from my SCH-I800 using XDA App

Actually, if someone could send me a deodexed framework.jar from a stock build, I can decompile it find a fix that way instead of wasting time on debugging
Sent from my SCH-I800 using XDA App

jt1134 said:
Actually, if someone could send me a deodexed framework.jar from a stock build, I can decompile it find a fix that way instead of wasting time on debugging
Sent from my SCH-I800 using XDA App
Click to expand...
Click to collapse
i can definitely do that for ya...
This is from the picknpack 3 for the showcase
http://www.megaupload.com/?d=93OJ5MTE
THANKS!!!!!!!!!!!!!!!

This is from phidelt82's Pick-and-Pack .3, which is based on Stock Froyo, I think.
EDIT: *shakes fist at elijah*

Updated Post#2 with how i fixed MY *228 and possibly other NONO debacle...
Be sure you read my exact problems before attempting my fix though please!!!!

Yeah the problem may be the fact there's no Cellular South info even in the apns-conf file haha. And some of the build.prop information is for Verizon, and there's values in there for GSM ? Er?

I flashed the one for the fascinate on my mez. My baseband still read eb16 I had 3g data idk will flash back at lunch and see if texting works but calls and data do. I was in a roaming area I work in a uscc home area that will tell it lol. Are those quadrant scores real? I mean I know that on the vibrant the test was high because of h.264 not working correctly.
Sent from my SCH-I500 using XDA App

stephenj37826 said:
I flashed the one for the fascinate on my mez. My baseband still read eb16 I had 3g data idk will flash back at lunch and see if texting works but calls and data do. I was in a roaming area I work in a uscc home area that will tell it lol. Are those quadrant scores real? I mean I know that on the vibrant the test was high because of h.264 not working correctly.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Are you asking if the scores in my pics on post #2 are real? lol, YES THEY're REAL!!!

I got the same scores lol I'm just saying that the test itself could be flawed kinda like oclf scores arent accurate
Sent from my SCH-I500 using XDA App

Also it still linpacks the same
Sent from my SCH-I500 using XDA App

stephenj37826 said:
Also it still linpacks the same
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
well, it definitely doesn't feel the same, no lagging and stuttering when skimming through contacts.. Even the market is smoother for me..

light sensor - custom kernels with Froyo stock

I have stock Froyo ROM.
With stock kernel, the light sensor works fine. I can use the built-in auto-brightness (settings/display/brightness / auto), and I can use my own Tasker auto-brightness routine, and I can see the tasker variable %LIGHT change with ambient light level (albeit in discrete steps).
I installed 3 different custom Kernel’s:
Defuse 1.4
Infusion 1.8
Infusion 2.0
With each of these, light sensor doesn’t seem to work. Built-in auto-brightnes doesn’t work. My tasker auto-brightness doesn’t work. Tasker %LIGHT value reads 100 lumens no matter whether you are in a dark closet or bright sunlight.
Just to make sure it wasn’t my phone, I disabled voodoo lagfix and went back to stock kernel again (from a backup I had made). Light sensor works fine once again. It’s definitely something about those kernels.
.
Question 1 - Does anyone else remember seeing this?
(I’m kind of surprised that searching didn’t show this in the general, q&a or developer forums....how could I be the only one to notice????).
Question 2 - By any chance, are any patch or fixes known?
(I doubt it, but just figure I’d ask)
By the way, this is by no means a complaint. I am very happy with the performance of those kernels and plan on keeping them as long as I’m in stock Froyo (which might be quite awhile). I can see the improvement in response time in menus, in swiping home screens (and in Quadrant fwiw). I tested all the other features I can think of and everything else works flawlessly (except possibly some extra flashing from BNL feature on Infusion 2.0, already well discussed in developer’s thread). I am very, VERY grateful to the developers that gave us these kernels last year and continue to work on great new things to share with us.

Probably just some wrong code that needs fixed... and it wont be fixed either, all have moved on bigtime lol. It would also seem useless to go back and change it...
Sent from my SGH-I997 using xda app-developers app

Ryanscool said:
Probably just some wrong code that needs fixed... and it wont be fixed either, all have moved on bigtime lol. It would also seem useless to go back and change it...
Sent from my SGH-I997 using xda app-developers app
Click to expand...
Click to collapse
It certainly wouldn't be useless to me. I got 5 Infuse phones for my five immediate family members, and I am sort of the go-to guy within the family for questions. For one thing I might do better helping them if I stick with Froyo (although I haven't quite made up my mind on that... might try for some stable GB either stock or AEON on my phone only) . For another thing, they are not interested in changing things they have figured out, so if I can give them custom kernel with their Froyo, it would make their phones faster wthout forcing them onto a new OS.
But since I don't have any ability to develop a fix myself and as you mentioned, those who do have long since moved on to bigger/better and newer things. So useless or not is probably an irrelevant point... it ain't gonna happen.
It's also weird that the same problem happened on all those different kernels from different developers. Makes me wonder if somehow I'm missing something and doing something wrong on my end, although I don't know what that could be. Oh well.
Thanks for responding.

BLN support

Is there an Infuse 4g kernel that supports BLN (capacitive lights turn on when there is a notification)?
If yes, is there one that works with the ParanoidAndroid ROM?

mesosmart said:
Is there an Infuse 4g kernel that supports BLN (capacitive lights turn on when there is a notification)?
If yes, is there one that works with the ParanoidAndroid ROM?
Click to expand...
Click to collapse
Bedwa's Froyo Infusion kernel 1.8 or 2.0 (I forget which but I'm pretty sure one and not the other) has BLN.... in the unlikely event that you want Froyo.
I tried it out and it worked, although had some extra flashes occuring on occasion when I didn't expect them.
I noticed this free App called NoLED... to accomplish various types of visual notification with display "off" except for a relatively few pixels on the AMOLED display.
Check out the developer's thread including a video overview:
http://forum.xda-developers.com/showthread.php?t=730692
haven't tried it.
Maybe others know of something more useful that I didn't mention...

Must have been too hard to search cause that's been talked about more times then I can count.
Planning my escape!