I believe that the radio on the device needs to match the version of the RIL (Radio Interface Layer.) Usually when you flash an RUU or update, it contains a radio firmware (radio.img) as well as associated RIL files. However, when you flash CyanogenMod or other third party ROM files they do not contain a matching radio, which means that your RIL and Radio can have interfaces that do not match causing issues.
My Google Spreadsheet (select "libhtc_ril.so" tab at the bottom of the spreadsheet) has a list of the various options associated with a RIL and Radio combination, including what RUU they are from. Which shows that RIL and Radio probably need to match.
This procedure may not work properly with CyanogenMod 7 (Android 2.3)!
I consider RIL files as the following on your Android system:
/lib/system/libhtc_ril.so
/lib/system/libril.so
/lib/system/libreference-ril.so
/lib/system/libganril.so
Conclusion: RIL files need to match the Radio you have flashed to have maximum compatibility!
Posts to Read
Flashable "Radio to RIL automatcher" which is ROM agnostic for matching your RIL to RADIO (by myself and rmk)
Stable RIL and Radio combination known to work with CyanogenMod 6.1.1 on HTC Vision
/system/build.prop settings to enable standard HTC Vision network performance and features on CyanogenMod 6.1.1
Radio & RIL Combination
2010-09-15 26.02.01.15_M2 (TMOUS 1.19.531.1) (MD5: 131444f66f3fd7ed62639cd5b291e988)
2010-09-24 26.02.00.24_M2 (WWE 1.22.405.1) (MD5: dc9fe8f440db4f609cb613d9510dcd21)
2010-10-08 26.03.02.08_M (WWE 1.31.405.1) (MD5: 1f96f09dc4a2b9383a7479fc6e21d46e)
2010-10-18 26.03.02.18_M3 (Asia HK CHT 1.34.708.3) (MD5: a70ee4f4b43011bb0efe209f86e97916)
2010-10-18 26.03.02.18_M3 (Asia India 1.34.720.3) (MD5: 3a02f88d1a8c2c6e7007ebc956ed6adc)
2010-10-18 26.03.02.18_M3 (Asia TW 1.34.709.3) (MD5: c668f5a9eea3c741aaa73d7f91e2d64c)
2010-10-18 26.03.02.18_M3 (BellMobility WWE 1.34.666.1) (MD5: 4b903470a1a020eee1aed59a8f88646e)
2010-10-18 26.03.02.18_M3 (WWE 1.34.405.3) (MD5: 7800526f22d74bb358e9702f18a00a87)
2010-10-26 26.03.02.26_M (WWE 1.34.405.5) (MD5: b89ccc5754e6b01090705d606b00dee2)
2010-11-17 26.04.02.17_M2 (Egypt 1.72.466.4) (MD5: 199cd21cbdc450c2ea1b0b839ed913fc)
2010-11-17 26.04.02.17_M2 (WWE 1.72.405.2) (MD5: 26991574aa541933e5e64de7b00314b7)
2010-12-20 26.04.02.17_M2 (ARA 1.83.415.2) (MD5: 4475dd875e20d37dc16c0e4a789b7685)
2010-12-20 26.04.02.17_M2 (Orange FR-B2B 1.85.73.2) (MD5: e6497a697f875bbc33a56be2cc71c669)
2010-12-20 26.04.02.17_M2 (WWE 1.82.405.1) (MD5: 4da76bb61684733f6c833eb5da17783c)
2011-01-27 26.06.02.27_M (Hutch AUS 1.85.861.3) (MD5: e699a37d4d7b9b26d5eaadf8e69be7dd)
But, am I correct in assuming that those settings do not matter if not used by the ROM in use on the device?
I mean, obviously the CM libhtc_ril.so behaves exactly like the T-Mobile USA one. So by using a CM flavoured ROM we quite litterally turn all our Desire Z in G2's only supporting the specific extensions/functions/features the T-Mobile USA network offers and, if such a thing exists, network extensions possibly widely used in Europe are not considered since not supported by the libhtc_ril.so-ROM-combination in use on the device? What a sentence...
Just to make clear what I am assuming or proposing: it's not like the G2 is crippled in any way compared to the Desire Z, I guess we just don't take full advantage of the radio's abilities/features by using CM on our Desire Z. More or less correct?
And, as usual with me lately, an Edit: I also assume further, that using a HTC-native libhtc_ril.so on a CM ROM wouldn't result in added functionality since the CM ROMs themselves are basically G2 ROMs, TMOUS-spin off's so to say and do not consider the unused potential of the radio used in HTC's ROMS. Correct...?
schaggo said:
it's not like the G2 is crippled in any way compared to the Desire Z, I guess we just don't take full advantage of the radio's abilities/features by using CM on our Desire Z. More or less correct?
Click to expand...
Click to collapse
Correct, but I'm almost wondering just how important having the RIL (libhtc_ril.so) match the radio that's flashed on the firmware. It could lead to some of the issues we see with certain subsets of people (high battery usage, etc.)
There could be subtle incompatibilities that lead to problems down the road if the RIL doesn't match the radio.
CyanogenMod is "crippling" the GPRS Class by setting it to 10 instead of 12, however.
Hm.. this is really interesting. How should we match them exactly? Ill flash every damn radio if it can stop my radio from using 40 percent of my battery..
Sent from my Rooted God-like HTC Vision running Liquid Metal.
I do suffer exorbitant battery usage on the latest CM7 builds.
The whole day today I was back on GingerVillain - an "older" CM7 mod, I know - and after 16h my battery is still well above 50%. Before I would lose 20% on the train ride to work which takes 30 minutes. Nothing changed apart from wiping CM7 nightly and putting GV on. And since CM7 RIL still matches the CM6 RIL, I guess the GV RIL is exactly the same file. I genuinely *do* wonder where that incompatibility comes from... :-\
I'm trying to figure out where the /system/lib/libhtc_ril.so (MD5: 2405b479910beefd618de322f425ea40) is actually from, it doesn't appears to be from the original TMOUS 1.19.531.1.
With my device I made sure that the following files matched the radio:
Code:
/system/lib/libhtc_ril.so
/system/lib/libril.so
/system/lib/libreference-ril.so
I took WWE 1.72.405.2 RUU extracted the rom.zip from it, flashed the radio.img from it and copied the above files from the system.img onto my CyanogenMod 6.1.1 installation and everything seems to work fine. On top of that, I tweaked some of the settings based on the other worksheet on my spreadsheet since /system/build.prop is read from top-down and ignores later entries (as far as I could tell)
Additions to /system/build.prop:
Code:
ro.ril.enable.a52=0
Removals from /system/build.prop (since /system/build.prop is read from top-down and ignores later entries):
Code:
ro.ril.enable.dtm=0
ro.ril.gprsclass=10
ro.ril.hsdpa.category=10
ro.ril.hsupa.category=6
ro.ril.hsxpa=2
I have to agree with this theory... I have switched to the Aussie radio but the battery life was horrible even after wiping dalvik cache. I ended up switching back to stock OTA tmobile radio and battery life was restored. I gave the new Aussie radio another chance by adding all the htc ril lib files except the wifi module and wiped cache. Battery life is now great like stock plus a bit better reception thanks to the newer radio. There's a thread that houses all the libs and new radio. Works nicely... worth a try for sure
pfak said:
I'm trying to figure out where the /system/lib/libhtc_ril.so (MD5: 2405b479910beefd618de322f425ea40) is actually from, it doesn't appears to be from the original TMOUS 1.19.531.1.
With my device I made sure that the following files matched the radio:
Code:
/system/lib/libhtc_ril.so
/system/lib/libril.so
/system/lib/libreference-ril.so
I took WWE 1.72.405.2 RUU extracted the rom.zip from it, flashed the radio.img from it and copied the above files from the system.img onto my CyanogenMod 6.1.1 installation and everything seems to work fine. On top of that, I tweaked some of the settings based on the other worksheet on my spreadsheet since /system/build.prop is read from top-down and ignores later entries (as far as I could tell)
Additions to /system/build.prop:
Code:
ro.ril.enable.a52=0
Removals from /system/build.prop (since /system/build.prop is read from top-down and ignores later entries):
Code:
ro.ril.enable.dtm=0
ro.ril.gprsclass=10
ro.ril.hsdpa.category=10
ro.ril.hsupa.category=6
ro.ril.hsxpa=2
Click to expand...
Click to collapse
I ended up deplicating all the higher hspa class values (gprs too) just to be safe. No harm in doing so. I had these that way for a while now.
What about the using a froyo libhtc_ril.so on a gingerbread rom?
I'm currently on SenseGinger with the latest 26.06.02.27 have noticed a slight decrease in reception capabilities. Would a transfer of the ril.so be necessary/possible?
Not to be an ass, but you think you guys can make some updates with the updated libs for us? Or post a tutorial? I would love to have these results like you guys let alone test.
Sent from my Rooted God-like HTC Vision running Liquid Metal.
bigmoew said:
What about the using a froyo libhtc_ril.so on a gingerbread rom?
Click to expand...
Click to collapse
Give it a try and tell us how it works
Shaquiel Harris said:
Not to be an ass, but you think you guys can make some updates with the updated libs for us? Or post a tutorial? I would love to have these results like you guys let alone test.
Sent from my Rooted God-like HTC Vision running Liquid Metal.
Click to expand...
Click to collapse
Download: 2010-11-17 26.04.02.17_M2 (WWE 1.72.405.2) [HTC-RIL 2.2.0039HM (Oct 21 2010,22:38:34)]
Instructions for CyanogenMod, assuming you have a S-OFF engineering HBOOT, and Android SDK installed and USB connectivity (along with appropriate Fastboot drivers, etc.)
Copy the updated RIL libraries to your phone (from the lib folder in the RAR)
Code:
adb remount
adb push libhtc_ril.so /system/lib/libhtc_ril.so
adb push libreference-ril.so /system/lib/libreference-ril.so
adb push libril.so /system/lib/libril.so
Then power down the phone, Boot into the boot loader (Power + Volume down) and select FASTBOOT.
Code:
fastboot flash radio radio.img
Wait for it to say "Completed." then reboot into CyanogenMod and you are done. I am successfully using these for the past 2 weeks on CyanogenMod 6.1.1 Stable.
pfak said:
Give it a try and tell us how it works
Download: 2010-11-17 26.04.02.17_M2 (WWE 1.72.405.2) [HTC-RIL 2.2.0039HM (Oct 21 2010,22:38:34)]
Instructions for CyanogenMod, assuming you have a S-OFF engineering HBOOT, and Android SDK installed and USB connectivity (along with appropriate Fastboot drivers, etc.)
Copy the updated RIL libraries to your phone (from the lib folder in the RAR)
Code:
adb remount
adb push libhtc_ril.so /system/lib/libhtc_ril.so
adb push libreference-ril.so /system/lib/libreference-ril.so
adb push libril.so /system/lib/libril.so
Then power down the phone, Boot into the boot loader (Power + Volume down) and select FASTBOOT.
Code:
fastboot flash radio radio.img
Wait for it to say "Completed." then reboot into CyanogenMod and you are done. I am successfully using these for the past 2 weeks on CyanogenMod 6.1.1 Stable.
Click to expand...
Click to collapse
Thanks alot. But kinda confused.. i push these files BEFORE flashing the new radio? kinda makes no sense to me. im about to update to .27 again since you said it works better with these files. (had a bad time before with it) and do you recommend wiping cache after the flash?
Do we need to do this every time we flash an update, or will they be copied over to the update? (the lib files...I know the radio stays put)
Copy the updated RIL libraries to your phone (from the lib folder in the RAR)
Code:
adb remount
adb push libhtc_ril.so /system/lib/libhtc_ril.so
adb push libreference-ril.so /system/lib/libreference-ril.so
adb push libril.so /system/lib/libril.so
Click to expand...
Click to collapse
is this cyanogenmod only? im not running cyan.
EdKeys said:
Do we need to do this every time we flash an update, or will they be copied over to the update? (the lib files...I know the radio stays put)
Click to expand...
Click to collapse
the lib files are part of the rom, so you'll have to do this again after an update
im gonna try this on the glacier using the libs from Glacier_TMOUS_1.17.531.2_Radio_12.28b.60.140e_26.0 3.02.26_M_release since the two phones are so similar build-wise
tnpapadakos said:
the lib files are part of the rom, so you'll have to do this again after an update
Click to expand...
Click to collapse
Copy the updated RIL libraries to your phone (from the lib folder in the RAR)
Code:
adb remount
adb push libhtc_ril.so /system/lib/libhtc_ril.so
adb push libreference-ril.so /system/lib/libreference-ril.so
adb push libril.so /system/lib/libril.so
If someone has the knowledge to make this into a flash.zip that would be great because it could be done in CWM right after flashing a rom (update). Anyone?
EdKeys said:
Copy the updated RIL libraries to your phone (from the lib folder in the RAR)
Code:
adb remount
adb push libhtc_ril.so /system/lib/libhtc_ril.so
adb push libreference-ril.so /system/lib/libreference-ril.so
adb push libril.so /system/lib/libril.so
Click to expand...
Click to collapse
It's also wise to backup the current lib files before pushing them, in case the updated ones make things worse.
The lines from the build. Prop......
rild.libpath=/system/lib/librilswitch.so
rilswitch.ganlibpath=/system/lib/libganril.so
rilswitch.vendorlibpath=/system/lib/libhtc_ril.so
If you look at the build. Prop these lines about the libganril. So and the librilswitch.so make me think they are important.
And if you compare the G1 build. Prop to ours it only has the line about the libhtc.ril. so.
So one day I made the G2 build. Prop look like the G1 and it would stay at 3G and max out at 364 mbs then when I changed it back the H icon came back and restored normal speeds. So I always thought that these parts were something to do with switching from E to G to 3G to H..... but I am not sure. I have copied all five of the ril related files to my system / lib and have better signal now. But still no G or 3G except when the phone does the power save thing when you have H but are not using it.... does anyone know why?
Also there are lots of ril options that are not used /unknown pupose....
#ro.ril.a53.%s
#ro.ril.ecc.%s
#ro.ril.def.agps.mode.%s
#ro.ril.def.agps.feature.%s
#ro.ril.def.agps.mode
#ro.ril.def.agps.feature
#ro.ril.oem.ecclist
#ro.ril.oem.nosim.ecclist
#ro.ril.enable.dtm
#ro.ril.gprsclass
#ro.ril.hsdpa.category
#ro.ril.hsupa.category
#ro.ril.hsxpa
#ro.ril.enable.nitz
#ro.ril.enable.network_identify
#ro.ril.qos.maxpdps
#ro.ril.qos.traffic.class
#ro.ril.qos.max.ul
#ro.ril.qos.max.dl
#ro.ril.qos.guarantee.ul
#ro.ril.qos.guarantee.dl
#ro.ril.qos.delivery.order
#ro.ril.qos.max.sdu
#ro.ril.qos.delivery.err.sdu
#ro.ril.qos.transfer.delay
#ro.ril.qos.traffic.priority
#ro.ril.always.laccid
#ro.ril.fast.dormancy.rule
#ro.ril.fd.scron.timeout
#ro.ril.fd.scroff.timeout
#ro.ril.fast.dormancy.plmn
#ro.ril.enable.3g.prefix
#ro.ril.3g.long.name
#ro.ril.htcmaskw1.bitmask
#ro.ril.htcmaskw1
#ro.ril.enable.homezone
#ro.ril.enable.vt
#ro.ril.enable.regucid
#ro.ril.enable.hsdpaind
#ro.ril.enable.a52
#ro.ril.enable.a53
#ro.ril.enable.dcm.feature
#ro.ril.enhance.htcdis
#ro.ril.enable.tim.feature
#ro.ril.enable.korea.stk
#ro.ril.enable.hsupaind
#ro.ril.enable.gea3
#ro.ril.enable.managed.roaming
#ro.ril.enable.enhance.search
#ro.ril.disable.mcc.filter
#ro.ril.search.first.pnn
#ro.ril.enable.ncell.ind
#ro.ril.enable.enhance.nws
#ro.ril.radio.svn
#ro.ril.wp.feature
#ro.ril.emc.mode
#ro.ril.ucsq.mode
There was a thread in the G1 forum were they were trying to figure out what they each did. But I don't think that much progress was made other than the commonly known ones..
I have always been interested in the "fast dormancy " ones and the ro.ril.qos. xxxx ones...... but I could never find much information...
Sent from my HTC Vision using XDA Premium App
indeed i think there is a correlation
before this, i was getting 2300-2800 down
pfak said:
Give it a try and tell us how it works
Click to expand...
Click to collapse
Used root explorer, mounted as read/write and copied the files w/ a reboot. Confirmed w/ at least the same data speeds and better network reception so far on SenseGinger
Related
Hey guys, it looked like you guys didn't have a real up to date aosp/cyanogenmod rom, so i decided to take my build and port it over for you guys. This is built from the latest cyanogenmod sources and whatnot. everything should work as fine as any other aosp rom. I Don't have a GSM hero, so you guys gotta tell me how this goes, and what needs fixing.
Thanks Cyanogen for the source to work off of, and experience for showing me how easy it is to port roms to other phones
Standard Order to flash this rom is first the Full Rom, then The Google bits. You only need to wipe if you are coming from a non cyanogenmod rom
HOW TO REPORT BUGS OR PROBLEMS? | kanged from cyanogen's guidelines for bugreporting, lol
- Was it a hard reboot? Get me the file "/proc/last_kmsg". adb pull /proc/last_kmsg
- Was it a soft reboot or a "boot loop"? Run "adb logcat" and get me the full output. Pastebin links preferred
- Please use the the bugreporter whenever possible!
well, here you guys go
Stable Darchdroid ROM
MD5SUM: c73584f2a52762b62f8e1a2acb26e5d6
Google Bits Flash these for the market app and other google proprietary stuff
MD5SUM: eee5a0de29831f913b2a40efa4df69ec
CHANGELOG
v1.1 - fixed youtube, gps, akmd issues, wifi, plus other additions made by cyanogen (check his github)
downloading now.
Will be interesting to see how it differs from VanillaEclair and aHero.
GSM
Is the rom directly ported from a non gsm hero, because is so wouldnt flashing this rom onto our GSM heros brick or cause problems with our hero? Any feedback from some1 who has flashed, or dev will be great
bratfink said:
Is the rom directly ported from a non gsm hero, because is so wouldnt flashing this rom onto our GSM heros brick or cause problems with our hero? Any feedback from some1 who has flashed, or dev will be great
Click to expand...
Click to collapse
no it wouldn't. flashing a cdma hero radio (most of the time) would, but flashing a rom would never ever brick your phone.
And really, why would someone ever release anything with the possibility of bricking your phone, eh?
darchstar said:
no it wouldn't. flashing a cdma hero radio (most of the time) would, but flashing a rom would never ever brick your phone.
Click to expand...
Click to collapse
Did you do something special with this rom? Cause it look interesting, but i don't think its gonna work without adjustments for HERO GSM.
Hope to see some progress with this rom. Thanks for sharing.
Flashing it now.
I will be running a logcat while booting, just to see if anything interesting turns up.
don't show to much gratitude
bratfink said:
Is the rom directly ported from a non gsm hero, because is so wouldnt flashing this rom onto our GSM heros brick or cause problems with our hero? Any feedback from some1 who has flashed, or dev will be great
Click to expand...
Click to collapse
you even know how to flash a update.zip?
CDMA
So if we could flash CDMA roms then why dont we grab the 2.1 roms off the cdma thread that are generally a step ahead in development than the roms we GSM owners have, unless they didnt work on our phones :S?
Pagan said:
Did you do something special with this rom? Cause it look interesting, but i don't think its gonna work without adjustments for HERO GSM.
Hope to see some progress with this rom. Thanks for sharing.
Click to expand...
Click to collapse
I made the adjustments necessary to get it to run on a gsm hero, such as i changed the kernel... but i don't think i edited the base when packing the boot.img, if that matters. I edited the build.prop to point to wcdma, i editeed the sensors libs... though i think i need to port akmd from your guy's hero rom, and i edited the keylayouts to suit hero gsm
Well, I'm at the blue nexus load screen, still going
Nothing odd in the logcat so far
It's booted
Just going through setup.
darchstar said:
I made the adjustments necessary to get it to run on a gsm hero, such as i changed the kernel... but i don't think i edited the base when packing the boot.img, if that matters. I edited the build.prop to point to wcdma, i editeed the sensors libs... though i think i need to port akmd from your guy's hero rom, and i edited the keylayouts to suit hero gsm
Click to expand...
Click to collapse
Flashed now but unable to start wifi.
ok guys, post all the bugs and i'll make one big update.zip to accommodate them all
Launcher2 force closes immediately after setup. :-(
Home is ok though.
just got it up and running, seems nice so far (battery indicator is good).. off to test..
Speed
Could anyone quickly run a neocore (W+w/o sound) and linpack test just to see what results this rom can give.
xanadu said:
Flashed now but unable to start wifi.
Click to expand...
Click to collapse
yup me too..
Wifi isn't working the rest looks good.
Used this wlan drivers before to try n fix wifi and its worked, give it a go worth a try
adb push wlan.ko /sdcard/wlan.ko
adb shell
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
cp /sdcard/wlan.ko /system/lib/modules/wlan.ko
reboot
Can't start Wifi.
logcat shows
Cannot open firmware file </system/etc/wifi/Fw1251r1c.bin>: No such file or directory.
I'll try grabbing it from another ROM.
@Darch,
I can post a full logcat somewhere if you need, from first boot until now (still going)
VillainROM 11.9.1 based on HTC OTA update WWE 2.1.
Fully deodexed beta test pre VR12.0 release
Why VillainROM11.9.1? It means if stuff breaks, tell us and we'll fix it, and the result will be the final VillainROM12 release.
What works:
Livewallpapers (not with sense)
Gallery 3D (With Picasa sync)
Voice Search
Voice Dial
Desire lockscreen
Dalvik2cache by default
Automatic apps2sd, just create an ext partition on SD card and we do the rest.
Recovery ROM patched to wipe dalvik on /cache with wipe dalvik
Everything else
What doesn't work:
Friendstream
What has been added:
19MHz to 748MHz OC kernel
Multi language support (even Greek works!)
Wifi tethering (aNetShare)
USB tethering
compcache enabled and tweaked
low memory management tweaked. NO NEED FOR AUTOKILLER.
cpufreq values set for balanced battery power/cpu performance
Latest busybox
Bash 4.1 (type "exec bash" once you're adb shelled in)
Updated APNs list
Cleaned up kernel CPU frequency table for less battery intensive speed switching
Rosie config screen added (2010-07-01)
Latest Google Maps as of time of release
How to install:
Backup/restore
Nandroid Backup
Wipe
Wipe data
Wipe dalvik cache
Wipe SD:Ext (If you have apps2sd and/or an ext partition)
Flash
Flash VillainROM11.9.1-Full-signed.zip
Reboot system now
A FULL WIPE IS AN ABSOLUTE MUST. DO NOT POST SUPPORT REQUESTS WITHOUT DOING THIS.
Download Here
(Refresh the page to get another mirror)
Code:
md5: 8fbeb43c7d5cf970c1669b2e833c9fa0
Thanks to netarchy for scripting help, kendon with patching the stock ROM, DMzda and Lenny with alpha testing, arshad14, venter and Billias with beta testing. Thanks to AdamM for Rosie config.
Note: This ROM has been built from the OTAs, not from any /system/ dumps.
EDIT:
For Windows users struggling in the dark ages with their cmd prompts that don't understand colours:
Download this script:
http://qap.la/~ninpo/villain/testing/ll
Code:
adb remount
adb push ll /system/xbin/
adb shell chmod 755 /system/xbin/ll
adb shell chown 0:2000 /system/xbin/ll
Then give it a whirl:
Code:
adb shell ll /data/
It also accepts regular ls arguments:
Code:
adb shell ll -al /system/bin/
Enjoy!
For those wondering, Hacre is Ninpo on the VillainROM Forums.
dowmloading now, will try it straight away.
cheeeeeeeeeeeeeeeeeeeeeeeeeeeeers
Oh happy day, thanks for the hard work. I can't wait to test this when I get home.
Link coming soon - how you downloading
Sent from my HTC Hero using XDA App
may I ask, why would this be any different from vr 10.3? they're both build from official 2.1 roms for the gsm hero. one is from europe, the other, asia. ok, same phone still.
Is it like the VR team has learned a few things from vr10 and are doing things differently in vr12 so this will be a better rom than vr10?
because vr10 is supposed to be the ultimate sense rom, no?
how can this be any better? I read the "Added" list above, sure there are some interesting things, but don't all of those things work in vr10.3? as well? maybe the cpu won't change speeds as often now, but in all honesty, will this work any differently than 10.3 did?
I finally left VR after vr10.x because I'm tired of the slowdowns in sense roms. villain superhero2 is much better to me, but oddly has some broken things (considering it's from the same rom I don't quite get it, but hell I'm not the one building the rom so I'm just happy you guys do all this hard work!
But what I really want is a sense rom where I can use whatever launcher I want (I love launcherpro right now) without having to move to a non-sense or almost-non-nense (IE: superhero) rom just to get the speed I need.
will this happen with VR12? or for pure speed is it still better to go with non-sense or partial-sense?
so many questions, sorry, rambling, but I'm confused about the big deal about euro hero 2.1 rom versus asian one. the languages were added, keyboard was changed, so the taiwan rom became the euro rom, no?
silly questions maybe? did I miss something LoL
cheers, thanks for indulging me. I'm su re I'm not the only one wondering this stuff.
rophaq said:
dowmloading now, will try it straight away.
cheeeeeeeeeeeeeeeeeeeeeeeeeeeeers
Click to expand...
Click to collapse
I'm curious what you think compared to superhero 2.0 (which I'm on right now).
try using launcherpro under 11 beta and see how it does compared to launcherpro under superhero 2 for example.
Anyone who grabbed this recently, please redownload if your md5sum does not match:
Code:
8fbeb43c7d5cf970c1669b2e833c9fa0
As there was a last minute fix required right as we went live, lol typical.
To address some questions, especially from dkelley:
This is a -fast- ROM. Fresh boots finish in 5-6 minutes, instead of the 10-15 most previous builds took. From power on to usable UI is under two minutes. It is smooth, it is fast, it is slick.
We've already had alpha and beta testers comparing it to Superhero and that's with Sense. Imagine LauncherPro...
We didn't just go from 10.3 and everything prior to that with some fixes. This is built from the base HTC ROM+OTA updates with further optimisations and fixes applied ourselves.
Apart from the additional European language support, we would not release a ROM if we didn't feel it to be an improvement over what we already have available. That's what 11.9.x is here, for you to help us test, report back bugs, so that VR12 can be the best ROM we've ever released.
dkelley said:
I'm curious what you think compared to superhero 2.0 (which I'm on right now).
try using launcherpro under 11 beta and see how it does compared to launcherpro under superhero 2 for example.
Click to expand...
Click to collapse
Also wondering the differences. +1
and....
Just go to the Application in the Setting,and clear the Sense"Default".
Then you can set LauncherPro(or what ever other Launcher)as your default launcher in any ROM.
just waiting for it to boot now.
will report when it's ready
Again please make sure your update zip matches the md5sum
Code:
8fbeb43c7d5cf970c1669b2e833c9fa0
as we had to make a last minute fix shortly after announcement.
came from super hero were everything worked including apps2sd..... wiped everything flashed but apps2sd not working automatic do you need to run the apps2sd.zip with this rom?
chrisjaggeruk said:
came from super hero were everything worked including apps2sd..... wiped everything flashed but apps2sd not working automatic do you need to run the apps2sd.zip with this rom?
Click to expand...
Click to collapse
are you sure it's not working? it takes a long time to copy thigns over to sd. when I do a titanium backup of 100+ apps after flashign a new rom it fills up app space pretty fast but after 10-20 minutes it lowers space down again in phone memory (not speaknig of 11.9 here but apps2sd in general)
chrisjaggeruk said:
came from super hero were everything worked including apps2sd..... wiped everything flashed but apps2sd not working automatic do you need to run the apps2sd.zip with this rom?
Click to expand...
Click to collapse
No you need to read earlier in the thread where I said to check md5sums. We had a problem with the release we initially went live with (missing /system/sd folder in dir structure) which broke apps2sd.
Please check the md5sum of your .zip, it should be 8fbeb43c7d5cf970c1669b2e833c9fa0
If it isn't, redownload and reflash.
Started off with about 145mb i think. now down to 119mb only installed about 6 things so far
Hacre said:
No you need to read earlier in the thread where I said to check md5sums. We had a problem with the release we initially went live with (missing /system/sd folder in dir structure) which broke apps2sd.
Please check the md5sum of your .zip, it should be 8fbeb43c7d5cf970c1669b2e833c9fa0
If it isn't, redownload and reflash.
Click to expand...
Click to collapse
oops just seen your post will re download and try again mate cheers
so far so good, quick'n'smooth. everything is syncronised, hotmail, google acc,twitter, facebook, etc...plenty of memory left on the phone...amazing staff. a big thank you to all of you, job done
here are a few picks.
Hacre said:
No you need to read earlier in the thread where I said to check md5sums. We had a problem with the release we initially went live with (missing /system/sd folder in dir structure) which broke apps2sd.
Please check the md5sum of your .zip, it should be 8fbeb43c7d5cf970c1669b2e833c9fa0
If it isn't, redownload and reflash.
Click to expand...
Click to collapse
ah. well, there it is.
Is there a new radio out to flash with this rom? preferably one that works with a locked orange hero?
Cheers
Warning: Use this fix at your own risk. Please do not pm me for support on this. I'm just sharing a fix I found already in place and used in another rom.
Credit: 100% credit goes to iamgpc http://www.mobile01.com/topicdetail.php?f=224&t=1957441&m=f&r=3&p=1 http://forum.xda-developers.com/showthread.php?t=909096 .
Problem:
- Outgoing (dialing out) volume defaults to the maximum. The work around is to either hit the volume + or - or turn the speaker phone on and off quickly during a outgoing to force the device to pick up the preset volume
- Depending on the preset volume, incoming calls could be quiet and outgoing calls can be extremely loud depending on the htcleo.acdb file
- I had this issue on almost every rom I used
Solution - libaudio.so
- During my testing of "gpc_hd2_gingerbread_v19b" rom, I noticed this issue did not exist on this particular rom.
- Traced this back to libaudio.so after comparing various libs under /system
- Pushed libaudio.so from the gpc rom to /system/lib/ using tyween's "Typhoon" rom and noticed the max outgoing call volume issue was not longer present
Fix
- Highly recommend doing a nandroid back-up prior to applying fixes. If fix does not work and cause boot loops, you will have to restore /system .
- Extract and push the lib files from the attached zip file to /system/lib/.
or
- Try flashing the zip using CWM. I quickly slapped it together so not sure if it is working correctly
Tested to work on following rom's:
libaudio-fix-CM-Typhoon.zip for the following builds:
- tyween's "Typhoon CM7 2.4.5" rom no longer needed. Incorporated in V2.5+
- Mdeejay 2.6 CM7 build - Based on user feedback
- Pongster's HyperDroidGBX v7 - Based on user feedback
libaudio-fix-NexusHD2-Ginger-tytung.zip for the following builds:
- Tytung's "NexusHD2 Gingergread 2.3" rom
- rafpigna's RAFDROID HD 3.2.2 - SD build only
- Untested on other builds
Change log:
- Mar 02, 2011 - Added separate zip file (libaudio-fix-NexusHD2-Ginger-tytung.zip) for Tytung's ginger bread
Nice man!
Edit: Just tried on a Desire build doesn't boot for me
after installing in rafdroid 3.1 it stucks in the first screen.....
Doesn't work on NexusHD2-Gingerbread
At startup:
E/AndroidRuntime( 94): java.lang.UnsatisfiedLinkError: Cannot load library: link_image[1962]:
66 could not load needed library 'libsystem_server.so' for 'libandroid_servers.so' (link_image[1962]:
66 could not load needed library 'libaudioflinger.so' for 'libsystem_server.so' (link_image[1962]:
66 could not load needed library 'libaudio.so' for 'libaudioflinger.so'
(reloc_library[1311]: 66 cannot locate '_ZN7android14AudioParameter7keyFmOnE'...
Click to expand...
Click to collapse
Maybe it worked only on CM7 builds
Works very good for me.
MDJ cyanogenmod 7 v. 2.6
It doesn't work with 2.2.1
Thanks for the hard work. Tested working perfect on Typhoon 2.4.5..
stanleywoon said:
Thanks for the hard work. Tested working perfect on Typhoon 2.4.5..
Click to expand...
Click to collapse
I am not sure I feel this really makes a difference.
All my calls starts with the other party saying:
"wow, it's very loud on your side."
or
"you are talking too loud"
I thought this fix would have solved the problem.
Any suggestions ?
Zagzag read again the first post its not fixing you "problem"
DimICE said:
Doesn't work on NexusHD2-Gingerbread
At startup:
Maybe it worked only on CM7 builds
Click to expand...
Click to collapse
Thanks for the logcat. Updated to work on Tytung's NexusHD2 gingerbread build. Use zip libaudio-fix-NexusHD2-Ginger-tytung.zip.
zagzag99 said:
I am not sure I feel this really makes a difference.
All my calls starts with the other party saying:
"wow, it's very loud on your side."
or
"you are talking too loud"
I thought this fix would have solved the problem.
Any suggestions ?
Click to expand...
Click to collapse
The high mic gain is a separate issue. There is a fix by using a different htcleo.acdb file. Try searching for the fix. I don't have the link at the moment.
pecora said:
Works very good for me.
MDJ cyanogenmod 7 v. 2.6
Click to expand...
Click to collapse
Yes. Ive got a same detection. Great work .......... Thanx
Tested working on RAFDROID Desire HD 3.2.2 - SD build. This should also work on Rafdroid Desire HD 3.2 nand build.
You think it will also work on Desire based build? (not HD)
DFT
will this work on the DFT version of MDJ CM7 2.6? If so how can I apply it?
Working with HyperDroidGBX v7! Thanks! libaudio-fix-CM-Typhoon.zip
But it feels like volume is loud at first, but than quickly became normal..is it ok?
The Phone Volumen works fine now,but the Media Volumn become too low?
Anyone have the same Problem?
PS: Typhoon_CM7_2.4.5
EDIT: The ideal solution for this problem is to fix the source code. Unfortunately, I don't have the time and proper tools to decompile the lib file libaudio.so. Any Dev's want to give this a try? I'm not sure if this lib is based on the passion(Nexus one).
ITAYSHARONI said:
You think it will also work on Desire based build? (not HD)
Click to expand...
Click to collapse
Which Desire build are you using? I'm not certain if these fixes will work on the Desire build you are using. Unfortunately the libs are not consistent between builds and contain different modifications. When changing anything in /system, there is always the risk of having to restore.
If you are comfortable with basic ADB commands, you could copy the original libs as backup and push them back using ADB if you get a bootloop. But be warned, you may have to reflash causing data loss if you use a DFT based flash(no clockwork mod recovery). I should note I've intentionally caused the bootloop on various builds just to identify the libs that are different between builds and have always been able to recovery from boot loop pushing the original files back.
lowrider262 said:
will this work on the DFT version of MDJ CM7 2.6? If so how can I apply it?
Click to expand...
Click to collapse
You could try using either adb or root explorer to manually push the file. Make sure you back up the original lib file. I would strongly recommend you try Typhoon CM7 rom. It is much more up to date in comparison to Mdeejay's rom.
Kefir.net said:
Working with HyperDroidGBX v7! Thanks! libaudio-fix-CM-Typhoon.zip
But it feels like volume is loud at first, but than quickly became normal..is it ok?
Click to expand...
Click to collapse
This appears normal. The volume is at max for half a second and corrects to the pre-set value.
freemanxp said:
The Phone Volumen works fine now,but the Media Volumn become too low?
Anyone have the same Problem?
PS: Typhoon_CM7_2.4.5
Click to expand...
Click to collapse
I'm running the same rom and don't notice any difference in media volume.
2000impreza said:
Tested working on RAFDROID Desire HD 3.2.2 - SD build. This should also work on Rafdroid Desire HD 3.2 nand build.
Click to expand...
Click to collapse
Which CWM-Zip file did you use , becouse i want to try it on my rafdaroid 3.2 NAND
Im using Bauner-LEO-V4_20.02.11_cwm Build
When i tried the first file it didn't eve got to a bootloop, it got stuck on htc logo
zaidsa3sa3 said:
Which CWM-Zip file did you use , becouse i want to try it on my rafdaroid 3.2 NAND
Click to expand...
Click to collapse
I would highly suggest doing a nandroid backup before flashing. As indicated on the first post, try zip file: libaudio-fix-NexusHD2-Ginger-tytung.zip for Raftdroid rom.
ITAYSHARONI said:
Im using Bauner-LEO-V4_20.02.11_cwm Build
When i tried the first file it didn't eve got to a bootloop, it got stuck on htc logo
Click to expand...
Click to collapse
Unfortuneately I don't have the time to look at the libs for this rom to figure what will/won't work. Since it uses CWM to flash the rom, you could do a nandroid backup followed by flashing zip file: libaudio-fix-NexusHD2-Ginger-tytung.zip to see if it works. Worse case, restore /system from the nandroid backup if it doesn't work.
The best solution is to rebuild libaudio.so from source to correct the issue. Unfortuneately I don't have the expertise nor time to do this. Any dev's willing to look at this?
I recompiled latest driver for broadcomm wifi on gingerbread, this may fix the battery drain issues, but i need testers.
File attached, place it under /System/Modules
before that copy a backup of bcm4329.ko in the same dir to a safe place and put one from zip.
Please put your comments here, this is first attempt
File that were posted with Gingerbread has version: 4.218.248.18
Latest builds of gingerbread (TEN region) has version: 4.218.248.6
this one is : 4.218.248.23
Changelist:
wireless: bcm4329: Reduce listen interval to 10 (from 20)
wireless: bcm4329: Add new and default wifi locale support
wireless: bcm4329: Prevent working thread to run during suspend path
wireless: bcm4329: Clean ARP offload table on IP update
Thanks!
EDIT: Added recovery zip, flash it using recovery menu. (hopefully it will work)
EDIT: Fixed recovery image (if you got error 6 then download it again and flash)
EDIT: Phone will reboot right after applying patch using recovery for these who are scared or something
how do i aply this
pixiejoe said:
how do i aply this
Click to expand...
Click to collapse
Copy it on rooted phone to proper dirs, i will create recovery package and attach it
pixiejoe said:
how do i aply this
Click to expand...
Click to collapse
With root explorer, I think.
wifi working like usual. no improvement(s) at all.
Will check it out... Thanks!
Wifi on this module doesn't work for me. I'm on miui.
This is to test the battery drain issue on stock ginger JV* not on custom mods. Post your review here and could someone make a recovery flash with it? i cant do it now.
Recovery zip added, you may simply flash it using recovery. It will also create backup of existing driver.
Anyway, I'm testing on kitchen jvh rom 3
Sent no matter where from. Concentrate on the topic...
Working fine on JPH (goatrip) . Too early to tell if it improves wifi drain, but I'm a compulsive flasher, always gotta have the newest rom/driver lols.
Any way to tell if the update worked?
I renamed the old driver file and rebooted (without copying the new one) but wifi still worked - is that normal behaviour?
Reboot the phone after replacing the file.
http://forum.xda-developers.com/showpost.php?p=13434007&postcount=2024
and jvo or jvh whatever you call it have
Firmware version = wl0: Apr 9 2011 23:33:08 version 4.218.248.184
Click to expand...
Click to collapse
JV* directly from module file: version 4.218.248.18
Mine is compiled at: Compiled on May 14 2011
And its higher version
Also, please be aware that i supply only new kernel module not firmware for chipset (your version is firmware version)
Grooby while you are it, can you check if the Bluetooth a2dp implementation is using the highest bit pool possible?
Sent from my GT-I9000 using XDA App
sure, let me look at teh sources
correct jvh has *.6 version - my mistake
still files posted by me have *.18 that is said to be fixing the issue
gut dżab
Tank ju to moj first attempt i hope it will bedzie dzialac ;P heheheh
And it including last 6 days fixes fresh and good
First things first: THANK YOU to all those involved in the coding of this, especially the msm8660-common kernel that so many folks have put so much effort into, and Mr. Cyanogen for the device tree, etc etc. NONE of this would be possible without your efforts. I stand on the shoulders of giants in providing these instructions, the code is NOT mine, I'm just documenting this so you all can help contribute. Kindest regards to everyone who has contributed to make this possible. Your work has enabled the community to beat the vendor to the punch, yet again!
DISCLAIMER: This contains information on working with very early code as well as hacking together a completely unsupported Frankenstein build with some proprietary samsung binaries from another device (ATT Note) and I will warn you: If you aren't willing to risk bricking your device, don't even think about this. Also, I'm not so much a coder as I am a QA engineer, so I know enough to be dangerous, but I couldn't code C++ get myself out of a virtual crashing airplane if I had to. I also might not be able to help you out of a sticky situation, so... have fun at your own risk! But do have fun
Looking for binaries? See post #2
That said, it's honestly not likely any of this will brick your tab, if you know what you're doing, but... early software always carries danger, and using binaries from a similar yet different device can do who knows what.
Also of note: you should probably back up your EFS partition if you're going to hose with the radios to get cellular data working... hasn't been an issue for me, but... corrupt EFS partition = no more cellular data for you. ever.
Cyanogen has added initial support for the i957 to the CM10 repository, and it's looking good so far! But, there are no nightly builds yet, probably because Cyanogen would like to do some more work on it before handing out binary packages... Or maybe he hasn't figured out how to get things quite functional yet. I considered releasing a binary package for you to toy with, but then realized that would defeat the purpose of helping along the development of an official Cyanogen i957 (p5att) release, and lock you into something I already built from "pre-alpha" code. It's best to check out the latest source tree and do your own build, then you can easily test and contribute your modifications, should you find any.
So with that, here's some instructions on how to build CM10 for your SGH-I957 ("p5att") device from source code. This will also ensure time is spent doing development work, not hand-holding the faint of heart (sorry, sue me!)
These instructions assume you've successfully built Cyanogenmod for a supported device and understand the basics of getting things going. If not, start with that first, then come back to this. I'm also assuming you've got the android tools that you get from any build of cyanogen (like mkbootimg) in your path for some of the "optional" steps, which is of course elementary...
I'm also going to assume you know what to do with the resulting zip... You know... backup, factory reset, wipe system, flashy the zippy...
I really recommend doing the boot image modifications after the build, without ADB on boot, if something goes wrong, you'll have no way of knowing whats going on. If you get the boot image modified properly as detailed below, you will be able to ADB to the device as soon as the second boot logo disappears. Also, there's probably a cleaner way (like changing something somewhere to invoke one of the other case statements in init.qcom.usb.rc), but I didn't have any luck with that. Feel free to school me! :laugh:
EDIT: If you don't feel like hacking the boot image, just flash the one attached (ps: none of the zips below are TWRP/CWM flashable, just zipped up files.. dd if=bootimagefilename of=/dev/block/mmcblk0p8 from a root shell to flash the boot partition on the i957)
I've attached the initlogo.rle file to this post so you don't have to fish it out of the ramdisk embedded in the stock boot image. Adding initlogo.rle to the ramdisk gives you confirmation the kernel is bootstrapping, and it's disappearance indicates ADB is now available. Also, use a linux box for ADB! silly wabbit, windoze is for kids.
According to comments in system.prop, the cyanogenmod boot animation is disabled because the framebuffer is "weird". Strangely, it sometimes displays for me, one in 10 boots maybe. Weird!
Here goes.
----
Initialize Repo:
repo init -u git://github.com/CyanogenMod/android.git -b jellybean
Sync Repo:
repo sync -j6
... Coffee Break!
Breakfast for p5att:
. build/envsetup.sh && breakfast cm_p5att-userdebug
Modify device/samsung/p5att/BoardConfig.mk to clean up a few things:
Comment out:
#BOARD_SDCARD_DEVICE_PRIMARY := /dev/block/mmcblk1p1
#BOARD_SDCARD_DEVICE_SECONDARY := /dev/block/mmcblk0p28
#BOARD_SDEXT_DEVICE := /dev/block/mmcblk1p2
Add above these lines:
BOARD_HAS_SDCARD_INTERNAL := true
Modify device/samsung/p5att/device-proprietary-files.txt:
Comment out all the entries, because they aren't really needed and probably dont work with jellybean. Worry about this later, blah blah.
Modify device/samsung/msm8660-common/common-proprietary-files.txt:
Comment out all the WiFi stuff, that is, like:
# Wi-Fi
# etc/wifi/bcm4330_apsta.bin
#etc/wifi/wl
#etc/wifi/nvram_net.txt
#etc/wifi/wpa_supplicant.conf
#etc/wifi/bcm4330_p2p.bin
#etc/wifi/bcm4330_sta.bin
#etc/wifi/bcm4330_mfg.bin
#etc/wifi/nvram_mfg.txt
To get WiFi working later, you need /system/etc/wifi/* from your honeycomb image. Go save them to /sdcard/wifi or something like that now, so you can just copy them over after CM10 boots
Edit: attached the files
Extract proprietary files from i717 Note CM10 image, since I have no idea where else to get these files, and they work:
from device/samsung/p5att, run ./extract-files.sh <path to an extracted CM10 i717 nightly .zip>
... The path you provide should contain the "system" folder.. IE the root of the extracted nightly zipfile.
I had used the 0831 nightly with luck here.
Get prebuilts:
run vendor/cm/get-prebuilts
Do the build:
from the system directory of your CM10 source tree run:
. build/envsetup.sh && brunch p5att
Go find something or someone to do, this is going to take a while...
You'll end up with a .zip file to flash.
After you flash, you'll need to, manually:
1) Copy back the /system/etc/wifi/* files (wifi firmware/tools, the note ones dont seem to work).
2) Install a Skyrocket ICS AT&T radio if you want cellular data, the honeycomb radio doesn't seem to work with CM10. UCLF6 works for me, although it's slower to acquire LTE than the official samsung HC image... but it works great once it finds a cell, and HSPA comes up pretty fast.
3) Consider doing the stuff below to enable early ADB and add back the second samsung logo, for debugging purposes, if you care...
----
Things you might want to do after the build, start by unzipping the resulting .zip pacakge...
Edit: I attached a the resulting boot.img to this post so you don't have to do all this if you so desire. Bonus: working i957 JB kernel binary for whatever else you might want to do with it..
Remove the assert for platform type if your TWRP recovery, like mine, thinks it's a i717 Note:
Edit META-INF/com/google/android/updater-script, remove the assert lines (first two lines of that file)
Do some handy ramdisk hacks:
First, unpack the boot image. From the root of what you unzipped:
mkdir boot
unpackbootimg -i boot.img -o boot
cd boot
Then Unpack the initial ramdisk:
mkdir rd
cd rd
zcat ../boot.img-ramdisk.gz | cpio -id
Edit init.qcom.usb.rc to enable early adb:
Search for "on property:sys.usb.config=mtp", you'll find: (line 340, for me)
on property:sys.usb.config=mtp
write /sys/class/android_usb/android0/enable 0
write /sys/class/android_usb/android0/idVendor 04E8
write /sys/class/android_usb/android0/idProduct 6860
write /sys/class/android_usb/android0/f_acm/acm_transports tty
write /sys/class/android_usb/android0/functions mtp,acm
write /sys/class/android_usb/android0/enable 1
setprop sys.usb.state $sys.usb.config
Make this section like:
on property:sys.usb.config=mtp
write /sys/class/android_usb/android0/enable 0
write /sys/class/android_usb/android0/idVendor 04E8
write /sys/class/android_usb/android0/idProduct 6860
write /sys/class/android_usb/android0/f_acm/acm_transports tty
write /sys/class/android_usb/android0/functions mtp,acm,adb
write /sys/class/android_usb/android0/enable 1
start adbd
setprop sys.usb.state $sys.usb.config
Add the glowing samsung initlogo:
Copy initlogo.rle from the root of a stock ramdisk to the root of this ramdisk
... So you'll get the second samsung logo, so you know the kernel is bootstrapping... if you care.
Turn off ro.secure:
Edit default.prop in the root of the ramdisk and change:
ro.secure=1
to
ro.secure=0
Repack the ramdisk:
find . | cpio -o -H newc | gzip > ../boot.img-ramdisk.gz
(you may want to save the original, if you care)
Make the new boot.img:
cd .. (ie get back to the directory with the files listed in the next line)
rm ../boot.img
mkbootimg --kernel boot.img-zImage --ramdisk boot.img-ramdisk.gz --cmdline "console=ttyHSL0,115200,n8 androidboot.hardware=qcom" --base 48000000 --ramdiskaddr 49400000 --pagesize 2048 -o ../boot.img
Repack the flashable zip:
cd .. (ie get back to where you unzipped the original flashable .zip)
rm -rf boot (remove the extracted boot.img and ramdisk under it, save it somewhere if you care)
(also remove the original .zip from here if you extracted it in the cwd)
zip -r ../somezipname.zip .
Then flash somezipname.zip or whatever you called it..
(Remember you'll need to put the Honeycomb files from /system/etc/wifi into /system/etc/wifi of the running image after you boot if you want wifi
(And flash a Skyrocket ATT radio if you want cellular data!)
WARNING: FOR SAMSUNG SGH-I957 NORTH AMERICAN DEVICES ONLY
GT-SERIES (IE: GT-7320, etc) ARE NOT SUITABLE FOR THIS RELEASE
UPDATE ZIP DOES _NOT_ CHECK YOUR PRODUCT CODE, WILL HAPPILY EAT OTHER DEVICES
THIS IS A TEST RELEASE FOR EXPERIENCED ANDROID HACKERS
SOME FEATURES MAY NOT BE USABLE OR WORK AS INTENDED
BOOTLOOP ISSUE? USE TWRP 2.1.4: https://www.dropbox.com/s/u07zrx808a5ae2z/i957_twrp_recovery.img.tar
Latest Flashable .ZIP, update 7: http://droid.arm.ee/957/cm10_p5att_nrvate_testrelease7.zip
Use TWRP, factory reset and wipe /system if you are coming from another ROM. Don't forget to install google apps http://wiki.cyanogenmod.com/index.php?title=Latest_Version/Google_Apps
Update 2
* h264 hardware decode fixes for youtube HQ and other hardware-decode enabled apps (vidc/yamato firmware update)
* camera fixes from kunals.shah -- thanks!! (camera library in system/lib/hw)
* wifi address fix - get MAC from EFS, no more random address (insert proper path to .nvmac.info in dhd.ko kernel module)
* move /mnt/secure to internal sdcard to fix asec apps (asec folder linked to /sdcard/.asec)
* disable adb on early boot -- fix mtp maybe? (change to init scripts in ramdisk)
* remove a couple of (probably) harmless references to sdcard1 in init scripts
* update vold.fstab with the correct partition for the sdcard (26), not sure if anything even uses that, but...
Update 3
* Kernel Lovins ->
--- Picked up slew of bugfixes from msm8660-common cyanogenmod jellybean kernel tree -- up to and including 09/13/2012 commits.
--- Enabled CONFIG_USB_ANDROID_SAMSUNG_MTP and CONFIG_SPI_QUP kernel options to match SHV-140 ICS samsung kernel config
--- Disabled CONFIG_XVMALLOC and CONFIG_ZRAM kernel options, also to match up to SHV-140 ICS samsung kernel config
--- Now compiled with newest Sourcery cross-compiler
--- Modified dhd.ko (Broadcom WiFi kernel module) -- you can now create file /data/.ranmac if you want your MAC address randomized on each reboot (ignores MAC on EFS partition, random generation expanded to 5 bytes)
* symlink for light sensor (/dev/i2c11 -> /dev/i2c-11) -- Doesn't fix auto brightness, but at least things that access the light sensor via the standard API will get values back now, FWTW.
* RIL stuff from SHV-140S (korean Tab 8.9 LTE) -- An attempt to resolve SIM_NOT_READY error -> Files replaced:
/system/lib/libril-qcril-hook-oem.so
/system/lib/libsecril-client.so
/system/lib/libreference-ril.so
/system/lib/libril.so
/system/lib/libril-qc-qmi-1.so
/system/bin/qmuxd
/system/bin/qmiproxy
/system/bin/netmgrd
* Update /system/etc/wifi stuff -- newer broadcom firmware images, wpa_supplicant.conf with p2p parameters
* Reenable early ADB since it appears MTP issues likely related to lack of CONFIG_USB_ANDROID_SAMSUNG_MTP kernel option -- Maybe someone who uses MTP can tell me whats up now?
Update 4
* Fix A2DP bitrate (48000 -> 44100 in /system/etc/audio_policy.conf)
* More invasive ASEC fix that might actually fix this jellybean nonsense (modified vold to use /data/secure locations, create /data/secure directory tree in init.emmc.rc)
* Revert SHV-140 RIL change, back to Note CM10 RIL libraries
Update 5
* Android 4.1.2 - Complete rebuild from CM10 tree retrieved on October 12th. Includes ASEC hack as in update4.
* SGH-i957 Radio Information Libraries (RIL) from official Telus ICS image - Thanks Dan!
Update 6
* Rebuilt from CM10 source code retrieved Nov 10 2012. ASEC hack applied.
* Update to latest msm8660-common kernel. Kernel unmodified (ie: no overclocking).
Update 7
* Rebuilt from CM10 source code retrieved Dec 20 2012. ASEC hack applied.
* Update to latest msm8660-common kernel. Kernel unmodified (ie: no overclocking).
Fantastic!
Are you saying everything seems to work pretty well except the 4G radio? (No guarantees, at my own risk, etc. etc. I know, I won't blame you)
If so, I'm going to try this right away. I don't have a data plan for my SIM, and haven't used the 4G yet. (Got a free upgrade from the wifi version after some shipping trouble with the vendor.)
The Galaxy Tab has been kind of a letdown when I have JB on my Galaxy Nexus and Kindle Fire both, and the "upgrade" is a bit disappointing since I checked on custom ROMs *before* I ordered, but the AT&T version is further behind.
Thanks for your hard work! I'll let you know what happens.
YellowRex said:
Fantastic!
Are you saying everything seems to work pretty well except the 4G radio? (No guarantees, at my own risk, etc. etc. I know, I won't blame you)
Thanks for your hard work! I'll let you know what happens.
Click to expand...
Click to collapse
I haven't had time to try "everything", but the stuff that I use on a regular basis is mostly functional. There's quirks, but... It's usable!
For example, one thing I just found out.. the Adreno (qualcomm MSM graphics) drivers aren't production-build.. There's no such thing available -- The current drivers available from qualcomm are "early sample" binaries for jellybean bringup testing, which is what this is... So, I've seen the random screen flicker, etc. Remember there are only a few devices with tested jellybean images, and most of them are google devices... And the i957 will probably never see an official JB release.
https://developer.qualcomm.com/mobi...phics-optimization-adreno/tools-and-resources
This release contains an early sample of the user-mode driver binaries for Qualcomm's Adreno 2xx GPU on Google Android 4.1 Jelly Bean. It has been tested with the CAF release M8960AAAAANLGD105210.1 and supports any Adreno 2xx GPU on Android 4.1 Jelly Bean. This release is intended only for developers that work on Jelly Bean bring-up work. It is an early release sample which will be replaced by a new driver binary in the future.
Click to expand...
Click to collapse
I'm sure there's plenty of little quirks you can find if you "twiddle all the knobs and flip all the switches" -- But it's certainly testable, and way closer to the "usable" end of the spectrum than the "barely functions" end.
Cheers!
PRE-ALFA CM10 Build
You did a great job nrvate !!. you inspired me to get ICS/JB on my SGH-i957. I did try your method and seems everything (3G, SMS, GPS, Bluetooth, Camera etc..) works except wifi. I am surprised that Voice calling is also working in this build !!! I will update you once I fix wifi issue. and also provide CWM/TWRP/ODIN flashable build if time permits.
Cheers !!
-KS
Its so exciting to see some real pregress.
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
Ditto. This is really good news. Thanks.
Cheers, y'all!
Only thing I had to do to get wifi working was stuff the original stuff (from honeycomb) in /system/etc/wifi.
first thing I'd do is make sure the dhd module is getting loaded.. dmesg will print your kernel log that'll show problems with loading that module.. also, try rmmod dhd and insmod dhd, see what happens.
If the DHD module doesn't report symbol errors or some nasty like that, make sure it's loading the firmware -- That'll probably leave an error in dmesg also if it's broke.
also check logcat for wifi-related nastiness
If you can find a specific problem post it and I'll try to help reproduce/solve.
Also working on hacking together a build of ICS based on what's been done with JB, but no idea how that's going to turn out yet. It'd be nice to have as a daily until qualcomm releases production-grade adreno graphics drivers (and, the CM9 ICS tree is now "final", might as well build it!)
update: due to needing the "late model" msm8660-common kernel for proper i957 device support, the later qualcomm (JB) graphics drivers are required too.. drat! however, looks like I'll still be able to hack together a build of CM9 based on the current "final" ics branch using the JB kernel and beta qualcomm graphics. got 'er booted, working out the kinks now. I'll start another thread for that when it's done
i wish i knew half as much as you do, keep up the good work!
orlandoxpolice said:
i wish i knew half as much as you do, keep up the good work!
Click to expand...
Click to collapse
Thanks! Learning as I go with half this.. It's just bits, try one way, get dirt.. try another way, get bacon!
Some of this is so touchy.. ie kernel versions vs adreno drivers, blah blah.. seeing what the SHV-140 kernel does.. it boots CM9, now to see if it'll play nice with video decoders. might forget CM9, i <3 jelly beans anyways!
nrvate said:
Thanks! Learning as I go with half this.. It's just bits, try one way, get dirt.. try another way, get bacon!
Some of this is so touchy.. ie kernel versions vs adreno drivers, blah blah.. seeing what the SHV-140 kernel does.. it boots CM9, now to see if it'll play nice with video decoders. might forget CM9, i <3 jelly beans anyways!
Click to expand...
Click to collapse
Solid work/mashery my friend. This indeed great news. I am currently waiting for my zip file to spit out, do a few mods and then give it a flash when I complete those things.
As far as the adreno drivers have you checked the site for them? I recall reading about them on another msm8660 device and perhaps may pertain to this project as well. The screen flicker has a few work arounds based on other devices that may relate to this device as well. Either to get rid of the flicker entirely or at least minimize them. Worth trying (here are a few I have seen work on some devices.. dev options, disable HW overlay, another is adjusting the debug.mdpcomp.maxlayer value in build.prop from 3 to 2, another is to set the min CPU freq to 486mhz).. last but not least, this was posted on cyanogenmod review, and can be cherry picked if not merged already: http://review.cyanogenmod.com/#/c/22782/ and may work. As far as getting LTE to light up in a more prompt manner, it may be worth exploring different modems (I see you are using UCLF6 from the i717 note), there are many others from the i717 leaks (ie. UCLF5, UCLE2/3, etc etc) and also of course any other Skyrocket ICS+ modems, as well as i717m (canadian, rogers modems such as XLA2 (gingerbread but worked on the i717 note in the US) and various others. If you cannot located them I will post links when I have more time. This is a great start, and I will help out when I have time to contribute to this project (I have a few on my plate plus a full time job so sometimes having the time is a difficult venture). In any case, great start and I can see this will progress very well in due time. Congrats and thanks for your contribution to the base of this, as this progresses and we work to manage these small issues, we will have something even solid
Regards,
th3g1z
th3g1z said:
Solid work/mashery my friend. This indeed great news. I am currently waiting for my zip file to spit out, do a few mods and then give it a flash when I complete those things.
As far as the adreno drivers have you checked the site for them? I recall reading about them on another msm8660 device and perhaps may pertain to this project as well. The screen flicker has a few work arounds based on other devices that may relate to this device as well. Either to get rid of the flicker entirely or at least minimize them. Worth trying (here are a few I have seen work on some devices.. dev options, disable HW overlay, another is adjusting the debug.mdpcomp.maxlayer value in build.prop from 3 to 2, another is to set the min CPU freq to 486mhz).. last but not least, this was posted on cyanogenmod review, and can be cherry picked if not merged already: http://review.cyanogenmod.com/#/c/22782/ and may work. As far as getting LTE to light up in a more prompt manner, it may be worth exploring different modems (I see you are using UCLF6 from the i717 note), there are many others from the i717 leaks (ie. UCLF5, UCLE2/3, etc etc) and also of course any other Skyrocket ICS+ modems, as well as i717m (canadian, rogers modems such as XLA2 (gingerbread but worked on the i717 note in the US) and various others. If you cannot located them I will post links when I have more time. This is a great start, and I will help out when I have time to contribute to this project (I have a few on my plate plus a full time job so sometimes having the time is a difficult venture). In any case, great start and I can see this will progress very well in due time. Congrats and thanks for your contribution to the base of this, as this progresses and we work to manage these small issues, we will have something even solid
Regards,
th3g1z
Click to expand...
Click to collapse
Thanks for the input! The flicker, as is, is really minor. It only really seems to happen, for me atleast, in the main launcher window and sometimes when scrolling in maps. It's intermittent, actually. I will have a look at that change you linked, nice catch!
Qualcomm's dev site is linked in post #4, hopefully they will post the final drivers soon. Do they have another site that would receive them faster, or with incremental builds? I really wish OEMs would share engineering builds more openly with the community, but I guess I'm just used to being on an engineering team, lol. I've been spoiled with working for a few of the larger OEMs and getting all the cool toys first...hehe.
I tried a few of the note ICS radios, got nothing at all from them besides errors in logcat -b radio, wouldn't bring up the SIM.
All the skyrocket radios seem to work to varying degrees.
Also, it may be more of the RIL -- The UCLF6 skyrocket modem works very nicely on the stock honeycomb image, insta-LTE and everything.
I have not tried any of the non-ATT radios... wasn't sure how that'd work out. I'll give some of the non-ATT radios a go, why not! Besides Skyrocket or Note, any other similar devices? Only thing I can think of is the SGS II LTE HD (SGH-i757) but not much is available for that device as AT&T punted it for the S III (747) and it never got popular.. If you want the HD screen, you get a S-III, which came out about a month later, which is just why ATT punted it all together.
I hear you on the job. I've got an interview lined up for a better one, too! Man, I'm hoping that works out!
nrvate said:
Thanks for the input! The flicker, as is, is really minor. It only really seems to happen, for me atleast, in the main launcher window and sometimes when scrolling in maps. It's intermittent, actually. I will have a look at that change you linked, nice catch!
Qualcomm's dev site is linked in post #4, hopefully they will post the final drivers soon. Do they have another site that would receive them faster, or with incremental builds? I really wish OEMs would share engineering builds more openly with the community, but I guess I'm just used to being on an engineering team, lol. I've been spoiled with working for a few of the larger OEMs and getting all the cool toys first...hehe.
I tried a few of the note ICS radios, got nothing at all from them besides errors in logcat -b radio, wouldn't bring up the SIM.
All the skyrocket radios seem to work to varying degrees.
Also, it may be more of the RIL -- The UCLF6 skyrocket modem works very nicely on the stock honeycomb image, insta-LTE and everything.
I have not tried any of the non-ATT radios... wasn't sure how that'd work out. I'll give some of the non-ATT radios a go, why not! Besides Skyrocket or Note, any other similar devices? Only thing I can think of is the SGS II LTE HD (SGH-i757) but not much is available for that device as AT&T punted it for the S III (747) and it never got popular.. If you want the HD screen, you get a S-III, which came out about a month later, which is just why ATT punted it all together.
I hear you on the job. I've got an interview lined up for a better one, too! Man, I'm hoping that works out!
Click to expand...
Click to collapse
I hear you on OEM not releasing the drivers in a timely fashion, and it is frustrating when you have sources for it as "leaks" .. pertaining to your question I did see a link to update drivers but in my 5 min search (short on time atm, work early in the morning), I didn't find it yet, but I will look a bit deeper and hopefully can find it. I recall it related to CM10 and addressing said drivers for a particular device or devices. I will see what I can find tomorrow, and hope that it pertains.
No harm in trying a few other modems, I would look at the i717/i717m (m is the canadian model, same device though and the modems from rogers work with the i717 as well as the skyrocket).. and obviously the skyrocket various modems which it seems you have tried at least a few of. They vary so much and your location has a lot to do with it. Some work better in certain areas, and others in other areas as I'm sure you know already. Worst case, even after trying a few you can always go back to UCLF6. I found it a bit odd that the rogers modems worked with ATT but hey I'm not complaining about that one I believe you are correct, however, pertaining to the RIL as being the issue, not so much the modem's themselves. (no telling though without trial/error)
I'm not sure the i747 modems would work or not, but, it will not hurt to try, as you can return to UCLF6 if it is a dead end. the i757 I have yet to even see, so I can't comment on that in particular.
I'd like to chat a bit more when we both have some time, not sure if you get on IRC (freenode network) at all but if you do look me up, same handle as here on XDA. It would be easier to chat that way.
I have more to say but having to be away in about 4 hours, I will have to get back to you. Good luck w/ the interview bud.
Take care, we'll catch up soon.
~th3g1z
th3g1z said:
I hear you on OEM not releasing the drivers in a timely fashion, and it is frustrating when you have sources for it as "leaks" .. pertaining to your question I did see a link to update drivers but in my 5 min search (short on time atm, work early in the morning), I didn't find it yet, but I will look a bit deeper and hopefully can find it. I recall it related to CM10 and addressing said drivers for a particular device or devices. I will see what I can find tomorrow, and hope that it pertains.
No harm in trying a few other modems, I would look at the i717/i717m (m is the canadian model, same device though and the modems from rogers work with the i717 as well as the skyrocket).. and obviously the skyrocket various modems which it seems you have tried at least a few of. They vary so much and your location has a lot to do with it. Some work better in certain areas, and others in other areas as I'm sure you know already. Worst case, even after trying a few you can always go back to UCLF6. I found it a bit odd that the rogers modems worked with ATT but hey I'm not complaining about that one I believe you are correct, however, pertaining to the RIL as being the issue, not so much the modem's themselves. (no telling though without trial/error)
I'm not sure the i747 modems would work or not, but, it will not hurt to try, as you can return to UCLF6 if it is a dead end. the i757 I have yet to even see, so I can't comment on that in particular.
I'd like to chat a bit more when we both have some time, not sure if you get on IRC (freenode network) at all but if you do look me up, same handle as here on XDA. It would be easier to chat that way.
I have more to say but having to be away in about 4 hours, I will have to get back to you. Good luck w/ the interview bud.
Take care, we'll catch up soon.
~th3g1z
Click to expand...
Click to collapse
I'll hit you up on IRC at some point for sure
So I sort of figured it out... Found how to get the radio to play nice, still don't know why... The kernel! Went back to the 3.0.8 kernel as provided by samsung for the SHV-140 (replaced zImage in boot.img, reflashed mmcblk0p8) and BAM. Nice quick 4G. Nothing in /system changed (so a bunch of other stuff broke) but the radio sure got happy.
Not sure what the difference is, quite yet... Should be an interesting needle in the hackstack for sure.
Is the package manager a problem with this the same as cm9?
Sent from my SGH-I727 using xda premium
orlandoxpolice said:
Is the package manager a problem with this the same as cm9?
Click to expand...
Click to collapse
yes, the issue actually originated with jellybean -- since there's no device tree in the cm9 repo for the p5att, i jammed the cm10 p5att device tree into cm9 source to make it happen. the device tree includes the init scripts, so the problem actually originated from cm10, lol.
same fix works.. mount tmpfs on /mnt/secure (in addition to /tmp/asec) and use wide-open (777) permissions.
nrvate said:
same fix works.. mount tmpfs on /mnt/secure (in addition to /tmp/asec) and use wide-open (777) permissions.
Click to expand...
Click to collapse
Heh! Is it just me or does that feel a little less than 'secure'? :silly:
i feel like a english lit major walking into an advanced calculus class with this jargon
This is how the sausage gets made.
Speaking of making sausage, I'm starting to think this is stable enough to share a binary build...
1) Camera is borked. I'm at a bit of a loss to figure it out, maybe I'll try again next week -- Suggestions very welcome, I'd like to get this working for video chat ala skype / gtalk.
2) MTP is borked. Again, at a bit of a loss, I suppose I'd care if I used it... Silly MTP.
3) New kernel fixes radio issues (mostly) - I've had it completely refuse to come up, showing no signal, fixed by rebooting the tablet. Goes right to LTE, but defaults to HSPA only. Change to LTE / GSM / WCDMA in mobile network settings -> network mode.
4) /mnt/asec / /mnt/secure issue (play store install problems) resolved.
5) FC in Settings -> Storage resolved by removing sdcard1 (which will never exist) from the build config
6) Boot animation is disabled due to framebuffer problems (supposedly) -- i know the spinny thing is cool, but you'll have to live with a black screen. Strangely, it comes up on some boots. lol.
7) Qualcomm graphics drivers are still the pre-release version. They seem to work pretty nice though. Haven't seen any of the flickering since some mdp changes in the kernel.
8) Video codecs aren't as screwed up as they are in the ICS build I did -- IE youtube works for all the videos I tried and bsplayer for android nicely plays my favorite x264 720P tv shows (win! gotta keep myself entertained at work some how...)
9) overclocked kernel HACK WARNING for you purists -- Modifed the kernel slightly, it now recognizes all MSM8660's as having the higher binned speed (1.66 vs 1.50 ghz) -- I didn't touch the frequency tables or anything, since it made more sense to just recognize the parts as 1.66ghz parts. Also, removed the logic that limited single-core mode to 1.2ghz (why?!). Gabe put out a OC kernel and most people reported stability at 1.7+ ghz, so... 1.66 seemed good. Hasn't borked for me. If you want stock speeds bad enough or run into problems.. http://d-h.st/8mB
Usual procedure, TWRP.. factory reset, wipe system, flash zip, receive bacon.
Bacon: http://d-h.st/Klu
I've been using this as my daily the past few days, and unless it starts behaving badly for some reason, it's probably going to be my daily for the foreseeable future. Really want to get the cams working, though!
Please share other issues. There has to be something else horribly broken I haven't noticed.
Usual "may make zombies run out of your tablet" warning applies to this test software.
Enjoy!