So the rom you compiled didn't work?
Sent from my SGH-I997 using Tapatalk 2 Beta-5
So the rom you compiled didn't work?
Sent from my SGH-I997 using Tapatalk 2 Beta-5
So the rom you compiled didn't work?
Sent from my SGH-I997 using Tapatalk 2 Beta-5
ugh...that was ****ing ridiculous
I originally started off with the kernel source used for CM7. Apparently that doesn't work as is. Switched to the latest kernel drop from Samsung for the AT&T version, and that boots using GB bootladers Now just have to reapply 100 ****ing kernel patches lol.
I don't know if it will help, but way back when, we had froyo roms.
Then the Canadian's Rogers Infuse showed up with GB.
All the customs kernels are derived from Rogers'.
Initially, when the Infuse was running with Froyo and then tried a GB based rom, without boot loaders, there was a rainbow, multicolor effect.
It still happens today on occasion, especially when a user use GTG's ultimate unbrick back to froyo and install a GB rom.
The unbrick - using repartition and pit files - may erase the previously installed GB bootloaders.
The work around has been to odin a GB leak, heimdall a Gb leak to obtain bootloaders.
I can't remember who, but one of the kernel dev (Linuxbozo, bedwa, gtg or Entropy) came up with a fix - and that was the end to the rainbow thread.
http://xdaforums.com/showthread.php?t=1197472
I have noted a few other users getting rid of rainbow simply by flashing entropy's kernel - i'm not sure if infusion kernel works too...there maybe some thing added to those kernels that "unlocks" or bypass the GB bootloaders.
1.The problem was that I flashed GB bootloaders, and they would not work with the kernel I was using that was based on the CM7 (rogers) source code. No rainbow, just no boot.
2. At that point I couldn't downgrade the bootloaders, so I switched to the newest kernel source from AT&T. It seems to work fine with the new kernel source and ROM, no rainbow effect, and fixed the issues I was having that caused me to start messing with the bootloaders to begin with. At this point everything seems to work OK with the GB bootloaders, no idea if it works at all with froyo bootloaders.
Here's a preview build now that my source tree is mostly sorted out: http://www.mediafire.com/?1nhagihfoqqpkf3
To flash, you must first flash this recovery: http://www.mediafire.com/?2000k5y512spft4
Then boot into recovery, wipe data/cache, go to mounts and storage and format system, then flash the rom. Gapps are here: http://goo.im/gapps/gapps-ics-20120317-signed.zip . You'll probably have to mount system manually under mounts and storage before flashing gapps.
I've only tested this using gingerbread bootloaders, no idea if it works using froyo bootloaders. If you don't want to deal with the caveats of gb bootloaders, then well, fix it yourself.
what works:
touchscreen
audio
wifi
sensors
hw acceleration
software and hardware video decoding
data usage monitor (for wifi at least)
what doesn't work:
camera/camcorder
bluetooth
anything else is either broken or completely untested.
Followed the process, CM9 Booted up. It's working so far Great job!
I am able to send texts, make calls, and connect to data if that's what you mean.
ROFL...camera was easier to fix than expected. ugh I need sleep
ROFL...camera was easier to fix than expected. ugh I need sleep
dman3285 said:
dman3285 said:The four devices I built aosp ics for... Not ports... Prove you wrong.. Period... I was building roms since the original.... But there's always some dew who thinks they know it all.... But this I know about.... I have a build for this device.. No kernel because our kernel is so hard to develop for....and when you port ics... What do u use as proprietary files? That's right... Gingerbread files... This is like talking to a wall... You have fun porting...
dman3285 said:Nonsense....have you built it... do you even understand what your saying??? I HAVE built it... all that technical mumbo means 0... bottom line...I've done it...3 now 4 other devs have also done it...