Am I correct that this is the previous-style hack on our .32 and not a full build on .35 from the i9000 CM7 source? The latter has a *lot* working (basically everything, including video and camcorder -- helped by new GB video drivers!), but obviously radio is an issue for us.
Was PK doing the .35 CDMA-ification or this sort of .32 hack?
After flashing and playing around I attempted to flash back to TW EC01 with nandroid and it bootloops at boot screen. I then Odined back to DL09 stock everything and worked back up. still cant boot anything.
Jt, can we use cm7 themes for this or are themes rom specific similar to your cm6 build?
For some reason Root Explorer doesn't display anything, just a black screen. On the other hand, the File Manager that comes with this will display files (except for the contents of data/), but can't be used to r/w. Is this known or am I missing something?
Super user is causing issues, if you flash the CM7 OTB kernel that nemesis put out, it will fix QTadb and root explorer issues.
JT: Titanium Backup FCs after getting sudo for me. Gonna try and re-flash.
http://pastebin.com/zGTAU2Di
No dice. Oh well. Looks good!
W/System.err( 3171): java.io.FileNotFoundException: /data/data/com.keramidas.TitaniumBackup/shared_prefs/filter_default.bin (No such file or directory)
Looks like your titanium install is corrupt. It's missing one of its data files.
Sent from my SCH-I500 using XDA App
As do I, which is why I haven't set it as my daily driver yet. I've been using jt's stuff since super clean; he and kaos well definitely get the camera working.
KangBanging since day one!
CommRom 1.3
OTB 1.4
OC'd (stable) 1200 mhz
ED03
Tapatalked!
jt,
I was building your stuff just now and these cyanogen commits from tonight gave me some errors.
https://github.com/CyanogenMod/andr...mmit/a400a9ae85ea24a1fe307a437f20d55efe453168
https://github.com/CyanogenMod/andr...mmit/f4c5fbac0b2dcc19749c7f37285d553149957e1a
I just re-synced, using the prior revision in the manifest. That got me around it for now, waiting for the rest of the build to finish. When you merge changes for frameworks/base in your tree it will get rid of the errors.
I was also wondering how to go about removing the recovery from the zip for the build (and possibly the kernel as well). I know I can manually remove them from the zip after it's made, but I'd rather do it properly if I can. I was fighting with device/samsung/fascinate/BoardConfig.mk for awhile but it seemed like whenever I settled on a change the build would explode.
i love this rrom , are we going to see any new updates? i understand if we arent going. to , but just checking up if this gets mms capabilities, i will use it for tue rest of my life
This may peg my level of knowledge but here goes. . .What logs would be most beneficial? Assuming alogcat is the standard method, there are a lot of different options of logs in there. Any specific ones that would be the most helpful in tracking down a bug?
Not trying to clutter, hopefully avoiding more in the future