Database Info

[PORT][3.22.x EBI1/32A]Cyanogenmod 5.0.8/6.1.0 DS EBI1/32A Port [December 8]

***I have recently switched to the Nexus One but I will continue to do these Magic ports as long as there is a desire (and I have time).***
This is a thread for the port files required to use the 32B Cyanogenmod ROM on 32a/EBI1 phones. Please see the following link for details on the ROM:
http://forum.xda-developers.com/showthread.php?t=567610
Note: Rogers users - if you find yourself without data upon flashing this ROM, use the settings found here to restore your APN.
Credit Radix for the following instructions - they are copy/pasted from his thread. Also thanks to all of devs who have contributed to the ROM scene - impossible to mention all of you, specifically Amon_RA, stericson, prash, cyanogen, riku, Radix, koush, TigerTael, haykuro, pershoot, zinx and more I am forgetting I am sure.
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
***Please note that the following steps require that you have a recovery with the option to flash any .zip file. I recommend Amon_RAs recovery, Clockwork Recovery, or ROM Manager
***
NOTE: All new ports will be based on Koush's Universal update.zip. This lets you flash just a kernel and matching libs to a phone without the need for a ramdisk. Basically, it takes the ramdisk currently installed and repacks with it the new kernel.
Basically, the port packages provided from now on will port ANY ROM from 32B --> 32A/EBI1.
CM5.x (Eclair base)
Upgrade from 4.2.x Cyanogenmod ROM
http://wiki.cyanogenmod.com/index.p...or_other_rooted_ROMS_to_5.0.x(Dream/Sapphire))
Gapps Mirror: http://briancrook.ca/android/gapps/gapps-ds-ERE36B-signed.zip
CM4.2.x (Donut Base)
NEW INSTALL (ie. never installed CM 4.1.99 or greater before):
Magic Users
Rogers Dream EBI1 Users
UPGRADE INSTALL (ie. already installed 4.1.99 or greater):
Cyanogenmod Wiki
ROM Manager
1. Download ROM Manager from the market
2. Flash the ClockWork Recovery
3. Go to Download ROM > CyanogenMOD > Choose the version you want to flash.
4. Select Gapps addon (if you want Google Apps)
5. This will reboot to recovery, make a backup if requested, flash all the components and reboot.
6. Win.
Theme Support
Themes CAN be applied overtop of this ROM/Port combo. Just make sure to reboot in between the Defanged Base/update-cm-/port file step and pick a theme that corresponds to the Cyanogenmod version you are running. Keep in mind that some themes include a boot.img (no idea why...), so just keep an eye out. If you apply a theme with a 32B boot.img, just reapply the port file afterwards. If you apply a theme with a 32B boot.img, the phone will not boot past your carrier lockscreen...you can easily restart and reflash the port file. Always backup before flashing anything!!
==================================================================================================
If you would like to donate, please use the following link. Any donations are greatly appreciated
==================================================================================================
Port Files:
CM-6.1.0
Download: http://briancrook.ca/android/cm-ports/bc-6.1.0-ebi1-signed.zip
md5sum
CM-6.1.0-RC1
Download: http://briancrook.ca/android/cm-ports/bc-6.1.0-RC1-ebi1-signed.zip
md5sum
ROM Manager Web Connect
For older -test versions of ports, go to: www.briancrook.ca/android/cm-ports/old
CM-6.0.0-RC1
Download: http://briancrook.ca/android/cm-ports/bc-6.0.0-RC1-ebi1-signed.zip
md5sum
For older -test versions of ports, go to: www.briancrook.ca/android/cm-ports/old
==============================================================================
CM-5.0.8
Download: http://briancrook.ca/android/cm-ports/bc-5.0.8-ebi1-signed.zip
md5sum
For older -test versions of ports, go to: www.briancrook.ca/android/cm-ports/old
==============================================================================
CM-4.2.15.1
Download: http://briancrook.ca/android/cm-ports/bc-4.2.15.1-ebi1-signed.zip
md5sum
Iptables was left out by mistake. Tether issues should be gone.
For other port versions, go to: www.briancrook.ca/android/cm-ports/old

Thank you

cheer

Worked great, thanks a ton!

Does anyone else have signal problems with this rom?
I have had lost signal, many many times today

bunny0007 said:
Does anyone else have signal problems with this rom?
I have had lost signal, many many times today
Click to expand...
Click to collapse
no problem
very nice！

i like this rom, but now i cant have Google navigation

elite_is3 said:
i like this rom, but now i cant have Google navigation
Click to expand...
Click to collapse
did you have it before you did the new rom? i had to go to a like 4.2.4 or 4.2.3.1 and then download the gmaps off the market and then took it back to the 4.2.5. I havent did the 4.2.6

can this be installed using the one click method from the unlockr.com
i have the amon ra recovery
also im on a perfect spl - do i need to change that- rookie questions i know-

Anyone else not able to access the dialer while in a phone call... or is just me?
1.33.2005
3.22.20.17

KeeganX said:
Anyone else not able to access the dialer while in a phone call... or is just me?
1.33.2005
3.22.20.17
Click to expand...
Click to collapse
Do you mean the dialpad, that you drag up while on a call? it works for me.

KeeganX said:
Anyone else not able to access the dialer while in a phone call... or is just me?
1.33.2005
3.22.20.17
Click to expand...
Click to collapse
I can access it just fine. Have you tried doing a wipe?

Moving the bug I'm having from another thread to this new one, here it is:
Can somebody confirm if this is just my problem or a ROM bug?
Steps to reproduce:
1) While listening to music using bluetooth
2) Answer an incoming call
3) use the bluetooth headset to pickup phone call
4) Cannot hear any audio nor can the caller hear you talk
I loaded back an android 2.0 rom (jd02 with x3rom 32A patch) and can confirm this is NOT a problem.
I also tried loading back 4.2.5 cyanogen and its a problem there as well.
Anybody can verify with there ROM or have a clue whats going on?

httpftp123 said:
Moving the bug I'm having from another thread to this new one, here it is:
Can somebody confirm if this is just my problem or a ROM bug?
Steps to reproduce:
1) While listening to music using bluetooth
2) Answer an incoming call
3) use the bluetooth headset to pickup phone call
4) Cannot hear any audio nor can the caller hear you talk
I loaded back an android 2.0 rom (jd02 with x3rom 32A patch) and can confirm this is NOT a problem.
I also tried loading back 4.2.5 cyanogen and its a problem there as well.
Anybody can verify with there ROM or have a clue whats going on?
Click to expand...
Click to collapse
I cant confirm, I dont have the proper bluetooth stuff. have you checked the cyanogen bugtracker?

I have a few issues after updating from 4.2.5 without wiping.
1. GPS kept losing signal during navigation.
2. Lost three 888 xxxxxxx call receptions today.
3. My wife complained she heard horrible static noises each time when I changed locations. For example, when I moved from outside to inside my building or I stepped out of my truck.
4. I couldn't listen to my voicemail through GV. FC every time.
The rest work great. The rebooting time is super fast.
Thank you so much, guys.

httpftp123 said:
Moving the bug I'm having from another thread to this new one, here it is:
Can somebody confirm if this is just my problem or a ROM bug?
Steps to reproduce:
1) While listening to music using bluetooth
2) Answer an incoming call
3) use the bluetooth headset to pickup phone call
4) Cannot hear any audio nor can the caller hear you talk
I loaded back an android 2.0 rom (jd02 with x3rom 32A patch) and can confirm this is NOT a problem.
I also tried loading back 4.2.5 cyanogen and its a problem there as well.
Anybody can verify with there ROM or have a clue whats going on?
Click to expand...
Click to collapse
I believe I suffer from this issue as well, or at least something related. This was also happening on 4.2.5, but was perfect on my previous ROM, MyHero.
In my case I use a mini USB Y-Splitter adapter in the car: one end goes to the mini-USB cigarette lighter charger, the other to a 3.5mm jack for the AUX-IN in my car stereo. This way I can listen to Pandora or whatever over the stereo. If I answer a call in this setup the other party cannot hear me. Similarly I cannot speak any Google searches, or use Shazam, or anything that requires my microphone to work. I was hoping this release would fix it. Evidently not.
As stated, worked great with MyHero. *sigh*
No one else could confirm this as an issue before, so I thought I was alone... maybe still am...

Newbie here
I'm confused as to what the differences are between the kernel port files and why it matters which one you choose?
Thanks

httpftp123 said:
Moving the bug I'm having from another thread to this new one, here it is:
Can somebody confirm if this is just my problem or a ROM bug?
Steps to reproduce:
1) While listening to music using bluetooth
2) Answer an incoming call
3) use the bluetooth headset to pickup phone call
4) Cannot hear any audio nor can the caller hear you talk
I loaded back an android 2.0 rom (jd02 with x3rom 32A patch) and can confirm this is NOT a problem.
I also tried loading back 4.2.5 cyanogen and its a problem there as well.
Anybody can verify with there ROM or have a clue whats going on?
Click to expand...
Click to collapse
I listen to music in my car audio which is connected to my phone via BT (music from my phone). When someone calls i just pick up call and talk through built in car system. After the call, music just continues playing.

sleepymatt said:
Newbie here
I'm confused as to what the differences are between the kernel port files and why it matters which one you choose?
Thanks
Click to expand...
Click to collapse
they 'adapt' to the roms for which they are written, allowing 32a owners to flash 32b roms on their devices.
you dont really have a choice on which port file to install. there is only one (generally) for each version of a rom.

sleepymatt said:
Newbie here
I'm confused as to what the differences are between the kernel port files and why it matters which one you choose?
Thanks
Click to expand...
Click to collapse
Pick the one that corresponds to the version of CM you are running. Assuming you want to use the newest cm (version 4.2.6), use the 4.2.6 port file

[ROM][V0.51][01-nov-2010] HTC 2.1 Senseui Mod for Milestone

(99% DISCONTINUED)​
See MotoIncred/MotoFroyoSense for new versions​
MotoSense, an adaption of the HTC 2.1 SenseUI(version 1.6) from HTC Desire
Image is only compatible with this a milestone A853 , and cannot be installed on other variants of "Milestone" XT720/A854/A855 branded models (yet).
You can also follow updates on Twitter now: Dexter Picard (DexterPicard) on Twitter or
me a Red bull, and you're sure i stay up working on this mod.
LATEST RELOAD PATCH for MotoSense MotoSense v0.51 patch
Old releases :
LATEST FULL MotoSense DOWNLOAD MotoSenseV05
MotoSenseV03​
a image folder goes into /nandroid/adbrecovery on your SDCARD its required to have OpenRecovery on your phone to install this image.[/COLOR]​LATEST PATCH FOR DOWNLOAD
MotoSense v0.51 patch (see top of post)
WIPE YOUR PHONE BEFORE ANY FULL IMAGE IS INSTALLED! (Recovery menu - factory reset)
If you don't you might get constant reboots with the M logo
INSTALLATION:
Use G.O.T Recovery / Open Recovery to install this rom.
Currently require you to install a 2.36 stock rom, before you install this one.
Radio Band Requirements for different countries
Some countries require the original 3G files of your current ROM to work ie.
Canada, Brazil, Venezuela, Germany and some others countries uses a different band for 3G. If u dont backup the 4 original 3G Files and restore it over this nandroid once installed u gonna have poor signal, sms problems and HSDPA loss (even if u set apn and get conection its gonna be crappy one).
Files should be in the /system/etc/motorola/bp_nvm_default/ of your phone.
This can be done using OpenRecovery and a adb shell.
You might check this thread , if a update-nosign.zip file exists for your model. which makes it easier for you to install.
Filenames are:
File_Audio
File_Audio2
File_GSM
File_Seem_Flex_Tables
generic_pds_init​​
STATUS of the functionality in image
Working​Radio (Calls,GPRS,HSPA)
USB
Milestone bootup AC charging
Wireless
Bluetooth (limited but works, only with a few functions)​Not Working​- PINCODE (will not be able to enter any pincode or boot normal)​
Changelog history
v0.51 1-november-2010
- Finally beat the reload issue with SenseUI, it should work alot better now​
v0.5 12 august 2010
- Corrected WorldClock bottom slider icons
- update HTC Camera to support more resolutions and moto recording.
- Changed Motorola VideoCamera & VideoRecorder to work with HTC framework for optimal use of Moto Camera.
Changed Moto Gallery for proper playback of your recordings.
- SDCard is now always "on", so you will notice status is "0 bytes" when you connect to pc. No conflict with wifi anymore.
- Apps2SD support, EXT2 supported.
Use G.O.T recovery or other application to partition your SDCARD Partition no. 2 should be EXT2 formatted
(G.O.T will do this automatically)
- Apps2SD remaining space can be seen in settings -> SD & Phone storage. Look under "Internal Phone storage" which is your EXT2 partition.
- optimized internal storage space. Most apps are now in /system. leaving your with 171MB free internal storage on your milestone.
- WIPE is 100% supported but you loose the following apps, if you do.
(Dock , GreekIME , Maps , MotoCarDock , PersonalPortal , VSuiteApp , QuickOffice , teeter )​NOT SOLVED
- Reloading of Rosie (HTC Launcer)
Reason for not fixing it is that Motorola Milestone simply do not have enough memory for HTC SenseUI to run stable with only 256MB.
the launcher is very memory hungry for all its plugins and graphics.. so sorry, no fix, unless you add 256MB more memory to your phone.
- Bluetooth headset​
v0.42 29 july 2010 (MotoSensev042-update-nosign.zip - attached to this post at the bottom) (type: nosign-update.zip)
build.prop correction (hopefully solves too many sense restarts)​Keyboard light enabled​HTC Camera fix (5M pixel)​
OLD REVISION DATA DELETED, OBSOLETE and not worth writing anymore
WARNING: Use this image at your own risk and i take no responsibility if
you brick your phone.. Image has been tested on a UK milestone and works fine if all files in ADB recovery image is used.

woah, nice work buddy. just got a question, if i apply this rom to my North American Milestone, do i lose the ability to access 3g/hspa network from rogers?

is gps working

i got one guy on IRC from Canada(im from europe, so im not sure on networks you got overthere), he tried it, and it works fine for him
You should try to only flash the system+data image of it, as the cust.img contains telephone info, which might be what you need to keep.
GPS is not working atm..

im new to the motodroids , will this work on the motorola droid or just the milestone ? ive had the droid eris so im not sure if there is a difference between the droid and milestone, sorry for the dumb question,

tazzpatriot said:
im new to the motodroids , will this work on the motorola droid or just the milestone ? ive had the droid eris so im not sure if there is a difference between the droid and milestone, sorry for the dumb question,
Click to expand...
Click to collapse
there is already a senseui for Droid, look for Zeusdroid they made that image.

Dexter_nlb said:
there is already a senseui for Droid, look for Zeusdroid they made that image.
Click to expand...
Click to collapse
ok ill google it to see if i can find it , it is much easier to find eris roms , ive only had this moto droid for to dayz and im lost lol
edit well i found it but it doesnt look like its very functional , if its the one i found

tazzpatriot said:
edit well i found it but it doesnt look like its very functional , if its the one i found
Click to expand...
Click to collapse
Porting is no easy task, when its not about development, and zeusdroid actually do have some customized wireless driver.
But i managed to use the existings drivers from Milestone..
And im probably not going to do programming to make the port perfect, as that not so easy, although i got some experience.. but none within driver programming.

im really happy with the progress dext3r, this is awesome.
just curious, any ETA for GPS fix?

gemini002 said:
is gps working
Click to expand...
Click to collapse
ive just tried to fix this, and GPS will be working in the next release.
as it works now

Dexter_nlb said:
Porting is no easy task, when its not about development, and zeusdroid actually do have some customized wireless driver.
But i managed to use the existings drivers from Milestone..
And im probably not going to do programming to make the port perfect, as that not so easy, although i got some experience.. but none within driver programming.
Click to expand...
Click to collapse
i know , ive ported some roms for the eris , i understand its not easy to make it all work, trust me im not disrespecting any1

crap need gps gunna wait until next update fak really miss sense ui

if i install this rom what happend to my apps also i have app2sd applied is this gunna be a problem???

Dexter_nlb said:
ive just tried to fix this, and GPS will be working in the next release.
as it works now
Click to expand...
Click to collapse
awesome pls release this on the weekend would love to try it out also if this is htc sense ui does it have flash lite and if it does have flash lite would the 10.1 flash that works for 2.1 roms work with this...

SplitSnake said:
im really happy with the progress dext3r, this is awesome.
just curious, any ETA for GPS fix?
Click to expand...
Click to collapse
if you know your way on a few linux commands,
then you're welcome to make it work yourself.
1 . copy the /system/lib/libgps.so from the original milestone 2.36.0 image.
2. flash motosense image.
3. mount /system
and copy libgps.so into the flashed image into /system/lib
and GPS works after a reboot.. So fixed!
of course all done from adb shell.

gemini002 said:
awesome pls release this on the weekend would love to try it out also if this is htc sense ui does it have flash lite and if it does have flash lite would the 10.1 flash that works for 2.1 roms work with this...
Click to expand...
Click to collapse
10.1 for 2.1 senseui roms are not real, it just looks like 10.1,
but the flashlite already reports that number.
and yes, flashlite works fine. tested on a few flash websites.

I have a Telus Milestone and I will consider trying this ROM at some point.
Just to crosspost from the other thread... in another thread I was told the following. Could be useful for keeping 3G.
DAGr8 said:
cmstlist , there is an easy way to retain your baseband just flash the HK sbf , then , copy paste these files and make sure you set the permissions correctly .
Probably safest to do via adb if you dont make sure you reboot ...
for the 3G baseband Hack/Swistch it 5 files from /system/etc/motorola/bp_nvm_default
File_Audio , File_Audio2 , File_GSM , File_Seem_Flex_Tables , generic_pds_init
Click to expand...
Click to collapse
So perhaps if you want to try Motosense on your Telus Milestone, then you should backup these 5 files (and take note of the permissions) before flashing the nandroid image. Then afterwards if 3G doesn't work on the Motosense image, restore the same 5 files.

Ok I wasn't able to flash only certain parts of the nandroid backup so what I did was make 1) a full nandroid backup of the Thai firmware (leaked from GOT) on my Telus Milestone unlocked for Fido, 2) a partial nandroid backup using the options --backup --nodata --nocache --nosystem
Then 3) I flashed all of the motosense backup. Trying a first boot. Will report on whether my NAM 3G is gone.
All I get after the M boot logo is a black screen, followed by a force close notification for system. Nothing else comes up. Long-press Home and I get no recent applications. Oh wait - spoke to soon! Wow, just got the HTC lock screen. Unlocked and now I have the setup screen. Asks me to insert SIM to place calls as if I don't have one inserted. My only option seems to be to press "Skip". Okay, home screen loading up now after the tutorial.
So yeah it's not seeing any phone service and I get "Unable to start Wi-Fi". I'm going to try a second reboot. This time the Droid eye shows up promptly (BTW this is very odd to see because Milestones don't usually have that animation). The phone boots up considerably faster than on the Motorlola firmware. *This* time, I do see cell service. In fact I just got a text message. Wait it just dropped again.
Trying to search for network operators. None showing. Strange! It does see wifi though this time. As the OP implied, DHCP not coming through. Meanwhile my Fido service just came back... VERY weak. Dropped again. Normally both EDGE and 3G are quite strong at my apartment so it's odd. Is it possible this ROM has weaker RF somehow?
Ok trying to set up the APN. Noticing the keyboard doesn't light up. APN set up but still no service. Reboot #3: Yes, wifi works now. Mobile network still very weak. Briefly connected to mobile data and it was EDGE. Test phone call fades in and out. Maps manages to wifi-geolocate me.
Alright, so I'm obviously having connectivity problems and only getting 2G. Let's try flashing back the partial I took from the Thai firmware. To be continued next post.

Okay! Flashed back my partial backup from Thai 2.1. Rebooting. Droid eye comes up, glares at me a couple times, back to the homescreen. Connects to Fido. Disconnects, connects again. I am still connected via EDGE, not UMTS. I try going to *#*#4636#*#* and selecting WCDMA only - no dice.
Alright well this has been fun. But obviously I need my phone service to work so this ROM is not for me. Despite having dutifully pasted the info up above about the 5 files to backup... I neglected to do so. So it's back to the full nandroid of my Thai firmware. But one thing for sure, Sense is very pretty!
Before doing this, I made one attempt to install Superuser.apk using the app installer, and then to install Root Explorer. Root Explorer was unable to get root. Maybe if I installed Superuser via OpenRecovery it'd be happier.
Okay back to normal. Goodbye for now Sense!

Backup restored successfully. I used Root Explorer to back up the 5 files in question to SD. Then I restored MotoSense one more time, and before even booting it up the first time I applied root from OpenRecovery. This time it booted much faster. (Is there any way the stock ROM can be hacked to boot this fast? Wow.)
Again, wifi fails to start on boot #1; succeeds but no DHCP on boot #2; works on boot #3. Signed into my Google account and installed Root Explorer (previously purchased). This time Superuser pops up like it should and we're in. I entered Airplane mode. I pasted in the 5 backed up files from the Thai firmware to /system/etc/motorola/bp_nvm_default after mounting read/write. Then I made sure to fix the permissions. Rebooted without exiting airplane mode.
After reboot I disabled airplane mode. Hey, FULL SIGNAL BARS! I did it. But now it's telling me unable to start wi-fi. Let me add in the APN next. Done.
YES! The little H pops up. I'm getting 3G data! But as soon as the icon pops up, it drops out again. In any case I know I'm connected to UMTS because my cell tower ID in Maps > More > About is 1957869 which is my local UMTS tower. Test phone call is *much* clearer and signal isn't dropping anymore. One more reboot.
On the next reboot, wifi is back. Upon disabling it, the lovely "H" shows up and then flits down to "3G". Testing in browser... hmm nope. Something still missing, don't know what. One more reboot, trying again. Internet works on wifi, but not on HSPA (even though the 3G/H icon comes up).
Sanity check: Dialed *#*#4636#*#*, Phone information. Run ping test.
Ping IpAddr: Fail: IP addr unreachable
Ping Hostname (www.google.com): Fail: Host unreachable
One more sanity check: Switched to GSM only, verified in Maps>About that it's connected to a 2G cell ID (57322). Full signal bars, good call quality. So swapping the files improved both 2G and 3G voice performance.
Since I had a bit more success with this approach, I'm saving a backup for future reference, and on my rare moments of idle time I'll play with it again. But back to stock for now.

[FIX] Inspire 4G Audio Fix (For use with DesireHD ROMs) !!

DISCLAIMER: It is now 5AM and I've had about 8 hours of sleep over the past 48 hours so I might be imagining things. I'm pretty sure there is a difference in audio quality, but without 2 phones side by side, it's hard to compare
Instructions:
1) Flash any DesireHD ROM, your choice!
2) Flash the attached zip file with CWM (it includes the Inspire 4G kernel)
3) Install the attached PropEditor apk, and run it.
4) Open build.prop using PropEditor and change
Code:
htc.audio.hac.enable=0
to
Code:
htc.audio.hac.enable=1
5) Hit the menu button and save! REBOOT!! win?
Let me know how it goes! I do hope I'm not going crazy
I'll update tomorrow with what exactly I did. Too tired to type it out now, GOODNIGHT.
THE DIFFERENT VERSIONS:
-V2: Better quality than V3, speakerphone microphone does not work
-V3-test: Slightly worse quality than V2, better than no sound fix, speakerphone microphone works 100%
palletguru said:
Went back to audio V2. I can personally attest to the fact that the sound is as good as stock - did a side by side with coworker's non routed inspire.
Click to expand...
Click to collapse
CHANGELOG:
V3-test: Removed extra files, sound quality is around the same (or slightly worse) compared to V2. Speakerphone Mic should work
V2: Removed AIC3254_REG_DualMic_MCLK.csv and AIC3254_REG_DualMic.csv as suggested by BelacNongaw to fix mic

Testing her now, thanks!!
Btw, which DHD Roms have you tested using this fix?
I'll report back after testing it (Core Droid DHD)

r34p3rex said:
DISCLAIMER: It is now 5AM and I've had about 8 hours of sleep over the past 48 hours so I might be imagining things. I'm pretty sure there is a difference in audio quality, but without 2 phones side by side, it's hard to compare
Instructions:
1) Flash any DesireHD ROM, your choice!
2) Flash the attached zip file with CWM (it includes the Inspire 4G kernel)
3) Install the attached PropEditor apk, and run it.
4) Open build.prop using PropEditor and change
Code:
htc.audio.hac.enable=0
to
Code:
htc.audio.hac.enable=1
5) Hit the menu button and save! REBOOT!! win?
Let me know how it goes! I do hope I'm not going crazy
I'll update tomorrow with what exactly I did. Too tired to type it out now, GOODNIGHT.
Click to expand...
Click to collapse
Hey whats up man...I know this might be asking a lot is there a way to a make a video about this? But no rush on it bro.. Cause you have been busy with this stuff

Although still not perfect, its 10x better than before with the telus. Unless I forgot the quality of stock which could be possible. But there is definitely a huge difference, to the point that I'm not going back to telus. Good work! Plus, the stock source kernel is being used which is always the best for stability eventhough telus didn't cause any stability problems.
Inspire (rooted)
Leedroid v2.0.0
Telus kernel
AOSP Lockscreen

Exception to my last post, it actually did fix everything! Audio in media player sounds as it should, ringtones sound perfect, etc. This thing is now perfect! Dhd roms, using stock kernel with perfect audio, themes, root access in less than a week! I love xda!
Inspire (rooted)
Leedroid v2.0.0
Stock kernel w/r34p3rex audio fix
AOSP Lockscreen

Could unrooted people use that apk to enable hsupa in the build.prop? I'm curious....
Sent from my Inspire 4G using XDA App

The hsupa category is 6. What would should it be at to enable hsupa?
Inspire (rooted)
Leedroid v2.0.0
Stock kernel w/r34p3rex audio fix
AOSP Lockscreen

No good on other end they can't here anything.
Inspire (rooted)
Leedroid v2.0.0
Stock kernel w/r34p3rex audio fix
AOSP Lockscreen

davwman said:
The hsupa category is 6. What would should it be at to enable hsupa?
Inspire (rooted)
Leedroid v2.0.0
Stock kernel w/r34p3rex audio fix
AOSP Lockscreen
Click to expand...
Click to collapse
Well I'd have to compare the stock build.prop to the DHD one that people have installed, but there are these values in the DHD one:
ro.ril.enable.dtm = 1
ro.ril.gprsclass = 12
ro.ril.hsdpa.category = 10
ro.ril.hsupa.category = 6
ro.ril.hsxpa = 3
Guessing one of those is changed in the stock. Will check later
EDIT: Just pulled the build.prop off my unrooted phone and they look the same... odd

failed to remount system rw
I keep getting an error when trying to save build.prop after editing. "failed to remount system rw". I tried creating a backup and editing that then restoring it but got the same error. Am I missing something simple?...lol...thanks

I've been working on this too. Remove AIC3254_REG_DualMic_MCLK.csv and AIC3254_REG_DualMic.csv from /system/etc/ in the zip and this will work without breaking the mic. Good job.

BelacNongaw said:
I've been working on this too. Remove AIC3254_REG_DualMic_MCLK.csv and AIC3254_REG_DualMic.csv from /system/etc/ in the zip and this will work without breaking the mic. Good job.
Click to expand...
Click to collapse
You guys are great!
Inspire (rooted)
Leedroid v2.0.0
Stock kernel w/r34p3rex audio fix
AOSP Lockscreen

wildace408 said:
I keep getting an error when trying to save build.prop after editing. "failed to remount system rw". I tried creating a backup and editing that then restoring it but got the same error. Am I missing something simple?...lol...thanks
Click to expand...
Click to collapse
Another way to edit build.prop is
Reboot into recovery
Under mounts and partitions mount system
On the computer:
adb pull /system/build.prop
Edit build.prop
adb push build.prop /system/build.prop

Yay sounds great with my HD2 !!

davwman said:
You guys are great!
Inspire (rooted)
Leedroid v2.0.0
Stock kernel w/r34p3rex audio fix
AOSP Lockscreen
Click to expand...
Click to collapse
does the sound now work on both ends? can you hear who you are talking to and can they hear you?

If the OP removes the two files from the zip that I mentioned in my post, yes. Until then, you can browse the zip with astro on the phone and delete them yourself before flashing.

so do I need to remove those two files from the zip? Im just about to flash a new rom and this kernel and then edit.

aNdroidnut said:
so do I need to remove those two files from the zip? Im just about to flash a new rom and this kernel and then edit.
Click to expand...
Click to collapse
Yes, or you won't have a working mic.

did i do it wrong?
I'm unable to save, so i save it to sdcard then move the file to /system
I did not remove anything.
I leave myself a voicemail, I can hear myself just fine!

netnerd said:
did i do it wrong?
I'm unable to save, so i save it to sdcard then move the file to /system
I did not remove anything.
I leave myself a voicemail, I can hear myself just fine!
Click to expand...
Click to collapse
Remove the two files as mentioned and follow the steps posted by the OP.

Working high upload/download speeds fix

Ok so i have been reading forum after forum after forum on how to make the data speed on the inspire 4g......well actually like 4g speeds.....i have found a working method that is working here in spokane, washington...where i do not have 4g but rather 3g....i have been playing and have found a consistent way to get better download/upload speeds that rival t-mobile 4g.....the first thing is you back up your build.prop ( just in case you need it) i use android commander to manage my files, then you delete the old one and replace it with the one i have posted, then you also go to system/lib and you backup the libhtc_lib.so and replace it with the one i posted...then reboot and then test......if you get good results post and let me know (and thank me if you want), if you don't post and let me know so i can play around a little more....i have posted screenshots for the people who are skeptical for you they display the speeds that im getting ant the speeds i was getting...good luck to you all.....
EDIT: This is the build prop from inspire saga 1.1.....DO NOT JUST COPY OVER AS I SAID....I WAS WRONG...OPEN THE BUILD.PROP IN WORDPAD AND THEN COPY OVER THE LINES THAT ARE MISSING FROM YOUR BUILD.PROP....SORRY FOR NOT KNOWING THIS TELL NOW......THANKS FOR THE HEADS UP GUYS.......

What ROM is this from?
Has anyone tried this? What are your results?

the rom is inspire saga 1.1...and i am hoping someone else tries this as well....but no one really looks in the general section anymore.....

itzsnookums said:
the rom is inspire saga 1.1...and i am hoping someone else tries this as well....but no one really looks in the general section anymore.....
Click to expand...
Click to collapse
I just flashed the ROM thats in my sig. Gonna see if this update fixes my crappy data speeds.
If I was still on saga 1.1, I would've definitely tried this. My speeds are really terrible lately and I don't know if its my area or some settings within the ROM.

ok that works...but you should open up the build prop i posted and there are a couple lines that are added and you should add them to yours as well...i have seen a difference from doing so....good luck let me know how it goes.......

itzsnookums said:
ok that works...but you should open up the build prop i posted and there are a couple lines that are added and you should add them to yours as well...i have seen a difference from doing so....good luck let me know how it goes.......
Click to expand...
Click to collapse
Not near my phone right now. Which lines are you referring to? Is it the one with the MTU setting? Or your build.prop doesnt have that.

WARNING - PLEASE READ
OP, I know you've got good intentions but threads like this are a can of worms waiting to be opened. You need to put a warning in your first post that states this build.prop is only for Inspire Saga 1.1. You can't move this file between different ROMs without risk. If you've got the wrong .prop file for your ROM it might cause your phone to go into a continuous reboot loop, or other problems. There are several settings in this file that are specific to the ROM it came from. This build.prop comes from a Sense/Gingerbread ROM, and may not work in a Froyo or non-Sense ROM.
Also, this file changes other things that many users might not appreciate. For example:
persist.sys.shutdown.mode = hibernate
This will cause your phone to never shutdown all the way when selecting shutdown, it will only hibernate. This can interfere with one method of getting into recovery mode, since the phone has to be all the way off when you press the power button & volume minus button at the same time.

henrybravo said:
WARNING - PLEASE READ
OP, I know you've got good intentions but threads like this are a can of worms waiting to be opened. You need to put a warning in your first post that states this build.prop is only for Inspire Saga 1.1. You can't move this file between different ROMs without risk. If you've got the wrong .prop file for your ROM it might cause your phone to go into a continuous reboot loop, or other problems. There are several settings in this file that are specific to the ROM it came from.
For example, let's look at this line is in your build.prop:
ro.build.fingerprint=cingular_us/htc_ace/ace/ace:2.2.1/FRG83D/318736:user/release-keys
The part I highlighted in red is the version of Froyo. Now what do you think will happen if this .prop file is applied to a Gingerbread ROM (version 2.3.3)
Also, this file changes other things that many users might not appreciate. For example:
persist.sys.shutdown.mode = hibernate
This will cause your phone to never shutdown all the way when selecting shutdown, it will only hibernate. This interferes with easily getting into recovery mode since the phone has to be all the way off when you press the power button & volume minus button at the same time.
Last but not least, your build.prop file is from a Sense/Froyo ROM, and there are my non-Sense/Gingerbread ROMs out there.
Click to expand...
Click to collapse
I agree, ROM version and more details on what changes are done, would be very helpful.
I had to "dissect" the build.prop using my mac to see what ROM this is from. I'm also sure the OP had good intensions.
EDIT: Once you open the build.prop up in textedit or notepad, you can see what ROM this is from.. ro.product.version=Inspired Saga v1.1.1

your right and im sorry.....didn't mean any harm...and actually didn't know that it was rom specific.....you always learn new things everyday...thanks guys....

itzsnookums said:
your right and im sorry.....didn't mean any harm...and actually didn't know that it was rom specific.....you always learn new things everyday...thanks guys....
Click to expand...
Click to collapse
No worries...thanks for updating the OP.

hey henry...im not running froyo on my phone...i have ginger sense??????

I hit those speeds already and am on cm7. It depends entirely on where I am located. A difference just two miles means a drop from over 4 down to 1.5 down. Upload stays above 1. This is in the booming metro of Athens, GA.

itzsnookums said:
hey henry...im not running froyo on my phone...i have ginger sense??????
Click to expand...
Click to collapse
Sorry I thought Saga was a Froyo ROM. Yes you've got a Gingerbread/Sense ROM. I've updated my previous post. Same warning still applies though.

[Kernel] Dragon-G2x v1.1.1 (OTA/Weapon) [9/2/2011]

First off, big thanks to Faux123. This is based on his repo with a few tweaks of my own. I'll be adding more as we go on. And of course, he's welcome to pull any patches he likes from my github.
Changes:
Added zram compressed swap support. I'll attach a script to turn it on and one to see what its status is. It's not like the older ramzswap that requires a special tool, everything is done through sysfs now. Very nice.
Added zcache compressed cache. This is a bigger win IMO, it compresses any compressible data in the cache. This means you can keep much more data in cache, which means you have to read it in from slow flash much less often.
Tweaked the low memory killer to take swap space into account, but only some of it.... This prevents swap thrashing while the system tries to kill processes and free up ram/swap. I also suggest using something like AutoKiller to set the levels to the best performance for your workload. We all run different apps and such, and that can affect how these things work for each user. There is no setup that is going to be perfect for 100% of users. Speaking of AutoKiller, I have found the advanced tweaks to help a fair bit as well. Don't use the memory management one, it overides your settings for things like swappyness. And the IO Scheduler doesn't do anything as we aren't using cfq. Unless you turn on cfq...
On Swap and compression:
While badly configured swap can slow things down, it's far more complex than people think. It also frees up RAM that's not being used frequently for apps that are. So your system can more efficiently use the resources it has. While compression does use some CPU time, our dual core 1Ghz+ CPUs can compress/decompress REALLY fast. Far faster than reading from the flash storage. In theory, this can affect battery life, though I haven't seen any significant issues from it.
Q: But we have 512M, that's a LOT!
A: Well, kind of... Not all of it is accessible to the kernel for running apps. 128M for the GPU, some for the cameras, wifi, etc... In the end, a little less than 400M is available. Then you have to add in system overhead from the kernel itself, Android's OS processes, etc.. That is quite limiting, IMO, so using it more efficiently is important to me.
Q: I don't like compression/swap.
A: Then don't run this kernel.
Download (OTA) v1.1: http://goo.gl/2dCK8
Scripts: http://goo.gl/M4SzG
Code:
OTA Changelog:
v1.1.1:
* Fixed Haptic Vibration
* Fixed some config settings
v1.1:
* Updates from faux123 to fix LG crap code
* Increase voltages and enable 1.5GHz
v1.0.3:
* Added low memory killer changes back in.
* Fixed Haptic Vibration
v1.0.2:
* Correct mis-applied zcache patch.

Does this kernel rebuild cache every boot like faux 1.3?
Sent from my MeGaBoT Transformer!

Haptic feedback doesn't work. Faux had the same problem in one of his earlier kernels bbut he fixed it .
Sent from my LG-P999 using XDA App

KingDavid63 said:
Does this kernel rebuild cache every boot like faux 1.3?
Sent from my MeGaBoT Transformer!
Click to expand...
Click to collapse
Yes. I've poked around, but haven't figured out why. It's certainly nothing I'm intentionally doing. I tried using the same initrd from the Weapon stock kernel, no joy. That's about the only thing the kernel should be able to change that would make a difference.

C-4Nati said:
Haptic feedback doesn't work. Faux had the same problem in one of his earlier kernels bbut he fixed it .
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
I'll test it again, but I know it was working at one point.
EDIT: Argh.. yeah, config got messed up. Compiling now.
OK. 1.1.1 is up, tested on my phone with working vibrate.

Data missing
Hey ttabbal, maybe you can help me a little bit with the issue im having with cyanogenmod based roms,
I've been trying to know a bit more bout RILs and ended up learning that it resides at the kernel. My objetive of learning about it is because no matter I do i cant have data conection on any CM7 based ROM but I DO have data on any Froyo / Gingerbread OTA rom, even tryed to change basebands, change sim card, push the apps related to the telephony from GB OTA to Cyanogen and replace Ril Libs also. Nothing had worked. And this is where you can help me a little: while using your kernel I have the exact same issue! No data whatsoever! No matter what ROM I use, in the other hand using Faux's kernel i got no issue, and bec you based yours in his work im sure you know what exactly changed between them and enlight me or make me understang what can I possibly do to fix my issue.
Thanks!
BTW I live in Guatemala CA, using a data plan from CLARO (America Movil) carrier
Look here at the Wikipedia Link to look at the baseband Im using.

albertorodast2007 said:
Hey ttabbal, maybe you can help me a little bit with the issue im having with cyanogenmod based roms,
I've been trying to know a bit more bout RILs and ended up learning that it resides at the kernel. My objetive of learning about it is because no matter I do i cant have data conection on any CM7 based ROM but I DO have data on any Froyo / Gingerbread OTA rom, even tryed to change basebands, change sim card, push the apps related to the telephony from GB OTA to Cyanogen and replace Ril Libs also. Nothing had worked. And this is where you can help me a little: while using your kernel I have the exact same issue! No data whatsoever! No matter what ROM I use, in the other hand using Faux's kernel i got no issue, and bec you based yours in his work im sure you know what exactly changed between them and enlight me or make me understang what can I possibly do to fix my issue.
Thanks!
BTW I live in Guatemala CA, using a data plan from CLARO (America Movil) carrier
Look here at the Wikipedia Link to look at the baseband Im using.
Click to expand...
Click to collapse
I'm happy to share any information I can. Your issue is interesting as I can't think of any changes that should affect the radio. Most of the radio code isn't in the kernel. It's handled by a daemon called rild. We could try reverting some patches. The first thing to try would be to test all the older versions of the kernel. I'll get links posted for you when I get to a computer. If one of those work, we can look at the differences between them to try and narrow it down.

albertorodast2007 said:
Hey ttabbal, maybe you can help me a little bit with the issue im having with cyanogenmod based roms,
I've been trying to know a bit more bout RILs and ended up learning that it resides at the kernel. My objetive of learning about it is because no matter I do i cant have data conection on any CM7 based ROM but I DO have data on any Froyo / Gingerbread OTA rom, even tryed to change basebands, change sim card, push the apps related to the telephony from GB OTA to Cyanogen and replace Ril Libs also. Nothing had worked. And this is where you can help me a little: while using your kernel I have the exact same issue! No data whatsoever! No matter what ROM I use, in the other hand using Faux's kernel i got no issue, and bec you based yours in his work im sure you know what exactly changed between them and enlight me or make me understang what can I possibly do to fix my issue.
Thanks!
BTW I live in Guatemala CA, using a data plan from CLARO (America Movil) carrier
Look here at the Wikipedia Link to look at the baseband Im using.
Click to expand...
Click to collapse
I'm not so sure the kernel is going to affect your issue much. As ttabbal said it lies in the RILD binary. CM7/Miui has known issues with no data connectivity though it seems to happen pretty random. Have you tried doing a hard reboot? (hold power + vol up approximately 10 seconds) On occasion I have the same issue with no data signal (though cell is just fine). Usually a hard reboot (or two) solves the problem though.

Whitehawkx said:
I'm not so sure the kernel is going to affect your issue much. As ttabbal said it lies in the RILD binary. CM7/Miui has known issues with no data connectivity though it seems to happen pretty random. Have you tried doing a hard reboot? (hold power + vol up approximately 10 seconds) On occasion I have the same issue with no data signal (though cell is just fine). Usually a hard reboot (or two) solves the problem though.
Click to expand...
Click to collapse
Yup, its someting else, i even managed to solve the APN dissapearing issue in other way: install market enabler, change SIM code to anything and ther revert back to defualt an it will show u again your APNs just like if you hard rebooted.
I even tried copying rild (/system/bin) from OTA GB rom to a CM7 rom and flash, and nothing, and why using your rom and faux's kernel i got data and if using ttabbal's one i have none? has to do something with the kernel! but thanks for ur posts anyways I know ur busy guys

albertorodast2007 said:
Yup, its someting else, i even managed to solve the APN dissapearing issue in other way: install market enabler, change SIM code to anything and ther revert back to defualt an it will show u again your APNs just like if you hard rebooted.
I even tried copying rild (/system/bin) from OTA GB rom to a CM7 rom and flash, and nothing, and why using your rom and faux's kernel i got data and if using ttabbal's one i have none? has to do something with the kernel! but thanks for ur posts anyways I know ur busy guys
Click to expand...
Click to collapse
Your description sounds like the known cm7 apn bug to me. Installing a kernel usually triggers the bug for me as it involves soft reboots. With dragon, do the data workarounds work? Exactly what ROM are you running?

I think im not leaving things clear, my above post was what I did to fix apn dissapearing when i flashed cm7... and even if i hard rebooted (or used the market enabler trick) and apns where restored still couldnt get data to work...
Im usign whitehawk's rom now, but if i pair it with your kernel, the issue i have is not that apn dissapear (like they did in cm7, bec of the known issue) but that I cant get data to connect.
Sent from my LG-P999 using XDA App

albertorodast2007 said:
I think im not leaving things clear, my above post was what I did to fix apn dissapearing when i flashed cm7... and even if i hard rebooted (or used the market enabler trick) and apns where restored still couldnt get data to work...
Im usign whitehawk's rom now, but if i pair it with your kernel, the issue i have is not that apn dissapear (like they did in cm7, bec of the known issue) but that I cant get data to connect.
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
OK, just making sure. Here are the older versions of the kernel. Try them out and see if any resolve the data issue you are seeing.
1.1: http://goo.gl/e913p
1.0.3: http://goo.gl/7QY0a
1.0.2: http://goo.gl/O6PDb
1.0.1: http://goo.gl/OWkG8
1.0: http://goo.gl/gLeFz
I honestly don't expect them to, but if the only change is the kernel, it seems like it could be related. Could you also attach a file with logs when it's trying to connect? Perhaps also with a log when booting from Faux's kernel when it works right?
adb logcat > log.txt
adb logcat -b radio > radio.txt
I might be able to see something in there...
Just to make sure we're on the same page, by Whitehawkx's rom you mean Weapon 2.4? I just noticed your sig says 2.3... I don't see sigs when I'm on my phone, so I missed that before. Have you tried updating to 2.4? It might help... it might not...

ttabbal said:
OK, just making sure. Here are the older versions of the kernel. Try them out and see if any resolve the data issue you are seeing.
1.1: http://goo.gl/e913p
1.0.3: http://goo.gl/7QY0a
1.0.2: http://goo.gl/O6PDb
1.0.1: http://goo.gl/OWkG8
1.0: http://goo.gl/gLeFz
I honestly don't expect them to, but if the only change is the kernel, it seems like it could be related. Could you also attach a file with logs when it's trying to connect? Perhaps also with a log when booting from Faux's kernel when it works right?
adb logcat > log.txt
adb logcat -b radio > radio.txt
I might be able to see something in there...
Just to make sure we're on the same page, by Whitehawkx's rom you mean Weapon 2.4? I just noticed your sig says 2.3... I don't see sigs when I'm on my phone, so I missed that before. Have you tried updating to 2.4? It might help... it might not...
Click to expand...
Click to collapse
hahahaha noob mistake... yeah im on 2.4 just updated my sig, thanks for pointing me that, thanks man! gonna use adb to get u some usefull logcats...
BTW i've seen some interesting updates on the nightly changelog for the p999, gonna try flashing latest nightly and see if something has changed....

Logs
Ok some logs from faux's and yours latest kernels, gonna start trying previous kernels from your links, muchas gracias!
BDW: flashed nightly #124 and still no data for me, i guess its bec im using it outside the states and/or its a SIM unlocked device..

just checking ttabal... did you ever figure out the cache rebuild on every boot thing?

How to use a script?

ILUHA_89 said:
How to use a script?
Click to expand...
Click to collapse
Script Manager from Market its free, or search any other script app...

Crashes on OTA
Used for half a day and had two lock ups using GB OTA. G2X would not come out of stand by. I will retry at a later time. It was nice to be able to use annyconnect vpn.

I cannot get the zswap stats script to run properly...it says syntax error (expecting ")") or some ****...what I'm I not understanding with this

Been running the kernel for about a day, both scripts running with script manager, no freezes or issues yet. Been trying to cause problems like I've had with other kernels, and i'm not getting them.