Related
Hello world ! 8)
I mannaged to mount my complete shares on my windows Network to SD-Card ...
I'm using CM6 RC1 and i can simply do a :
modprobe cifs
mount -t cifs //192.168.0.X/share /sdcard/smbshare -o username=XXX,password=YYY
on Computer (PC-here 192.158.0.X) you have to make a share with the name "share" - on SDCARD in your android you have to make a directory with the name smbshare - the dir you are going to mount the PC-Share into)
magicly my sdcard is now a 1,5 Terabyte hdd ... 8)
No more streaming clients are need - just access MP3/DivX/MKV/PDF/etc.
WITHOUT DOWNLOADING TO SDCARD FIRST ...!
(watched a DivX movie directly with Rock-Player 5 minutes ago ... no copy to SDCARD nessasary)
Problem : after a reboot everything is gone ... 8) ... no automatic rermount - no difference between different WLAN-Routers
I am not firm enough on linux to write a script and do the neccasary things to get some logic behind this feature.
It would be wonderful if someone can programm a gui which fires up the nessasary mount when connecting to a wlan - differing between different wlans (networks) with different ressources.
shelling arround is not the best way for android users - something GUI like (e.g. Astro with SMB Modul - but mounting the share instead of copying to sdcard) would give everyone direct access to every file on the network without the nessasary streaming.
Even VPNing to the share should be possible ... giving direct access without streaming servers like ORK/etc.
Good idea ? please add some comments ...
************************************************************
************************************************************
Edit :
A small GUI frontend for managing CIFS shares is available in the following thread:
http://forum.xda-developers.com/showthread.php?t=756158
Let the show beginn !
Very good idea.
I'll take a look into it. Maybe after the weekend. We'll see..
That sounds f**** great! 8)
Thanks for the positive reply!
Sent from my Desire using XDA App
fogbav you can use GScripts for have a link to a script that do this command for you, and have differents scripts for do the same on different WLan.
Code:
#!/bin/bash
MY_USERNAME="your_user_name_here"
MY_PASSWORD="your_password_here"
modprobe cifs
mount -t cifs //192.168.0.X/share /sdcard/smbshare -o username=${MY_USERNAME},password=${MY_PASSWORD}
Wow ... that looks promising ... will test soon.
Thank you very much for the script !
Edit : Works like hell ... thank you ! Now let's see if beidl can do some magic tricks with "usability" and "different WLAN/Shares" logic.
Thank you all ...
What firmwares are you guys using? I'm on LeeDroid 1.6 and seems like cifs is not present for me after doing 'lsmod'. Thanks.
Cyanogen. 6 RC1. So it is Froyo...
Sent from my Desire using XDA App
If someone can provide me a cifs.ko module working with the official HTC Froyo (kernel version 2.6.32.15) then I can start working on a GUI.
I honestly don't want to go back to CM until it's problems are solved and 720p is working.
beidl said:
If someone can provide me a cifs.ko module working with the official HTC Froyo (kernel version 2.6.32.15) then I can start working on a GUI.
I honestly don't want to go back to CM until it's problems are solved and 720p is working.
Click to expand...
Click to collapse
Isn't the kernel source needed to compile a module for that specific kernel?
martino2k6 said:
Isn't the kernel source needed to compile a module for that specific kernel?
Click to expand...
Click to collapse
Well, it depends. One of the today released ROMs has a tun and ext4 module included, still we don't have HTCs new kernel sources. The thing is that I'm sure someone here on xda has access to the private HTC repositories. I remember the old days of the G1 community when someone gave "cyrowski" (old G1 dev) a dump of HTCs private git repository.
But I guess I'll most probably try the newest CM nightly anyways. So then I can also try to write a nice little GUI.
If you can get this working on roms with no cifs in app form it will be epic. I'll be more than happy to be a tester.
Had the above script workin fine in Adams OD 3.02 but had to go back to DeFrost without cifs (I think, didn't work anyway). I miss being able to stream EVERYTHING.
You can dooooo iiiiiiit!
Sent from my HTC Desire using XDA App
Sorry if this is a nooby question. Which ROM should i try this on and what should i enter the commands in?
I am happy to test this as it looks promising.
Thanks.
Bump......
Hi... i think you have to use a non stocked rom compiled with kernel from source code like cm6 opendesire. Stock roms dont have cifs function even new 2.2 official build doesnt have it until source is released by HTC.
Sent from my HTC Desire using XDA App
So do i enter the code in a terminal app?
ukmaddnes1 said:
So do i enter the code in a terminal app?
Click to expand...
Click to collapse
Yes.
(too short blah blah blah)
i get an error with modprobe that file or directory does not exist
su
modeprobe cifs
if this gives an error ... it seems there is no CIFS modul in your rom ... use CM6 ...
again error....it seems that i don't have the module installed........can anyone upload the module and tell me where to put it ???? i mean into what folder it should be
are there any guides on adding cifs into an existing rom/kernel? dont mind doing the work, just have no idea where to start atm.
I am Developing an AOSP Froyo build for the Samsung Captivate.
It is being built from the ground up and will be missing many of the
bells and whistles that this community has grown accustom to.
NO samsung or att bloat
although that also means no samsung goodies.
I also won't be including google apps. (this can easily be added in later)
This is not a CM build. although a lot of help comes from that arena.
I feel it would be better to build from a pure AOSP base.
knowing that it was created and fully compatible with the device that
it is being used on.
from there, all the optional extras can be added.
for now it will need to be built from source
here is some reading material for those that don't know how...
http://forum.xda-developers.com/showpost.php?p=6243873&postcount=1
http://help.github.com/
http://www.cmsgs.com/mediawiki/index.php?title=Howto:_Install_the_Android_SDK
http://developer.android.com/sdk/index.html
http://source.android.com/source/index.html
some helpful sources
www.github.com/CyanogenMod
www.github.com/teamhacksung
www.github.com/cmsgs
these are just a few I had immediately available.
IF ANYONE HAS BETTER SUGGESTIONS PLEASE LET ME KNOW AND I WILL ADD IT HERE.
what doesn't work:
cell network...( probably just needed to flash a modem)
wifi...
bluetooth
sdcard (internal & external)
audio
camera
gps
accelerometer/sensors
keymapping incorrect Fixed 4/21/2011
what works:
boots up
most apps that I had installed (I didn't wipe data so it kept all my apps)
live wallpapers
crazy fast graphics (next time I will run some benchmarks to compare)
the dim settings for brightness was a TON dimmer than stock (most likely better on battery)
touchscreen very responsive/accurate.
I am looking for any assistance on this. I have a lot that I plan on doing still but I don't have a lot of time to work on it.
So the more help I get the faster it gets done.
HOW TO BUILD FROYO FOR CAPTIVATE
After reading the reference material above
I use Ubuntu 10.04 32bit at ubuntu.com
10.04 is a LTS release (long term support) so even though there are newer releases I would stick to that one.
you will need java5 NOT 6 so if you have 6 installed already you should uninstall it.
(there is a way to have both at the same time but I don't recall the steps at the moment)
Code:
sudo apt-get install sun-java5-jdk
some extra stuff you will need
Code:
sudo apt-get install git-core gnupg flex bison gperf libsdl-dev libesd0-dev libwxgtk2.6-dev build-essential zip curl libncurses5-dev zlib1g-dev valgrind
make sure you are in your home directory (~/ = home directory)
Code:
cd ~/
create a working directory and go into it
Code:
mkdir mydroid
cd mydroid
copy my repo to your computer
Code:
git clone git://github.com/aosp4captivate/froyo.git
once that is done. (takes a while)
download this captivate_update.zip
and this initramfs.zip
Place the captivate_update.zip in the ~/mydroid/froyo folder.
Extract the initramfs folder from the initramfs.zip into ~/mydroid/froyo/device/samsung/captivate
there seems to be a permissions issue transferring from github
for now here is a quick fix for this
Code:
cd ~/mydroid
chmod -R 777 froyo
go into the captivate folder and run unzip script
Code:
cd ~/mydroid/froyo/device/samsung/captivate
. unzip-files.sh
yes that is a period before unzip-files.sh
now from the froyo directory setup the build
Code:
cd ~/mydroid/froyo
. build/envsetup.sh
lunch
select the captivate build
then
Code:
make -j4
I use 4 because my computer can handle 4 Jobs at once
just leave the -j4 off if you have a slow single processor.
this takes a LOOOOOOOONG time
for me an initial build takes about 1 hour.
subsequent builds are faster.
the result is in ~/mydroid/froyo/out/target/product/captivate
this is just off the top of my head so again
IF YOU HAVE ANY BETTER BUILD INSTRUCTIONS PLEASE LET ME KNOW...
Hey Man before you put all of this work in, why dont you make a gingerbread asop rom. I dont see the point in putting all of this work into an outdated os
bpodz34 said:
Hey Man before you put all of this work in, why dont you make a gingerbread asop rom. I dont see the point in putting all of this work into an outdated os
Click to expand...
Click to collapse
why don't you?
bpodz34 said:
Hey Man before you put all of this work in, why dont you make a gingerbread asop rom. I dont see the point in putting all of this work into an outdated os
Click to expand...
Click to collapse
Froyo is easier at this point.. and im sure some people prefer aosp over touchwiz
a.vandelay said:
why don't you?
Click to expand...
Click to collapse
No need to be a ****, just trying to help
bpodz34 said:
Hey Man before you put all of this work in, why dont you make a gingerbread asop rom. I dont see the point in putting all of this work into an outdated os
Click to expand...
Click to collapse
I already addressed this statement in the OP...
a.vandelay said:
why don't you?
Click to expand...
Click to collapse
bpodz34 said:
No need to be a ****, just trying to help
Click to expand...
Click to collapse
please don't clutter this up with this nonsense!!!
An AOSP Froyo build would be an important step for the Captivate community, good luck with your work!
good luck, look forward to it.
Appreciate your work. Good luck.
Awesome. Looking forward to it.
Sent from my liberated Captivate via XDA App.
Good idea ! I can help with testing if you like.
Sent from my SGH-I897 using XDA App
Sign me up for testing I actually am in the minority for working GPS so I can test that
I'm glad to hear that!
I'm in for testing as well if you need help.
Good luck!
Yes please.
And I'm DTT.
Down To Test.
not a troll, or hater, or dev but I thought an asop build was not possible because the touchwiz framework is tied in to deep and no open source drivers..
best of luck to you, im here to help test if needed
Grandelama said:
An AOSP Froyo build would be an important step for the Captivate community, good luck with your work!
Click to expand...
Click to collapse
I fail to understand this statement please explain ?
g0dzilla32 said:
not a troll, or hater, or dev but I thought an asop build was not possible because the touchwiz framework is tied in to deep and no open source drivers..
Click to expand...
Click to collapse
everything is possible , not that I understnad the need for it ...
mnjm9b said:
I was going to get involved with the CM builds but
I feel it would be better to build from a pure AOSP base.
knowing that it was created and fully compatible with the device that
it is being used on.
Click to expand...
Click to collapse
Maybe im misquoting you , and dont get me wrong here , any captivate development is good , but I fail to understand why starting form CM is a bad idea and even why we need to work of ( like fork roms of ) something that was AOSP build for samsung while you already stated that :
mnjm9b said:
the only captivate roms are actually hacks from the samsung builds.
Click to expand...
Click to collapse
we woudl then be makin roms 'ripped ' from CM like sooooo many other phone ..
IMHO , your work is redoing what CM is doing for many phones already , wouldnt it be much easier / not to mention rewarding for the community to just try and build cm 'from source' for the samsung captivate ?
g0dzilla32 said:
not a troll, or hater, or dev but I thought an asop build was not possible because the touchwiz framework is tied in to deep and no open source drivers..
Click to expand...
Click to collapse
Naw, I'm running an AOSP build myself right now. While the drivers aren't opensource for the Captivate, do you remember that there is a little phone called the Nexus S that has almost IDENTICAL hardware? Everything from the Nexus is opensource (pretty sure...) and the drivers are compatible with our Captivates. The only thing that we have that they don't is the second SD Card, which is an easy hack-in, and the audience noise-canceling mic (also easy, as the Nexus 1 has the same mic/chip.)
did the OP's cappy blow up or something, the accounts disabled >,> ~inches back~ joke aside, if you do have any thing needed testing give me a shout looking for something built off the cappys them selfs to though I must admit there is a (explicit) ton of roms for nomage as it is from the vibs source that are all well and good. Good luck, well back to flashing
**Last update! This thread will (shortly) be locked, and a new one will be posted With Galaxian-Soup ICS Alpha 2
Check back in a few hours!
**Update, this tread will be retired and locked come this Thursday 1/5/2012
Read between the lines, and you will see that a brand new thread in its place will be posted, complete with a yummy new alpha of ICS for our dedicated fans to enjoy... We thank you for your patience, after this alpha goes out we believe tere will be more frequent releases and postings
Stay tuned, but from what I've seen so far we have many surprises in store for our next release, and you, is ICS nirvana just around the corner? Check back on thursday!
Please don't take this to mean we've fixed every outstanding bug, but we have made major core improvements, and fixed some of the big "items"
We are seaking anyone with expeirence working HAL's and drivers.. if you are interested please PM me.
TTFN!!
** Update ** Work around for voice search
It appears that voice search is broken in several AOSP roms, during my research I managed to get voice search working, however its the older version (prior to ICS). So far it seems to work fine!
So until Google fixes (or we do hah) do this to get voice search to work
Download
Voice_Search_2.1.4
Go to the location the this file was downloaded and from a terminal (linux/mac) or the command prompt (windows)
Code:
adb shell
su (if not root)
rm /system/app/VoiceSearch.apk
reboot
Then side load adb Voice_Search_2.1.4
Code:
adb install Voice_Search_2.1.4.apk
After the install click on the microphone icon near search at the top left of the home screen, accept the permissions (you have to do this a few times, 3 by my count), don't panic if it asks a few times, it does stick.
Enjoy!
** Update** Happy New Year XDA and esp our friends with the Galaxy Tab 8.9! is this the year of the droid? We shall see!
Hey everyone I wanted to give everyone an update and general goings on! Im sorry to inform you that there will not be a New Years alpha, but we will have something for you all very soon after.
Here is a taste of what early 2012 will bring to Alpha 2.
1. We have decided to use ASOP source rather than Cyanogen Mod, this is primarily why there hasn't been a new release since xmas. After reviewing some of the initial bugs, and reflecting on what we accomplished in under 4 days, we decided we wanted the focus of this rom to become "best in breed" optimized for the Galaxy Tab 8.9. Meaning we are going to cherry pick the best features of both to create the best possible experience, with the lightest footprint, and most importantly stock ICS launcher! NoWiz, no Trebuchet. So far it has yielded very positive results.
2. Moving to ASOP and stock launcher has fixed one of the big bugs, automatic home screen orientation. I know more than a few of you were hoping this would be resolved fast, well there.. happy now?
3. MTD
4. General cleanup and optimizations have resulted in improved launcher response, it feels more fluid and less laggy...
5. Our repo is nearly finished, we are just ironing out some manifest bugs, when alpha2 arrives, so will our git links!
6. We have chosen a team name! Galaxian-Soup!
Thanks for supporting us, and we look forward to celebrating a "Droid 2012".
In the spirit of openness, if you would like to use our rom in your work please credit us in your OP and release notes. Our git repo should be up soon.
***Update*** Xmas Dinner Edition ***
Updated links to a 1.1 version, I added the livewallpaper.apks and re-zipped, no other changes.
and a newer version of Google Apps, seems to be more stable, but I've only been using it an hour, let us know!
Good Morning and Merry Christmas!
Is there something in your stocking for your GT7310? Well Santa Clause (in the form of _Motely, nycbjr, poisike, termleech (still need a team name!)) is delivering the first public alpha!
This build has been tested on the 7310 (Gtab 8.9 wifi, no 3g), and 7300 with no 3g (3g is being looked at).
Standard YMMV tag: You are flashing this at your own risk, make a nandroid backup first! If this breaks your tab we are NOT responsible.. now go play and have fun!
ICYXMAS-p5wifi-alpha1.1-cwm
icyGapps V2
Alpha V1 - ICYXMAS!
ICS 4.0.3_r1 vanilla
Rooted, deodexed,
Includes motley kernel v2e beta (see his thread for git details)
WiFi, GPS, Bluetooth
Installation:
In CWM recovery, clear your data/factory reset
Clear the dalvik cache (under advanced, or under the wipe menu in overcome cwm)
Flash the provided zip using CWM recovery
Flash gapps from CWM recovery
Bootup and setup your Google account
Install cpu control of choice, and set to interactive governor (this is required!)
*tested SetCPU, No-frills CPU control, and Antuantu.
Give it a chance, this is a deodexed ROM and will boot slow the first time and when you use apps the first time.
Doesn't work/Limitations:
WiFi-only, but 3G will be looked at for a future version (no ETA at the moment)
Camera doesn't work, don't know when or if it can be fixed.
Some video limitations, youtube HD vids not working. Some stuttering will occur until we get the kinks out.
Charger screen doesn't look correct when you plugin without booting up (charging status)
Voice search doesn't work - May have something to do with this error:
W/PackageManager(257): Failure retrieving resources forcom.google.android.voicesearch: Resource ID #0x0
Probably more that we haven't listed, this is an alpha - please let us know.
Team members:
nycbjr - project manager, dev (first working build), testing/troubleshooting
motley - lead dev, p5 device tree, final build, kernel development
poisike - pioneer testing with other tegra ICS ROMs, testing/troubleshooting
termleech - testing
Credits:
Google - for the releasing the OS
Cyanogen Mod Team - for their awesome git repo and developers. We used the p4 device tree as a starting point.
We would like to offer our p5 device if they are interested.
Samsung for the awesome device and kernel source (for HC 3.1 at least)
digetx - for pointing us in the right direction on the green frame buffer fix!
alterbridge - for his CWM Recovery port for 73xx.
JaeCar99 - for the sweet "Blue Hallway" bootanimation
I'm looking forward to a fully working ICS rom But a good thing takes time. Keep up the good work, guys!
great to see this development start
Sent from my HTC Incredible S using Tapatalk
Do you guys want some help? I'm currently working on a rom for the nexus with some other guys but could lend a hand here as well. What's the best way to get a hold of you guys?
Sent from my Full AOSP on Maguro using Tapatalk
termleech said:
Do you guys want some help? I'm currently working on a rom for the nexus with some other guys but could lend a hand here as well. What's the best way to get a hold of you guys?
Sent from my Full AOSP on Maguro using Tapatalk
Click to expand...
Click to collapse
I would never turn down any help, I'm very new at this (long time sysadmin, but only been a droid head since march hah).
Only caveat is you will need approval from motley before I can release anything to you, for now you can PM me and I will give you my aim/gchat and offline email, but I think we should setup an IRC, or aim/gmail chat to make this go faster.
As this is coming from CM9 sources I need to contact them too, I don't want to flub any licensing issues, etc, and maybe they will want to help, or us to help them!
Awesome! Thanks fellers!
great work
_motley said:
As far as WiFi, the P4 (Galaxy 10.1) uses a broadcom 4329 and we (the P5) uses the newer 4330. This is where the challenge will come it. When I get a better look at the Android code and have a flash up and running, hopefully it will become clear if something needs to be done on the kernel side or the Android side. If we start making good progress, we will need to get a git setup for our P5 stuff so we can share changes and files etc.
Click to expand...
Click to collapse
I don't know... I just flashed my P7300 with P7500 rom and wifi driver loads just fine. I only edited the build.prop and used a kernel from overcome rom, i didn't touch anything else. Also if you look in \system\etc\wifi you will see that both 7500 and 7510 roms have bcm4330 files there, so it looks to me that the wifi card is the same as our.
I also tried the kernel you sent me with 7500 rom and wifi driver still loads.
this is awesome guys.. after the posts yesterday and staying up till 3:Am , I got the sucker booting.. of course that was it though. Great to see this post today.. Sounds like it's not too far off.. at least for me wifi would be the only thing left that's important since I havent touched the camera app or bluetooth yet.
poisike said:
I don't know... I just flashed my P7300 with P7500 rom and wifi driver loads just fine. I only edited the build.prop and used a kernel from overcome rom, i didn't touch anything else. Also if you look in \system\etc\wifi you will see that both 7500 and 7510 roms have bcm4330 files there, so it looks to me that the wifi card is the same as our.
I also tried the kernel you sent me with 7500 rom and wifi driver still loads.
Click to expand...
Click to collapse
right, I'm going back over the source, and the board config, some wifi stuff seems commented out. I know I need to get on irc.. but work interjects lol..
for the record on linux to use broadcom it has to extract the firmware for the card, I don't think it has to for droid as in this case the firmware is provided to us. I should probably stop spinning my wheels and go back and read/learn more about how android treats these things.
I am all ears however, anyone with debugging exp can have the rom with permission to use the kernel from motly.
I don't think that the problem is in your build. I have tried 3 different builds and they all have the same error:
Code:
ERROR/WifiStateMachine(168): Failed to load driver!
ERROR/WifiStateMachine(168): DriverFailedState
So it looks to me that the problem is in kernel. Of course i could be wrong.
Also it looks to me that the bcm4330 driver source is posted on github (https://github.com/cyanogen/galaxy-2636/tree/ics/drivers/net/wireless/bcm4330), so i hope _motley finds time to take a look.
poisike said:
I don't think that the problem is in your build. I have tried 3 different builds and they all have the same error:
Code:
ERROR/WifiStateMachine(168): Failed to load driver!
ERROR/WifiStateMachine(168): DriverFailedState
So it looks to me that the problem is in kernel. Of course i could be wrong.
Also it looks to me that the bcm4330 driver source is posted on github (https://github.com/cyanogen/galaxy-2636/tree/ics/drivers/net/wireless/bcm4330), so i hope _motley finds time to take a look.
Click to expand...
Click to collapse
ok thanks I was looking at the source on my build system remotely, and the drive went oiffine, I think my ssd is going, so I'm going to get a new on on the way home. pisses me off!
Great work!
I'm seeing forward to try this out.
Gesendet von meinem GT-P7300 mit Tapatalk
poisike said:
I don't think that the problem is in your build. I have tried 3 different builds and they all have the same error:
Code:
ERROR/WifiStateMachine(168): Failed to load driver!
ERROR/WifiStateMachine(168): DriverFailedState
So it looks to me that the problem is in kernel. Of course i could be wrong.
Also it looks to me that the bcm4330 driver source is posted on github (https://github.com/cyanogen/galaxy-2636/tree/ics/drivers/net/wireless/bcm4330), so i hope _motley finds time to take a look.
Click to expand...
Click to collapse
Sorry, I misspoke, the 10.1 does indeed use the 4330 like us...been looking at Iconia, Xoom, and ASUS TF1 ROMs too much lately.
Well other than the green screen affect, wifi, camera,bluethooth this thing really runs well.
HC was a pig for memory, as I noted on my Acer when I ran ICS for a bit, memory mamagment is hugely improved over honeycomb, I never had more than 200mb free on a regular basis, with ICS its well over 400mb.
and the thing really cooks along, I snap in and out of screens really fast, and angry birds works! haha
I will spend some time tonight on wifi, and making a new build.
poisike I'll setup irc tonight, I may have to rebuild the macpro, who knew running an os other than apple would cause a problem lol..
_motley said:
Sorry, I misspoke, the 10.1 does indeed use the 4330 like us...been looking at Iconia, Xoom, and ASUS TF1 ROMs too much lately.
Click to expand...
Click to collapse
The otapackage build does spit out a file called "kernel" would that help you any?
I can drop it in my dropbox
actually there is a boot.img.cm9 in my alpha zip you have, but I can still upload just the file called kernel if yoi think it would help.
also once I have my macpro back in op I'm not against setting up accounts for you and poisike, or setting up our own git repo, would be beneficial to work against the same source once we zero in and attempt to create a working port for everyone.
oh and btw, your OC settings work, running ICS at 1.4ghz
This is great news!! Once the wifi is working, I'll be using this as my daily driver. Will this be a completely AOSP project or still based on TouchWiz. I wish I could have stock e-mail, calendar, etc.
Excellent news! I will be waiting patiently....
Asop only! "Don't wiz on my ICS"
Sent from my SGH-I777 using xda premium
nycbjr said:
The otapackage build does spit out a file called "kernel" would that help you any?
I can drop it in my dropbox
actually there is a boot.img.cm9 in my alpha zip you have, but I can still upload just the file called kernel if yoi think it would help.
also once I have my macpro back in op I'm not against setting up accounts for you and poisike, or setting up our own git repo, would be beneficial to work against the same source once we zero in and attempt to create a working port for everyone.
oh and btw, your OC settings work, running ICS at 1.4ghz
Click to expand...
Click to collapse
That sounds like it is just the zImage binary for their build, I think I remember seeing it there too. It won't do me any good. Sounds good about the repo. I can still browse the repos to look at code as necessary for the time being. Glad to hear that the OC is is still working good.
I just sent poisike a 3G kernel with the touchscreen fix so he can start working on that end.
"Don't wiz on my ICS!" haha
Many of us will use CyanogenMod 10 and Siyah kernel build by gokhanmoral, as it is maybe one of the best combinaison for a powerful and smooth device. My past experience with CM7 and Syiah Kernel show me some questions will hardnessly find a right place in the CyanogenMod 10 nightly builds | DISCUSSION THREAD neither in [KERNEL][ICS] SiyahKernel v3.0 thread. The issues you may experience could in fact be due to this specific combinaison, and when posting in CM10 thread you will be told to use only the custom Cyanogenmod Kernel, and when posting in Syiah thread you will be told your issue is CM10 relative and has nothing to do with the Kernel!!
Thus the idea to create an area dedicated to users running both Syiah kernel and CM10 ROM. They won't waste time posting and being flamed on both threads. I already can see some users jumping from one thread to another one.
When posting in this thread, you will lighten the main discussion threads, and browsing them will be easier.
Before you post, do a minimum of search in both threads to ensure there is not an easy and quick answer.
Then think twice, be as much as precise as you can when presenting your issue. We all will gain in efficiency and save our time.
Please keep this thread clean and useful in order to avoid "mass browsing". Refrain from flaming and adding to the crap ; do not offense, even in case of n00bish and stupid question; avoid any needless posts about your mood such as "Go Syiah", "Codeworkx, you are the best", "I love my phone" or any out of topic consideration.
learn a litle bit about BBC Code, and try to organise your post.
Be accurate and smart as much as you can. Answering will be easier and your post will help other users.
Both main threads are heavily busy, so I hope this one will help us in getting quick answers for both advanced users AND n00bs.
[color=#ooBFFF]It is up to you now to keep this place clean and convenient.[/color]
SEE POST 2 FOR LAST UPDATES AND POST 3 FOR BOOT TO GECKO
Unfortunately Mozilla decided to drop SGS2 development. I will still let the post in case Mozilla Dev team change their mind.
All credits are given to Teamhacksung, Cyanogenmod and Gokhan for their hard and clever work. Below are links to original work:
CM9 :
XDA Forum main discussion thread : http://forum.xda-developers.com/showthread.php?t=1419102
Cyanogenmod : http://www.cyanogenmod.com/
Teamhacksung : http://teamhacksung.org/
ROM download link : http://download.cyanogenmod.com/?device=galaxys2
You can download directly the nightly build to your device with Rom manager Premium.
Unless you are a flash addict, best is now to stick with official and stable CM9, currently 9.1
http://www.cyanogenmod.com/devices/samsung-galaxy-s2
CM10:
XDA Forum main discussion thread : http://forum.xda-developers.com/showthread.php?t=1794758
Modem + RIL installer : http://forum.xda-developers.com/showthread.php?p=31416701
CM10.1:
XDA Forum main discussion thread : http://forum.xda-developers.com/showthread.php?t=2036229
Still under development as Samsung code source is missing.
Syiah kernel :
XDA Forum Dev thread : http://forum.xda-developers.com/showthread.php?t=1555259
XDA Forum discussion thread : http://forum.xda-developers.com/showthread.php?t=1658647
Syiah Kernel for SGS2: http://www.gokhanmoral.com/
Kernel download link : http://www.gokhanmoral.com/
Extweaks thread by droidphile : http://forum.xda-developers.com/showthread.php?p=23616564#post23616564
Comprehensive and exhaustive list of Extweaks UV values by gecko95gek: http://forum.xda-developers.com/showpost.php?p=26755476&postcount=850
You can download directly the kernel to your device. Open your browser, go to gokhanmoral website. You will find an optimized version for device, with all listed kernels. Clic on it, the changelog will appeared as well as a download link.
Extweaks and Dual Booting FAQ by Droidphile
http://tinyurl.com/cvjcl52
http://forum.xda-developers.com/showpost.php?p=24233132&postcount=5
UNDERSTANDING ANDROID
Below is a link to a must read document about Android and how it works on your device. The pdf is quite big, 485 pages, but do not be afraid. All is very well explained, in a very clear english and academic fashion, so even n00bs can understand. There is a lot of pictures and very practical explainations.
http://tinyurl.com/dxr8dpx
All rights reserved www.hardkernel.com
Kernel cleaning scripts
Most often, custom Kernels create special directories and config files. If you want to switch from one custom Kernel to another one, it is not a bad idea to run this script before flashing the new Kernel. It will do some cleaning on your file system by removing all custom tweaks let by the Kernel.
http://forum.xda-developers.com/showthread.php?t=1363738
##My current configuration : [color=#ooBFFF]CM10-nightly-20121107[/color] + SyiahKernel [color=#ooBFFF]5.0.1[/color]##
##I am an Archlinux user, and some settings and way to operate are sometimes different from Ubuntu. So do not hesitate to ask here in case of any problem with Linux in general, and Arch in particular.##
Below is a list of major usage difference, known issues or tricks.
I will do my best to keep it up to date and exhaustive, according to my own usage of my SGS2 device and what I can read on the forum.
Noteworthy differences
Syiah Kernel use its own touch CWM. You can move around with touchscreen or screen buttons. When you backup, restore or install zip from sd card, use INTERNAL SDCARD instead of SDCARD (the opposite of CM9 practice).
Most kernel settings are done with an app called EXTWEAKS. This is a free app from Android Play. You need to give root access to Apps under Settings > Developper options > Root acess to allow EXTWEAKS to operate the changes. Settings from Extweaks will override the ones from CM9, like CPU govenor and clock speed.
Flashing Syiah kernel will install many .syiah folders and config files on your device. If you want to get rid of them when back to CM9 default kernel, flash syiah-resetdefaultprofile.zip (link to the file on his website under SiyahKernel v3.0beta3 section). It is NOT mandatory, as CM9 will be fully functional with these config files, but it is best to keep your system as clean as possible.
Using this kernel in the correct way, enjoying all the fine tunings, is not so easy and need a bit of knowledge. IF you have no idea about how work your CPU and GPU, stick to the default configuration. Wrong settings will cause malfunction, lags, glitches and make scrolling jerky.
Since version 3.1b1, dual booting is enabled. All settings are done in the Syiah custom CWM. It allows you to choose at boot time between two ROMs
[*]BLN IS WORKING NATIVELY SINCE KERNEL 3.2b4
GOOGLE NOW IS A HUGE BATTERY DRAINER ON CM10
2012/09/13
CM10 is now my first ROM. Flashed CM10-nightly 0913
flashed syiahkernel 4.1.5.
2012/09/13
Flashed CM10-nightly 0928
Battery is still draining very fast
some issues with superuser. Moved to SuperSu from chainfire (Play store)
2012/10/15
Flashed CM10-20121015-experimental-i9100-jbmalioshwc2-vsync_sysfs-changmin (link above under CM10)
Battery is better, memleak fixed.
Flashed Syiah-s2-v4.1.5-cm10-jbmali-vsync-sysfs
Flashed new gapps 20121011
2012/10/20
Flashed CM10-20121017-nightly
Flashed Syiah-s2-v5
2012/11/07
Flashed CM10-20121107-nightly
Flashed Syiah-s2-v5.0i
2012/12/09
You will find a 4.2.1 experimental CM10 ROM at this following link :
http://forum.xda-developers.com/showthread.php?t=2036229.
Teamhacksung has made a very hard work to port 4.2.1 to the SGS2, as they don't have any opensource drivers/kernel from Samsung.This build is still experimental.
2013/01/04
I am still on my old config with CM10 as I am not convinced CM and SyiahKernel are yet fully stable.
2013/02/28
I WILL NOT FOLLOW THIS THREAD ANYMORE .
CM 10.1 is totally broken on this device and there isn't even a stable release. Samsung broke things.
Gokham has some trouble building Kernels.
DUAL BOOT CM9/B2G : A QUICK & DIRTY HOW-TO
DEVELOPMENT ON SGS2 HAS BEEN STOPED. IT SEEMS WE WILL NEVER SEE THIS OS FULLY WORKING ON OUR DEVICES
B2G is Boot To Gecko, a Mozilla OS for device project. I have been following it since a while, and it is a very active and promising OS for your SGS2. It is in its very early stage, so do not expect to use it daily, but it is improving very fast.
When Gokham talked about dual boot, I immediatly think to B2G, as I am not interested in any other custom ROM than CM9. Thanks to its new 3.2.2 Kernel, it is now very easy to give it a try.
The work has been done by PULSER, building the B2G image, and GOKHAM, for dual boot capability. So a warm thanks to both of them, and of course to the B2G Team.
I will come back in the coming weeks with a more fine tuned How-To, as I did the install in the rush this morning.
How-To
I did everything on Ubuntu 11.10. Windows users will use Odin, and I am sure it works with other Linux distro.
I assume you have SyiahKernel v3.2.2. on your SGS2
I assume you have a working SGS2/Linux communication. It means a working ADB, USB and Heimdall. I used heimdall 1.3.1, and some users report issues with 1.3.2. Furthermore, I used Command Line, as the heimdall GUI front-end didn't work for me, and I didn't take time to investigate.
I assume B2G will be your second ROM.
Download the last two files of the list here (system and data image):
http://villainrom.co.uk/pulser/B2G/
Untar <Boot2GeckoDualBootsystem.tar> and rename it <hidden.img> if Pulser haven't changed the name (was mistakenly named <hiddenfs.img>)
Unzip <data.img.zip> and get a 2G <data.img>
Boot your device in CWM Recovery.
As mentionned on SyiahKernel website, Mounts and storage > format /secondrom_data and /secondrom_cache.
Reboot your device in Download Mode.
Plug your device
Run this command is to make sure heimdall is working
Code:
$ heimdall detect
Device detected
It shall return <detected>
Code:
$ heimdall flash --hidden <PATH/TO/HIDDEN.IMG>
---- you will see progress until 100%. It hangs a litle bit around 88%, just wait.
Reboot device on Android
Run this command on Linux:
Code:
$ adb push <PATH/TO/DATA.IMG> </sdcard/.secondrom/data.img>
File is big, so it takes a while (a few mn).
Reboot. On the dual boot screen, you have 3 sec to press your Home Button. Then you shall see :
Booting for the second ROM...
IF second ROM doesn't boot quickly (around 10-20 sec), then there is a mess somewhere.
Normally, you will quickly boot to B2G Lock Screen.
!!At this state, you will have nothing more than the lock screen. You need then to make-isntall Gaia!!
Let's make-install Gaia now
1-Dirty and quickest way-TRY THIS ONE FIRST
I did not yet tested this shortest way. It will save you a lot of time cloning unusefull stuff from Git.
You may have in this case an error with adb. Try to copy your own adb executable in the path where make gaia is supposed to find it.
Plug your device running the second ROM, B2G.
Then:
Code:
$mkdir ~/B2G
$ cd ~/B2G
$ git clone https://github.com/mozilla-b2g/gaia
$ mkdir /glue/gonk/out/host/linux-x86/bin
==> copy your adb executable in this directroy. Check permission
$cd gaia
$ make install-gaia
This is very minimal, but shall work.
2-Academic way
Code:
$mkdir ~/mozilla/gits/B2G
$ cd ~/mozilla/gits/B2G
$ git clone https://github.com/mozilla-b2g/B2G
$ cd B2G
$ make sync
Time for a beer...or two!! It takes long
Boot your device to second ROM, B2G now.
Plug your device to the computer.
Check if adb is fully working :
Code:
$ cd ~/mozilla/gits/B2G/
$ adb devices
List of devices attached
00194a183cd97e device
!!If you have no number and device, adb is not properly working on your system.!!
copy adb executable in /usr/bin
*EDIT : do not stress on adb, as in this case, when making gaia, an adb will be built.
Assuming you are still in the gaia folder
Code:
$cd ..
$ make install-gaia
ET VOILA.
You will soon see the gaia frontend.
useful links:
https://developer.mozilla.org/en/Mozilla/Boot_to_Gecko/Setting_Up_Boot_to_Gecko_Build_Environment
https://developer.mozilla.org/en/Mozilla/Boot_to_Gecko/Building_B2G_for_Samsung_Galaxy_S2
http://forum.xda-developers.com/showthread.php?t=1518467
https://www.villainrom.co.uk/forum/threads/introduction-to-dual-boot-of-boot2gecko-b2g.5436/
http://johnhammink.blogspot.ca/2012/05/part-3-updating-your-gingerbread.html
There is a very active B2G mailing list.
All credits to B2G dev, PULSER and Gokham.
On a serious note now first of all great posts you have made here. You have one way a right to be here so people can talk about the development issues that they are facing with the kernels but on the other hand this has nothing to do with development and you are actually not developing anything. Thus this thread should be moved to General Section and not here.
Plus there are threads of were people can talk about what they are facing on the perspective threads of the kernels that they are using. But anyway best of luck.
While the thinking and intention are good,I think this thread would best be put in the General or Q&A section,as it isn't development.
Anyway,the threads are already too cluttered,that's a fact...
Please, may a Mod move this thread to Samsung Galaxy S II I9100 > Galaxy S II General.
It has no reason to be under the development section.
Thank You
EDIT: Thread has been moved to a best place, as it is not mint to talk about development, but more of daily use.
This thread is a very good idea. Will be using it in the near future when I try cm9 again.
Sent from my GT-I9100 using XDA
That's a good idea.
But gokhanmoral him self change his mind twice a day regarding the support of CM9.
So I m afraid your thread would have no sucess until he clearly stand that:
1) Siyah will support CM9
2) Siyah wil NOT support CM9
That's a good idea.
But gokhanmoral him self change his mind twice a day regarding the support of CM9.
So I m afraid your thread would have no sucess until he clearly stand that:
1) Siyah will support CM9
2) Siyah wil NOT support CM9
Click to expand...
Click to collapse
No need for you negativity. If you don't think it will work. Don't use the thread.
There is a need. Because people are using siyah on cm9. Whether they will continue, another persons guess, but why do you have to point out the negatives. Is it to prove your knowledge to the contrary? Well done!
Just say nice thread, or even better, nothing if you don't agree and let people get on with it.
rice and pea(ce)
bleuxeon said:
That's a good idea.
But gokhanmoral him self change his mind twice a day regarding the support of CM9.
So I m afraid your thread would have no sucess until he clearly stand that:
1) Siyah will support CM9
2) Siyah wil NOT support CM9
Click to expand...
Click to collapse
1-I am not after sucess , just think there is a place for such a thread, being me or anyone else. If I am wrong, that's fine the thread will die by its lack of participation.
2-your post is exactly what I don't want here: unusefull from a practical standpoint. You are not helping anyone with your remark.
I was trying nightly 20120319 and siyah beta3 for a while and had no major issues.
In comparison to the kernel compiled by codeworkx, I had massive scrolling lags in trebuchet launcher with siyah.
more2come said:
I was trying nightly 20120319 and siyah beta3 for a while and had no major issues.
In comparison to the kernel compiled by codeworkx, I had massive scrolling lags in trebuchet launcher with siyah.
Click to expand...
Click to collapse
Which governor did you use?
Sent with Tapatalk from my GT- I9100
gabx said:
1-I am not after sucess , just think there is a place for such a thread, being me or anyone else. If I am wrong, that's fine the thread will die by its lack of participation.
2-your post is exactly what I don't want here: unusefull from a practical standpoint. You are not helping anyone with your remark.
Click to expand...
Click to collapse
I anderstand.
My main idea remains : how can you create a thread about a kernel while in the same time the father of that kernel say that he wont support CM9..or maybe he would?
It sounds crystal clear that your thread is like talking about Galaxy SIV when Galaxy SIII isnt here
well actually Gokhanmoral said so himself:
"kjetal advised me a nice and good build of cm9 and I hope to install it tomorrow. and I hope not to come back to a samsung rom in near future...
that's all for now. I have to go back to work"
And I'm pretty sure his signature says 'cm9 nightly' as well...
shr33kant said:
well actually Gokhanmoral said so himself:
"kjetal advised me a nice and good build of cm9 and I hope to install it tomorrow. and I hope not to come back to a samsung rom in near future...
that's all for now. I have to go back to work"
And I'm pretty sure his signature says 'cm9 nightly' as well...
Click to expand...
Click to collapse
great news!
I simply hope he will not change his mind again.
more2come said:
I was trying nightly 20120319 and siyah beta3 for a while and had no major issues.
In comparison to the kernel compiled by codeworkx, I had massive scrolling lags in trebuchet launcher with siyah.
Click to expand...
Click to collapse
Did you install Extweaks? If no, I would recommend.
Start to play a litle bit with CPU and GPU settings. Do not hesitate, it won't break your device. Just go step by step. You should quickly see some improvment.
I'm using b3 with the latest nightly and loving it . I don't need mtp when I've got airdroid!
Sent from inside a black hole.
bleuxeon said:
I anderstand.
My main idea remains : how can you create a thread about a kernel while in the same time the father of that kernel say that he wont support CM9..or maybe he would?
It sounds crystal clear that your thread is like talking about Galaxy SIV when Galaxy SIII isnt here
Click to expand...
Click to collapse
it is not quite true that I won't support CM9.
actually, I am thinking about using it as my primary rom.
but there are some facts now: I am using Samsung ROM, I cannot test anything about CM9 and I am very busy.
those facts make it impossible for me to support CM9 now.
when I install CM9, it will be harder to support Samsung ROM. that is why I want to finish dual-booting.
subscribed.
gokhanmoral said:
it is not quite true that I won't support CM9.
actually, I am thinking about using it as my primary rom.
but there are some facts now: I am using Samsung ROM, I cannot test anything about CM9 and I am very busy.
those facts make it impossible for me to support CM9 now.
when I install CM9, it will be harder to support Samsung ROM. that is why I want to finish dual-booting.
subscribed.
Click to expand...
Click to collapse
Many thanks Sir for this clarification.
PS : I just tried to make you a donation, but when I click "donation" then I go to PAYPAL in Turkish (or other that I dont know) and I can't anderstand it at all.
I have allready made you a donation but PAYPAL was in my own language this time.
Ramelov said:
Which governor did you use?
Sent with Tapatalk from my GT- I9100
Click to expand...
Click to collapse
I tried ondemand (default), interactive and smartassV2 .
All lead to the same result, very laggy scrolling.
Scrolling lags decreased with beta5, but performance still is worse than the CM9 kernel by codeworkx.
this is not to rush the devs, just asking, are they gonna wait till ( i really hope it actually hapens) jb update comes to us to start developing? couse i think our phone haves a lot more to give to us than the stock rom can, again i am not rushing the devs, just asking your oppinion, and since im kinda new to theese forums hardly think any dev is going to bother to even answer this thread
so im pretty much.asking your oppinion
this is just a question , please dont kill me
sent from the gray stuff inside my skull
demonoid phenomenom said:
this is not to rush the devs, just asking, are they gonna wait till ( i really hope it actually hapens) jb update comes to us to start developing? couse i think our phone haves a lot more to give to us than the stock rom can, again i am not rushing the devs, just asking your oppinion, and since im kinda new to theese forums hardly think any dev is going to bother to even answer this thread
so im pretty much.asking your oppinion
this is just a question , please dont kill me
sent from the gray stuff inside my skull
Click to expand...
Click to collapse
If you mean Custom Roms... we can't do anything until we can pack / unpack the boot.img/or recovery.img to make a custom recovery.
jeah thats right, i was wondering because my expirience with atrix 2 , previous to the ics update, i was using supercharger rom series, but again i understand that they got a leak to work on, and a bootstrap to flash the restores they where creating, and that stock leaked rom was awesome
sent from the gray stuff inside my skull
mattlgroff said:
If you mean Custom Roms... we can't do anything until we can pack / unpack the boot.img/or recovery.img to make a custom recovery.
Click to expand...
Click to collapse
Only for my own curiosity: what's prevents that ? The x86 arch ? or something else ?
Le_Poilu said:
Only for my own curiosity: what's prevents that ? The x86 arch ? or something else ?
Click to expand...
Click to collapse
Would be nice to know for sure. The current methods cannot find 'Android Magic'.
I'm looking forward to seeing this forum get some custom ROMs too...
Looks like progress is getting on with it now
Any updates on custom ROM making for this device?
I've followed the README from <link to Motorola's sourceforge for razr i, deleted because I'm a new user> , got to the final step, but now I'm stumped. What make target should I choose? 'make full_x86-eng' and 'make generic_x86' have no make rules. A simple 'make' generates a framework build error.
What do I have to do in order to get a bootable image (built from source) for the Razr i?
I'd appreciate any kind of advice. Thanks in advance.
PS: Many thanks Matt, turl1 and the other developers that worked on this device.
tiberiu24 said:
Any updates on custom ROM making for this device?
I've followed the README from <link to Motorola's sourceforge for razr i, deleted because I'm a new user> , got to the final step, but now I'm stumped. What make target should I choose? 'make full_x86-eng' and 'make generic_x86' have no make rules. A simple 'make' generates a framework build error.
What do I have to do in order to get a bootable image (built from source) for the Razr i?
I'd appreciate any kind of advice. Thanks in advance.
PS: Many thanks Matt, turl1 and the other developers that worked on this device.
Click to expand...
Click to collapse
You won't be able to build a full android system from that source. The most you can do is
Code:
$ . build/envsetup.sh
$ lunch generic_x86-eng
$ make [I]target[/I]
Where target is something like out/target/product/generic/system/bin/bluetoothd or bluetoothd
I am working on a device tree. Writing it from scratch isn't easy because there is no device I can base this on. No other x86 tree out there. And I still dont have a device. I did make threads requesting for a device but they got closed down. So once I have something built I'll make a new thread.
Sent from my GT-I9300 using xda app-developers app
hiemanshu said:
I am working on a device tree. Writing it from scratch isn't easy because there is no device I can base this on. No other x86 tree out there. And I still dont have a device. I did make threads requesting for a device but they got closed down. So once I have something built I'll make a new thread.
Click to expand...
Click to collapse
There's at least 10 device trees on the android-x86 project. And AOSP itself has a generic one, to build the x86 emulator platform. And I made a basic one to build recovery already, with support to generate the newer x86 boot image format.
Just saying
PS: I don't own the phone either
turl1 said:
There's at least 10 device trees on the android-x86 project. And AOSP itself has a generic one, to build the x86 emulator platform. And I made a basic one to build recovery already, with support to generate the newer x86 boot image format.
Just saying
PS: I don't own the phone either
Click to expand...
Click to collapse
Generic x86 and the razr I are too far apart. Also the android x86 ones are too far apart too (I am working on a android x86 tablet). I have already written more than 450 lines of the device tree by hand, and there is a lot more to go right now. I have patched bionic for x86 builds, I need to patch the build folder next, and even busybox needs patching, etc. I am now working on making a perfect set of the 3 important files, BoardConfing.mk, device.mk and proprietary-files.txt. My android x86 tree is a total of 181 lines (which in itself is twice the size of the trees on android-x86). Its fun, but really time consuming. Also the AOSP ones are generic ones, they will work on any system if you have all the correct drivers installed or compiled via the kernel, but Razr I needs the files to be pulled from the stock build, and it needs a lot of them, including kernel drivers.
-H
hiemanshu said:
Generic x86 and the razr I are too far apart. Also the android x86 ones are too far apart too (I am working on a android x86 tablet). I have already written more than 450 lines of the device tree by hand, and there is a lot more to go right now. I have patched bionic for x86 builds, I need to patch the build folder next, and even busybox needs patching, etc. I am now working on making a perfect set of the 3 important files, BoardConfing.mk, device.mk and proprietary-files.txt. My android x86 tree is a total of 181 lines (which in itself is twice the size of the trees on android-x86). Its fun, but really time consuming. Also the AOSP ones are generic ones, they will work on any system if you have all the correct drivers installed or compiled via the kernel, but Razr I needs the files to be pulled from the stock build, and it needs a lot of them, including kernel drivers.
-H
Click to expand...
Click to collapse
I'm playing a bit with AOSP 4.2 as I got some free time. This is what I found out so far:
bionic needed no patches. I seriously doubt it needs any on 4.1 (CM) either as recovery built fine.
build needed no patches either on both cases.
dalvik needed a 4-liner to build on AOSP (makefile fixes), I haven't tried to build it on CM
there's no busybox on AOSP, I patched the one on 4.1 already to be able to build recovery, it's all on CM Gerrit as you'd expect from a CM developer like myself
my tree is already 120 lines, as soon as you add the media decoder config and audio routing config you'll go over 180 lines
having proper drivers isn't enough, you need proper HALs too. And I haven't really looked, but I'd be surprised if you had to pull kernel drivers from the stock rom
turl1 said:
I'm playing a bit with AOSP 4.2 as I got some free time. This is what I found out so far:
bionic needed no patches. I seriously doubt it needs any on 4.1 (CM) either as recovery built fine.
build needed no patches either on both cases.
dalvik needed a 4-liner to build on AOSP (makefile fixes), I haven't tried to build it on CM
there's no busybox on AOSP, I patched the one on 4.1 already to be able to build recovery, it's all on CM Gerrit as you'd expect from a CM developer like myself
my tree is already 120 lines, as soon as you add the media decoder config and audio routing config you'll go over 180 lines
having proper drivers isn't enough, you need proper HALs too. And I haven't really looked, but I'd be surprised if you had to pull kernel drivers from the stock rom
Click to expand...
Click to collapse
1) bionic needs patching, patch already submitted to CM gerrit libdvm basically
2) build needs patching for the boot.img
3) dalvik has been patched
4) Odd, didn't notice that
5) Probably wont required pulling in kernel drivers, but would required pulling in the correct drivers for the defconfig
I'd be happy if you wanted to work together to get this working. PM me
hiemanshu said:
1) bionic needs patching, patch already submitted to CM gerrit libdvm basically
2) build needs patching for the boot.img
3) dalvik has been patched
4) Odd, didn't notice that
5) Probably wont required pulling in kernel drivers, but would required pulling in the correct drivers for the defconfig
I'd be happy if you wanted to work together to get this working. PM me
Click to expand...
Click to collapse
Let's continue talking on PM then
re. 2, I actually did need to patch build on AOSP after all . CM on the other hand, has BOARD_CUSTOM_BOOTIMG_MK from the tf tablets.
Hey I posted a rom over at droidrzr.com for use till aosp is ready. This should be enough till we get a jb leak
Sent from my XT890 using Tapatalk 2
Hi Folks
While I don't own a RAZR I , I have been Jaffing around with building CM10.1 and AOSP for x86, I've been getting in going on my FX8120, just need to sort the OpenGLES MESA drivers out.
Anyways I've got CM10.1 built for x86 using the mr1-staging branch ( I think it's been merged to cm10.1 ) and an edited mini-x86 device tree .
Busybox was a B**stard to build though, although on one of the branches there is an .config-minimal-x86 .config-full-x86, still needed tweaking tho.
I submitted my patches http://review.cyanogenmod.org/#/c/27377/ and http://review.cyanogenmod.org/#/c/27373/, however It seems x86 isn't top of cm's agenda.... or I'm missing something about assigning reviewers.
Obviously a base x86 build is only part of the story for you guys as you'll face all the regular problems that emedded devices have, not checked the specs for the RazR but I'm sure there's some binary blobs in your future,
Hack On Folks! :good: