Man, many Telcos, blocks IMEIs with 0000 at front. You should restore your right IMEI (in system/efs).
Working links are in this post by krarvind: http://xdaforums.com/showpost.php?p=24138570&postcount=2788
I've patched CM9 sources yesterday (it's actually one single number regarding memory reservation), recompiled, tested - seems to work. Users reporting working hw acc and 720p recording with patched Slim-ICS and 386Mb kernel version. This would be a great addition for our low RAM device for sure (if we don't find anything else breaking).
In which parts does the SGS camera require more RAM than crespo?
When you open a new threat with the nightlies, please post here the threat link.
@pawitp
Now, we have nightlies? No more kang builds?
When you open a new threat with the nightlies, please post here the threat link.
Thanks!!!
Wow the screen sucking my battery...72%
Sent from my GT-I9000 using XDA
Anyone running BUILD 17 or the 4.0.4 build and can reliably reproduce the hello-hello bug (or similar bugs)? Looking for testers.
did you load the latest gapps 20120317?
just ..... keep ..... looking ..... at ..... your ..... screen.......
you ... are ... feeling .... sleepy .... and comfortable ......
don't look awayyyyyyyyyyyy
Broken links, but I'd say that it's not really possible. Our camera (which is different from crespo) requires more RAM.
But after Krarvind Patch Over his Slim ICS(for SGS)Camera working Perfectly with 387MB of RAM !!
So if you can reproduce the HHB bug (or a similar bug), try flashing this zip containing a fix FaultException made for a similar bug on the Vibrant and then report back if it fixes it or breaks it further or has no effect. If you're not experiencing the bug, you might want to try it anyway to see if it breaks anything.
Wow the development on this is going enormously fast. And now we're already getting nightlys after such a short amount of time. Can't thank you and everyone involved enough.
Tapatalked
Current build
Last build without the problem
Stock kernel?
Current modem
Any other modification you've made to the ROM.
What were you doing
How often does the problem occur?
Attach a logcat
Attach last_kmsg if it's a random reboot (If it rebooted into recovery, get it while booted into recovery. Also get /proc/cmdline.)
setprop persist.sys.usb.config mass_storage,adb
setprop persist.sys.usb.config mtp,adb
touch /datadata/.nodatadata