Related
Hi,
I'm now trying to use Android on HTC fulltime (way too many crashes in WM6.5+HTC Sense, phone becomes unusable) but I'm having some trouble with the microphone when someone calls.
I've read the problem is solved in the latest build of Froyo, but that is the one I have installed.
Is there a difference between the "Reference version" and the "BLAZN version" found on this page: http---sites.google.com-site-androidport-downloads ?
I have installed the "BLAZN version" of Froyo 2.2, which has a different update date.
Can someone recommend installing the "Froyo Reference version" to solve the microphone issue?
You can try updating to the newest kernel to try & fix the mic issue.
I thought this was resolved for everyone, but evidently not. Can you try the newest kernel and post back your results?
arrrghhh said:
You can try updating to the newest kernel to try & fix the mic issue.
I thought this was resolved for everyone, but evidently not. Can you try the newest kernel and post back your results?
Click to expand...
Click to collapse
I don't follow... :$
What do you mean with "try the newest kernel"?
I have copied the contents of the Froyo BLAZN 2.2 - cab to my phone SDcard and installed the cab. Previously I have updated the phone with all the patches and fixes HTC made available for download.
Did I miss a step in the installation process?
Some more information that might be useful:
Belgian bought HTC Touch Pro 2 (no sim-lock, no fixed telecom provider),
now running the AndroidonHTC Rhodium - Rhod100_UK (to have the correct keyboard mapping) installation with maximum overclocking and HW3D unchecked (read the updates list today and should have checked it, I know )
Thanks for your quick reply btw
ps: I didn't find anyone else with this problem, so it is probably resolved,
I think it's a small missing update in the Froyo BLAZN pack, but wanted to verify before having to reinstall the whole thing again (takes quite some time for sth stupid like importing my contact list from my SIM, linking FB contacts,... not sth I like to do on a daily basis )
Uhm... update using the kernel autobuild service?
The issue is certainly kernel related, and I know the 'newest' blazn uses a kernel that's quite old (nearly a month!)
The new reference build is quite new, but still is behind several kernel commits.
There's a new kernel out all the time - I've said it before, sometimes there's several daily patches to the kernel, sometimes there's a week between commits. Just depends on what's going on in the developer world.
arrrghhh said:
Uhm... update using the kernel autobuild service?
The issue is certainly kernel related, and I know the 'newest' blazn uses a kernel that's quite old (nearly a month!)
The new reference build is quite new, but still is behind several kernel commits.
There's a new kernel out all the time - I've said it before, sometimes there's several daily patches to the kernel, sometimes there's a week between commits. Just depends on what's going on in the developer world.
Click to expand...
Click to collapse
http-//forum.xda-developers.com/showthread.php?t=788837&page=5[/url]
Found this using google and does seem like a kernel update could do the trick, but I still don't get where I could do a "kernel update" or the "kernel autobuild service".
I have never used such function, so I'm sorry for the newb-question...
Could you hand me some more keywords/hints to find the most recent kernel build for my phone?
Is this kernel you're talking about some kind of update for the radio? As far as I get it now, it is some sort of unofficial update/patch provided by (open-source) developers?
RealReality said:
I don't follow... :$
now running the AndroidonHTC Rhodium - Rhod100_UK (to have the correct keyboard mapping) installation with maximum overclocking and HW3D unchecked (read the updates list today and should have checked it, I know )
Click to expand...
Click to collapse
same microphone issue, but with the 14. Oct energy ROM.
Can you please help me ..where to find this program for the correct key mapping?
thank you.
bogdan_wrc said:
same microphone issue, but with the 14. Oct energy ROM.
Can you please help me ..where to find this program for the correct key mapping?
thank you.
Click to expand...
Click to collapse
Correct key mapping is a setting in your startup.txt/default.txt file OR when you use the XDAndroid Starter application in WM, you just have to select "Rhod100_uk" (in my case, I don't know your keyboard layout?)
The latter is the easiest solution btw.
Kernel Autobuild
RootFS autobuild
Initramfs autobuild
Alright,
thank you for your help, the problem is solved!
Solving process:
1) Android Startup app didn't want to update
2) Downloaded the newest Android Startup app (version 1.3)
3) Hit "update"
4) Found new Kernel > installed
5) Working microphone with incoming calls...
bogdan_wrc said:
same microphone issue, but with the 14. Oct energy ROM.
Can you please help me ..where to find this program for the correct key mapping?
thank you.
Click to expand...
Click to collapse
For the keymapping thing, if you look in the startup.txt file on the sim card, look for: "physkeyboard=Tilt2" (minus quotes). Change "Tilt2" to "tilt2". I've found that by changing the capital T to a lowercase t, it fixes the key mapping issue. It's worth a shot.
Solving the microphone problem has triggered another one...
I had Launcher Pro Plus installed and could use the "Home key" to show an overview of my different homescreens...
Now the Home key doesn't work anymore...
Most recent builds etc are installed now, so I have no idea what to do to solve this issue.
RealReality said:
Solving the microphone problem has triggered another one...
I had Launcher Pro Plus installed and could use the "Home key" to show an overview of my different homescreens...
Now the Home key doesn't work anymore...
Most recent builds etc are installed now, so I have no idea what to do to solve this issue.
Click to expand...
Click to collapse
Check this
Best thing to do otherwise is to wait for a fix.
contributor_M said:
Check this
Best thing to do otherwise is to wait for a fix.
Click to expand...
Click to collapse
Thank you
Quite a relief it's just a minor bug,
I can live with the workaround you suggested,
instead of "Home" for the End Call button, I choose "Home, Then Sleep"
RealReality said:
Correct key mapping is a setting in your startup.txt/default.txt file OR when you use the XDAndroid Starter application in WM, you just have to select "Rhod100_uk" (in my case, I don't know your keyboard layout?)
The latter is the easiest solution btw.
Click to expand...
Click to collapse
thank you! that worked. Now, i am still fighting to solve the microphone problem...because this:
"1) Android Startup app didn't want to update
2) Downloaded the newest Android Startup app (version 1.3)
3) Hit "update"
4) Found new Kernel > installed
5) Working microphone with incoming calls..."
did not help
Hey guys, I have the same problem with the mics. I am running the newest kernels on Rhodium 400. I updated everything with the startup utility. It only is a problem when someone calls me, I can't hear them but they can hear me. If I disconnect and then call them, it works fine. Just recently, I had the problem of my mic not working in a call.
I have just been keeping my head down because I really appreciate what the developers are doing, but I figured if I don't say anything, they won't know there are still problems. Thanks again for everything you guys are doing!!
OK can we all ignore the update utility for the time being, go and grab the newest kernels and let us know if it's solved? Supposedly the newest kernels solve this issue, but I personally never experienced it on my RHOD, so I'm not a good test...
minikirchner said:
Hey guys, I have the same problem with the mics. I am running the newest kernels on Rhodium 400. I updated everything with the startup utility. It only is a problem when someone calls me, I can't hear them but they can hear me. If I disconnect and then call them, it works fine. Just recently, I had the problem of my mic not working in a call.
I have just been keeping my head down because I really appreciate what the developers are doing, but I figured if I don't say anything, they won't know there are still problems. Thanks again for everything you guys are doing!!
Click to expand...
Click to collapse
I tried pressing "Volume Up" when I picked up a call today and sure enough it worked. I previously experienced the same issues you describe. When pressing volume up I did it quickly about 3-4 times.
arrrghhh said:
OK can we all ignore the update utility for the time being, go and grab the newest kernels and let us know if it's solved? Supposedly the newest kernels solve this issue, but I personally never experienced it on my RHOD, so I'm not a good test...
Click to expand...
Click to collapse
for beginners, just like me, how and from where can we take the newest kernels?
bogdan_wrc said:
for beginners, just like me, how and from where can we take the newest kernels?
Click to expand...
Click to collapse
The search is not strong with this one...
Kernel Autobuild
RootFS Autobuild
initramfs Autobuild
The kernel by far gets more updates than any of the other two.
arrrghhh said:
The search is not strong with this one...
Kernel Autobuild
RootFS Autobuild
initramfs Autobuild
The kernel by far gets more updates than any of the other two.
Click to expand...
Click to collapse
sorry....but i still can not understand what i have to download can you please more specific?
When building an androidinstall.tar from scratch, do I need to include the META-INF file as well?
I will try without it as this build was for a different phone that I extracted and decompressed. I have already separated the apps and placed them in their own /data folder and removed them from the /system folder.
It is an unodexed build so no .odex files were included.
I was looking through other builds I have on hand and noticed no META-INF file, thats the reason for asking.
First error:
[ 127.061609] init: Unable to open persistent property directory /data/property errno: 2
Then a whole mess of kernel errors, possibly due to wrong system...
FIXED! Awaiting boot animation to finish.
Honeycomb boot animation is SO cool looking!
EDIT: NOT fixed, refuses to finish booting. Will work on it more to see if I can get it to boot up.
So far I've gotten to the point where the D-pad and keyboard light but boot animation continues.
Build is Android 3.0 Honeycomb with parts and drivers taken from "system_gingerbread_unodex" listed on sourceforge.
Someone tell me what I've missed here as it's about 80% finished booting and hangs after D-pad lights, animation continues until I pull the battery, about 10 minutes.
Getting an error "cannot execue /system/bin/leds.sh, no such file or directory", even though I made sure to copy it and went back and checked it.
Sorry if this looks like I'm using the forum as a sounding board, but I found an experimental build of Honeycomb for the MSM7201A and wanted to try it out.
Watch me cook the only Kaiser I have left...
All but giving up for now, will dig deeper. I know HC was NEVER meant to run on our Kaisers but it would be fun to see it happen.
Wow you are insane! (I mean that in a good way)
I have a Xoom tablet that runs honeycomb, but can't even imagine it running on our sweet Kaiser. Heck, I don't even like gingerbread: uses too much RAM.
Keep us posted, it sounds like a wonderful experiment.
I'm so close yet so far with it because I'm using more and more of Gingerbread in the build. I even ended up trying to change the build.prop file to accomidate some of the changes in dimensions and clock speeds...
I think I'm about 90% there, just have some issues with the bootanimation restarting, which I may change to the nexus for the smaller size. (HC boot animation is somewhere around 14mb compared to our partly 875kb nexus animation). That could be half the problem because the bootanim uses so much of the ram...
To be continued...
Ok This is a very interesting project
I am from the vogue forum but since my touch broke and the build process is identical I just sort of wander around trying to help with what I know.
So at one time I did a lot of porting and it appears according to your first post this is what you did. What phone did you take the rom from?
If its from the wildfire (I know there was a honeycomb movement in there for a while) I can definitely help because that is where I did most of my porting from
And the META-INF question... When I port I usually trash a bunch of folder straight away ... including META-INF
Good to know there are "floaters" around helping as needed.
BTW, it IS from the Wildfire port. Considering the MSM family is bascally the same, I'm trying to use that as a starting point.
The META-INF file contains certificates and what-not but isn't needed for our phones.
My biggest issue right now, as with any Gingerbread release, is finding drivers for our devices. Froyo drivers won't work because they lack the correct signature. Same as if someone tries to install the HTC flip clock on a plain android without the sense build, it just doesn't work.
I have this project and trying to port the kernel we use to the Raphael (Touch pro/Fuze), which is a major task in and of itself. I tried HaRet before with the Kaiser and I jus HATE it.
Biggest issue with the Fuze right now is to get it CID unlocked so I can try installing the kernel to NAND and go from there.
With that being said, I don't know what kind of progress I'll be making with HC in the near future, if any.
Ok, I went back and restarted the project from scratch. Someone else ported the bootanimtion and different aspects of HC to a Froyo port on the Xperia X1 forum.
I recompiled everything at first, moving the "app" folder inside a new folder named "data", since our NAND constraints limit the build size to under 102mb for /system.
Once again I am stuck at the boot animation. It will go full-speed for a minute then restart and run slow. The only parts taken from the X1 were the app folder and media/bootanimation.zip
I'll dig a little deeper, maybe ask around the X1 forum for help.
Would be nice to finally figure this out though.
Hi PoXFreak. It seems like you're a very good dev. Could i help you somehow or could you link me to somewhere where i could get all the tools for rom and kernel building. Im a C++ learner, i've written a few apps, but only big thing i've done in android is installed sdk and modified a rom to have apps i need after install. I'd rly like to improve our kaisers.
P.S. dou you put anynthing compilled by urself in android rom (without kernel)? And where are the drivers located? system/lib/modules/[kernelversion]/ or system/lib/modules/ ???
zxxxy said:
Hi PoXFreak. It seems like you're a very good dev. Could i help you somehow or could you link me to somewhere where i could get all the tools for rom and kernel building. Im a C++ learner, i've written a few apps, but only big thing i've done in android is installed sdk and modified a rom to have apps i need after install. I'd rly like to improve our kaisers.
P.S. dou you put anynthing compilled by urself in android rom (without kernel)? And where are the drivers located? system/lib/modules/[kernelversion]/ or system/lib/modules/ ???
Click to expand...
Click to collapse
The .so files go into /system/lib/modules/(kernelversion).
Sent from my Android on HTC Kaiser using XDA App
I have yet to make a complete working build from my work so no, I have nothing "new" to contribute to any android builds. All I'm doing is combining and rearranging/replacing/removing files already in builds.
To date, I have not had the time to work on this. I would like to be able to devote more time but I have too much on my plate already. Not to say I'm dropping the ball, just putting it on the rack for awhile.
I'm trying to install Hyperdrive RLS10. The flash instructions say to install an AT&T build prop and I've also seen users mention that you will need to fix the google client database for the rom to function properly on AT&T. I can not locate any AT&T build prop to flash and do not know how to fix the google client database. Would anyone be able to help me so that I can get this rom working properly?
mrpoe222 said:
I'm trying to install Hyperdrive RLS10. The flash instructions say to install an AT&T build prop and I've also seen users mention that you will need to fix the google client database for the rom to function properly on AT&T. I can not locate any AT&T build prop to flash and do not know how to fix the google client database. Would anyone be able to help me so that I can get this rom working properly?
Click to expand...
Click to collapse
If you don't know how to do those, you might wanna look into flashing a AT&T ROM first and learn more about what you're attempting to do. (Google is a good friend)
P.S.: Please, don't double post.
BWolf56 said:
If you don't know how to do those, you might wanna look into flashing a AT&T ROM first and learn more about what you're attempting to do. (Google is a good friend)
P.S.: Please, don't double post.
Click to expand...
Click to collapse
I'm aware of what I'm attempting to do. The build prop on this rom needs to be edited or replaced or reflect AT&T since the rom base is Verizon. I'm not new to flashing roms; I've just never had to edit/replace a build.prop for a rom port from another carrier. I've searched google and the rom thread before posting this question. I'm just trying to see if anyone else from the community would be able to advise me what edits I would need to make to the build.prop or if they could help point me in the right direction for a build.prop zip that I could flash through TWRP. I expected the typical "why don't you just google it" response, but was hoping that someone would be helpful enough to actually assist me.
P.S.: I only started this thread after I realized my original post was in a thread with little to no activity.
mrpoe222 said:
I'm aware of what I'm attempting to do. The build prop on this rom needs to be edited or replaced or reflect AT&T since the rom base is Verizon. I'm not new to flashing roms; I've just never had to edit/replace a build.prop for a rom port from another carrier. I've searched google and the rom thread before posting this question. I'm just trying to see if anyone else from the community would be able to advise me what edits I would need to make to the build.prop or if they could help point me in the right direction for a build.prop zip that I could flash through TWRP. I expected the typical "why don't you just google it" response, but was hoping that someone would be helpful enough to actually assist me.
P.S.: I only started this thread after I realized my original post was in a thread with little to no activity.
Click to expand...
Click to collapse
I didn't mean to sound like ''Why don't you just google it''. You gave really low information on your experience and such, therefor, I made a safe suggestion.
Basically, you have to change the phone model to SGH-I747 in the build.prop file with something like notepad.
As for the other part, I have no idea, and this time, google will actually be helpful as I'm sure people attempted this before.
BWolf56 said:
I didn't mean to sound like ''Why don't you just google it''. You gave really low information on your experience and such, therefor, I made a safe suggestion.
Basically, you have to change the phone model to SGH-I747 in the build.prop file with something like notepad.
As for the other part, I have no idea, and this time, google will actually be helpful as I'm sure people attempted this before.
Click to expand...
Click to collapse
I was able to locate the build.prop edits buried in a thread about google wallet. I'm still not sure about the other part, but I have the rom up and running on at&t LTE with no issues. I appreciate your patience. I try to search as thoroughly as I can, unfortunately, work often gets in the way.
mrpoe222 said:
I was able to locate the build.prop edits buried in a thread about google wallet. I'm still not sure about the other part, but I have the rom up and running on at&t LTE with no issues. I appreciate your patience. I try to search as thoroughly as I can, unfortunately, work often gets in the way.
Click to expand...
Click to collapse
Clearing client database means clearing data and cache in the play store app. That's what worked for me on with that issue...or loading another Google account then deleting it then adding your main one.
Verizon Galaxy S3 running RLS10 - call echo issue
Hey, first of all I wanted to say to the developers of the Hyperdrive RLS ROM, this has become one of my preferred ROMS - great stability, battery life, etc. I just upgraded from RLS9 to RLS10. FYI, I always wipe everything prior to installing a ROM. Anyway, installation went off without a hitch and the ROM runs great, but since I upgraded to this ROM, I am getting an echo with every single call even with bluetooth. Not sure if anyone else is having this issue, and if there's a fix for it? Would appreciate any feedback! Thanks, and thank you to the developers for all the work you do.
jpc477 said:
Hey, first of all I wanted to say to the developers of the Hyperdrive RLS ROM, this has become one of my preferred ROMS - great stability, battery life, etc. I just upgraded from RLS9 to RLS10. FYI, I always wipe everything prior to installing a ROM. Anyway, installation went off without a hitch and the ROM runs great, but since I upgraded to this ROM, I am getting an echo with every single call even with bluetooth. Not sure if anyone else is having this issue, and if there's a fix for it? Would appreciate any feedback! Thanks, and thank you to the developers for all the work you do.
Click to expand...
Click to collapse
the echo is just on your end, correct?
go to settings >accessibility and make sure turn off all sounds is not checked to begin with. now go to settings > sound and make sure your volume levels are correct and sound is turned on.
also, phone > menu > Call settings > additional settings and then uncheck noise reduction. some people have reported less echo and clearer calls with this turned off.
jpc477 said:
Hey, first of all I wanted to say to the developers of the Hyperdrive RLS ROM, this has become one of my preferred ROMS - great stability, battery life, etc. I just upgraded from RLS9 to RLS10. FYI, I always wipe everything prior to installing a ROM. Anyway, installation went off without a hitch and the ROM runs great, but since I upgraded to this ROM, I am getting an echo with every single call even with bluetooth. Not sure if anyone else is having this issue, and if there's a fix for it? Would appreciate any feedback! Thanks, and thank you to the developers for all the work you do.
Click to expand...
Click to collapse
A few have reported the same issue on the thread but no real solution beyond hit speaker on then off and it goes away. Reason that works ? I have no clue.
Flashed AOKP version task650 I cannot access general Settings. I can get into ROM settings and KERNEL settings but when I try to access general settings I get a popup that says unfortunately, settings has stopped. Any idea on this or do you guys need anything else like a log file. If so could you please let me know how to get the log file. Thanks
Does no body have any thought on how I can fix this? I'm new to this ROM I am used to CM but changed because of the bugs in it. AOKP so far only has this one bug but I kinda need to access my settings. I flashed a newer nightly build that doesn't even have the settings option. So please any help would be great
No one can help you here as this is for a different model s3.
I will get a mod to move it for you.
Edit: Done, thanks @Faiz Malkani
Good Luck.
If the settings option was taken out of the newest nightly then that pretty says that its a known problem to the dev and will get fixed later
Hello,
I am new at building a custom kernel, and I seem to have no luck at all. I was wondering if some could give me guidance.
I have loaded CM12 on my V500 using TWRP. That all worked fine. I then compiled just the kernel boot.img and loaded it (this was a test to see if it would work, after this I was going to make my code changes in the kernel source code), which gave me:
:Footer is wrong:Signature verification failedOk I figured that the bootloader did not like the signature. And this is where I have gotten stuck, and was hoping someone could confirm I am right, or better yet, guide me as to where I am wrong.
As I understand it, it seems that I only have a few options:
Degrade to CM10 (JB) and use loki to bypass the signature.
Degrade to CM11 (KK) and use BUMP to overwrite the signature. Although, I am not sure how BUMPing is done since I cannot seem to find the codefire site that would BUMP my boot.img
Replace the aboot.img in CM12(LP) with that of KK, and then, use the BUMP method.
I would expect that a lot of people would be making modified kernel images and that it should be relatively easy, am I just not understanding something? Thanks for any help.
-Erik
https://forum.xda-developers.com/showthread.php?t=2628951
Should give you info.
Thank you very much sleekmason, this gives renewed hope I can figure this out.
One question sleekmason, I noticed that you did this on a V510, will that work as well on a V500? I assume that since I installed CM12.1 the V500 is now an AOSP, correct?
Sorry, ignore this, I did not read far enough down.
Thanks.