SS ROM:
SS stands for SimonsStock, for the HTC Wildfire S (Virgin Mobile USA ONLY)
I spent a long time compiling and testing this ROM, and am still working on modifying it, as I have school on weekdays and a big test in math coming up, so my developing time is limited. Ive de-odexed the entire ROM, made sure the carrier key logger was NOT present, added WiFi tethering (native htc, check the quick settings tab in status bar), added root, removed most of the crapware, however you can still activate your phone on my ROM, zip-aligned, ADHOC Networks are supported, and buisybox. NOTE: UOT's theme kitchen will work for this device anything you'll need to upload to them is in this zip as well. Eventually, I will get around to making a new boot.img but as of now, this one is stock. If you'd like to make one with apps2sd support and receive credit, PM me. Also, to anyone brought here looking for CM7, I am currently porting it, but have run into problems with the boot.img and kernel, its getting there, slowly. When I have a release of it I'll post, so dont ask for updates.
WARNING:
Any bricks are not mine, XDA's or anyone besides yourself's fault. The procedures used to flash my ROM may cause semi-bricking, However, it is always reversible.
So heres the flash-able zip:
you know the drill on flashing.. Dont forget to wipe everything
https://docs.google.com/open?id=0BwZZjRHl9NIJMGI1MTI3ZTEtYTk4YS00NzAwLWE3YjktMWRhZmRkODIzNTA1
ADDED:
WiFi tethering (check the quick settings tab on notification bar)
DeOdexed the Rom, so it is now themeable.
zipaligned for speed
fixed some small problems with memory (got you guys a little more)
fixed the link2sd problem
Added adhoc network support
MADE THE FIRST ROM (with these modifications)
Nice another ROM for the vm wildfire s
Sent from my HTC_A510c using xda premium
Will the CM7 be universal or just for the VM 510c?
d33ps1x said:
Will the CM7 be universal or just for the VM 510c?
Click to expand...
Click to collapse
CM7 should be universal, CDMA phones share the same hardware, so i plan on having a separate zip for the VM files that i want to include. This is stock VM firmware, the only reason that this is only for VM. Also, when CM9 Comes out, im only updating to make cm7 stable and as bugless as i can then permenately moving over to the CM9 source.
Update: sorry for the long wait, dialup is a killer on uploads
EDIT:
Also be looking for my next build, im going to include DSP and look through and see if i can unlock any more goodies. Ill also be posting some tutorials that allow for development on the phone, here. Not this thread, but a new one.
Great news m8,keep it up
I was wondering if you are going to add sense 3.0 lockscreen ?
Sent from my HTC_A510c using xda premium
New build is up
https://docs.google.com/open?id=0BwZZjRHl9NIJMGI1MTI3ZTEtYTk4YS00NzAwLWE3YjktMWRhZmRkODIzNTA1
cpie20 said:
I was wondering if you are going to add sense 3.0 lockscreen ?
Sent from my HTC_A510c using xda premium
Click to expand...
Click to collapse
Thanks for the reccomendation I think i will try to add it in there, but i am working on another rom at present, this is only a holdover until then to make our phones useable
No problem is that rom for the wildfire s??
Sent from my HTC_A510c using xda premium
Yes that is the Rom for the VMUS wildfire s. Next im going to try to add and remove some things. Im also working on the kernel, so if anyone knows how, and would like to teach me how to develop kenels, PM or email me
Oh I know someone that knows how to compile kernels but he is in another forum
Sent from my HTC_A510c using xda premium
What forum, send me to him lol. I have the thing booting, but i need the kernel for stability im a member of all forums, i can sent him a PM
His name is tiny from the htc incredible forums
Sent from my HTC_A510c using xda premium
Im going to look him up. I took a crash (google) course on kernels today. So i keep getting this error i dont know how to fix lol.. Fun fun.. Anyways, if anyone knows how to fix it it is
[email protected]:~/kernelsense$ make ARCH=arm CROSS_COMPILE=$CCOMPILER -j`grep 'processor' /proc/cpuinfo | wc -l`
scripts/kconfig/conf -s arch/arm/Kconfig
CHK include/linux/version.h
CHK include/generated/utsrelease.h
make[1]: `include/generated/mach-types.h' is up to date.
CC kernel/bounds.s
cc1: error: unrecognized command line option ‘-mlittle-endian’
cc1: error: unrecognized command line option ‘-mapcs’
cc1: error: unrecognized command line option ‘-mno-sched-prolog’
cc1: error: unrecognized command line option ‘-mno-thumb-interwork’
kernel/bounds.c:1:0: error: unknown ABI (aapcs-linux) for -mabi= switch
kernel/bounds.c:1:0: error: bad value (armv5t) for -march= switch
kernel/bounds.c:1:0: error: bad value (strongarm) for -mtune= switch
make[1]: *** [kernel/bounds.s] Error 1
make: *** [prepare0] Error 2
EDIT: I couldnt find him on there
its me ttying to make a stock kernel, with added supports.
I know nothing of kernels well the full avatar name is tiny4579 or something like that
Sent from my HTC_A510c using xda premium
lol still couldnt find him. Im going to look around XDA some
Got Cm7 to build, and a dev built me a kernel. Touchscreen and network dont work and some graphics issues but its getting there everyone
Nice to see progress going along
Ok, this is the real deal. An alpha release. There are lots of problems, but i need testers while im at school. This should work on any carrier. Please check the listing for my rom post
ssrom
This Rom is sick. Use this as my stock. Works well with Jikantaru oc kernel. WiFi is working. Thanks
Related
Hey guys!
i am very new at this but i have ported a build from fascinate over to our continuum and am looking for some devs to jump in and start helping me fix stuff.
this is very early but you can grab my first port here.
it is very much not ready for every day use.
Please flash if you are going to help me fix this for everyone
Code:
[B]
Rap sheet of things to fix will be here:
Screen placement overlaps the ticket screen, i was thinking we could
somehow code this thing so it will ignore the ticker
screen and only use the top.
Also we need to enable the soft keys.
Keyboard is non existent.
phone is not functional yet.[/B]
Well since this phone is virtually Unbrickable.... why not try our best.
Sent from my SCH-I400 using xda premium
Porting what build? Please tell me it's MIUI!
Sent from my SCH-I400 using XDA App
I've tried this before, and didn't get anywhere xP so, good luck
Sent from my SCH-I400 using xda premium
thanks for the well wishes... anyone know where to go in the rom to edit the screen dimentions yknow so it uses the top screen only? i think this is kernal
yea the problem with ports on the continuum is u cant flash mtd files in recovery a friend and i tried to port the fascinate miui 2.3.2 rom to the continuum we got everything resised and made it flashable but it just said installation aborted. the fascinate can flash mtd files straight from recovery and the continuum can not.
i still have all the files for miui if someone wants them pm me the problem is converting it to a .tar file so we can install via odin.
Bierce22 said:
yea the problem with ports on the continuum is u cant flash mtd files in recovery a friend and i tried to port the fascinate miui 2.3.2 rom to the continuum we got everything resised and made it flashable but it just said installation aborted. the fascinate can flash mtd files straight from recovery and the continuum can not.
i still have all the files for miui if someone wants them pm me the problem is converting it to a .tar file so we can install via odin.
Click to expand...
Click to collapse
mtd files? what's those for? the above build was ported from a fascinate rom. very asop
most roms use mtd sum to install everything im not going to go into detail about everything because i would just sound like an idiot lol.
Bierce22 said:
most roms use mtd sum to install everything im not going to go into detail about everything because i would just sound like an idiot lol.
Click to expand...
Click to collapse
lol i hear you, nah the above build ported fine.... no errors installing, i had to adjust scripting and also include imnut's kernal but it works. just need to fix stuff inside the rom
can u shed some more light on the rom such as is it froyo and aosp more information would be nice.
Bierce22 said:
can u shed some more light on the rom such as is it froyo and aosp more information would be nice.
Click to expand...
Click to collapse
sure, gimme a few and i'll update post 1, last night late i posted it with minimal info then went to bed...
alright here goes nothin im going to see what happens lol
The demensions seem to be within the framework, or at least the call to the kernel for the screen size..
So porting it is pointless, because you'll have to modify the framework back to the continuum's which would defeat the point...
As far as I think/know
That is actually why I stopped
But, feel free to prove/show me up
Sent from my SCH-I400 using xda premium
it does boot but i couldnt even get to settings and about phone to tell what it was and he still hasnt updated the op yet.
Yeah, i know it boots, haha.. I did this like two months ago
But the screen isn't divided properly for the ticker/softkeys... And won't be unless you can find the right part to edit
What language are we talking about? If it's Java I'm happy to help.
Sent from my SCH-I400 using XDA App
trailblazer101 said:
Yeah, i know it boots, haha.. I did this like two months ago
But the screen isn't divided properly for the ticker/softkeys... And won't be unless you can find the right part to edit
Click to expand...
Click to collapse
From what I have seen, in other posts about other phones, the screen size is written into the kernel. So, to do this, we need the source code for the kernel.
joshkoss: Great effort, but to do any serious mods, we must have the kernel source code. Without that, there is no way to compile the fixes/changes into the kernel. I have been able to use modprobe to do a few things, but, generally, the modules must be compiled against the source code of the kernel to work properly.
If someone can get us the kernel source code, we will be golden... Up until then, porting anything is not going to be fun.
If one was REALLY interested in doing this, one would take the generic Gingerbread kernel and ROM and work a build from the ground up that way. Especially since I don't think Samsung, nor Verizon will be handing out the kernel source code.
There is an off chance that Samsung might give the Continuum kernel source code to a developer AFTER Verizon sunsets this phone... (It's a very remote chance...)
Verizon gave me this number for the Samsung Mobile Helpline: (888) 987-4357. I haven't called them yet, but if enough of us call, someone MIGHT be able to knock something loose... Who knows. Let me know if I can help... This phone is my only phone, so I can't go flashing it every night to try things, but, over the weekend, I can try things.
Ciao!
I agree...collectively we should be capable of anything...even gettn sammy source...sumhow
sent from my XDA phone - its more than a continuum
I for one think y'all can do anything. Y'all have already done so much and I really think y'all are on to something huge!
Put a thread on cyanogen.com asking for assistance with this topic. What do you guys think of doing a donation pool to get a build working on our device?
Has anyone successfully built the kernel or a kernel module against the source released by Amazon? I have tried the following and get a error about a missing arch/arm/mach-omap2/Makefile:
Code:
$ export CCOMPILER=/path/to/android/toolchain/bin/arm-linux-androideabi-
$ make ARCH=arm CROSS_COMPILE=$CCOMPILER mrproper
$ make ARCH=arm CROSS_COMPILE=$CCOMPILER omap_4430sdp_defconfig
$ make ARCH=arm CROSS_COMPILE=$CCOMPILER modules
... a lot of stuff builds then ...
... arch/arm/mach-omap2/Makefile: no such file or directory
Any ideas?
I was just having this discussion last night with a fellow dev. Its definitely missing when it obviously shouldnt be. and I believe the board number is kc1 at least according to the stamp on the board.
Anyway, I'll be contacting them shortly. Their source code is incomplete.
arch/arm/plat-omap is missing as well.
I am trying android_4430_defconfig, the omap one doesnt have CONFIG_ANDROID & too many driver build issues to continue fiddling with
i start the channel in freenode #kf-dev
Here are my makefile replacements, I dont consider these correct, they are a big hack & a work in progress that gets vmlinux linked for me.
driver wise i have laak display off, *hdmi* off, and lgd display on.
havent debugged further.
Did you guys pull the configuration from the device? I didn't find it at /proc/config.gz
SikYou said:
Did you guys pull the configuration from the device? I didn't find it at /proc/config.gz
Click to expand...
Click to collapse
We cant get it unless amazon gives it to us...
death2all110 said:
We cant get it unless amazon gives it to us...
Click to expand...
Click to collapse
Forgive me, I have not not built a kernel in a long time. Why can't the configuration file be pulled from the device? I use to just do something like
adb pull /proc/config.gz
config.gz does not appear to be in /proc on this device but we should be able to pull the configuration from somewhere
Sent from my ADR6400L
SikYou said:
Forgive me, I have not not built a kernel in a long time. Why can't the configuration file be pulled from the device? I use to just do something like
adb pull /proc/config.gz
config.gz does not appear to be in /proc on this device but we should be able to pull the configuration from somewhere
Sent from my ADR6400L
Click to expand...
Click to collapse
Its not in /proc and i cant find it elsewhere. I agree there SHOULD be another way to do it. The only other way I know is to take the kernel by itself and run the extract-ikconfig script. But that doesn't even work. I've tried it multiple times. And people seem to be avoiding answering my question on here if there is another way. I'm sure there is...
Isn't the processor similar to galaxy nexus? Try using some of those files and as for the config, they may not have it in /proc, galaxy s doesn't from what I know, that makes you dependent in good source release. Start with galaxy nexus source and work from there I think
Sent from my Nexus S 4G using Tapatalk
The kernel stores its config only if configured to do so (the IKCONFIG options).
So a kernel with IKCONFIG disabled (most stock kernels of any phone I've ever worked with) won't have the config available anywhere.
Until we can get Amazon to cough up a complete kernel release including config we might start with the omap4430_sdp config with console on ttyUSB0. The KF certainly feels like the BSP was done by the ODM, so hopefully the kernel changes are minimal from the TI reference board...
ECOTOX said:
Isn't the processor similar to galaxy nexus? Try using some of those files and as for the config, they may not have it in /proc, galaxy s doesn't from what I know, that makes you dependent in good source release. Start with galaxy nexus source and work from there I think
Sent from my Nexus S 4G using Tapatalk
Click to expand...
Click to collapse
I was looking at the Droid Razr too
Alright.... Now I cant seem to get the kernel to compile past this
Code:
CC kernel/time/timekeeping.o
make[3]: *** No rule to make target `security/smc/omap4/tf_comm_mshield.o', needed by `security/smc/omap4/tf_driver.o'. Stop.
make[3]: *** Waiting for unfinished jobs....
CC security/smc/omap4/scxlnx_device_mshield.o
make[2]: *** [security/smc/omap4] Error 2
make[1]: *** [security/smc] Error 2
make: *** [security] Error 2
make: *** Waiting for unfinished jobs....
Any ideas?
cant disable the smc driver. (won't let you)
Is there anything helpful here? I don't know jack about android programming
http://mingfeng6865.blogspot.com/2011/05/build-linux-kernel-android-2635.html
death2all110 said:
Alright.... Now I cant seem to get the kernel to compile past this
Code:
CC kernel/time/timekeeping.o
make[3]: *** No rule to make target `security/smc/omap4/tf_comm_mshield.o', needed by `security/smc/omap4/tf_driver.o'. Stop.
make[3]: *** Waiting for unfinished jobs....
CC security/smc/omap4/scxlnx_device_mshield.o
make[2]: *** [security/smc/omap4] Error 2
make[1]: *** [security/smc] Error 2
make: *** [security] Error 2
make: *** Waiting for unfinished jobs....
Any ideas?
cant disable the smc driver. (won't let you)
Click to expand...
Click to collapse
Is CONFIG_SECURITY_MIDDLEWARE_COMPONENT set to y in your config?
richardg42 said:
Is CONFIG_SECURITY_MIDDLEWARE_COMPONENT set to y in your config?
Click to expand...
Click to collapse
Yes it is:
Code:
#
# Security options
#
# CONFIG_KEYS is not set
# CONFIG_SECURITY is not set
CONFIG_SECURITYFS=y
CONFIG_TF_MSHIELD=y
CONFIG_SECURITY_MIDDLEWARE_COMPONENT=y
# CONFIG_SMC_KERNEL_CRYPTO is not set
# CONFIG_SECURE_TRACE is not set
# CONFIG_TF_DRIVER_DEBUG_SUPPORT is not set
# CONFIG_DEFAULT_SECURITY_SELINUX is not set
# CONFIG_DEFAULT_SECURITY_SMACK is not set
# CONFIG_DEFAULT_SECURITY_TOMOYO is not set
CONFIG_DEFAULT_SECURITY_DAC=y
CONFIG_DEFAULT_SECURITY=""
CONFIG_CRYPTO=y
There's a new drop for 6.2 now:
http://www.amazon.com/gp/help/customer/display.html?nodeId=200203720
Maybe that'll have a working kernel tree?
randallu said:
There's a new drop for 6.2 now:
http://www.amazon.com/gp/help/customer/display.html?nodeId=200203720
Maybe that'll have a working kernel tree?
Click to expand...
Click to collapse
No .config ... haven't looked much beyond that yet.
Sent from my Kindle Fire using xda premium
randallu said:
There's a new drop for 6.2 now:
http://www.amazon.com/gp/help/customer/display.html?nodeId=200203720
Maybe that'll have a working kernel tree?
Click to expand...
Click to collapse
kernel hasn't changed.
Please keep in mind this is a work in progress and is currently intended for devs only. Do not flash if you don't know what you're doing.
Ok, after making some progress towards getting this thing ready for user-space, I've decided to finally start a thread on it just to see if I can get anyone interested or willing to help... This ROM is currently in below Alpha status (if there is such a thing) and does not boot, but I believe I can get it booting in about a week barring a system crash or a zombie apocalypse. Again, this is only meant for a jumping off point towards getting AOSP ICS on our I957s, so don't blame me if you flash this and your tab becomes bricked...
Source
Link to source ------> Here
Github
Link to Github ------> Here
Want to Help?
Code:
Downloading and Building from Source
Edit
Follow the Repo instructions to download and install Repo.
Download the Android source tree by specifying the branch and manifest for a specific Code Aurora release. In this example the download the carrot.cupcake branch using manifest ''M7201JSDCBALYA6380.xml''
$ repo init -u git://codeaurora.org/platform/manifest.git -b ics -m M8260AAABQNLZA30120.xml --repo-url=git://codeaurora.org/tools/repo.git
$ repo sync
Build the source tree
$ source build/envsetup.sh
$ choosecombo 1 1 msm8660_surf eng
$ make -j4
Running choosecombo with no arguments will prompt for Android build options and target.
Downloads
Link to ROM------> Here
Thanks to Da_g for the kernel base, and thanks to the people at Code Aurora for the msm8660 source.
Great stuff jo
Sent from my SAMSUNG-SGH-I727 using xda premium
Sweet, Thank you for start a build for i957 and Finally about time!
great start, thank you!!!!
MaX
Great news, keep up the good work.
Yes thank you very much for this start!
ICS for i957?
I'm ready to test when you have a bootable ROM! Where are you getting ICS-compatible hardware drivers for the i957?
Thanks
phil_white99 said:
I'm ready to test when you have a bootable ROM! Where are you getting ICS-compatible hardware drivers for the i957?
Thanks
Click to expand...
Click to collapse
Base drivers can be used from the msm8660 ics source code provided by Code Aurora, and proprietary can be used from the stock Honeycomb firmware. Hopefully.
1. THANKS JO!
2. In order to boot, what is needed?
I'm assuming this is a CWM zip, not an odin package, right>
With ics for the skyrocket leak hopefully things will get easier
Sent from my SAMSUNG-SGH-I727 using xda premium
Thank You. Hell yeah! You guys rock. I'll help out if I can.
I'm willing to test too.
hey Jo there are some ICS CWM roms starting to come out for the skyrocket (ICSMOD5 is what I was looking at). Do you think with some script edits this could be flashed to the i957?
thanks to OP for attempting this. there are enough of us i957 users out there I think !
orlandoxpolice said:
hey Jo there are some ICS CWM roms starting to come out for the skyrocket (ICSMOD5 is what I was looking at). Do you think with some script edits this could be flashed to the i957?
Click to expand...
Click to collapse
Yes, but the problem is we would probably need our own ICS kernel to get most of the stuff working. I'll try my hand at ICSMOD5, but I'm not sure if anything will work without a dedicated kernel.
jomeister15 said:
Yes, but the problem is we would probably need our own ICS kernel to get most of the stuff working. I'll try my hand at ICSMOD5, but I'm not sure if anything will work without a dedicated kernel.
Click to expand...
Click to collapse
yes you are right about that, but i think the tmobile guys got ics running with the skyrocket kernel but they are having issues with data.
orlandoxpolice said:
yes you are right about that, but i think the tmobile guys got ics running with the skyrocket kernel but they are having issues with data.
Click to expand...
Click to collapse
Ok, I'm not really going to be able to use my tab for dev purposes this weekends, but if you want to try a port here's what you need to do.
1) Setup a build enviornment in dsixda's kitchen with ICSMOD5.
2) You'll need to look at the updater-script and change the partition blocks according to the Tab (e.g system needs to be 25 instead of 24).
3) Two ways to do 3. One: grab the kernel from this thread and put it in ICSMOD, or Two: You could just leave the kernel as is. I'm wary of option Two.
4) Flash it. If it doesn't boot, try to get a logcat and send it my way. If it does, then yay ICS.
jomeister15 said:
Ok, I'm not really going to be able to use my tab for dev purposes this weekends, but if you want to try a port here's what you need to do.
1) Setup a build enviornment in dsixda's kitchen with ICSMOD5.
2) You'll need to look at the updater-script and change the partition blocks according to the Tab (e.g system needs to be 25 instead of 24).
3) Two ways to do 3. One: grab the kernel from this thread and put it in ICSMOD, or Two: You could just leave the kernel as is. I'm wary of option Two.
4) Flash it. If it doesn't boot, try to get a logcat and send it my way. If it does, then yay ICS.
Click to expand...
Click to collapse
OK I have followed these instructions; downloaded ICSMOD5, set up the kitchen, grabbed the kernel (assuming that's boot.img) from your zipfile in the first post of this thread and copied it to the working folder, overwriting the Skyrocket kernel.
Then I looked at the updater script to see if partitions need changing. Per this post the layout looks OK. Example: /system is p24 and /boot is p08 already.
So far so good? Planning a test for later today.
Exciting let me know how it goes
Sent from my SAMSUNG-SGH-I727 using xda premium
Also don't use the default generated kitchen updater script
Sent from my SAMSUNG-SGH-I727 using xda premium
After seeing how popular the HW codecs are in the 3.0 kernel test build, I realize that testers may consider building their own test ROMs and we're probably far enough along that the projects needed to be updated out at:
https://github.com/KFire-Android
So here's a quick explanation of how to sync down your own source for the android build (for right now it's CM9 and AOKP specific):
To start you will need to determine which code base you want to build for: CM9 or AOKP.
And then find that branch in the following project:
https://github.com/KFire-Android/android_local_manifest
The default branch is "ics" and this should work for building both AOSP and CM9 (AOSP untested as of yet). If you want to build AOKP change the branch to "ics-aokp".
The README.mkdn contains the setup instructions for how to get started.
Once you've followed those instructions you can execute the following from the command line:
. build/envsetup.sh
brunch otter
At the end of the long compile you can find your flashable ROM in the out/target/product/otter directory.
AS ALWAYS THE NEW KERNEL IS IN DEVELOPMENT. PLEASE WATCH YOUR BATTERY AND POWER OFF THE DEVICE WHEN NOT IN USE.
I'm looking up to the heaven's
wondering which cloud is yours
thank you
Sent from my Amazon Kindle Fire using xda premium
U r our hero hashcode
Sent from my LG-P500 using Tapatalk 2
Grrrr I can not for the life of me get ics to build. I need a new machine. If anyone gets an aokp build with 3.0 kernel would you mind sharing? Thanks
Sent from my Kindle Fire using Tapatalk 2 Beta-5
Will be doing this tonight!! Thanks!
CM9 Infuse - XDA Premium
pbailey212 said:
Grrrr I can not for the life of me get ics to build. I need a new machine. If anyone gets an aokp build with 3.0 kernel would you mind sharing? Thanks
Sent from my Kindle Fire using Tapatalk 2 Beta-5
Click to expand...
Click to collapse
The new AOKP build is totally untested btw. I can debug it later.
EDIT: And I fixed at least 1 issue where the existing amazon/otter projects need to be removed from AOKP (they're the old gingerbread kernel based build).
Re-grab the local_manifest.xml file here:
https://raw.github.com/KFire-Android/android_local_manifest/ics-aokp/local_manifest.xml
Hashcode said:
The new AOKP build is totally untested btw. I can debug it later.
EDIT: And I fixed at least 1 issue where the existing amazon/otter projects need to be removed from AOKP (they're the old gingerbread kernel based build).
Re-grab the local_manifest.xml file here:
https://raw.github.com/KFire-Android/android_local_manifest/ics-aokp/local_manifest.xml
Click to expand...
Click to collapse
I'm gonna try and build an AOKP rom from this, gonna start the repo sync soon just waiting on my VM to finish cloning.
So the build went fine, and I'm currently using the AOKP
Rom. The system UI keeps force closing but so far everything else seems to be working OK so far.
Sent from my Amazon Kindle Fire using xda premium
johnwayne007 said:
So the build went fine, and I'm currently using the AOKP
Rom. The system UI keeps force closing but so far everything else seems to be working OK so far.
Sent from my Amazon Kindle Fire using xda premium
Click to expand...
Click to collapse
Yep. As the kernel dev ramps down, I'll dig into that.
Sent from my XT894 using XDA
Hashcode said:
Yep. As the kernel dev ramps down, I'll dig into that.
Sent from my XT894 using XDA
Click to expand...
Click to collapse
Also the soft buttons do something kinda weird, it could just be a scaling/DPI problem at the moment Screenshot below. I also uploaded it if anyone else was interested in testing it out, its a pure AOKP rom with hashcodes 3.0 kernel, i didnt change anything.
Uploading a New build with Kernel 4 included, will post link to dropbox as soon as its done.
Special thanks to Hashcode for his awesome work, as well as the AOKP Team for their awesome ROM.
johnwayne007 said:
Also the soft buttons do something kinda weird, it could just be a scaling/DPI problem at the moment Screenshot below. I also uploaded it if anyone else was interested in testing it out, its a pure AOKP rom with hashcodes 3.0 kernel, i didnt change anything.
AOKP Otter Build 32 with Hashcode 3.0 Kernel
Special thanks to Hashcode for his awesome work, as well as the AOKP Team for their awesome ROM.
Click to expand...
Click to collapse
Where's the OP of that rom??
Sent from my LG-P500 using Tapatalk 2
http://forum.aokp.co/page/releases/_/build-32-r16
I'm assuming that you mean this link?
Sent from my Amazon Kindle Fire using xda premium
Hey hash, if i wanted to use this as a base and start modding the rom. Changing Icons etc, is their some guides out there as to how to do that? I am relatively new to modding a rom, i can follow the instructions to build one, but now i think i'd like to try and make my own.
Nevermind i found what i'm looking for.
johnwayne007 said:
Hey hash, if i wanted to use this as a base and start modding the rom. Changing Icons etc, is their some guides out there as to how to do that? I am relatively new to modding a rom, i can follow the instructions to build one, but now i think i'd like to try and make my own.
Nevermind i found what i'm looking for.
Click to expand...
Click to collapse
Could you post the link(s)/docs you found. I'm always looking for some good docu regarding CM and modding.
I don't have issues setting up my build environment, that's no problem. In fact I just built CM9 from the latest sources including Hashcodes kernel#4 from this evening and it's running like a charm on my KF. Thanks Hash!
So far i've found theme guides so far, now i'm looking for how to add in apps change build.prop before building.
http://forum.xda-developers.com/showthread.php?t=1377128
http://forum.xda-developers.com/showthread.php?t=916814
Is anyone else coming across these errors? Pastebin
loki154 said:
Is anyone else coming across these errors? Pastebin
Click to expand...
Click to collapse
Looks like a permissions or space / mounting issue on your ccache area.
Thanks Hash that worked!
Could we use your kernel and vendor and device files to pure AOSP?
Help? I just setup a vittualbox running ubuntu so I could make my own builds. On 5/9 I had a successful compile lots of warnings but it compiled all the way thru. Today I did:
. build/envsetup.sh
repo sync
brunch otter
Now it errors out:
GEN /root/android/system/out/target/product/otter/obj/KERNEL_OBJ/Makefile
HOSTCC scripts/kconfig/zconf.tab.o
scripts/kconfig/zconf.tab.c:206:24: fatal error: zconf.hash.c: No such file or directory
compilation terminated.
make[3]: *** [scripts/kconfig/zconf.tab.o] Error 1
make[2]: *** [otter_android_defconfig] Error 2
make[1]: *** [sub-make] Error 2
make[1]: Leaving directory `/root/android/system/kernel/amazon/otter'
make: *** [/root/android/system/out/target/product/otter/obj/KERNEL_OBJ/.config] Error 2
What am I doing wrong?
oh yeah what is the difference between the ota.zip and the update.zip that comes out.
Thanks
mlpmail said:
GEN /root/android/system/out/target/product/otter/obj/KERNEL_OBJ/Makefile
HOSTCC scripts/kconfig/zconf.tab.o
scripts/kconfig/zconf.tab.c:206:24: fatal error: zconf.hash.c: No such file or directory
compilation terminated.
make[3]: *** [scripts/kconfig/zconf.tab.o] Error 1
make[2]: *** [otter_android_defconfig] Error 2
make[1]: *** [sub-make] Error 2
make[1]: Leaving directory `/root/android/system/kernel/amazon/otter'
make: *** [/root/android/system/out/target/product/otter/obj/KERNEL_OBJ/.config] Error 2
What am I doing wrong?
oh yeah what is the difference between the ota.zip and the update.zip that comes out.
Thanks
Click to expand...
Click to collapse
I also got an error yesterday:
Code:
make[6]: *** [/u02/dev/android/otter/cm9/out/target/product/otter/target/kbuild/services4/srvkm/env/linux/module.o] Error 1
make[5]: *** [_module_/u02/dev/android/otter/cm9/out/target/product/otter/target/kbuild] Error 2
make[4]: *** [sub-make] Error 2
make[3]: *** [all] Error 2
make[2]: *** [kbuild] Error 2
make[1]: *** [build] Error 2
make[1]: Leaving directory `/u02/dev/android/otter/cm9/kernel/amazon/otter/external/sgx/src/eurasia_km/eurasiacon/build/linux2/omap4430_android'
target Symbolic: libOMX.TI.DUCATI1.VIDEO.MPEG4E (out/target/product/otter/symbols/system/lib/libOMX.TI.DUCATI1.VIDEO.MPEG4E.so)
make: *** [KERNEL_EXTERNAL_MODULES] Error 2
When checking the build log a little further up I noticed a few errors like this:
/bin/sh: dos2unix: not found
These log messages did not appear in previous builds. So I went ahead and installed the tofrodos package:
apt-get install tofrodos
cd /usr/bin
ln -s fromdos dos2unix
ln -s todos unix2dos
Then the build went fine.
However, I then removed the dos2unix link in /usr/bin to see if the build will fail again - but it didn't - go figure.
In other words I'm not sure what really caused the error - all I know it works again in my environment...
hii guys
after CM 10 geting almost full working i'v decide to port Miui jelly bean for xperia S based on it
but i need some help from you guys
__
so if anyone can give a help pleas tell me
for now the rom didnt boot yet im still trying to know why
any body know how i can make logcat for the rom booting !!?
Which MIUI ROM do you use for porting? Only Nexus devices have Jelly Bean? I think Galaxy Nexus is the least bad.
i was on galaxy nexus now im trying the nexus s but bouth give me bootlop !! if you recomnded a device tell me because im not sure what device to use as base
For 2011 devices we use nexus s, but as Xperia S is XHDPI, I recommend Galaxy nexus.
Please get in touch with thetrisatria, he's the unofficial MIUI jelly bean expert
I tried galaxy nexus but the Rom didnt boot!! Stock on miui bootanimation I need to edit framework.jar
Sent from my LT26i using xda premium
is any body here knows how to make logcat ?! system debug !!??
i want to know why the rom do not boot up
Hey sparxx
I've also tried to port MIUI Jelly Bean, even though I'm not experienced with porting and cooking at all. I have found this great guide where most of my knowledge about porting comes from.
To get the logcat of your booting device you need adb (included in the android SDK), and a PATH to platform-tools.
Open cmd.exe and execute 'adb logcat'
If you execute 'adb logcat >logcat.txt' you'll get your logcat as a .txt file.
Be aware of the big experience gap between knowing how to get a logcat and porting a ROM, though.
I'd be glad to help with this project, good luck.
I use the qtabd tool for logcat, has a friendly ui.
@jaapp, looks like I didn't help you further
Can you point out which file exactly gives you errors?
Via Tapatalk
I suggest a change of plans:
Maybe try to use HTC Sensation MIUI V4.1, it has the same CPU, so probably less fiddling with decompiling stuff is needed.
http://forum.xda-developers.com/showthread.php?t=1841196
They used Crespo as base though, so maybe the screen res doesn't matter, but CPU is more important.
All we need someone with knowledge with merging the framrwork jar
We have a bootup Rom but no ui showes up
We are close lts see what will happen
Sent from my LT26i using xda premium
You can try contacting SaossinX if he has time. He's very skilled.
Via Tapatalk
Just have to add a line to the kernel now to start shelld on bootup, no knowledge at all but i'm trying.
I've already contacted hei1125 to add the line for me, we'll see how it goes.
The rom boots up for the time being, MIUIHome, SystemUI, Android Keyboard and Google TTS FC.
I had contact almost with every body who could help
Will I had learn new things around but defiantly not the compiling part
I had contact Milad and he said he will work on it but he busy now
And another person who can help
For now we foucs on nepythys version JB hopefully he will make it work
Other plan is the ics
Lts see what we will get
Sent from my LT26i using xda premium
I've also got MIUI JB to boot today, lockscreen, setup manager, statusbar, wifi (finding singals) work, but I now have the problem that the keyboard doesn't work, i'll look more into it tomorrow. Please tell if/when you have found a fix for this.
Jaapp said:
I've also got MIUI JB to boot today, lockscreen, setup manager, statusbar, wifi (finding singals) work, but I now have the problem that the keyboard doesn't work, i'll look more into it tomorrow. Please tell if/when you have found a fix for this.
Click to expand...
Click to collapse
Can you send it to me?
Sent from my LT26i using xda premium
sparxx4 said:
Can you send it to me?
Sent from my LT26i using xda premium
Click to expand...
Click to collapse
I'll attach the services.jar and framework.jar, I find the ROM too big to upload at this stage.
I used FXP CM10 151 as base and ported the latest MIUI from Galaxy Nexus.
Jaapp said:
I'll attach the services.jar and framework.jar, I find the ROM too big to upload at this stage.
I used FXP CM10 151 as base and ported the latest MIUI from Galaxy Nexus.
Click to expand...
Click to collapse
Did you tried third part apk for keyboard??
Sent from my LT26i using xda premium
im getting statuse 7 install aborted when flashing the rom
any body know why this happen ?!!
I've got keyboard working now. MiHome isn't responding with 'waiting for miui.shell' error. It seems that MiHome needs the shelld service to be started, requiring an extra line in the kernel.
the good new we have a bootup rom with no fc so far
bad new still need to edit it