Related
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
Dear all,
I ask around in the past days if anyone was doing it, but no luck, I even try to look myself if it was easy to do starting from CM kernel, but then, looking better on sourceforge.net the androidhtc project... in the git repo I've seen the htc-vogue-2.6.32 branch!!! Obviously started by dzo.
To get it I've done:
mkdir androidhtc
cd androidhtc
git clone git://androidhtc.git.sourceforge.net/gitroot/androidhtc/kernel
cd kernel
git checkout -b htc-vogue-2.6.32 origin/htc-vogue-2.6.32
Click to expand...
Click to collapse
Than to configure and compile it (I have a crossdev environment)
cp arch/arm/configs/vogue_defconfig .config
make ARCH=arm menuconfig
# need to be adjusted the config...
make ARCH=arm -j3 CROSS_COMPILE=arm-none-linux-gnueabi-
Click to expand...
Click to collapse
Or you can take the nbh in DZO site and edit with NBH editor.
Everything is working right now:
wifi http://forum.xda-developers.com/showpost.php?p=7869029&postcount=5586
GPS, 3g, touch screen, camera, 3d... bluetooth.
In two days I didn't have any trouble.
Can't wait for the new compcache
Original thread on HTC Vogue by DZO
This is GOOD NEWS!!! I bet theres a shed load of work to be done yet though but it'll be good to get things up to date!
WOW.. nice keep your good work Dude..
I'm just newbie, only can hope and waiting
this confused me when i saw it. according to the internet the google foryo release already is .32
blindguyinanorgy said:
this confused me when i saw it. according to the internet the google foryo release already is .32
Click to expand...
Click to collapse
Our kernel is .25 I think. This is what's in the nbh regardless of whether we're running Donut, Eclair, or Froyo. Froyo is just the "top layer" if you will. The kernel is what makes the hardware work with Froyo.
*I'm not 100% on this:* dzo started with .25 and has just been hacking away at it to get it where we could get each piece of hardware working on our devices. Because he's been working so hard and altered so much, it's difficult to port all of his changes to a new kernel. That's why we haven't upgraded. If we could do what dzo has done for the past 2 years on the latest kernel I'm sure there would be much improvement on our devices, but there's a LOT that needs to be done.
This thread is kind of confusing. dzo said in the Fresh Froyo thread that he was pretty busy at the moment and what he meant with that is very likely that he is spending his available time on getting 2.6.32 ready for our devices.
It's very obvious if you keep an eye on the repo: http://androidhtc.git.sourceforge.n....git;a=shortlog;h=refs/heads/htc-vogue-2.6.32
The very best thing to do right know is propably to not disturb dzo more than necessary. I'm sure he'll let us know when it's has evolved to a somewhat useable state.
loserskater said:
Our kernel is .25 I think. This is what's in the nbh regardless of whether we're running Donut, Eclair, or Froyo. Froyo is just the "top layer" if you will. The kernel is what makes the hardware work with Froyo.
*I'm not 100% on this:* dzo started with .25 and has just been hacking away at it to get it where we could get each piece of hardware working on our devices. Because he's been working so hard and altered so much, it's difficult to port all of his changes to a new kernel. That's why we haven't upgraded. If we could do what dzo has done for the past 2 years on the latest kernel I'm sure there would be much improvement on our devices, but there's a LOT that needs to be done.
Click to expand...
Click to collapse
You are correct that we are using an older kernal. .25 is from before cupcake, wow.
I guess what I saw on the web was that new devices with froyo are also going to already come with .32
I wonder if there is much difference for any phone
There's already nbh for vogue with kernel 2.6.32 posted yesterday. Do You think we can use it? Of course after customizing it to Kaiser with NBHEditor.
new kernal
voyteckst said:
There's already nbh for vogue with kernel 2.6.32 posted yesterday. Do You think we can use it? Of course after customizing it to Kaiser with NBHEditor.
Click to expand...
Click to collapse
Used kernel 2.6.32 after using nbheditor, boots fine running fine so far. Shows kernel version 2.6.32.9 in android settings using Fresh Froyo. Taking it to work tomorrow to test it more.
So far from some testing gps work, 3g work, wifi got error, video works
Sent from my Full Android on Vogue using XDA App
handle223 said:
So far from some testing gps work, 3g work, wifi got error, video works
Sent from my Full Android on Vogue using XDA App
Click to expand...
Click to collapse
From my tests:
- had to reinstall whole system because of force close errors after changing nbh...
- 3g works, camera works, bt probably works (it enables, so probably it works ;-) )
- cannot even enable wifi
- probably location don't work (I wait about 15 minutes without results)
- didn't check gps
for me on pola200 camera doesnt work... bt activates, but wlan as with all devices - not working. feeling pretty smooth with this kernel...
Wifi fix - new 26/08/2010 kernel
dzo said:
I've fixed wifi on the 2.6.32 kernel. Attached is the new module, put it in /system/lib/modules. You'll also need the very latest kernel. I made some very big changes to the sd driver so this could break other things..
Click to expand...
Click to collapse
http://forum.xda-developers.com/attachment.php?attachmentid=389254&d=1282909102
Try this...
tiagoclc said:
http://forum.xda-developers.com/attachment.php?attachmentid=389254&d=1282909102
Try this...
Click to expand...
Click to collapse
Thanks, now wifi can be enabled ;-)
hello all
maybe a stupid Question how can I put the wlan.ko in the lib module
kisses
Rose Red
Hi Rosered,
you must put it into androidinstall.tar(tgz) and reinstall it,(keep the data, don't wipe it).
That what I have done.
vArrow said:
Hi Rosered,
you must put it into androidinstall.tar(tgz) and reinstall it,(keep the data, don't wipe it).
That what I have done.
Click to expand...
Click to collapse
No, You don't have to reinstall. You can mount /system partition rw and replace old one wlan.ko in /system/lib/modules/
Use this android update
thx all for your help
kisses
Rose
haret
Did someone try haret already? I've problems with zimage 2.6.32 ...it hangs on startup...can someone drop here the haret.exe, initrd and default.txt ?
Hugs
Original thread here! >>http://www.neopeek.com/forum/Android-ROMs/5764-Ooops-WE-did-it-again!-Gingerbread-Alpha2-available <<
EDIT: Not for Sony Xperia X1. Works on my HTC Diamond so I can't say what other devices will do...Thanx everyone for testing the Pre-Alpha! I could fix several bugs! Now we are officially Alpha and it's quite usable on my HTC Diamond!
Ooops WE did it again...
My wife's still knocking my brain saying I am an idiot B) (while writing this she stands behind me). I spent some hours yesterday and several hours during the night cause I know everyone wanna try this out. I want especially say thanx to Chann who always is inspiring me with his ideas while I am doing some nice conversations with him on dev-section of this forum. It's really helpful to have such kind of member here.
More details later -> as always: I don't have time to test anything out on my own -> so I didn't! It's up to you to come back and report your experiences.
Alpha-release 26-12-2010
Before continuing be aware of: This is an Alpha release and now it seems usable (on my HTC Diamond it is!)! So before you do anything I suggest you to make a backup of your data / files! So read everything careful now :
What's inside ?? :
[ul]
[li]Gingerbread 2.3[/li]
[li]Working: Wifi, Data, Phone, SD-Card, Compcache 25%, automatic lcd-density settings and maybe more[/li]
[li]BT activating produces reboot (needs fix)[/li]
[/ul]
Important now!!!!!! Read:
[ul]
[li]First boot takes quite some time! [/li]
[li]I suggest you to open all apps and sync your account with google. Then reboot your device![/li]
For Download, click above link!
As always: Use this on your own risk!
Thanx go to: Balsat, XDAndroid-Project, Martin DZO and everyone else whom I forgot!
Download is a 1-file-download, again! Including everything you need!
EDIT: I need your experiences / feedback in this thread!
Installation:
[ul]
[li]Installation Instructions (Link) thanx to chase21[/li]
[li]Test-Kernels to try out (Link) thanx to hayabusa94[/li]
[/ul]
Please update your signature! It's always hard to find out which device / smartphone you use and which kernel(s) you are referring to!
Click to expand...
Click to collapse
-Neopeek!
Don't thank me! Thank Vatoloco/Neopeek!!
HTC raphael 800 can run but wifi not working (status: error) and battery drain fast.
I still waiting for Neopeek Team.
I am just instaling it... I can not wait for the final fully functioning version.
Cheers
Not stable enough for me at least (Fuze/RAPH110)... Guess I'll just have to deal with FRX03/FRX02 for now... ^_^
Kernel package: htc-msm-linux @ 20101204_005141
I have a Fuze and it works fine for me, but it is just a bit laggy (kernel does not support so well).
Remember he just hacked gingerbread to work with froyo settings but I can promise that future builds will be much better once every one else has started the development of gingebread on our devices
I kind of figured, just wanted to report my experience since it seems most of the newer kernels seems to half work on my Fuze with FRX03. Might just be something I'm looking over About to try again with newest kernel from Glemsom's site and see if the FCs are any less frequent.
Yeah, i'm using the latest glemsom kernel and it is slightly laggy but stability is much better. I have not tried any other kernels yet..
I'm using the old kernel & module 01238 from FRG83 R5 build in this Raph100 & it works just fine except for the known Android issues that we still have.
Some minor glitches in Gmail & root access rights reported by SetCPU, but overall a good build (stable) considering that it's still in Alpha stage. Anyway, we get to test run Gingerbread while most native Android devices are still running Eclair or Froyo!
hello, it runs fine with kernel 1190 from camera thread, for the keyboard use jap input. Reboot you can, do with the dev tools-bad behavior-crash system server. keep going man very good!
UPDATE
Gingerbread is working nicely! I have not tested everything but at least there are less FCs! I am using kernel package from Dec 26, 2010:
zImage & modules
NOTE: Check out F22's note about this specific kernel package from THIS post.
Better performance ?
Gingerbread is supposed to be faster than Froyo. I wonder whether this will translate into a better performance on the Diamond. The Diamond is a slow device (compared to the HD2) and there's not much that can be done about it, except overclocking.
HD2_addict said:
Gingerbread is supposed to be faster than Froyo. I wonder whether this will translate into a better performance on the Diamond.
(post trim)
Click to expand...
Click to collapse
Anyway we could interest you into test driving and giving it a once-over with your diamond?
I would love to try it myself on my touch pro cdma (raph800), but i can't afford to mess around with creating the separate partition to try this. Is there yet an alternative way, as i would love to test this out also?
I suppose I could try to make it into a .sqsh file so you can just boot off of it on sd card but no garuantee it will work...
I wouldn't mind trying it if you don't mind doing that. I keep my android2.2 in "setpath=android2.2" directory, and assume i could also do the same with this "setpath=android2.3" to keep them separate.
here it is: http://www.multiupload.com/6QEW8OFBMJ
*may or may not work*
Thank you much sir. I just unzip the sqsh file from that archive file into the main SD stick directory, correct? So far i followed the instructions and (at the time of writing this) was at the "run the install from the subdirectory, after it's done, it will reboot back into WM" part, and continuing.
Yes, that is correct. You don't need to run "install.exe" or need the npkinstall folder. It should be fully compatible with xdandroid and you don't need the files from neopeek.com.
Just boot it as if it were an xdandroid build and hopefully, it should display android logo. Ext2 is much faster.. give it a try when you can.
I might have to do that. All i get is the following (last 2 lines of the screen at boot)
"mmc1: error -22 whilst initialising SDIO card"
"Waiting for root device /dev/mmcblk0p2..."
and then just sits there for ever.
Are you using an xdandroid startup.txt or neopeek?
Spacemoose1 has a special request:
ssserpentine presents......
Android 3.x Honeycomb for the Samsung Galaxy Tab (GSM)
Download Rom: GSM | Source Repository | Development Log | Donate
A Spacemoose1 production
Firstly, if you cannot commit to reading 3 posts completely, and carefully, please go here. for a quick look into your future.
Or go here for a look into your tabs future.
1) Yes, you MUST start off in FROYO, no exceptions! your reported bugs will be useless and of no help to me or anyone else. & as everyone should be following the guide, & coming from FROYO, don't expect to not get yelled at!
2) Everyone follow the installation guides in post # 2 step by step exactly!
3) This is presented in unfinished Alpha mode, for you to see what is to come and help bug test. EVERYONE needs to install exactly the same way so that they may report actual bugs, and not ones because you didn't listen.
4) Please, everyone, start off EVERY reply with your carrier (T-Mobile, Unbranded, AT&T, ect..) & country of origin of the Tab, so that it may be decided if any bugs are specific to any of these conditions.
This is an ALPHA version.
There is no 3g nor phone, among many other things (like BT, gyro, hardware accel.)
Using an alpha rom can be very dangerous. Don't just flash, because you see its HONEYCOMB, read everything very carefully first!
Wackymixing has created an excellent video of this HONEYCOMB alphaV2.5 running on GSM device.
(6/14/11)
After being up way too many hours in a row, and trying to do too many things at once, work on a new kernel has officially begun!
*what's in the oven. .
»new cwr with internal external support.
»1.2ghz
»uc ability
»reliable charging while power is off.
«doubtful, but cross your fingers for lagfix?
(6/13/11)
GSM owners. Alpha 2.5 has arrived!! (No 3g nor phone, ect.)
I highly recommend you start off in FROYO, as coming from GINGERBREAD causes crashes, and will make your bug tests not needed by me.
But, beware, changing your bootloaders is very dangerous![/COLOR]
*modded build.prop to identify itself as a Samsung Galaxy Tab as GT-P1000. - test runs, not included in cdma release
*modded audioflinger to accept dsp manager setting. (more equalizers coming soon) - test runs, not included in cdma release
*what I have planned, and currently in the works.** New kernel with 1.2, 1.4 oc
* Flexible scaling
* Attempted lagfix
* New CRW version with internal and external sd support
* SD cart mount upon boot
Until SD card load upon boot happens,
Instal Terminal Emulator from the market, and try these commands:
su
mount -t vfat /dev/block/mmcblk1p1 /mnt/sdcard/
Now your SD cards should be mounted!
(6/11/11)
GSM owners, I'm sorry to say that I have to put you off once again. The new kernel works and the crash issues have been resolved but I can't get vold to behave and the sd card simply refuses to mount at boot. The files in the repository are current though, so feel free to download and install them that way if you would like to test. You can mount the SD from a command line (adb shell) and activate UMS after boot using the following commands:
mount -t vfat /dev/block/mmcblk1p1 /mnt/sdcard/
echo /dev/block/mmcblk1p1 > /sys/devices/platform/s3c-usbgadget/gadget/lun1/file
-or-
download Android Terminal from the Android Market, and try these lines:
su
mount -t vfat /dev/block/mmcblk1p1 /mnt/sdcard/
Hopefully this issue will be resolved soon.
Edit: Also had a tester report the return of the screen sleep-state crash (power button), but the issue was resolved by flashing froyo, and then installing HC. He used the overcome 1.6 instructions. It ended his crash issues and returned his lock-screen. Just FYI.
Alpha GSM v2.5 has the following!
*A fully working tablet marketplace.
*Maps, places and streetview.
*Working audio (it needs work, but it's there.)
*The lastest version of voodoo sound integrated into the kernel.
*The voodoo sound control app.
*A couple of widgets from the Asus Transformer.
*A setup wizard that allows you to select your language at startup.
*A tablet keyboard apk that makes text entry easier.
*Multitouch.
*And a handful of stability and speed fixes.
What it doesn't have...yet
*Gyro (no rotation, there is an app installed but rotates wrong way)
*Settings window not appearing when expanding from the Notifications menu
*3g data nor phone abilities
*BT,
*gyro,
*hardware acceleration
*SD card on boot
*headphone audio
*mic
*GPS
The Guides
A very important thread for all to read before you do anything!
http://forum.xda-developers.com/showthread.php?t=1047500
How to go back to stock FROYO and get HONEYCOMB
Download the overcome based guide, created by thepittbull
and modded with help and permission by Sҡȳᴪʌɩҡͼṟ
Be sure to thank both, as this is an great guide.
(You will know it is going well if it goes from SAMSUNG splash screen, to dark, then your soft button lights will blink and then it will boot. - the time in between these things is hard to gauge)
TWEAKS
Tired of that red border?
1) Open up Dev Tools
2) Go to Development Settings
3) StricktMode Visual Indicator - turn it off
4) back out of app and now open it again.
5) If this doesn't get rid of MOST of the red borders, REBOOT and open app again.
WANT STREAMING MUSIC VIDEOS?
try looking for
Qello (get tbe tablet version)
its like you tube for music videos. thanks chris 49424 in cdma thread.
WANT IMPROVED UI AND SCROLLING?
Try adw launcher. for some reason just having it instaled helps just as much as using it.
PROBLEMS CONNECTING TO WIFI?
some users have problems with routers that use high channels. try to set your channel around 7 on router.
TV SHOWS STREAM
A very few users have reported that this does work.
Does not for me, but you might wanna try. there is a free version on market, but not our market. Google or maybe appbrain.
Dropbox
Great way to transfer files on gsm hc!
Apps confirmed working on port:
http://forum.xda-developers.com/showthread.php?t=1114916
thanks jjhiza!
Great news for GSM users! Thanks for your efforts.
Sounds good. Let's kick this thing!
Time to get this party started
ETA ON DOWNLOADABLE ROM:
SOON! sorry no exact time, i need to make sure everything is perfect!
ssserpentine said:
ETA ON DOWNLOADABLE ROM:
SOON! sorry no exact time, i need to make sure everything is perfect!
Click to expand...
Click to collapse
I'm comming from cm 7 will I be able to flash this or do I need froyo?
Edit got so excited I forgot to read
maxtcee said:
I'm comming from cm 7 will I be able to flash this or do I need froyo?
Click to expand...
Click to collapse
would still recommend on going back to Froyo, as mentioned in previous posts. There are way too many crashes and random errors if you were to start from Gingerbread.
That could change in the future though.
Sounds like it's flashing time again. Awesome stuff.
Looking forward to a new thread of garbage posts and new releases
Sent from my GT-P1000 using XDA App
maxtcee said:
I'm comming from cm 7 will I be able to flash this or do I need froyo?
Edit got so excited I forgot to read
Click to expand...
Click to collapse
I was on CM7 before trying out Alpha 2.5 (GSM). As said, I got frequent crashes and reboot problems. Just follow Overcome 1.6's guide and go back to Froyo. And then install Alpha 2.5, you will get less crashes.
maxtcee said:
I'm comming from cm 7 will I be able to flash this or do I need froyo?
Edit got so excited I forgot to read
Click to expand...
Click to collapse
FROYO.
everyone please start from froyo, as if you come from gb, i cannot promise sd cards will mount, wifi will work or power button will not cause crashes.
Thank goodness we get our own thread! Having to check the general thread was getting tiresome reading about those lucky CDMA users
Thanks for this ssserpentine! Ill be flashing as soon as I wake up
| Don't Revive Me Bro | Follow me on Twatter
robkoehler said:
Looking forward to a new thread of garbage posts and new releases
Sent from my GT-P1000 using XDA App
Click to expand...
Click to collapse
hopefully this thread will be clean.
Final testing, getting really close.
robkoehler said:
looking forward to a new thread of garbage posts and new releases
sent from my gt-p1000 using xda app
Click to expand...
Click to collapse
hahahaha! Lolz
Can't wait to test it.
This is the best thing since sliced Moose!
Sent from my SPH-D700 using Tapatalk
hussmanne said:
This is the best thing since sliced Moose!
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
0.o Er...
Just out of curiosity, do we refer to the GSM version as a fork? Or does that pertain just to the kernel? I want to know how to refer to the GSM version, relative to the CDMA, in the You Tube video that I throw up.
EDIT: Or, is it more of a port? Burning questions, people! Gotta make sure that we get our terminology right.
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!