cud anyone share with me how to get sync fixed and wifi fixed on eclair??
Im compiling an elair sapphire rom, ive got it booting, and it runs ok. just no wifi or sync.
please help!
bump!
cmon guys... i need help with this, im a noob to developing....
think i dun ok gettin it to compile and boot!
please help me out... and share ur fixes... it'll only mean more choice of roms!
I dont know a lot but I imagine its two seperate things.
the WiFi I imagine is a driver issue, and the sync is because you are missing the google apps.
I am guessing, but after compiling my own 1.6 rom and overcoming some of the strange things I found in doing that its a somewhat educated guess.
you re right! it is two seperate issues..
i have compiled the rom with the google apps from the milestone included. however i am experiencing the same issues with the sync that other devs did when they started working on eclair.
i am wondering how the other devs fixed the issues as this is the only thing preventing me releasing the rom
can anyone shed any light on these issues for me??? will credit u appropriatley on release.
bump again! sorry
can a dev help me out then??
thought this community was about sharing knowledge??
i think this would be a question that actually does belong in development. try there.
this thread already got moved from the development section!
just need pointin in the right direction, will figure the rest out myself!
bump, bump, bump!
can no one help me with this??!!
im guna try and pull sum stuff from the nexus one dump.. see if that works...
feels like im bangin my head against a brick wall tho..
ive downloaded loadsa roms off this site... and now im tryin to put something back, no one will help me out!
cmon devs, pm me, help me out with a fix for sync and wifi.
thanks!
ok, first of all, you're making a sapphire build but is it for the sapphire or the magic? They both use different kernels. If you're building for the sapphire (32b) then the stock kernel and wlan modules work fine. You might have a bluetooth problem, so, if bluetooth won't start, in your /vendor/htc/sapphire-open look for init.sapphire.rc and at line 59 change where it says "texas" to "texasalt". If you don't have bluetooth problems then don't change it.
Did you change your kernel by any chance? This could happen if you're using somebody else's boot.img or if you knowingly used another kernel and packed it to the default boot.img, or further, if you built your own kernel.
If you used somebody else's kernel, then you need to replace the wlan.ko module, again, in /vendor/htc/sapphire-open with the wlan.ko module from the kernel you took.
If, instead, you built your own kernel, then you need to rebuild the wlan.ko module doing the following (taken mostly in part from Johan de Koning's blog), ~/mydroid reffers to your working android path (mine's ~/Desktop/android/master):
Code:
export PATH=$PATH:~/mydroid/prebuilt/linux-x86/toolchain/arm-eabi-4.X.X/bin
(replace X.X with the toolchain version numbers you used to build your kernel)
Code:
cd ~/mydroid/system/wlan/ti/sta_dk_4_0_4_32
export KERNEL_DIR=~/mydroid/kernel/
make
and then copy the just-created module to sapphire-open
Code:
cp wlan.ko ~/mydroid/vendor/htc/sapphire-open
And about the sync problem? I'm wondering myself too. My last AOSP master build had gapps on it, but sync was still broken (you had to disable it), and so is still everybody else's based on AOSP, except for JAC/Cyanogen's.
The only other eclair build out there with working sync is Manup's, but his is based on the 2.0.1 sdk system image and he didn't fix sync, it just works on 2.0.1, so whatever was preventing sync from working on the 2.0 aosp build was fixed on 2.0.1, he just tossed the gapps in there and they worked.
I'm interested too in learning how Cyanogen worked out the sync problem on AOSP, he tweeted something like "I think I know how to solve the sync problem" a few days ago, but he didn't elaborate. We have to find someway to lure him to this thread and let us know how to fix it on our repos rather than copy his own.
If you do find out about fixing the sync problem (programatically), let me know please, I'm also interested.
Actually, looking through cyanongen's github, I think I found the answer. I'll make a quick eclair build and test.
http://github.com/cyanogen/android_...mmit/eea38a1ad7a61b4426612222a654da610e02855a
---edit---
nope, not it.
Here's the sync fix:
http://github.com/cyanogen/android_frameworks_base/commit/9fb8bb8a9542dfcaf9f546d9cee545517a03bed1
I think this would be pretty easy to patch into a non-AOSP build using smali/baksmali too since it's so simple.
Not sure what kind of wifi problem you have.. I've had no problems with it.
thanks 10chars
---edit---
nevermind
thanks guys.. i will start my own build as soon as i get home!
Also.. You should be able to build using my sources and get a system.img that actually works 100% and can be fastbooted.
Related
So, I'm messing about with building android from the source, just as a learning process and for my own personal satisfaction at this point.
I've come most of the way under my own steam.. got a build up and running from the donut-plus-aosp branch, all google apps included and working.. but I don't actually know how to include root access in the build.. I know this is probably an embarrasingly simple question for a dev, and I feel suitably stupid for having to ask.
Also.. now you're here.. apps2sd.. do I need to compile anything special for that or is it just a bunch of symlinks in init.rc?
Muchos gracias.
I believe the root access is located in the kernel (boot.img)
You would also want to include the SU binaries and busybox.
For the apps2sd, the apps2sd script is run from the init.rc IIRC
Do not hold me up on this because I have not even looked at Android yet, but this is what I gather from reading the forums. I'm hoping it may give you a little direction while someone who has actually built from the source steps in
Thanks. I've already included the su binary and superuser apk but couldn't launch them, so I thought I must be missing something either in the kernel or init.rc.
I was hoping not to have to build the kernel manually just yet.. walk before you can fly and all that, but maybe it's time to grow some wings.
You should just compile cyanogen's kernel. he has it on his github. btw.. did you add busybox? i think apps2sd requires it but im not sure.(check logcat on startup, see what errors its throwing)
I've just added busybox in, but I can't do anything with apps2sd until I get root sorted.
I'm sticking with the 2.6.29-donut kernel for now.. cyan's includes loads of patches that I don't understand yet.. I'll compile it and see what happens purely as an experiment but I reckon it'll give me problems...
Just looking at the configuration options for cyan's kernel makes me feel like a dad trying to program a vcr
This post was infected with retardation. Please ignore.
goldenarmZ said:
This post was infected with retardation. Please ignore.
Click to expand...
Click to collapse
LOL
btw if your building from ASOP, it should already have root. I think you only need to add it to T-mobile OTA's
I know I hate looking at kernels. Liquefies my mind
B-man007 said:
btw if your building from ASOP, it should already have root. I think you only need to add it to T-mobile OTA's
Click to expand...
Click to collapse
It's not working for me.. I just get "permission denied"
Well I've got root by running chmod 4777 on /bin/sh, but this leaves root access wide open to everything and bypasses the confirmation check from superuser.apk... Come on devs, I could really do with a few tips here!
I think I've got it now... thanks to all the devs, you were a real help here.
goldenarmZ said:
I think I've got it now... thanks to all the devs, you were a real help here.
Click to expand...
Click to collapse
XD
i know, they are so helpful right?
Actually they never come by here anymore because of the supernoob questions
I suggest you try to pm,twitter, or website the devs. many of them are very helpful, but cannot stand noobs. as long as you do your research (like u did) you should get help
Hmmm, as I'm also building AOSP from scratch, I would have liked you to have at least posted the conclusion. I feel like several pages were ripped out of my copy of the story.
Guys,
Seems like there are lots of threads popping up with new 'packages'. I thought we should create a thread solely for the discussion of kernel hacks/patches so that we can separate the two:
For those of you who dont know, http://gitorious.org/linux-on-qualcomm-s-msm/linux-msm-xdadev is the repo were are working on.
Just to clarify, this topic is ONLY for discussion regarding Kernel patches. Thanks to vdelf's headset patch it seems sensible to focus on:
1. Backlight always on problem FIXED 01/05/10 (vdelf)
2. Battery Issue FIXED 11/05/10 (drlucky)
3. Camera
4. USB
5. GPS
Makes sense. Lets add USB to the list. While charging works, data transfer does not. Also USB might allow us to debug kernel/android on the x1 and that is what dev's always dream of
:suggestion: why not add the latest kernel as download in the 1st post if there is progress. So everyone know where to download the latest updates u ppl do
dexteral said:
:suggestion: why not add the latest kernel as download in the 1st post if there is progress. So everyone know where to download the latest updates u ppl do
Click to expand...
Click to collapse
It will be great to do this, and stick it
@dexteral,
Anyone can checkout the kernel from the above repo I posted. To do what you require we would need to upload the Kernel everytime someone adds a patch...
vdelf said:
Makes sense. Lets add USB to the list. While charging works, data transfer does not. Also USB might allow us to debug kernel/android on the x1 and that is what dev's always dream of
Click to expand...
Click to collapse
Is data transfer even possible in haret? I mean how would system unmount sdcard if it's running from sdcard itself?
not fast data but normal will work
love it
vietdoan20062006
Hi, Lets add fm-radio to the list
Great idea ... otherwise we are creating such a mess with lots of different kernel versions in different threads.
If anyone is interested in compiling the kernel as well as the wifi modules, I have setup a VMWare debian appliance containing all necessary tools and scripts to compile everything. Since this is a few hundes MB, I haven't got a place to upload ... need to check this first. If you are interested, let me know.
@drlucky
Have you had a chance to look at the backlight issue? I am almost out of ideas
Can you post your modifications on the microp-module and what you found out until now?
_Sensible said:
Guys,
Seems like there are lots of threads popping up with new 'packages'. I thought we should create a thread solely for the discussion of kernel hacks/patches so that we can separate the two:
For those of you who dont know, http://gitorious.org/linux-on-qualcomm-s-msm/linux-msm-xdadev is the repo were are working on.
Just to clarify, this topic is ONLY for discussion regarding Kernel patches. Thanks to vdelf's headset patch it seems sensible to focus on:
1. Backlight always on problem
2. Battery Issue
3. Camera
4. USB
5. GPS
Click to expand...
Click to collapse
hey could you post the steps involved for compiling the kernel i am able to comile the kernel but it is not running
Wich toolchain do you use? arm-2008q1 or arm-2009q3?
X1iser said:
Wich toolchain do you use? arm-2008q1 or arm-2009q3?
Click to expand...
Click to collapse
arm-2010q1
could u write all the commands used by you
the way i have written
Personally I'll start to see how to compile the kernel. Can you share the link to download arm-2010q1?
Have you read this post ?
X1iser said:
Personally I'll start to see how to compile the kernel. Can you share the link to download arm-2010q1?
Have you read this post ?
Click to expand...
Click to collapse
http://www.codesourcery.com/downloa...-none-linux-gnueabi-i686-pc-linux-gnu.tar.bz2
but may be it is not the right one it has got 202 in it insted of 67
ya i read that post only
i was able to compile the kernel but it is giving some errors
_Sensible said:
@drlucky
Have you had a chance to look at the backlight issue? I am almost out of ideas
Click to expand...
Click to collapse
Sorry, haven't had the time. Could you push your changes to the git repo, I will try to have a look at it this week ...
okay i tried to make the kernel bt following the guide above by fatsal...
but i got stuck at
make htckovsky_defconfig ARCH=arm
htckovsky_defconfig doesn't exist (in the new repo anyway, i believe)
any help? which defconfig to use? :S
drlucky said:
Sorry, haven't had the time. Could you push your changes to the git repo, I will try to have a look at it this week ...
Click to expand...
Click to collapse
Just played with the klt-driver a bit. I always get version 0x0000, which on a hero means "bootloader mode". I have tried to migrate the hero code, but with no luck. It seems that the microp-klt needs a "reset", which shoudl be done by using a magical GPIO (on hero: 76), but this doesn't currently work at all. Kernel boots up, but still gets no valuable version number.
I found out the hard way that apparently the WPA2 implementation in Android is faulty. This means it can not connect to WPA2 secured APs which enforce strict specs:
https://forum.openwrt.org/viewtopic.php?id=25870
Would it be possible to fix that in CM ?
Cheers,
Karl
Android is using wpa_supplicant, it doesn't implement the protocols on its own.
So you are saying the bug is actually in wpa_supplicant ?
Should i try to make them aware of the problem ?
First time I hear that, although I have at home WPA2 personal and my Legend connects with it normally.
I have a WPA2 personal network both at home and at my dorm, and my HeroC has been able to connect to them fine no matter what ROM I've used (stock, Sense 2.1 custom ROMS, and CM6/7)
According to the openwrt link i posted above it seems to be a problem with the drivers on openwrt enforcing strict RFC compliance and the wpa_supplicant not sticking to it. So it might just be a problem for a specific setup.
However, the question now is if that should be fixed in android or if openwrt should relax its rules.
I just try to find out which community would be the right one to address...
Hey AliBa !
People at openwrt think its a problem of the TI wireless drivers, and that it could be fixed in CM:
This is not a problem with OpenWRT, hostapd, or wpa_supplicant (the latter two are the same project, and mostly written by one person). This is a bug with Android wifi drivers that do not properly follow spec.
The TI Wilink driver I referred to is particularly at fault, and disabling WMM on the router is a band-aid to the problem - not a fix or a real solution. wpa_supplicant is not even involved in this process since the Wilink driver generates the RSN on its own.
The people who need to address this are TI, not openwrt or CM or someone else (or CM can put in a patch to fix the TI Wilink driver, which is probably a good idea anyway).
Click to expand...
Click to collapse
https://forum.openwrt.org/viewtopic.php?id=25870
There are two RSN settings in tiwlan.ini:
Code:
RSNPreAuthentication
RSNExternalMode
...try setting latter to external.
Hey BlaY0 !
This .ini file is in the build tree, not on the phone, right ? Or can i set that on my phone ?
If its a part of the build files, do you think I should file a bug at CM ?
It's on the phone... /system/etc/wifi/tiwlan.ini. It's configuration file for driver itself.
Might be a noob-problem, but i am unable to write to the file.
I tried terminal emulator, su, vi /etc/wifi/tiwlan.ini, but its read-only.
Any other way i can try this ?
Use recovery to do that or you can use system overlay.
Sent from my HTC Legend
Tried switching the RSN..-config to external as mentioned, but it's not working here.
Hmm, anything else we can do ?
AliBa, are you sure you could not fix this ?
People at openwrt think it could be patched in CM:
https://forum.openwrt.org/viewtopic.php?id=25870
Cheers,
Karl
Yes, I'm sure I can't fix that.
If it's not caused by wpa_supplicant then there's nothing we can do. Sources for neither firmware nor kernel module are open sourced so there's no way to patch them.
Hey !
ali ba said:
Yes, I'm sure I can't fix that.
If it's not caused by wpa_supplicant then there's nothing we can do. Sources for neither firmware nor kernel module are open sourced so there's no way to patch them.
Click to expand...
Click to collapse
Too bad. Didnt know that some (?) kernel modules are closed source in android. What a shame !
Anyway, thanks for trying to help !
karl_k said:
Hey !
Too bad. Didnt know that some (?) kernel modules are closed source in android. What a shame !
Anyway, thanks for trying to help !
Click to expand...
Click to collapse
It's a royal PITA, and we all dislike HTC, Motorola, Samsung etc. for doing it. That said, the CM team do an unbelievable job of dealing with it as well as they do
karl_k said:
Too bad. Didnt know that some (?) kernel modules are closed source in android. What a shame !
Click to expand...
Click to collapse
Every Google device was as close to open source as possible with all kernel sources being released. It's companies like HTC that corrupt that whenever they can. For example they put code into the framework that would normally go into the kernel just to not having to release it.
Moreover, the sources for wl12xx were open sourced by TI using a BSD-like license. The even sadder problem is that HTC modified them and then deliberately removed those modifications (headers) from the kernel sources they released.
So its a dead end, and really nothing can be done about it?
Can't believe that!
I tried the latest build of CM7 done by the Atrix Dev Team and it is awesome. Very reliable, fully functional, etc. I figured I'd give a whirl to compiling the real ICS version to see what that was like.
CM9 build system with the appropriate Atrix Dev Team repos in place actually spit out a working ROM. There are a number of issues aside from the general preview state of CM9. I figured I would share them in case anyone else was as curious as me. Apparently, the internal atrix dev teams are well beyond these issues already, so kudos.
Probably related to CM/atrix specific stuff
- Camera and finger print sensor don't work
- Launcher crashes pretty often
- Some openGL demos don't seem to work right (or at all)
- No mounting the SD as USB storage
Probably related to the specific gapps package I used.
- Maps crashes after 3 seconds (signal 11 - native code crash)
- Maps wants to update, but it can't (sharedId conflict if you actually remove maps)
- Earth won't run (missing the earthmobile library)
- Google Voice Search bombs (signal 4 - illegal instruction - currently suspecting the native packages might have some NEON instructions that the atrix cpu doesnt support)
- Calendar will not sync for google or exchange. App loads, but the sync service is failing
- Lots of null pointer exceptions for the NFC stuff in the log.
Anyway, this is just a build of the code that's out there, nothing special done by me. It might be useful for a dev phone or something but not for use on a real day-to-day device. Obviously it doesn't have the google apps embedded in it.
http://www.multiupload.com/XT9QPPQYF1 thanks xploited for uploading
md5: 670068584eb94bf1d660c0450815ad0d
Personally, I had trouble going back to CM7 afterwards, my clockwordmod backups were screwed up (bad boot.img? cross-linked files on the SD card) and I had a very hard time getting back to the good ole working state. Ultimately, I had to restore the partial backup and then reflash the CM7 image + gapps.
So, if you were curious what building a random repo on the web and installing it on your phone would do, then feel free to try and lose all of your data. There are no updates/support for this, etc. It's just a curiosity... what is the state of this stuff right now?
BTW... I am back on CM7/Atrix now which is AWESOME!!!!
Source Code Links:
https://github.com/CyanogenMod/android
https://github.com/Atrix-Dev-Team/android_device_motorola_olympus
Not sure how the dev team would react to this ..we do not want any bricked phones because of this ..there maybe some experimental dangerous code in there in those sources as of now ..not sure though
Hmm... figured since I spent quite awhile getting a build set up, it might be worth sharing. I am happy to take down if it is inappropriate.
Well I am not the best person to answer that ...but yeah thanks for your work.
Eh, I wouldn't be mad about it, but I think it needs more caution. I would just wait. As you say, it kindof screwed with a lot and wasn't very usable, so why flash it? Maybe ok for someone who wants to look at the code, but I wouldn't flash it.
Awesome news man. Thanks for being a lab rat and giving us an update.
Sent from my MB860 using xda premium
Not so much take it down as change the title of the post.
the current internal atrix-dev-team cm9 is way further ahead of this, we have some different patches. this is missleqading as it makes it sound official and is not.
Could you please change the tittle to [KANG] CM9 Test Build by "your name"
and please link to the sources, as is proper practice for open source projects
thank you
samcripp said:
Not so much take it down as change the title of the post.
the current internal atrix-dev-team cm9 is way further ahead of this, we have some different patches. this is missleqading as it makes it sound official and is not.
Could you please change the tittle to [KANG] CM9 Test Build by "your name"
and please link to the sources, as is proper practice for open source projects
thank you
Click to expand...
Click to collapse
and I guess you guys deserve a Xmas break now ...
It's nice to see that! Thanks for your hard work.
I'm looking forward to the CM9
Thank you for this.
!
Anyways, Just out of curiosity... where can you find the official Atrix Dev team's CM9?
The one been worked on by turl is with him, that is not for public release.
Dont forget to tell him merry xmas!
I always forget what kang means.
Sent from my MB860 using XDA App
wrldsuksgo2mars said:
I tried the latest build of CM7 done by the Atrix Dev Team and it is awesome. Very reliable, fully functional, etc. I figured I'd give a whirl to compiling the real ICS version to see what that was like.
CM9 build system with the appropriate Atrix Dev Team repos in place actually spit out a working ROM. There are a number of issues aside from the general preview state of CM9. I figured I would share them in case anyone else was as curious as me. Apparently, the internal atrix dev teams are well beyond these issues already, so kudos.
Probably related to CM/atrix specific stuff
- Camera and finger print sensor don't work
- Launcher crashes pretty often
- Some openGL demos don't seem to work right (or at all)
- No mounting the SD as USB storage
Probably related to the specific gapps package I used.
- Maps crashes after 3 seconds (signal 11 - native code crash)
- Maps wants to update, but it can't (sharedId conflict if you actually remove maps)
- Earth won't run (missing the earthmobile library)
- Google Voice Search bombs (signal 4 - illegal instruction - currently suspecting the native packages might have some NEON instructions that the atrix cpu doesnt support)
- Calendar will not sync for google or exchange. App loads, but the sync service is failing
- Lots of null pointer exceptions for the NFC stuff in the log.
Anyway, this is just a build of the code that's out there, nothing special done by me. It might be useful for a dev phone or something but not for use on a real day-to-day device. Obviously it doesn't have the google apps embedded in it.
http://goo.gl/39NnA
Personally, I had trouble going back to CM7 afterwards, my clockwordmod backups were screwed up (bad boot.img? cross-linked files on the SD card) and I had a very hard time getting back to the good ole working state. Ultimately, I had to restore the partial backup and then reflash the CM7 image + gapps.
So, if you were curious what building a random repo on the web and installing it on your phone would do, then feel free to try and lose all of your data. There are no updates/support for this, etc. It's just a curiosity... what is the state of this stuff right now?
BTW... I am back on CM7/Atrix now which is AWESOME!!!!
Source Code Links:
https://github.com/CyanogenMod/android
https://github.com/Atrix-Dev-Team/android_device_motorola_olympus
Click to expand...
Click to collapse
Thinks for your works,
Come from Chinese thinks!
i shall say this.. if this is behind where the dev team actually is...things are looking good! and btw.. i believe fruitcaker maker works. installed and is now creating;]
edit: yep. it does.
Thanks man very very good work android congratulations for share work whith comunity
Sent from my MB860 using xda premium
it looks very nice but id needs a bit more work to be a experimental daily driver.
ps: to solve the corrupt backup problem just copy the files to your computer before flashing and copy to your phone before restoring.
good luck!
where can I get google apps for this rom? Tryed gapps for CM7 from CM wiki - fail, setup wizard crashes.
try the one on this link
http://rootzwiki.com/topic/11854-romcm9-encounterics-x-beta-2-with-working-radio-401/
good luck!
---------- Post added at 07:52 AM ---------- Previous post was at 07:47 AM ----------
ilya11g said:
where can I get google apps for this rom? Tryed gapps for CM7 from CM wiki - fail, setup wizard crashes.
Click to expand...
Click to collapse
try the one on this link
http://rootzwiki.com/topic/11854-rom...ing-radio-401/
good luck!
For a preview build it looks pretty nice. Surprisingly stable for what it is. Definitely keeping an eye on this, especially since the code is out there to make DIY kangs with.
samcripp said:
The one been worked on by turl is with him, that is not for public release.
Dont forget to tell him merry xmas!
Click to expand...
Click to collapse
Random SamCripp memory....
"We're rapping them, we're rapping them!!!"
Sorry, guess you had to be there.... aahhh memories... nevermind, sorry for the off topic post.
Thanks though for the effort of getting this ported btw.
This rom is based from zukriaksah's miui 1.12.16. His had a good foundation just some issue. I have made some changes to it and so far things are working (keep in mind that this has not been tested for a little more than 2 days).
Link https://docs.google.com/open?id=0B6a1DYyFKfu1YjI4MDg0YTEtZGExOC00ZGZkLTg4MGEtMmM0Y2ZjYTQwYzlh
(sorry file are on work pc and this is the only way that I can get them up...so if some one can move to a better site for downloading...pls feel free to do so)
you will have issues with wifi on this rom - the work around that I used it to load cacingkalung's modded version of the sd kernel...get it here http://forum.xda-developers.com/showpost.php?p=20326475&postcount=240
had to change the build.prop this phone keep rebooting with some of the files that I had to switch out. I used files from tj and issac.
usb and headphone issues are gone (so far)
added the miui 4-way reboot (hold power button for options)
the fm radio that is in the rom fc's (wish someone can fix this..I am at a loss, I know that it has to be a driver issue but I have no clue which one have been searching for weeks it seems to correct this...I really miss the radio)
added some init.d tweaks...these are found in the various forums here on xda
you might have to load script manager to get them to work (I load this anyways so I dont know if it is needed)
what I added to the init.d:
10cpu - sets the cpu values and govenor
11 iosched - set i/o scheduler
both of these you do not need if you use setcpu or other program like it...I just dont like to have these loaded they take up space and memory.
80netspeed - internet speed hack (helped on mine)
97ks - some kernel mods - helps rom run smoother in my opinion
98kt - internal task killer values
you dont need these you can remove them...play around with the settings you might be able to tweak the rom more to you liking...these are the values that worked best for me
I dont have much of a clue on the battery life yet...have had phone up and down so much that I have not let it go threw my daily pace
So far things seem stable...still no HDMI, dont know if we will ever have this...I am not that good with dev have look at other roms but if the drivers aint right it wont work
I also use force2sd to move the programs to the sdcard to free up the internal memory...everytime that I have tried to include apps2sd thing go wrong..this way works for me so I am not going to worry about it
you will probably get unknown for the carrier...if you know your spn values you can edit it and the name will show up...there are progams in the market that will fix it...other have had luck with out needing a program...In the miui forums they have miui extra setting and they say that you can use it to change the carrier name (never tried)
make sure that you do a system wipe before installing....I dont know what issue you will get if you dont
**latest update**
http://forum.xda-developers.com/showpost.php?p=20803286&postcount=35
Thanks for helping me
Sent from my CSL-MI410 using xda premium
zukriaksah said:
Thanks for helping me
Sent from my CSL-MI410 using xda premium
Click to expand...
Click to collapse
zukriaksah, not a problem, hopefully we can get hdmi and fm working
can someone post the austrie kernel in a seprate thread so everyone can see it with wifi module of course
cowsgo said:
zukriaksah, not a problem, hopefully we can get hdmi and fm working
Click to expand...
Click to collapse
FM Radio Not Work Open FC
preyesh1 said:
can someone post the austrie kernel in a seprate thread so everyone can see it with wifi module of course
Click to expand...
Click to collapse
preyesh,
Here you go:
http://forum.xda-developers.com/showthread.php?t=1407689
mibsut said:
FM Radio Not Work Open FC
Click to expand...
Click to collapse
Please read carefully... As they say, they are trying their best to make the hdmi and fm working... please be patient and hope they can overcome the problem. And to be honest, its not an easy task... So, just wait and give the developers some time to fix it.
preyesh1 said:
can someone post the austrie kernel in a seprate thread so everyone can see it with wifi module of course
Click to expand...
Click to collapse
what is that kernel? for miui? if yes for which version?
---------- Post added at 10:48 PM ---------- Previous post was at 10:42 PM ----------
ohh got it ... the SD kernel
anyone who tries the kernel please update on battery backup
cowsgo said:
This rom is based from zukriaksah's miui 1.12.16. His had a good foundation just some issue. I have made some changes to it and so far things are working (keep in mind that this has not been tested for a little more than 2 days).
Link https://docs.google.com/open?id=0B6a1DYyFKfu1YjI4MDg0YTEtZGExOC00ZGZkLTg4MGEtMmM0Y2ZjYTQwYzlh
(sorry file are on work pc and this is the only way that I can get them up...so if some one can move to a better site for downloading...pls feel free to do so)
you will have issues with wifi on this rom - the work around that I used it to load cacingkalung's modded version of the sd kernel...get it here http://forum.xda-developers.com/showpost.php?p=20326475&postcount=240
had to change the build.prop this phone keep rebooting with some of the files that I had to switch out. I used files from tj and issac.
usb and headphone issues are gone (so far)
added the miui 4-way reboot (hold power button for options)
the fm radio that is in the rom fc's (wish someone can fix this..I am at a loss, I know that it has to be a driver issue but I have no clue which one have been searching for weeks it seems to correct this...I really miss the radio)
added some init.d tweaks...these are found in the various forums here on xda
you might have to load script manager to get them to work (I load this anyways so I dont know if it is needed)
what I added to the init.d:
10cpu - sets the cpu values and govenor
11 iosched - set i/o scheduler
both of these you do not need if you use setcpu or other program like it...I just dont like to have these loaded they take up space and memory.
80netspeed - internet speed hack (helped on mine)
97ks - some kernel mods - helps rom run smoother in my opinion
98kt - internal task killer values
you dont need these you can remove them...play around with the settings you might be able to tweak the rom more to you liking...these are the values that worked best for me
I dont have much of a clue on the battery life yet...have had phone up and down so much that I have not let it go threw my daily pace
So far things seem stable...still no HDMI, dont know if we will ever have this...I am not that good with dev have look at other roms but if the drivers aint right it wont work
I also use force2sd to move the programs to the sdcard to free up the internal memory...everytime that I have tried to include apps2sd thing go wrong..this way works for me so I am not going to worry about it
you will probably get unknown for the carrier...if you know your spn values you can edit it and the name will show up...there are progams in the market that will fix it...other have had luck with out needing a program...In the miui forums they have miui extra setting and they say that you can use it to change the carrier name (never tried)
make sure that you do a system wipe before installing....I dont know what issue you will get if you dont
Click to expand...
Click to collapse
thats great.......
but I am not able to download.............. can some one who already downloaded can upload on other site as this download link is not working with me ...
guys, can you make softkey vibrate?
thanx for the build cowsgo!
does the front camera flip-up? last time i used ur build the front camera is working fine, but after flashing cacingkalung's SDKernel it flipped up
hey COWSGO thanks for this.... can you please resolve the headphone and wifi issues for 1.12.2 build.... I really liked that 1.12.2
Perhaps this is the last version we stay on gingerbread. Keep on and go stable.
Sent from my CSL-MI410 using XDA App
To easily download frm google docs, 1st dont use stock browser, use 3rd party, eg. Opera mini, 2nd change yr google docs view to desktop mode
Sent from my CSL-MI410 using xda premium
anyone having problems with bluetooth? i cannot seem to activate it.
mi410 said:
hey COWSGO thanks for this.... can you please resolve the headphone and wifi issues for 1.12.2 build.... I really liked that 1.12.2
Click to expand...
Click to collapse
mi410, I will look at this after the holliday
emt said:
anyone having problems with bluetooth? i cannot seem to activate it.
Click to expand...
Click to collapse
emt,
I will look at the files and see what I missed for the bluetooth. Sorry I dont use it so I didnt test it.
hey COWSGO..... really thanks for the this beautiful ROM.
quite smooth ...... experience .....
really happy with the ROM.
next time when you update the ROM with Bluetooth wish following update also ....
1. Camera if possible (Front)
2. Time should be at center of status bar like what you did with 1.12.2
3. FM if you able to repair ....
enjoy your holidays .....
Dont know if anybody has gps issues or proximity issues....I did....this is what I did to solve this
use root explorer goto system\lib\hw and rename two files to .old
the files are gps.fb0.so and sensors.fb0.so
then goto settings click programs and goto call settings and turn off enforce proximity (what ever the option is under use proximity sensor
reboot....after I did this the sensor works with incoming and outgoing calls and the gps locks in under 30 seconds. used gps status from the market to confirm...dont for get the you might have to edit the gps.conf file in system\etc (I think)...if you didnt edit this file after you loaded the rom then it will be set for north-america.
dont know why this worked....has to be a issue in the files...when I get more time I am going to decompile them to see what is different