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?
Related
Do Not Bother xdandroid devs, with fillrate or hw3d being faster on donut than on eclair, plz they are not mages, stuff dont just magically work out of no were
Here is what iv been working on for the past couple of weeks, this was ready before but iv been holding back on releasing it because i was trying to get BT and gsensor fixed or at least attempted to. I figured i wont be able to do it or it will take some more time(if i decide to keep this up to date).Also the system img included is NOT my work it is from HTCClay, the zimage and rootfs.img is from me, what i did to get hw3d on donut was to change the hw3d driver configuration from eclair to donut,for the rootfs i edited and fixed a typo in wpa supplicant part , it was causing wifi to scan and then crash, but now its fixed. This port is not perfect expect bugs
Go ahead and try games and benchmark's this build should be pretty fast.This Rom is based on Cyanogenmod, also donut does not have fillrate bug, so 3d apps and overall system should be faster
I get 4.5mflops in linpack if thats impresive?
Click to expand...
Click to collapse
Screen shots:
Initial Release
Now to the good stuff currently working:
wifi
hw3d
JIT (Working Confirmed by babijoee)
gsm
Data?(i dont have a data plan you have to test for your self)
SDcard
Brightness control
Contacts syncing from SIM
Market (working fine now)
Now whats not working:
BT
gsensor( it works but it seems axis are reversed)
GPS? (probly not havent test so goes in here)
Click to expand...
Click to collapse
[Root access fix][08.01.10]: Place this in Storage Card/andboot/conf and replace the file
http://www.mediafire.com/?sn84lv46b9a244l
Click to expand...
Click to collapse
Update:7.22.10
Added:
AWD launcher
Advance Task Killer
Different Contact app version SIM sync working fine now
AOSP osk, fixes market problems and i also update market app to a newer one
Click to expand...
Click to collapse
Update:7.23.10
Removed some unused apps
Updated zimage to latest one
Still no root, im still looking into this
Click to expand...
Click to collapse
To make shure Hw3d is working fine restart phone after first boot
Compache is disabled on first boot, make shure you activate it in spareparts
Download Link:
Initial Release
http://www.mediafire.com/?z55tvxmb5gldydx
Update 1 07.22.10
http://www.mediafire.com/?zyj8pg53z9q562e
Update 2 07.23.10
http://www.mediafire.com/?e0m32ta3lq0xdn0
Link to original system thread:
http://forum.xda-developers.com/showthread.php?t=654771
Click to expand...
Click to collapse
Also the zimage and rootfs provided are not the latest one, i will try to update the zimage, rootfs i cant because it breaks hw3d for reasons that i dont know
And Last but not Least
Thanks To:
Phh (for teaching me how to compile the kernel and all the quirks that go with it, and ofcourse baring with my noobish knowledge on Android)
Babijoee (helping me figuring out stuff and overall help)
Stinebd (for teaching me how to compile android from source and baring with my noobness, and overall editing and stuff of rootfs)
hamagc
dcordes
Cass
and everyone else i forgot
BTW: this is Unholy from #htc-linux,#xdandroid
reserved for future updates
wooooooooooooooooooo 3rd post
Testing and posting feedback right now
Edit:
I think you should remove the boot command or value
Code:
acpuclock.oc_freq_khz=700000
as some people's device such as my own won't boot on those speeds.
gprs works
A few fs when trying to open app menu
Also you are welcome to steal my startup configs
as i think you shouldn't provide a specific / custom one as other people may want to use this
And it does seem that JIT is enabled
Market works fine
Hrmm no notification/ringtones. Will try a reboot soon
Running neocore crashed phone. Rebooting.
babijoee said:
wooooooooooooooooooo 3rd post
Testing and posting feedback right now
Edit:
I think you should remove the boot command or value
Code:
acpuclock.oc_freq_khz=700000
as some people's device such as my own won't boot on those speeds.
gprs works
A few fs when trying to open app menu
Also you are welcome to steal my startup configs
as i think you shouldn't provide a specific / custom one as other people may want to use this
And it does seem that JIT is enabled
Market works fine
Hrmm no notification/ringtones. Will try a reboot soon
Running neocore crashed phone. Rebooting.
Click to expand...
Click to collapse
thx for the feedback babijoee really apreciate it, neocore works fine here, 18.1 fps with sound,20.9 without sound
I have a little trouble, which comes with the space key on the keyboard and suddenly closes my process: android.inputmethod.latin
So it is impossible to conduct a search or a message of several words.
Otherwise, almost perfect, some delays, but I use it on a Diamond 100.
skypy said:
I have a little trouble, which comes with the space key on the keyboard and suddenly closes my process: android.inputmethod.latin
So it is impossible to conduct a search or a message of several words.
Otherwise, almost perfect, some delays, but I use it on a Diamond 100.
Click to expand...
Click to collapse
witch version are you using?, anyways i will look into that, thanks for reporting it
Edit: osk is working fine here, make shure you are using latest version dated Update 2 07.23.10, and if it the phys keyboard that is also working fine
I use the latest version: 7.23.10.
I will try to clean up properly.
skypy said:
I use the latest version: 7.23.10.
I will try to clean up properly.
Click to expand...
Click to collapse
yea delete data img, start from zero osk should work fine
Sorry for the off-topic, but how did you port this rom from the mytouch.
kdub94 said:
Sorry for the off-topic, but how did you port this rom from the mytouch.
Click to expand...
Click to collapse
search for a guide on touch pro>android development>android cooking
I have been trying for a clean base, same worries, concerns Diam100? French language?
skypy said:
I have been trying for a clean base, same worries, concerns Diam100? French language?
Click to expand...
Click to collapse
im no longer going to keep updating this rom, to many bugs stability issues plague it, JIT makes everything unstable, so i am now in the works of releasing another donut rom, this time its goin to be based on a ASOP rom, it will be themed by me, when its ready i will release it so stay tuned
I trying this build on my Topaz, is good and very fast.
But why WiFi cannot find networks?
DmK75 said:
I trying this build on my Topaz, is good and very fast.
But why WiFi cannot find networks?
Click to expand...
Click to collapse
as i said before you have to use my rootfs, if not wifi will break it is stated very clearly on first post
Donut AOSP released Follow this link http://forum.xda-developers.com/showthread.php?t=739730
test it now post feedback in a few minutes
Ok my Feedback
Compcache -- work
jit ? didnt found any settings oO
headphone -- works
market -- works
widgets -- work
linpack -- 3.4 mflops without overcloack
Mufflon12 said:
Ok my Feedback
Compcache -- work
jit ? didnt found any settings oO
headphone -- works
market -- works
widgets -- work
linpack -- 3.4 mflops without overcloack
Click to expand...
Click to collapse
there is a working and not working list already, and JIT is always on.
i cant sync my kontakt via google oO mail and kalender works !
Mufflon12 said:
i cant sync my kontakt via google oO mail and kalender works !
Click to expand...
Click to collapse
gmail sync if i remeber right worked just fine.
I just did a software update check, and it came up with a new OTA firmware. It's also listed on the HTC support site.
yup - it's here too.... updating now.
Let's see what it do
Screenshots of versions when it completes would be nice.
Wonder if theres a new radio.
edit: from a post below:
32.44.00.32U_5.09.05.30_2
2.6.32.15
2.10.405.2
downloading as we speak... Damnit! well, its not gingerbread..
The RUU has been out for a while, been running it over a week now...doesn't do a lot but you now get the voice mic on the keyboard and new radio (well, old but new to stock WWE ROMs)
I'm very disappointed
They still haven't fixed the AAC (he-aac v2) bug. What's the problem with implementing the patch google have released HTC???? I guess I have to delete my whole music collection and re-encode into ogg instead.
Talk about multimedia phone!
Also peep is messed up again, to bad since it worked fine in 2.2 since twitter fixed the bug since apparently HTC was to lazy to try themselves.
It seems I'll be getting a Samsung device next time...
*** EDIT *** Forget about the peep issue, it started to work after a few sync tries but the music issue is there and that's what bugs me the most...
EddyOS said:
The RUU has been out for a while, been running it over a week now...doesn't do a lot but you now get the voice mic on the keyboard and new radio (well, old but new to stock WWE ROMs)
Click to expand...
Click to collapse
Any consensus on the new(ish) radio?
Seems to work fine, it's been out a while anyway
has someone extracted the new radio yet?
It's not new, it's been in the radio thread for ages, see my signature for version
It's here anyway (link from the radio thread)
http://android.adamg.co.uk/bravo/radio/32.44.00.32U_5.09.05.30_2.zip
owziee said:
It seems I'll be getting a Samsung device next time...
Click to expand...
Click to collapse
Good luck with that one! The Galaxy S issues (GPS, lag etc) seem far worse than the Desire's. I'm sure these things will be fixed, but then again I'm sure your AAC issue will too - eventually!
Regards,
Dave
foxmeister said:
Good luck with that one! The Galaxy S issues (GPS, lag etc) seem far worse than the Desire's. I'm sure these things will be fixed, but then again I'm sure your AAC issue will too - eventually!
Regards,
Dave
Click to expand...
Click to collapse
the S in the galaxy stands for **** lol
EddyOS said:
It's not new, it's been in the radio thread for ages, see my signature for version
It's here anyway (link from the radio thread)
http://android.adamg.co.uk/bravo/radio/32.44.00.32U_5.09.05.30_2.zip
Click to expand...
Click to collapse
many thanks eddy
Any issues for Orange users who have unbranded their Desires?
Sent from my HTC Desire using Tapatalk
Just installed it in 5 minutes.. my phones seems a little bit zippier then before.. dont know what the android patch is.. but it seems ok !
I become a signature error with my rooted Desired (rooted with unrevoked).
Any ideas?
Maybe with a rooted device you need to use the RUU version, but you loose the root
If you were branded first you'll need your gold card
Did anyone encounter wifi problems after the update? On my device I get I can't enable it anymore. Reboot doesn't solve the problem.
PierreLeDark said:
Did anyone encounter wifi problems after the update? On my device I get I can't enable it anymore. Reboot doesn't solve the problem.
Click to expand...
Click to collapse
no wi-fi problema on my device. Maybe you need to remove a not compatible app or make a hard reset
Scoot CyanogenMod 7.1.0 RLS3
This is a build I have compiled from the official CyanogenMod source files and adapted for Kaiser/Vogue. Feel free to give it a go at your own risk!
Well, it still isn't quite as snappy as Froyo and the camera still doesn't work properly but it's probably about as fast as Gingerbread will get on our devices. I'm bound to have messed a few things up but i'll continue to work on it when I get time
All the usual things are working as far as i know, GPS works fine for me but the camera is as always not fully functional.
All of this is thanks to the guys working on the CyanogenMod roms and of course, none of this would work without all the hard work on the kernel so big thanks to dzo, vilord, l1q1d etc...
-------------------------------------------------------------------------------------
RLS 1:
Initial Release
Includes most of the Google Apps including Maps, Gmail etc..
Latest Market is included
RLS2:
Built from the latest 7.0.2 source
Optimised EGL for our devices
Updated Market
LDPI and PNG optimisations to save space & increase speed
ADW Launcher updated
Loads of tweaks and status bar changes
Updated RIL lib
Loads of fixes and optimisations
**I recommend leaving the phone for 5 minutes after installing to sort itself out and cache apps etc...**
RLS3:
I can't really be bothered to list all of the changes, there are quite a few but I just compile the thing, the changes are in the CyanogenMod repository. I have included the updated RIL and all of the Google Apps are up to date. The camera is still ****e but that's a driver issue. This release hasn't been heavily tested as I don't use my Kaiser as a main phone anymore So i'm sure you will find issues in which case we can sort them out as and when. Enjoy!
LINKS:
RLS1:
English: http://www.mediafire.com/?6708ud8kc9l9ex5
All Languages: http://www.mediafire.com/?amhd996w81xfldp
RLS2:
English: http://www.mediafire.com/?yhsc6jyl47wgpkv
All Languages: http://www.mediafire.com/?v3hhbh5tufoedfp
RLS3:
English: http://www.mediafire.com/?76vn9k0cx3debzd
All Languages: Coming soon!
Google Apps
28.04.11 : http://www.mediafire.com/?4yc9ubn2m513k3q
07.08.11 : http://www.mediafire.com/?c86rpae5kopdicc
I think that's it for now, have fun
OOOOOyyyyéééééé OOOOoyyyyyéééé !!!!
download'n !!!
thinx scooter & all android developers for our old kaiser
'll try your build this night & report any bugs...
keep working i realy apreciate your work sccooouut
xcuse my stupide bad english
cordialement esolks.
scooter1556 said:
Scoot CyanogenMod 7 alpha RLS1
This is a build i have compiled from the official CyanogenMod source files and adapted for Kaiser/Vogue. Feel free to give it a go at your own risk!
This is an alpha and still needs a fair bit of work to get it running to it's full potential but you can get an idea of what it will be like. Feel free to report any bugs that you find, by this i mean application crashes and things that don't work or look correct. I already know the system can hang and it isn't as fast a froyo
I have had to make a LOT of modifications for this to work, some of which may affect battery life but i haven't tested it for long enough to know so let me know how it goes. I'm bound to have messed a few things up but i'll continue to work on it when i get time
All the usual things are working as far as i know, i have not tested GPS fully and the camera is as always not fully functional.
All of this is thanks to the guys working on the CyanogenMod roms and of course, none of this would work without all the hard work on the kernel so big thanks to dzo, l1q1d etc...
-------------------------------------------------------------------------------------
RLS 1:
Initial Release
Includes most of the Google Apps including Maps, Gmail etc..
Latest Market is included
LINKS:
RLS1 :
English : http://www.mediafire.com/?6708ud8kc9l9ex5
All Languages : Coming soon hopefully.....
I will try and get some screen shots posted for those that like pretty pictures
I think that's it for now, have fun
Click to expand...
Click to collapse
This might be a stupid question but I need to ask anyway...is CM 7 based on gingerbread?
-Arturo- said:
This might be a stupid question but I need to ask anyway...is CM 7 based on gingerbread?
Click to expand...
Click to collapse
It is indeed
scooter1556 said:
It is indeed
Click to expand...
Click to collapse
Excellent, thanks Scooter.
downloading now keep up the good work man
woot...gonna give it shot ... hoping for not getting same data/wifi reboots
woow, million thanks to you scooter
finally a gingerbread based build for our kaiser
btw, which kernel do you suggest for this build?
thanks in advance
Hmm for some reason I cannot boot to android the phone has been stuck in boot loop for the last 15 minutes. I have an app.img file with about 80 applications so this might be a problem I'll try to boot it without the app.img. Both data and system on sd card imgs + latest '25 kernel.
Edit.
Ok I have removed the apps.img and it still doesn't boot.
I have noticed that there have only been modules for '32 kernel included in the build. Should it work with '25 kernel with proper modules added?
I'll wait for All Languages version to test it with the new kernel.
1. this was my first attempt to instal android on nand.. noob here ;P
downloaded kernel VOGUIMG-320-FROYO-01-16-11.NBH, then changed with editor to kaiser and painel 2. Install occured ok.... but phone isn't working.. "no service".
2. I do i see my batery status? can only see that bar on the top but don't no accurate bat status in %.
3. after this install can i install another another version overwrithing this one? for example now the phone isn't working so i want to change to another version of android can i simply put another "androidinstal.tar" in andboot folder and install?
Thanks and sorry for this noob questions...
chinomoreno said:
1. this was my first attempt to instal android on nand.. noob here ;P
downloaded kernel VOGUIMG-320-FROYO-01-16-11.NBH, then changed with editor to kaiser and painel 2. Install occured ok.... but phone isn't working.. "no service".
2. I do i see my batery status? can only see that bar on the top but don't no accurate bat status in %.
3. after this install can i install another another version overwrithing this one? for example now the phone isn't working so i want to change to another version of android can i simply put another "androidinstal.tar" in andboot folder and install?
Thanks and sorry for this noob questions...
Click to expand...
Click to collapse
YES! you can
To view Battery percentage, you need to set that in Cyanogenmod Settings (correct me if I'm wrong here since its been ages when I used CM build)
Yes, you can do that it's actually very simple. Just remember to edit your .nbh before every install if you are changing versions (donut, froyo, eclair).
Cheers. Welcome to Android world
-Arturo- said:
Hmm for some reason I cannot boot to android the phone has been stuck in boot loop for the last 15 minutes. I have an app.img file with about 80 applications so this might be a problem I'll try to boot it without the app.img. Both data and system on sd card imgs + latest '25 kernel.
Edit.
Ok I have removed the apps.img and it still doesn't boot.
Click to expand...
Click to collapse
Try a .32 kernel, also i have only tested it on NAND so it may be an issue with Haret. To be honest we're lucky it works with the .32 kernel so i expect problems with the .25 kernel. Sorry
scooter1556 said:
Try a .32 kernel, also i have only tested it on NAND so it may be an issue with Haret. To be honest we're lucky it works with the .32 kernel so i expect problems with the .25 kernel. Sorry
Click to expand...
Click to collapse
Yes I have noticed that there have only been '32 modules included in the build.
I think I'm going to skip the '32 kernel as It was acting up on me in the past. I'll try nand install in the evening hopefully it will work. Thanks Scooter.
-Rif- said:
woow, million thanks to you scooter
finally a gingerbread based build for our kaiser
btw, which kernel do you suggest for this build?
thanks in advance
Click to expand...
Click to collapse
I recommend using the latest .32 kernel you can find, either one that L1q1d has compiled or one from Clemsyn's thread You can find the latest kernel here: http://androidhtc.git.sourceforge.n...7c0bf5edc4f5c6d64ce4df29254e8332ce26b;hb=HEAD
Well have installed 6.1 and phone now works... =)
Will wait until a new version of this one to come out and then try again...
- Already found how to show percentage in bar status thanks dark_prince.
- Thanks for advice slimas, to edit .nbh do i need to reinstall kernel? and can i reinstall without mess up with previous android install or do i need to install again android?
- Some bugs that occurred to me .. sometimes bar on the bottom disappear can't access apps... ; some freezing sometimes, do you guys recommend to overlock? if so how to do it? Weather widget can't find info too lol not a serious prob...
I'm reading forum and these are some questions i couldn't find answer, for now i think that's all.. i'm enjoying android on kaiser think this is the time i will change forever...
thanks for fast feedback any good tips are welcome ;P
chinomoreno said:
- Some bugs that occurred to me .. sometimes bar on the bottom disappear can't access apps... ; some freezing sometimes, do you guys recommend to overlock? if so how to do it? Weather widget can't find info too lol not a serious prob...
Click to expand...
Click to collapse
The bar at the bottom of the scrren can disappear if you swipe down on the screen, it is a bit random but is a flaw in ADW launcher. To get it back you need to press the 'menu' button and go to 'settings' then go to 'ADW Settings, UI Settings and untick 'Dockbar'. Re-select 'Dockbar' and exit settings and it should be back I expect some freezing, it is still under heavy development and our devices are quite limited hardware wise so there won't be any miracles yet I overclock my Kaiser to 500Hz using ATools, a lot of people don't recommend it but it is what i have always done and i have never had any problems, it speeds the phone up a fair amount. Just tick the option when editing your NBH. The phone obviously needs to be connected to data or wifi for weather widget to get location information, i just tried it with wifi and it worked ok, there may be an issue with data though, i'll look into it Thanks for testing.
CAMERA
camera is not working properly but it looks awesome i will try to apply the update from previous cm to see if this will work
camera
after applying the update android can`t start so i am going reinstall it
Hi,
I am really full of compliments about the good work of some guys that have done a good job in building the actual CyanogenMod versions for Wildfire S.
Thank you sooo much!!
But what I currently do not completly understand...
Why are most of the CM users really happy about version 10.2 or version 11.0 (like orig. CyanogenMod or WFSY) when those versions - last version of CM 9.2.2 included - do not even have GooglePlay/PlayStore and Data2SD (or Link2SD) installed?...
The last (and obviously most advanced CM version) CM9 (alpha9, v.9.2.2) would already be a wonderful solution for the WFS phone (I tested it!!) and it is said to be nearly finished (even video camera is working now at the version of Olivier) BUT both mentioned, absolutly necessary components are missing (and nobody mentioned it yet). Or what can I do with a phone where I cannot install new apps at all?..
So what is it that I misunderstand?...
I would be very happy if anybody could inform me about how I can find a version that has a complete set of system apps or how/where I can find both missing components to complete them by myself. (and even more happy if the cyanogenmod update function would still find some updates)
Otherwise I would guess that not any of the existing CM-based versions for Wildfire S can be used at all...
Should all the past work for creating a CM version (Android 4.x !!) for the (unfortunately!) one and only COMPACT smartphone on the world, 'Wildfire S' (I must admit, it is in fact!!) should have been completly in vain ???... I couldn't believe it.
Thank you guys very much for your nice explanations!
All the best to this wonderful community,
from Falk
CyanogenMod said:
Google Apps are the proprietary Google-branded applications that come pre-installed with most Android devices, such as the Play Store, Gmail, Maps, etc. Due to licensing restrictions, these apps cannot come pre-installed with CyanogenMod and must be installed separately.
Click to expand...
Click to collapse
Gesendet von meinem Xperia Z mit Tapatalk
Hi Olivier,
many thanks for your tip. You did not mention the point directly but I could answer most of my questions by mayself then.
Now I installed CM9 'cm-9-20140720-Olivier-marvel' together with 'CronMod-INT2EXT+_signed'. Works pretty fine!
Only little questions have been left now...
1.) How can I sort my app icons by subjects/folders (s. HTC Sense)? This Trebuchet launcher does not seem to support anything like that. If there is no chance, which launcher would you suggest instead?
2.) There is no really 'useful' version of CM10 or CM11 for WFS yet, is there? I couldn't find. Do you think there will be s.o. still working for a final version next time?... (why is Wildfire but not Wildfire S an official CM development?)
2b.) At your current version CM9, is there any problem left that should still be fixed? Everything works fine here yet...
3.) Therefore the OTA updater for CM would be a fine feature like in CM9 vers. 9.1.0 (but no updates found yet!). But your current CM9 version does not support it any more. Any reason for that?
3a.) Are updates possible anyway without flashing the whole ROM?
3b.) Is there anybody managing OTA any update of CM (v. 9..11) for WFS?
3c.) Are OTA updates from cm9 to cm11 possible?
4.) Skype does not react when clicking the icon to start it. Any idea what is the problem?...
5.) Some system programs (e.g. contacts or call manager) do not have that nice design than before. There is no chance/choice to exchange them?... (if yes, how and where to find alternatives?)
Thank you again for your final responses!
First of all this really does not belong in the development section, in Q&A perhaps.
And you just can't ask every single think that comes up in your mind, you gotta search a little bit and try it out for yourself.
Now, 1. Trebuchet does support folders but not auto-arranging. Most of the popular launchers support this.
2. The current CM10 and CM11 are perfectly functional and working. Though they lag a bit (which is fair considering our old device). And the wildfire only had an official CM7 which is very old now.
2b. If you don't have a problem it does not contain a problem.
3. OTA is working for CM11. But for CM9 a OTA makes less sense considering that its stable now.
4. No idea.
5. Again you have to look for yourself, nobody can babysit you all the time.
thanks very much!
Okay, maybe question 1 might belong to Q&A. That's it. Sorry.
To make you understanding (sorry to write again so much!)...
to 1.) Did not expect that it would support it. So I did not even search for!... Thanks, this drag/drop solution is more than perfect!!
to 2.) Sorry, then I am not able to find them. I searched a lot and found actual version like 'WFSY11.0-WFS-V5.5, 20140723' or 'cm-11-20140726-NIGHTLY-marvel' where not even back button or Android option menu worked. Lots of functions are missing. I did not try 'cm-11-20140810-NIGHTLY-marvel' but do not expect more within one month. The same with cm version 10.2. In a thread I read that it was give up because cm11 is already working better.
**** So would you please give me the link to the finished versions of cm10 and cm11, please? ****
(a patch for the video camera problem seems to be existing shortly now...)
to 2b.) My first problem I saw was missing updater in cm9 for version 10 and 11. And the strange Skype problem. And video problem was fixed JUST before!! BT seems to have restrictions as well. So there is good reason to ask this question!?..
to 3.) It seems as if simple updating from Android 4.0 to 4.2 (cm10) and 4.4 (cm11) isn't possible!?... Officially it seems to work. E.g. OTA of Samsung offered update from 4.2.2 to 4.4. Strange!... How/why does it work here?...
Remark: So I suppose it is CyanogenMod which does not support it... It will not work without 'Titanium Backup' here...
to 4.) I suppose you will have the same problem!? Maybe you have opportunity to try out quickly!?... Skype really does not seem to run on WFS cm9+INT2EXT+. Isn't that strange?... (I reinstalled it already. No chance.)
to 5.) I asked this HERE because it belongs to SYSTEM apps (contacts or call manager) that cannot easily be exchanged, as far as I know!... Can they?...
There is one thing I would like to add, after your remarks to my point 2... Maybe I could not find the right sources. But this is because there is no resource pool (about WFS at XDA anywhere. Instead there just appear 'lonely' links in some threads. And instead of telling/explaining the systematics (if there is one) you guys generally just mention the fact (e.g. a link). So this makes it hard for non-insiders. You understand what I mean?...
(so e.g. I will have to ask (in another thread) how I can find the 'FM radio' app (no streaming!) which is missing in CM9 - instead of just looking at the right page where they are collected)
I would be really happy to get to know at least where you guys have found the informations for all what you do when 'cooking' new versions, etc.!...
Cause then I would have read about all that much more!... Instead of blaming me. Sorry, if I do not have that general info that you got already.
Maybe you understand better now!?... Would be fine.
Anyway, thanks a lot for your short repsonses. Have a nice day!
Again only things that are directly related to development are to be placed in development section. And NO if you have a problem with a rom you have to ask it in Q&A. Read the development forum rules in the stickies attached to the top of the section.
And you could also try reading through the stickies in the general section. It will give you some understanding.
Now CM10 and CM11 works, the threads are pretty high in the development section, you can find them if you look. The version of CM11 you used is the right one (the NIGHTLY) and back button does work. Try the later versions. Officially updating to a higher version is different and large corporations can spend time and money to make it work. But it just is not possible (or rather safe) with the variety of unofficial roms. You could try but most probably fail. You can install different apps for call and messaging and they will work. Search for those apps. CM9/10 works fine and have very less amount of problems. Now remember that this is a very old device and the devs are doing it NOT as a profession. So every single thing will never work.
Now as a last your largest problem is you think everything will be written somewhere in front of your eyes. It will not be. You have to use Google before asking a question. And also you just have to calm down and fix your attitude.
aWFSuser said:
First of all this really does not belong in the development section, in Q&A perhaps.
Click to expand...
Click to collapse
That was my fault, I'd moved this out of a thread and mistakenly put it in the Development section. All sorted now.
thanks again for your time to answer!!
I know, I sound as if I would not know which hard work you guys do. But I do, aWF Suser. And I mentioned that already in the beginning.
And I have heard already from your collegues that it would be a good idea if things could be organised some better. The official cm versions e.g have a central resource pool. Or the android-Wiki and CM-Wiki notes are all out-dated (from 2012) !!... Etc.
But PLEASE understand this more as a suggestion than a criticism - from a user that in your eyes only expects and criticises but cannot give. This is not the case!
Thank you!
I know it is an old smartphone I have. And I would have bought a new one already a long time ago. But even Samsung Galaxy Mini is too big in size and some important functions you will only find in the big version. Why is that so? Nobody can explain!... (i would pay the same price for a small phone!!! Handy devices must not be worse and more expensive than big ones!!)
The WFS is just the only really COMPACT smartphone all over. And I am sad that the industry detected a trend to bigger displays. The opposite is the trueth. Nearly all my friends e.g. like to have a compact phone but those always a beginner versions/hardware which cannot be understood at all.
Really sad. It is a big strange hole in products on market, isn't it?...
Unfortunately you did not give me tips how I could find a way to get more familiar with what and how you guys are doing. Is it a secret? I could imagine to do some work here as well. I am very interested in how you are doing your development work!...
Thank you again...
Now it is sure...
Olivier's last CM9 version still has bugs, not only the problem with lgCamera and Skype but also at the akku loading status.
It seems as if it is not correctly refreshing. The loading curve (s. settings) slows down a lot and shows e.g. after 4 hours loading still 43%. But after rebooting it changed to the right value finally: 100%.
So again my question before, as Olivier unfortunately put away the OTA update function (but ment that it is not necessary anymore):
How can this version be fixed?
As far as I know you don't offer patches but only complete ROMs...
Okay first sorry for being rude as posting in the development section was not your fault.
Now the main problem with our device is not that its old but that it has a armv6 cpu which is not supported by later android versions. So development for developers is tougher and bugs will remain. I mentioned the general stickies before there you can find some useful guides.
And have you installed GAPPS in CM9 because some apps depend on it and won't work without it.
And just to be clear, I'm not really a developer but just a user like you.
I never said CM9 doesn't have bugs. It's is clearly stated in its OP that:
modpunk said:
This ROM is not meant for daily use!
Click to expand...
Click to collapse
Hallo Olivier,
never mind. But I just understood it like that. As you gave the reason for the OTA non-support in your ROM.
So if I misunderstood you... what is your reason then?...
In fact it would bring us forward if you could please comment my questions and/or give tips to solve the mentioned problem.
@so please give me a chance to fix the akku status bug. This is really annoying.
Can you confirm that problem? And if so will you fix it?
And if so how can I update it by OTA updater? Or alternatively at least by a patch but not by a new complete ROM !?...
@TO the Skype problem...
First of all: can you confirm my problem?...
To your question: I used your ROM from 20th Aug. (119.518 KB) This one contains already gapps, I suppose. Cause Google Play and the other stuff was already installed!...
@TO lgCamera...
This wonderful camera app worked fine with EQDKP (v.2.3.5) but now it is too slow and hops a lot. Can you confirm that?
And if so do you have any idea why this is a problem?...
@how can I add FM Radio (analog) support?...
Thank you very much for your feedback!
PS: So if the last version of CM9 is not ment for daily use... which CMx version is it then? Is there none?...
Currently your cm9 works fine. Only those three problems so far...
Do you care for my bug messages?... (or where can I post them?)
Hallo aWF Suser,
yes, I know the problem with the arm version. You must not excuse for any bug in CM.
I do not have problems with bugs. I have more problems when they cannot be fixed easily (missing OTA updater) or errors are not heard or cared for so that bugfixes will not be available at all...
By the way the phone Wildfire (without 'S') is supported by Standard CyanogenMod and also has an ArmV6 processor!...
You mean I should read again the forum rules?... What is it that is is still annoying you in my style of writing?...
Olivier's ROM I used (s. previous message) obviously contained GAPPs already. GooglePlay atc. was already installed. So this should not be the reason, should it?...
First of all: can you confirm my Skype problem, aWF Suser?... I expect it to be in each CM9 version!...
Thank you very much for your support!
PS: By the way, I have compatibility problems when flashing ROMs. For nearly each ROM I have to change the recovery. Is there any that can read all 'formats' of zip files?...
Falk2 said:
Hallo aWF Suser,
yes, I know the problem with the arm version. So you must not excuse for any bug in CM.
I do not have problems with bugs. I have more problems when they cannot be fixed easily (missing OTA updater) or bugfixes are not available at all...
By the way the phone Wildfire (without 'S') is normally supported at CyanogenMod and also has an ArmV6 processor!...
You mean I should read again the forum rules?... What is it that is is still annoying you in my style of writing?...
Olivier's ROM I used (s. next message) obviously contained GAPPs already. GooglePlay atc. was already installed.
So this should not be the reason, should it?...
First of all: can you confirm my Skype problem, aWF Suser?... I expect it to be in each CM9 version!...
Thank you very much for your support!
PS: By the way, I have compatibility problems with ROMs. For every second ROM I have to change the Recovery. Is there any that can read all 'formats' of zip files?...
Click to expand...
Click to collapse
The Wildfire is listed officially only for CM7 (gingerbread) . After that it has not been supported. I am not asking you to read the rules, in the stickies in general section there is a thread that lists some guides to some useful things. And is OTA that necessary because in most cases a dirty flash is enough to upgrade from one version to another as long as its the same android version. Upgrades between different android version would not be possible even with OTA (as lots of things change, it will probably end in a bootloop). I am not using CM9 currently so can't speak for that.
So then which CM version are you using on your WFS? And why?
I flashed cm11 shortly but it still has too many problems. E.g. the camera app crashes after successfully recording a video, the launcher only has two pages, launcher does not seem to support folders, etc.
Do you know where I can find the actual todo list? (AndroidWiki unfortunately is not maintained anymore!)
I will give Paranoid 4.45 a try yet. Maybe this is better!?...
Otherwise I will keep cm9 and hope that we can find out why Skype is not running.
Oooh, that is important... I can make a 'dirt flash'? This is very fine!! Then OTA is not that necessary, of course. But there is still no reason to left it away, is it? Especially because all this observing and searching for the update is NOT necessary! Can't understand Olivier here...
Could you comment my PS as well, please?...
(error log: "cannot load volume /misc. Can't partition non-vfat: /sto .. (vfat)")
http://forum.xda-developers.com/htc-wildfire-s/development/cyanogenmod-10-t2908631
is there any better rom than this rom? how can i improve battery life with screen on? i want it for daily driver, i do not use bluetooth ad2p but i dont know what armv7 features means...
for me its affordable atm and give a new life to the oldie and shiny wfs
Which rom is the most stable for everyday use?
(With working wi-fi tethering)
Hello,
I detected the following systematic problems of cm9..11
1.) Skype cannot be started at all. It does not even react on a click of its icon. And no error message appears.
2.) the akku load status is shown incorrect during load process. E.g. after 4 hours load it shows 37% instead of true 100% (which is shown after reboot).
3.) The wonderful app 'lgCamera' runs very slow and jerky. This was fine in Android 2.x versions.
4.) the FM radio app for the WFS radio tuner (no internet radio!). How can I find it (and flash it into the system folder as a system app)?
I suppose that everybody can confirm my problems!?...
Are those already known by the development team? Cause I wonder that they are not fixed in ALL CyanogenMod versions yet!
Will there be a chance to expect their fix soon?...
5.) Furtheron I have big compatibility problems when flashing cm9..cm11 ROMs and others. Error message: "cannot load volume /misc. Can't partition non-vfat: /storage (vfat)". For nearly each ROM I have to change the recovery. Currently I change between the following recoverys (one of them allways works):
twrp-2.2.2.0, twrp-2.7.1.0, Phil-Z 6.43.7, cwm-5.0.2.8, cwm-6.0.5.3. Nobody else having that problem?...
Is there any recovery version that can read all 'formats' of zip files?...
Will there be compatibiliy at least at the backup files between all of them?...
Thank you VERY much for a quick help!
1.) not compatible anymore, say Thanks to Skype
2.) This is probably problem with battery not reading voltage correct anymore on charger (happens) for me on all roms even stock. (After 100000 of flashes and almost 3years old down sucked battery
3) ics and up isn't made for this phone, slow downs and other incompatibility can happen.
4) There is a solution called spiritfm(free) Google it, you will find the xda thread.
5) twrp 2.2.2.0 and cwm 5 is working on all ROMs beside newer kk builds (needs recovery compiled with TLS support, newest ones available)
Greetings Kevin
Hallo Kevin,
I am so glad that you answer! Thank you very much!!
to 1.) Yes, I realised meanwhile that Skype 4 ist still running fine. So the reason why the new Skype 5 version does not work on Wildfire S (or even on all CM versions of all devices??) you don't know!?...
to 2.) So this is a general Andrid 4.x problem of Wildfire S device only?... (cause e.g. on Galaxy S4 stock (of my girl-friend) it works fine!...
to 4.) Thank you. I installed this free version '0918fr.apk' but I get the error message (su rights confirmed): "Error: No FM accessible. SU: 0 Fm:BC2 SU:0 Bt:3 Ht:0 Mo:BCU". It does not seem to be compatible although I have read everywhere that it should work. Is this maybe antoo old version? Or what can be the reason?...
to 5.) So I used newer version 'cwm-6.0.5.3' and 'twrp-2.7.1.0', as I mentioned, but then these versions do not support older version than KK. E.g. 'CronMod-INT2EXT+_signed.zip'. This is the problem. Any solution?...
Is TLS ment as 'Thread-local storage'?...
Another short request:
a) Video recording with cm11 on Wildfire S works now without any patch. But if I record a video longer than about 5 seconds and I want to watch it directly after having stopped recording (timeframe about 7 seconds) then the camera app crashes. Can you confirm that on Wildfire S? What can be the reason?...
If Olivier's camera patch will help here as well I have not tested yet...
b) Management of Launcher and App screen is somehow circumstancial or not even possible. This is why the option 'Homescreen' is missing in 'Personalization' ('cm-11-20140816-Nightly') although the related screenshots of cm11 in XDA show this option!! E.g. App icons cannot be sorted alphabetically or cannot be manually moved within the screen. Or the home panel is the most left one instead of the middle one. Etc.
Any reason why the option 'Homescreen' was deleted (in XDA cm11 screenshots for Wildfire S still show it!! S. http://forum.xda-developers.com/showthread.php?t=2735775 )?...
c) CM11 OTA update suggests me 'cm-11.0.0-RC9' as the first in the list. Is this really more actual than the installed 'cm-11-20140816-Nightly' (version 11.0-20140816) ?...
d) In this version the Email system app is missing. Why?
Any zip to flash it anywhere? Or do I have to use one of the market?...
e) No warm reboot option available anymore in cm versions?...
Thanks for your help again, Kevin!
Many greetings, Falk
to 5.) I could solve that problem meanwhile by myself. I downloaded a modified version of cwm 6.0.5.3 here:
http://click.xda-developers.com/api...5.0] - Post #52 - XDA Forum&txt=the new build
But I still do not know what was modified! You?...
6.) you forgot the ever present mobile data bug at least for cm9 and cm10. Which no1 evens bothers to mention
Beeefalo said:
6.) you forgot the ever present mobile data bug at least for cm9 and cm10. Which no1 evens bothers to mention
Click to expand...
Click to collapse
Because it does not exist? I never faced any bug like that.
aWFSuser said:
Because it does not exist? I never faced any bug like that.
Click to expand...
Click to collapse
oh, its super present .
It was a "common" problem in cm9, cm10 based roms, at least judging from the various threads dating back to 2013. And as I discovered yesterday its also present in CM11 RC9 for me.
Occurence of the bug is very random and seems to be bound to certain providers which makes it hard to debug/fix i guess.
Sadly, from what I've read "deal with it and toggle airplane mode when you need mobile data" or "install cm7" are the ways to handle this bug.
cheers
Beefalo