After trying several combinations with rom, radio, kernel, build and so on i think i finaly found a solution to the problem described in this post:
http://forum.xda-developers.com/showthread.php?t=805002
As posted in thread above the solution to Bad sound and Mic Gain was renaming or deleting the default.acdb. In the later builds this resulted in non responcing error and I personaly feelt that it did something bad with the build/kernel.
When testing out [build][1.12.2010][beta] desire hd2 I suddenly had no mic gaing or high volume in call.
So I copied the default.acdb and htcleo.acdb from that build and pasted them in to my daily build(see signature) in /system/etc/firmware.
The files are attached to this post below. REMEMBER TO BACKUP YOUR OLD FILES FIRST
You have to do a full reboot for the changes to take effect.
Tip: Use "root explorer" from marked and remember to update SU.
And now I have crystal clear sound both ways.
Maybe some of the devs should look into this?
I know many of the members that was using the [build][1.12.2010][beta] desire hd2 has problems with to low sound when using the attached files so they had to replace these files with the files that gave me high mic gain and to high volume.
EDIT 07.12.2010: letama clarifyed somethings. We actually just need to copy in the htcleo.acdb and that will overrule the default.acdb.
I will give these files a try. I recently switched from froyostone v3.1 to MDJ FroYo HD v.4.3. I had froyostone running very sweet. But wanted to give the Desire HD build a chance. I also noticed in HDv4.3 that the over sensitive mic and high volume was back and was actually on xda to look for a new solution.
Was about to mention it in the respective thread till I saw this. I will post back to let you know if it worked for me. Then maybe you can post it on the
MDJ FroYo HD v.4.3 thread for others. BRB
Didn't work on MDJ FroYo HD v.4.3.
thoiroi said:
Didn't work on MDJ FroYo HD v.4.3.
Click to expand...
Click to collapse
Strange.. What file explorer did you use? Try update SU and use root explorer and not ES. (I have had some problems with ES i the past and always use root explorer instead.)
It does work with MDJ v4.3. You have to do a FULL reboot for the changes. However there is no htcleo.acdb file in this version. Strange that it is in one HD desire version but not the other.
Agoattamer said:
It does work with MDJ v4.3. You have to do a FULL reboot for the changes. However there is no htcleo.acdb file in this version. Strange that it is in one HD desire version but not the other.
Click to expand...
Click to collapse
Great. Im going to update post 1 with info on full reboot.
sorry, i have some problems.
when i copied the 2 file in /system/etc/firmware. there were a box "the file is read-only"
i would like to know why this problem appeared...thx
im using root explored.
oyvpet said:
Strange.. What file explorer did you use? Try update SU and use root explorer and not ES. (I have had some problems with ES i the past and always use root explorer instead.)
Click to expand...
Click to collapse
Thanks, i got it work after tried update SU and use root explorer. Now my HD2 ready forget Windows moblie
apple123boy said:
sorry, i have some problems.
when i copied the 2 file in /system/etc/firmware. there were a box "the file is read-only"
i would like to know why this problem appeared...thx
im using root explored.
Click to expand...
Click to collapse
When you are inside the folder /system/etc/firmware, in root explorer you have a white button in top right corner IF that button says: "Mount R/W" touch it ones and it will change to "Mount R/O".
If you still having problems try reboot and update SU. Now you can try pasting the acdb files in that folder.
What do you mean by "Update SU". What does SU stand for. Sorry, for the nooby question.
bteljuice said:
What do you mean by "Update SU". What does SU stand for. Sorry, for the nooby question.
Click to expand...
Click to collapse
No probl. Pretty new to this myself. Just fun to be able to help.
SU is the SuperUser application.
Open SuperUser application and go to settings. Push on the bottom option and it will look for updates.
If that dosnt work i think Im out of suggestions
oyvpet said:
No probl. Pretty new to this myself. Just fun to be able to help.
SU is the SuperUser application.
Open SuperUser application and go to settings. Push on the bottom option and it will look for updates.
If that dosnt work i think Im out of suggestions
Click to expand...
Click to collapse
Thanks man. Just updated SU. Will try out your suggestion.
Thanks again for the fast response and the tip
Hello everibody, it work correctly on Froyo ver. 4.1 Great work, thank you.
i've done!!
thank you for your help...=}
oyvpet said:
After trying several combinations with rom, radio, kernel, build and so on i think i finaly found a solution to the problem described in this post:
http://forum.xda-developers.com/showthread.php?t=805002
As posted i thread above the solution to Bad sound and Mic Gain was renaming or deleting the default.acdb. In the later builds this resulted in non responcing error and I personaly feelt that it did something bad with the build/kernel.
When testing out [build][1.12.2010][beta] desire hd2 I suddenly had no mic gaing or high volume in call.
So I copied the default.acdb and htcleo.acdb from that build and pasted them in to my daily build(see signature) in /system/etc/firmware.
The files are attached this post below. REMEMBER TO BACKUP YOUR OLD FILES FIRST
You have to do a full reboot for the changes to take effect.
Tip: Use "root explorer" from marked and remember to update SU.
And now I have crystal clear sound both ways.
Maybe some of the devs should look into this?
I know many of the members that was using the [build][1.12.2010][beta] desire hd2 has problems with to low sound when using the attached files so they had to replace these files with the files that gave me high mic gain and to high volume.
Click to expand...
Click to collapse
Let me clarify things a bit.
I did the htcleo.acdb file, it was designed specifically for hd2 running android. It only works with a relatively recent evo kernel as there is some changes in the kernel to use it. Most of the kernel floating around are now compatible except the one that are "rmnet" compatible, based on the previous linuxtogo kernel.
The patch I did for kernel is working like this:
1) search for htcleo.acdb, if present, use it with the appropriate modification. It should behave like wince regarding audio/mic.
2) If no htcleo.acdb, search for default.acdb, if present, use it. As it's for native android, it should have louder audio, but also inappropriate mic gain.
3) no acdb, or acdb renamed, it uses values in memory that was previously set by wince. Audio/mic should be fine if your radio and rom are compatible with linux audio driver. If not, you could end up with "robotic" voice or some other problems.
So, if you're using an evo kernel, the best solution should be htcleo.acdb, you can even remove default.acdb.
If you like louder sound, you can use default.acdb, but you will suffer of the mic gain/echo problem.
If you are using a rmnet kernel, rename default.acdb should be your best option, but make sure your radio/rom are compatible.
One last point, a wrong camera/camera libs could crash audio badly up to the point that you'll get robotic/audio problems.
LeTama
Thanks for that explanation!
letama said:
Let me clarify things a bit.
I did the htcleo.acdb file, it was designed specifically for hd2 running android. It only works with a relatively recent evo kernel as there is some changes in the kernel to use it. Most of the kernel floating around are now compatible except the one that are "rmnet" compatible, based on the previous linuxtogo kernel.
The patch I did for kernel is working like this:
1) search for htcleo.acdb, if present, use it with the appropriate modification. It should behave like wince regarding audio/mic.
2) If no htcleo.acdb, search for default.acdb, if present, use it. As it's for native android, it should have louder audio, but also inappropriate mic gain.
3) no acdb, or acdb renamed, it uses values in memory that was previously set by wince. Audio/mic should be fine if your radio and rom are compatible with linux audio driver. If not, you could end up with "robotic" voice or some other problems.
So, if you're using an evo kernel, the best solution should be htcleo.acdb, you can even remove default.acdb.
If you like louder sound, you can use default.acdb, but you will suffer of the mic gain/echo problem.
If you are using a rmnet kernel, rename default.acdb should be your best option, but make sure your radio/rom are compatible.
One last point, a wrong camera/camera libs could crash audio badly up to the point that you'll get robotic/audio problems.
LeTama
Click to expand...
Click to collapse
Thanks for clarifying this. I will update the the thread.
If i understand u right we only need the htcleo.acdb file.
And a question, why do someone need this fix and someone dont?
Thx again.
Sent from my HTC HD2 using XDA App
oyvpet said:
Thanks for clarifying this. I will update the the thread.
If i understand u right we only need the htcleo.acdb file.
Click to expand...
Click to collapse
That's right, for evo Kernel.
oyvpet said:
And a question, why do someone need this fix and someone dont?
Click to expand...
Click to collapse
Two possibilities:
1) some builds already incorporate htcleo.acdb
2) Renaming or deleting default.acdb works like htcleo.acdb if you have the right rom/radio combination.
LeTama
Hi, I am using Android on my hd2 from the last 4 months. I don't have any problems till the last week. But now I am getting different sounds like rain drops in ears while in call which is really unbearable. I could find this thread could help me.
I have this issue on all Desire HD builds I tried. I am currently using motoman's glacier sense. My wm Rom is stock 3.14 Indian version with 2.15.50 radio version.
I tried the work around posted in this thread in the first post, but it doesn't helped me even a little. If this is the situation I can not run Android on my mobile anymore.
Can some one please help me?
Thank you!
Sent from my HTC DesireHD2 using XDA app
shree.cse said:
Hi, I am using Android on my hd2 from the last 4 months. I don't have any problems till the last week. But now I am getting different sounds like rain drops in ears while in call which is really unbearable. I could find this thread could help me.
I have this issue on all Desire HD builds I tried. I am currently using motoman's glacier sense. My wm Rom is stock 3.14 Indian version with 2.15.50 radio version.
I tried the work around posted in this thread in the first post, but it doesn't helped me even a little. If this is the situation I can not run Android on my mobile anymore.
Can some one please help me?
Thank you!
Sent from my HTC DesireHD2 using XDA app
Click to expand...
Click to collapse
I dont think that "drop sound" is fixed by this. You should try searching or make a question post in the Q/A forum. I personally never heard about this before.
Related
UPDATE from 26.10.2010
Darkstone has investigated on this issue and his final patch has been pushed to GIT and is now included in newer kernels.
The new stock-kernel can be found here or here.
Also hastarin has updated his kernel here.
Thanks to Darkstone and all guys who had helped!
-----------------------------------------------------------------
Message before 25.10.2010 (Thread can be closed):
I think we have a solution workaround for the problem with music stuttering.
Edit: Users reported that with this workaround quadrant stalls to appr. 1.000 points (confirmed) and some youtube issues...
For video and youtube-issues you can find an explanation & workaround here.User ChrisM001 gave me the critical hint in this post.
Here is the guide once more:
Reason is the stagefright player. Try disabling it by setting
media.stagefright.enable-player=false in /sytem/build.prop
build.prop can be manipulated by droid explorer.
To be safe I checked the previous FroyoStone Sense - V3.1 build and voila - the parameter was originally set to false.
This explains why the FroyoStone Sense - V3.1 was the only build for me without any music stuttering but also the only one with about 1.000 quadrant scores.
Interestingly the low quadrant score didn't let me feel to have a slow android. User hastarin confirmed my investigations here.
I tried the solution workaround with several builds, i.e.
FroyoStone Sense - V3.2
mattc Leo + Froyo w/Sense 1.8
mdeejay FroYo Sense v.1.1 clean
and it works for me!
It is very important to restart after applying the 'patch'.
Edit: User memin1857 reported another possible workaroud here.
However, the conclusions of success are inconsistent.
Users report that Android isn't booting anymore.
As far as I could not test it yet (have to go to university)
use it at your own risk or better do backup in advanceAll credits go to ChrisM001
I can confirm it works with mdeejay evo sense 1.6
What does stagefright do?
Bloody hell... It worked~! THANKS MATE~
Fixed my mdeejay's HD 3.6~
Could someone explain to me how to open the build.prop file? When I go into Droid Explorer and try to open the file, I get a message that says "Windows can't open this file". Is there something I have to do in Droid Explorer, to open the file and reright it? Thanks.
schoei1 said:
Could someone explain to me how to open the build.prop file? When I go into Droid Explorer and try to open the file, I get a message that says "Windows can't open this file". Is there something I have to do in Droid Explorer, to open the file and reright it? Thanks.
Click to expand...
Click to collapse
First copy the file to your harddisk.
Then open it with an editor (I am using notepad++).
After editing copy it back using droid explorer.
please make this post a sticky!!!!!! I have seen this issue everywhere and in almost all of the roms....... Finally a working solution!!!!!!!!!!!
Many thanks!!!!
Oooo, Thanks..My music working fine now ....
plotzkella said:
First copy the file to your harddisk.
Then open it with an editor (I am using notepad++).
After editing copy it back using droid explorer.
Click to expand...
Click to collapse
Thank you!
thanks so much.i love you..
Awesome, thanks a lot!
Simply fantastic!!!! Thank you!!!!!!
Oh ****, I edited the build.prop with ASTRO but now my Android isn't booting any more, just a black screen! Please does anybody know how to fix this issue?
Wow...thx man!!
Sent from my HTC HD2 using XDA App
Wow, it actually worked.
Tested on:
MDeejay froyo z and hd, mattc1.8, darkstone froyo, and mdeejay evo warm.
Tested with multiple kernels too (hastarin 4.1, 7.4 and 7.5, and michyprima r1 and r2.) (I was just trying to see if I could get it to skip).
Thank you soooooo much
Dude! You ROCK! Thanks so much for the fix! Tried it on Mdeejay's Evo v1.7 and it works! Gonna go thru the other 4 versions on my sdcard and fix them. Thanks A LOT!
Thank you :>
THANK YOU!!!!!
used root explorer (android app) and edited file within android (long press on file).
after reboot - perfect sound!
Android Build: mdeejay evo warm v1.1
anap40 said:
What does stagefright do?
Click to expand...
Click to collapse
Anyone know the answer?
Thanks
iosub said:
Anyone know the answer?
Thanks
Click to expand...
Click to collapse
It fixes mp3-player and slows cpu my bench results in quadrant went back to 1100 (down from 1700), the cpu score is very low
edit: especially decoding time for video / audio in quadrant increased, strange one..
*** This thread is now outdated ***
Please follow this link for a much better solution - Also, be sure to hit the Thanks! button to show your support for DizzyDen's excellent work!
********************************************************************************
I have removed all the files from this post and I encourage everyone to migrate to DizzyDen's superior solution. If for some reason you are unable to use Dizzy's tool you can PM DizzyDen or myself (Martian21) and one of us should be able to get you want you need.
********************************************************************************
[Original Thread]
I have seen several threads regarding this topic and thought I'd try to consolidate as much as I can in one place.
Credit for the original IMEI work goes to mthe0ry His original thread is here.
Because the NOOK Color is not a phone it does not have an IMEI number. This is why some apps that check for an IMEI number do not work on the NOOK.
Thanks to the work of mthe0ry and now DizzyDen it is possible to modify the framework.jar file in order to create a fake IMEI number on the NOOK Color. Doing so will allow programs such as Swype Beta, the free version of the XDA app, HBO GO, and the Xfinity app to work on the NOOK Color.
Unfortunately you need to have a framework.jar file that matches the ROM you are running as changes to the framework between ROMs can (and probably will) cause problems.
[See DizzyDen's thread for the IMEI generator tool]
*** This is mostly obsolete now that Dizzy's tool handles replacing the framework.jar file and backs up your original file - but I will leave it here just in case it is still useful to someone. ***
Installation:
You will need a file manager with Root access such as Root Explorer.
Download the framework.jar file for your Rom.
Unzip the file and transfer the framework.jar file to your NOOK Color.
Navigate to /System/framework using Root Explorer.
Mount the /System/framework folder R/W.
Rename the original framework.jar to framework.jar.bak.
Using Root Explorer, copy the new framwork.jar file.
Paste the modified framework.jar into /System/framework.
Long press the newly copied framework.jar and select "Permissions".
Change the permissions to match framework.jar.bak [rw-r--r--].
Mount the /System/framework folder R/O.
I recommend you reboot your NOOK although resetting the launcher may be enough.
For those that used my original files or the ones from mthe0ry, the original IMEI used in those files is "12-34567-89012-45". If you wish to continue using this IMEI number [NOT RECOMMENDED] you can manually enter it into Dizzy's tool.
Martian21
Request pls
I know that nightly 78 was the last nightly that runs on .29 kernel all the new nightlys 80,82,83 and 84 need uboot 1.2 and .32 kernel. I have read that some people have been experiencing problems on these builts. Also being that .32 kernel is still label beta i would like to ask you if you could please make a framework for nightly 78. I have attached the framework file from my nightly 78. Thank you
Finally was able to reboot after copying framework82. Was able to sign in but have yet to play a movie. I get stuck in the spinning circle.
Sent from my Vision using XDA Premium App
MACLUIS1 said:
Finally was able to reboot after copying framework82. Was able to sign in but have yet to play a movie. I get stuck in the spinning circle.
Sent from my Vision using XDA Premium App
Click to expand...
Click to collapse
I did a total wipe, stock 1.2 install, then a second total wipe before n82. I then added the modded framework and HBO GO worked really well! But, after adding Dal's 5/13 OC, I then got the spinning circle problem you describe.
I tried re-flashing just n83 to fix it (without Dal's OC), and re-installing the modded framework, but the spinning circle problem remains.
I can't say for sure that the OC kernel broke it -- it could be one of a dozen apps I installed? -- but it's certainly the leading culprit in my case. The 5/13 OC kernel also appeared to break a few of my other apps as well (360 Live failed too, but started working again after I returned to vanilla n83).
I'm going to start the entire process over again tonight to try and narrow down the problem...
I have the 5/13 OC installed but HBO GO is now working on my Nook. Just need to uninstall and reinstall HBO GO. Worked like a charm for me.
Sent from my Vision using XDA Premium App
MACLUIS1 said:
I have the 5/13 OC installed but HBO GO is now working on my Nook. Just need to uninstall and reinstall HBO GO. Worked like a charm for me.
Sent from my Vision using XDA Premium App
Click to expand...
Click to collapse
Didn't work for me -- still stuck on spinning circle after intro clip plays.
I used TiBu to wipe data, uninstall, then install app. Did you reboot in between, or take any other steps?
martian21 said:
I am using the same IMEI of "12-34567-89012-45" that mthe0ry used.
Click to expand...
Click to collapse
So every one gets the same IMEI?
We are going to fix this in CM soon. Please don't break every other program that uses IMEI to identify a UNIQUE device! I suggestion that no-one uses this. You are really playing with fire here.
nemith said:
So every one gets the same IMEI?
We are going to fix this in CM soon. Please don't break every other program that uses IMEI to identify a UNIQUE device! I suggestion that no-one uses this. You are really playing with fire here.
Click to expand...
Click to collapse
I do appreciate your warning (and, as always, all your hard work), but Dal came out and stated plainly that an IMEI solution would not get added to cm7 builds, so the rest of us took his word for it and had to solve the problem some other way.
Now, if you're saying that the solution WILL be built into one of the next few nightlies -- with unique IMEI's -- then that's fantastic!!
However, without it, there's currently no other way to run HBO GO, Swype, etc -- unless we compile our own framework.jar... which isn't an option for some of us noobs.
Has work already begun on a better solution?
paleh0rse said:
I do appreciate your warning (and, as always, all your hard work), but Dal came out and stated plainly that an IMEI solution would not get added to cm7 builds, so the rest of us took his word for it and had to solve the problem some other way.
Now, if you're saying that the solution WILL be built into one of the next few nightlies -- with unique IMEI's -- then that's fantastic!!
However, without it, there's currently no other way to run HBO GO, Swype, etc -- unless we compile our own framework.jar... which isn't an option for some of us noobs.
Has work already begun on a better solution?
Click to expand...
Click to collapse
I meant the static IMEI hack as presented in this thread. This hack will not be added to CM7.
We are working on a real solution as we speak.
dalingrin said:
I meant the static IMEI hack as presented in this thread. This hack will not be added to CM7.
We are working on a real solution as we speak.
Click to expand...
Click to collapse
You're a good man, thank you!
dalingrin said:
I meant the static IMEI hack as presented in this thread. This hack will not be added to CM7.
We are working on a real solution as we speak.
Click to expand...
Click to collapse
This is great news!!!
I will cease and desist as soon as it it completed. Obviously the best thing would be for people to follow mthe0ry's instructions and do this themselves (it's really not that hard) using their own unique IMEI number. That said I'm happy to continue the "hack" method for those who don't wish to do it themselves.
Yes, having multiple devices with the same IMEI could become problematic but so far it's worked for the apps people want. I do appreciate the warning as I probably wasn't as clear about the "hack" nature of this in the OP as I should have been.
Martian21
jzibit17 said:
I know that nightly 78 was the last nightly that runs on .29 kernel all the new nightlys 80,82,83 and 84 need uboot 1.2 and .32 kernel. I have read that some people have been experiencing problems on these builts. Also being that .32 kernel is still label beta i would like to ask you if you could please make a framework for nightly 78. I have attached the framework file from my nightly 78. Thank you
Click to expand...
Click to collapse
Attached:
enjoy
slide it
please disregard below. in reading the thread better I can see it's not for swype at all but for setting the nook up with an IMEI.
I don't mean to be rude, but why not just use slide-it? I'm cognisant of the simplicity of swype as I use it daily on my Galaxy S, but slide-it is nearly as good and works without fault on the nook (rooted stock and CM7) without any mods.
smiley1960 said:
please disregard below. in reading the thread better I can see it's not for swype at all but for setting the nook up with an IMEI.
I don't mean to be rude, but why not just use slide-it? I'm cognisant of the simplicity of swype as I use it daily on my Galaxy S, but slide-it is nearly as good and works without fault on the nook (rooted stock and CM7) without any mods.
Click to expand...
Click to collapse
Many of us use this hack for HBO GO, not just Swype...
First zip file is for which Rom?
Sent from my NookColor using Tapatalk
RASTAVIPER said:
First zip file is for which Rom?
Click to expand...
Click to collapse
Opps - Typo. It is for CM7 Stable 7.03
I added a note to the first post. I'll try to fix the file name when I get home tonight. I'm sure there will be 1 or two more nightly builds as well.
paleh0rse said:
Many of us use this hack for HBO GO, not just Swype...
Click to expand...
Click to collapse
It's also needed for a number of Gameloft titles.
Rodney
Concerns about unique devices make me wonder... I have a broken HTC Kaiser sitting on a shelf above my desk. It will never again be a functional device, but yet it has it's own unique IMEI.
Does the IMEI alone tell apps anything about what sort of device belongs to the number? If not, then it seems that I could use the IMEI from that Kaiser or the broken G1 I have.
It doesn't seem like these apps know anything about the device from the IMEI alone, given that people have been implementing this fix with no repercussions. That means apps probably don't check any hypothetical IMEI-device info against what's recorded in the build.prop, so this seems like a safe, workable solution for those of us with defective devices on our shelves.
Is there a way to make this work on a ManualNootered nook with 1.2, or does it only work if you have a custom rom.
Thanks
integrate in CM7
could you not ask the maintainers of CyanogenMod to integrate this in the future nightlies?
they would probably welcome the added functionality
WANTED: Users to port SGS roms to the 4.0. You will need to know how to complete a full restore if something goes wrong, but that's it. I cannot go through the forums searching for good SGS roms, as I have several threads to manage, and a rom to work on. The steps are easy for you though, and if you port a rom I will add it in the OP.
First of all, I want to say that I take NO credit on any of these roms. All I did was port them over and add speed tweaks, or added ones that users have ported. If the rom creators or mods have any issue whatsoever with this thread, I will happily take it down, even though I think it would be a large contribution to the 4.0 community. I will continue to update this forum with info as I go along.
I, after a fortunate afternoon of boredom, have managed to successfully begin porting I9000 roms to our devices! Fortunately, they are similar enough that it boots without any modifications. I will put up here any ports that I make, and any that the users create. Note that these WILL NOT BE UPDATED! These are one-time ports, to be used and improved upon by the community. Anything that is broken now will stay broken, unless a user decides to fix/update it, then I will include it in the OP.
What *should* work in all ported roms:
wifi
GPS
home buttons
everything else
What will probably *not* work on ported roms:
Bluetooth
Camera
backlight on buttons
Ported roms:
~GamerzRom odexed V11-~
Link to original thread: http://forum.xda-developers.com/showthread.php?t=1656081
Added:
V6 supercharger, and build.prop tweaks from it.
init.d tweaks from my rom
ext4 filesystem
Advanced mount options
Auto zipalign and Database optimize
Removed apps that do not work on our Player (such as the Dialer)
Download:http://www.mediafire.com/download.php?ctuu2w295w2xlk6
~Saurom~
Original thread:http://forum.xda-developers.com/showthread.php?t=1388342
Ported download link:http://www.mediafire.com/download.php?csua40hkg1r3m86
~JellyBeanRom~
Original thread: http://forum.xda-developers.com/showthread.php?t=1260709&highlight=gb
Ported download link:http://www.mediafire.com/download.php?mgec81f3ifck221
~Ario Rom (ported by ChaosChris)~
Ported thread link : http://forum.xda-developers.com/showthread.php?p=29950015#post29950015
Original thread: http://forum.xda-developers.com/showthread.php?t=1536558
To use these Roms:
You MUST use a Gplayer kernel! GT-I9000 kernels will not boot!
A full wipe may be necessary with some roms if you encounter issues.
Converting (for porters)
Steps:
1. Download wanted rom (must be GB)
2.Move the zip to the internal sdcard
3.Reboot into recovery
4.Flash zip, then boot into download mode
5.Flash a SGP kernel
6. apply my mod pack to the rom, by either copying/pasting the system directory over the SGS rom's system directory, or by pushing it via adb, (eg. adb push /path/to/modpack /system).
7. Profit!
NOTE: after applying this, porters may want to remove non-working packages such as the dialer and mms, as they may cause issues with the end result if they are kept in. Do not delete phone.apk though!! This is required for the camera and some other things, and breaks stuff on certain roms. You have been warned.
NOTE: If you use this modpack, please give me credit, and link back to this thread so that more people can use it. Also, you should probably link back to the ported rom's thread as well, to avoid "ripping off" those devs.
Modpack:
Changelog
V1-
Preliminary release
Fixes wifi and GPS
Includes v6 supercharger and init.d tweaks
V2-
fixed vold.fstab so sdcard is mounted properly.
Download:
ModpackV1:
http://www.mediafire.com/download.php?diaq6im4i18ktf7
NOTE:Note that this is preliminary. It fixes everything listed, and attempts to fix some broken things. Your mileage may vary. This is not a cwm flashable zip! you much extract and adb push this over the existing system directory. This is mainly intended for porters, so users apply at your own risk. This will work, but is a very early release.
Modpack V2 (thanks to ChaosChris):
https://docs.google.com/open?id=0B9OVlH2Pl76DZk5Pa3lJVXlrYzA
Looking good! Does the gamerz port have the 388mb of ram, I thought that was kernal related?
Sent using Tapatalk
iJimaniac said:
Looking good! Does the gamerz port have the 388mb of ram, I thought that was kernal related?
Sent using Tapatalk
Click to expand...
Click to collapse
Yeah, it says that because it includes semaphore's kernel, which raises the max rom to 380, which we could do on our kernel's, but apparently that breaks a lot of stuff if you go much further then 350 (according to klin).
is the wifi fixed in your port or do we have to do your fix after flashing?
Just a word of advice, make sure you get permission from the devs! Also surely this will work with ICS roms right? Just swap out the SGS kernel with the SGP CM7 kernel and it should work (I think)
Sent by my Robot Butler
Supermaster34 said:
Just a word of advice, make sure you get permission from the devs! Also surely this will work with ICS roms right? Just swap out the SGS kernel with the SGP CM7 kernel and it should work (I think)
Sent by my Robot Butler
Click to expand...
Click to collapse
check over in the operation: ics for the 4.0 thread I believe they are already attemping to use the cm7 kernel to boot a cm9.
daniel644 said:
is the wifi fixed in your port or do we have to do your fix after flashing?
Click to expand...
Click to collapse
Yeah, it is fixed before you flash. Once I manage to iron out a few more bugs, I will probably release a "conversion pack" that fixes all the issues. I already have one that fixes wifi and gps, but bluetooth and camera have me stumped, and I do not want to replace the entire hw/lib folder, because some of these roms have lib optimizations, but I may have to.
Sent from my GT-I9000 using xda app-developers app
Supermaster34 said:
Just a word of advice, make sure you get permission from the devs! Also surely this will work with ICS roms right? Just swap out the SGS kernel with the SGP CM7 kernel and it should work (I think)
Sent by my Robot Butler
Click to expand...
Click to collapse
Since I am merely redistributing their work, not incorporaring it into anything I have made, or taking any credit for it, I don't asking permission is necessary. I may be completely off base, but I think that as long as you give devs 100% credit, and link to their original work, it is okay. It may not be the best option, but neither is asking EVERY dev if I can port their rom, or ask permission for user-ported roms.
Youay have an idea there, althouh I think that zaclimon has tried it, and he said it wouldn't boot. I have 2 efs backups, so I guess I can try, although even if the kernel boots, I bet I will have to do a LOT more work before it is usable. I also believe that he said the issues may have been rom based, so here it goes, and wish me luck.
Sent from my GT-I9000 using xda app-developers app
hanthesolo said:
Since I am merely redistributing their work, not incorporaring it into anything I have made, or taking any credit for it, I don't asking permission is necessary. I may be completely off base, but I think that as long as you give devs 100% credit, and link to their original work, it is okay. It may not be the best option, but neither is asking EVERY dev if I can port their rom, or ask permission for user-ported roms.
Youay have an idea there, althouh I think that daniel has tried it, abd he said it wouldn't boot. I have 2 efs backups, so I guess I can try, although even if the kernel boots, I bet I will have to do a LOT more work before it is usable.
Sent from my GT-I9000 using xda app-developers app
Click to expand...
Click to collapse
I've already tried with a cm7 kernel and I got an error of looping (netd1.0 starting) that's why I'm trying to do something. Now I need to backport 3.0.8 usb gadget drivers.
zaclimon said:
I've already tried with a cm7 kernel and I got an error of looping (netd1.0 starting) that's why I'm trying to do something. Now I need to backport 3.0.8 usb gadget drivers.
Click to expand...
Click to collapse
Whoops, I meant you . I will try with a official cm9 build from the SGS forums, and see if that fares any better. Probably will not, but it doesn't hurt to try.
EDIT: well, nevermind about that. He seems to have pulled all of his download links, and I cannot get to the CM7 build. Oh well...
I am going to try anyway with the I9000 package since it seems to have EXT4 support, and I *think* that was what was bootlooping me earlier. This as all just my hopeful rationalization, of course . A lot farther out there, but maybe I can use a SGP5.0 kernel to get it booting. A LOT less likely, but hey, i'm experimenting .
EDIT: I cannot try ICS, since I need to reboot into recovery a second time, and I cannot do that, as I have the intl bootloader on my US device, and it would require it to be booting first.
hanthesolo said:
Whoops, I meant you . I will try with a official cm9 build from the SGS forums, and see if that fares any better. Probably will not, but it doesn't hurt to try.
EDIT: well, nevermind about that. He seems to have pulled all of his download links, and I cannot get to the CM7 build. Oh well...
I am going to try anyway with the I9000 package since it seems to have EXT4 support, and I *think* that was what was bootlooping me earlier. This as all just my hopeful rationalization, of course .
Click to expand...
Click to collapse
I think we should do like entrophy's because I get bored from mtd. Also just tried the gamerz rom port. As I see the camera works, don't know about bluetooth (it can turn on). Vibration works too. I was able to connect to wifi pretty fast and I have one word for this rom. FAST!!!!
Good job!!
zaclimon said:
I think we should do like entrophy's because I get bored from mtd. Also just tried the gamerz rom port. As I see the camera works, don't know about bluetooth (it can turn on). Vibration works too. I was able to connect to wifi pretty fast and I have one word for this rom. FAST!!!!
Good job!!
Click to expand...
Click to collapse
Well, thet camera shows a preview, but fails when a pic is taken, for some reason. Bluetooth does turn on, but is not seen by any other devices, and cannot scan for others either. I did do a little tweaking with Gamerz, so it will be even faster than it was already, which is pretty blazing! I have 2 more that I can put up (I have a preliminary package that I just adb push over the system files that works for now). I have also gotten the camera apk onto my rom, and it works really well! It doesn't take 5 MP pics, or record 720p video (which may be because I am using Terrasilent, which reduces the amount of Vram the system can have), but tap to autofocus and everything else works pretty well. I have a sneaking suspicion that the camera is soft limited, not hard-limited.
I also noted that the external sd card isn't working too (a problem with vold.fstab I'll correct it right now)
zaclimon said:
I also noted that the external sd card isn't working too (a problem with vold.fstab I'll correct it right now)
Click to expand...
Click to collapse
I don't use an externel sdcard, so thanks for pointing that out! I will include a fixed version in my mod pack.
hanthesolo said:
I don't use an externel sdcard, so thanks for pointing that out! I will include a fixed version in my mod pack.
Click to expand...
Click to collapse
Here's the vold.fstab if you need it
Okay, it seems that the zip hosed my partitions (converted them to yaffs2 and mtd), so I am going to perform a full restore, and just keep porting GB roms. As soon as you can get the usb gadget driver working, zaclimon, I guess I can keep working on it, but for now I will just keep to GB.
Two more roms up! I will probably not port any other unless I see an especially good one, but I will put up my mod pack tomorrow.
has anyone found out if the ported roms enable tv out or has someone found out if tv out support is in the i9000 kernal?
TV out has to have hardware, or your not going anywhere. I think the galaxy player lacks the hardware unfortunately. If it does have the hardware, it was very dumb of Samsung not to enable it.
Sent using Tapatalk
iJimaniac said:
TV out has to have hardware, or your not going anywhere. I think the galaxy player lacks the hardware unfortunately. If it does have the hardware, it was very dumb of Samsung not to enable it.
Sent using Tapatalk
Click to expand...
Click to collapse
what hardware does the galaxy s i9000 have that allows for tv out? I thought the galaxy s i9000 and the galaxy player 4.0 had the same gpu?
This modification definitely fix the low mic issue on call without affect anyone else.
Simply extract the rar file and put LowMicFix.zip and LowMicFix.prop files on your phone. Reboot your phone into custom recovery mode (TWRP, CWM) and flash LowMicFix.zip.
This solution work now on All ROM !
For more confort if you are on Rom with CyanDelta installed, put LowMicFix.zip and LowMicFix.prop in the Cyandelta folder and in the app option add LowMicFix.zip to " Install additional zip after ROM ".
Change applied in build.prop by the fix V1_Final
BEFORE FIX
ro.qc.sdk.audio.fluencetype=fluence
persist.audio.fluence.voicecall=true
AFTER FIX
ro.qc.sdk.audio.fluencetype=fluence
persist.audio.fluence.voicecall=true
persist.audio.fluence.voicerec=false
persist.audio.fluence.speaker=false
Click to expand...
Click to collapse
[UPDATE V1_Final (All Rom)]
- Fluence Noise reduction works for all android Rom version ( KK - Lollipop )
- " Ok google " hard voice detection fixed
- I need your back if all is Ok or Not !
[UPDATE LOLLIPOP ROM] OUTDATED
- Fluence Noise reduction is back and functional for all Call Mode !
[UPDATE V0.2] OUTDATED
- Reactivate voice clarity
- Reactivate 2 mic and fluence for speaker Mode ( now people may not hear themselves )
[UPDATE V0.1] OUTDATED
- Works on ALL ROM for One Plus One.
- For prevent BootLoop if one or more lines on the fix exist in original build.prop, the script remove it before install the fix.
OPO - LowMicFix_V1_Final_tazzkiller is the best for all Rom, install or update to it !!
thank to klenamenis for his "tweakprop" tools.
has anyone tried this?
tazzkiller said:
After few day on test, this modification definitely fix the low mic issue on call without affect anyone else. The solution comes from the same problem encountered on the LG G2 and fixed by LG in its stock Rom. I create a recovery zip for apply it.
Simply extract the rar file and put LowMicFix.zip and LowMicFix.prop files on your phone. Reboot your phone into recovery mode (TWRP, CWM) and flash LowMicFix.zip.
This zip change and add the necessary lines to fix it in the build.prop file. this solution work on all rom based on CM11 or CM12.
thank to klenamenis for his " Dynamic automated build.prop editing ".
Click to expand...
Click to collapse
has anyone confirmed that this works as stated?
Please and thanks in advance.
sanjsrik said:
has anyone confirmed that this works as stated?
Please and thanks in advance.
Click to expand...
Click to collapse
dont take this the wrong way but you can test it out and let the community know. I mean its just addition to your build.prop as I read it and it wont blow your phone up
Also he has 3 thanks and I would assume thats there for a reason
Never unheard of to ask for second opinions, don't you think?
playya said:
dont take this the wrong way but you can test it out and let the community know. I mean its just addition to your build.prop as I read it and it wont blow your phone up
Also he has 3 thanks and I would assume thats there for a reason
Click to expand...
Click to collapse
1. I'm sure this is harmless, yet, asking for backup isn't unheard of here. I'd rather ask before trying to see if this has been vetted by others. Not clubbing baby seals by asking.
2. People click "thank you" all the time. Look I even clicked it for you.
Don't worries, the zip create a backup of your build.prop before change and add new line on it. But you are right, 200 download and nothing people say it's good or not ! But i think, no news.... Good news !
Good Morning. I could not even test the impact , but the OPO remains functional in any case. The changes in the build.prop set the OPO not in the bootloop .
Does this patch fix the 2G issue that the voice is scrambled in calls when using the internal mic?
Will this mod affect this "true stereo mod"?
http://forum.xda-developers.com/oneplus-one/development/mod-oneplus-one-stereo-mod-t2967925/
I'm on cm11 with ak kernel
remix96 said:
Will this mod affect this "true stereo mod"?
http://forum.xda-developers.com/oneplus-one/development/mod-oneplus-one-stereo-mod-t2967925/
I'm on cm11 with ak kernel
Click to expand...
Click to collapse
No my fix doesn't touch any xml config file of android, only edit your build.prop for specific configuration of the hardware mic material.
Added to OnePlus One index thread:
[INDEX] OnePlus One Resources Compilation Roll-Up
Transmitted via Bacon
Updated to V0.1 ( see first post for details )
sanjsrik said:
1. I'm sure this is harmless, yet, asking for backup isn't unheard of here. I'd rather ask before trying to see if this has been vetted by others. Not clubbing baby seals by asking.
2. People click "thank you" all the time. Look I even clicked it for you.
Click to expand...
Click to collapse
I get it but I mean research the zip and see what it's doing then try it. We flash roms to our phones from people we do not know everyday. Oh well I hope you tried it and it helped you out. No seals were harmed in this post.
Take it easy
This fix (the first version) did NOT work for me. I'm running on the latest nightlies of CM12 on my OPO. Is it worth trying v0.1? Also, for those worried about anything going wrong you can easily just flash the latest nightly directly or via CyanDelta and all the changes will go away.
+yamsta have you see in the build.prop if new lines are here ?
Wouldn't it be easier just to provide the required changes as well? I do not like flashing ZIPs without exactly knowing what is going to be changed.
_TB_TB_ said:
Wouldn't it be easier just to provide the required changes as well? I do not like flashing ZIPs without exactly knowing what is going to be changed.
Click to expand...
Click to collapse
If you want to know exactly. Open that updater.script then read and know.
Sent from my A0001 using Tapatalk
_TB_TB_ said:
Wouldn't it be easier just to provide the required changes as well? I do not like flashing ZIPs without exactly knowing what is going to be changed.
Click to expand...
Click to collapse
for more reliability, it's easier for the user to flash a zip than manually edit a file and less dangerous.
For more simplicity, add the zip to Cyandelta additional zip automated the process after all new nightly
gnan10 said:
If you want to know exactly. Open that updater.script then read and know.
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Simply open LowMicFix.prop the process are stored here
tazzkiller said:
for more reliability, it's easier for the user to flash a zip than manually edit a file and less dangerous.
Click to expand...
Click to collapse
Maybe so, but for more clarity, it's always better for someone who puts up a fix to state exactly what the fix is doing, so users can evaluate whether they want to try it or not. Please list out the changes that your patch makes, and how it tries to fix the issue. Thanks.
Updated to V0.2 ( see first post for details )
Updated for all lollipop rom ( see first post for details )
Hi,
My z5c is rooted and running MM (build 32.2.A.5.11). Pretty sure I should be able to install & utilize Camera 2.0, but
(a) It never showed up for me in "what's new" (which I defrosted for the purpose) and
(b) when I try to install by clicking on the apk on the sd card, it launches the install process; but, then it stops and gives a simple (but unhelpful) "X App not installed." message.
Any ideas on how to force a manual install?
Thanks, Kirk
PS I have tried both the 2.0.0 apk which I believe is Android 5.0 and up as well as the 2.0.0-10003 one which purports to be Android 6.0+
Frustrating!
How do you rooted ur z5c e5823 pls i need help steo by step with links plsss
kirkzp said:
Hi,
My z5c is rooted and running MM (build 32.2.A.5.11). Pretty sure I should be able to install & utilize Camera 2.0, but
(a) It never showed up for me in "what's new" (which I defrosted for the purpose) and
(b) when I try to install by clicking on the apk on the sd card, it launches the install process; but, then it stops and gives a simple (but unhelpful) "X App not installed." message.
Any ideas on how to force a manual install?
Thanks, Kirk
PS I have tried both the 2.0.0 apk which I believe is Android 5.0 and up as well as the 2.0.0-10003 one which purports to be Android 6.0+
Frustrating!
Click to expand...
Click to collapse
The latest firmware is Nougat .54. Its already include there afaik. Camera 2.0.0 isn't just the apk file, its also the libs and HAL that could have been modified, so just installing the app might not be enough.
Anyway, if the app you want - root and go to /system/app (or priv-app, i think it was priv-app) and replace the old Camera apk with the new one.
unar51 said:
How do you rooted ur z5c e5823 pls i need help steo by step with links plsss
Click to expand...
Click to collapse
There are LOTS of guides here on how to do that. I also dont think this thread is the place to ask. Search before you post
trax7 said:
The latest firmware is Nougat .54. Its already include there afaik. Camera 2.0.0 isn't just the apk file, its also the libs and HAL that could have been modified, so just installing the app might not be enough.
Anyway, if the app you want - root and go to /system/app (or priv-app, i think it was priv-app) and replace the old Camera apk with the new one.
There are LOTS of guides here on how to do that. I also dont think this thread is the place to ask. Search before you post
Click to expand...
Click to collapse
Thanks for the help. By what I have read, the app should be compatible with MM, not just nougat; now that the phone is old, maybe I'll try mucking around in the system files...
I actually did quite a bit of research before I posted. And, how can "Q&A, Help, and Troubleshooting" NOT be the place to ask this question? Am I totally missing something? This query seems to be perfectly placed (imho)
kirkzp said:
Thanks for the help. By what I have read, the app should be compatible with MM, not just nougat; now that the phone is old, maybe I'll try mucking around in the system files...
I actually did quite a bit of research before I posted. And, how can "Q&A, Help, and Troubleshooting" NOT be the place to ask this question? Am I totally missing something? This query seems to be perfectly placed (imho)
Click to expand...
Click to collapse
Ah, my apologies then, good sir! I could have sworn I was looking at SONY Cross Device forums... :silly:
Good luck!