Related
New to Kaiser. What's everybody's opinion on the best ROM out right now?
TIA!
anubus12 said:
New to Kaiser. What's everybody's opinion on the best ROM out right now?
TIA!
Click to expand...
Click to collapse
it all depends.. it's all personal preference.
Best way to decide is just to try it all out yourself.
Dutty's is most popular for the most part. Radio depends on your area etc.
I can't believe you have 150 posts and post a question like that. You should know already that everyone has their own opinion on what is the best rom. I will let you know that Dutty seems to be the most popular roms, but I don't use any of his roms cause I cook my own.
Just giving you a heads up on these forums. We have a lot of new people in here and a lot of these new people ask the same questions as you did.
i noticed that the radio performance varries by area also?
the best rom, which came bundled with the best radio, was removed from the Internet by HTC.
It had full dual core utilization, 3d drivers, multi-touch capability, flash 3, and ran Mac OSX.
I think it was called you_should_know_better v1.24.2234
otheruser said:
the best rom, which came bundled with the best radio, was removed from the Internet by HTC.
It had full dual core utilization, 3d drivers, multi-touch capability, flash 3, and ran Mac OSX.
I think it was called you_should_know_better v1.24.2234
Click to expand...
Click to collapse
boo ya, 150 post senior member burned by a 2 post junior member. good job there otheruser
dutty most popular
anubus12 said:
New to Kaiser. What's everybody's opinion on the best ROM out right now?
TIA!
Click to expand...
Click to collapse
dutty seem to develope the most popular. Its stable and there are several different versions. the WIKI's here are very good. I suggest you read and study and try some different ROM's and decide for yourself.
Sorry for the dumb question. Just got the Kaiser to try out for a few days only and am travelling. Just don't have the time to really evaluate the phone (not an excuse really). Have to return it if I don't like it. Hence the question to get the best feel. If I had more time with the phone, I would try them all.
anubus12 said:
Sorry for the dumb question. Just got the Kaiser to try out for a few days only and am travelling. Just don't have the time to really evaluate the phone (not an excuse really). Have to return it if I don't like it. Hence the question to get the best feel. If I had more time with the phone, I would try them all.
Click to expand...
Click to collapse
Travelling - RETURN IT?
You are travelling and willing to mess with your phone - you have GUTS man!
You know that if you mess with the phone you will most likely NOT be able to return it without putting it back to the shape it was in BEFORE you hosed with it?
All of that from someone who sounds like he has not done this before?
Whew - I am not worthy!
Bill
anubus12 said:
New to Kaiser. What's everybody's opinion on the best ROM out right now?
TIA!
Click to expand...
Click to collapse
I got Random Freeze and Hang using Dutys on my TILT. (i got the worse experience using it)
Once i change to ALEXs ROM ... everything allright... run smooth... and little tiny itsy bitsy small bugs.... fine with me
This may sound like a stupid question but I know radios work for reception but why did I lose audio on my device when i upgraded to dutty 6.1 release? I fixed the issue on the same day of course but I was just wondering why I lost audio.
redbandana said:
This may sound like a stupid question but I know radios work for reception but why did I lose audio on my device when i upgraded to dutty 6.1 release? I fixed the issue on the same day of course but I was just wondering why I lost audio.
Click to expand...
Click to collapse
because you have 6.0 radio, and will need to upgrade it to 6.1
tak.japan said:
because you have 6.0 radio, and will need to upgrade it to 6.1
Click to expand...
Click to collapse
Yeah i knew that but quite don't understand why it affects audio
Can the 2.1 version for Rogers can put onto the T-Mobile version of the HTC Magic or will it be problematic?
Looks like it works on 32a
http://twitter.com/Amon_RA/status/24101277025
http://twitter.com/Amon_RA/status/24113346424
http://twitter.com/Amon_RA/status/24116479740
Yeah i'm curious if it can be ported to us on 32b. Would probably work smoother than those legend ports
Sent from my U20i using XDA App
Anyone know if this has "Smart Dialer"?
Sent from my HTC Dream SparksMod using XDA App
is it sense ui?
asb123 said:
is it sense ui?
Click to expand...
Click to collapse
Yes it is sense
http://www.youtube.com/watch?v=1lNeYGQWymM
Come On Dudes! Do It! A Magic Sense Rom must run good on the G1!
Maybe somebody could replace the Sense UI for the Android original. The hardware is not so different, just a little bit more memory.
I want this ROM ported to HTC Magic 32B because since Android 2.x we always have memory leaks in the camera driver.
I definitely want this ported!
I definitely want this ported too! Especially if it finally bring Sense to the G1 without draining our battery in less than day. Or in another cases requires so many changes that it becomes too unstable.
hmmm what did rogers do that cyanogen didn't?
qipengart said:
Can the 2.1 version for Rogers can put onto the T-Mobile version of the HTC Magic or will it be problematic?
Click to expand...
Click to collapse
Some1 ported to 32b please please please
R3N0V4D0 said:
hmmm what did rogers do that cyanogen didn't?
Click to expand...
Click to collapse
Dude its Sense I love sense = o )
solaresdonis said:
Dude its Sense I love sense = o )
Click to expand...
Click to collapse
this is definitely possible. Most people Dont know that the cause for battery drain is a combination of:
1. swap
2. "optimized kernels"
These both exist to make sense roms usable on our phones, and they do make them usable but they drain battery.
the only advantage that this 32a build with sense may have is optimizations of the apk's and frameworks that could account for a speedier experience, and therefore introduce the possibility of cutting down on the two factors listed above.
It is very possible to do, and in fact easy. If the demand is high enough, i'll do it myself... add ideas/input here.
I definitely am up for a port
Sent from my Htcclay's SuperBad 3G using XDA App
jcarrz1 said:
this is definitely possible. Most people Dont know that the cause for battery drain is a combination of:
1. swap
2. "optimized kernels"
These both exist to make sense roms usable on our phones, and they do make them usable but they drain battery.
the only advantage that this 32a build with sense may have is optimizations of the apk's and frameworks that could account for a speedier experience, and therefore introduce the possibility of cutting down on the two factors listed above.
It is very possible to do, and in fact easy. If the demand is high enough, i'll do it myself... add ideas/input here.
Click to expand...
Click to collapse
Another thing to remember is that 32A's have about 100 mb more ram, so 32B's actually need some of those things to make them more usable. Anybody know anything about the radio that released with it? I mean, is it still a locked down 3.X rogers radio, or is it something 2.X, or even 6.X? Another thing of interest would be bluetooth, but I'm not sure if 32A's and B's share the same bluetooth chip. +1 for the port jcarzz, I would try it myself but I'm still learning. We should also try to extract the camara drivers, the way I understand it in CM5/6 we're using a hacky method with backported donut drivers and a few other things. We could really pull a lot from this.
Okay, so I looked a few things up and answered some of my own questions. It does include a new radio 6.35.16.19, but it's not something we can use. Maybe some of the guys who have JTAG equipment can experiment with flashing it. Since it's not a G1 radio we shouldn't get bluetooth working so cross that off the list too. Still a promising release though.
jcarrz1 said:
this is definitely possible. Most people Dont know that the cause for battery drain is a combination of:
1. swap
2. "optimized kernels"
These both exist to make sense roms usable on our phones, and they do make them usable but they drain battery.
the only advantage that this 32a build with sense may have is optimizations of the apk's and frameworks that could account for a speedier experience, and therefore introduce the possibility of cutting down on the two factors listed above.
It is very possible to do, and in fact easy. If the demand is high enough, i'll do it myself... add ideas/input here.
Click to expand...
Click to collapse
Please my liege. Do it.
Request: Make it awesome .
mejorguille said:
Another thing of interest would be bluetooth, but I'm not sure if 32A's and B's share the same bluetooth chip.
Click to expand...
Click to collapse
No, just like all the early 1.5 Hero roms that were from 32a phone... no Bluetooth.
I did a quick dirty port... got to boot but runs like crap... nonstop FC's and crashes. Really no time to play with it.
fishman0919 said:
No, just like all the early 1.5 Hero roms that were from 32a phone... no Bluetooth.
I did a quick dirty port... got to boot but runs like crap... nonstop FC's and crashes. Really no time to play with it.
Click to expand...
Click to collapse
Hehe I figured so, but I wasn't rooted yet when all the hero rom's started coming out so I didn't know that til now. And I looked through cyanogen's twitter and he mentioned that the camera drivers were tied to the radio so we can't pull that from it either. GL on porting it.
I cannot pair my vehicle's headunit to a CM-powered device, starting with CM6 RC2. (RC1 worked as expected).
I would like to build the stock Android Bluetooth stack and replace that portion of CM with it, in an effort to see if it resolves this problem for me. I'm also curious how the new Bluetooth stack in Gingerbread will behave, as it's apparently received an overhaul.
Ultimately, I'd like provide a package so that CM users could easily "flash" a new BT stack if they're having problems with CM's modified version.
I'm a junior developer, and I have Ubuntu on my machine, as well as AOSP Gingerbread and CM6/7, all building correctly. However, I lack the knowledge (or even a starting point) on what I need to do to accomplish this.
Anyone willing to offer some advice?
Additionally, if anyone else out there is having problems, please post here--once I get this working, I'll need test candidates to see if it helps resolve their issues as well.
EDIT: Starting here. http://source.android.com/porting/bluetooth.html
Never had an issue with bluetooth and my vehicle or a couple of others while running CM 6.x or any of the nightly builds of cm6. Sometimes a kernal I flashed would break it, but otherwise it worked fine. I done this one both a alpine blue tooth module and factory ones.
What are you syncing to?
aduljr, the type of headunit I have is called "BlueConnect", and is built-in to my 2009 model year Hyundai Elantra. This is the manufacturer's website: http://www.autointelligence.com/
Like I said, it worked with CM6.0.0 RC1, but stopped working starting with RC2 and hasn't worked since.
So far I've started reading about the BlueZ stack, but haven't made more progress than simply reviewing some make files.
As always, if anyone has any pointers (or if anyone is also having BT-related problems), please post.
Thanks.
While you're working on the bluetooth stack, can you look into the lack of DUN/PAN support on the the Evo?
timwoj said:
While you're working on the bluetooth stack, can you look into the lack of DUN/PAN support on the the Evo?
Click to expand...
Click to collapse
I suppose I might as well--I'll have to delve into Bluetooth pretty deep I suppose, so I'll see what I can do.
What are you hoping to do with DUN/PAN support? Mobile networking/Ad-Hoc of some sort?
Shidell said:
I suppose I might as well--I'll have to delve into Bluetooth pretty deep I suppose, so I'll see what I can do.
What are you hoping to do with DUN/PAN support? Mobile networking/Ad-Hoc of some sort?
Click to expand...
Click to collapse
The Savage Team will help.
my suggestion is start a private google group, its a great way to collaborate with your team
have you tried updating to cm6.1 and trying with a stock kernel?
jsseidel1 said:
The Savage Team will help.
my suggestion is start a private google group, its a great way to collaborate with your team
Click to expand...
Click to collapse
Interesting, and appreciated. I'll look into a Google Group, although for now I'll work out of this thread unless this grows into a large project.
BrianDigital said:
have you tried updating to cm6.1 and trying with a stock kernel?
Click to expand...
Click to collapse
I have tried 6.1 with an alternative kernel (Kings) to no avail. Do you have a kernel you'd suggest I pair with 6.1 for testing purposes? I'm more than willing to do so for testing purposes.
Shidell said:
What are you hoping to do with DUN/PAN support? Mobile networking/Ad-Hoc of some sort?
Click to expand...
Click to collapse
Basically, I'd like to be able to tether my phone over BT. The Evo doesn't provide a DUN or PAN service that OS X can see (never tried windows), so things like Android-Wifi-Tether don't work in bluetooth mode.
does you phone work with any other bluetooth device?
aduljr said:
does you phone work with any other bluetooth device?
Click to expand...
Click to collapse
It works fine for other Bluetooth profiles (phonebook, etc) but it doesn't provide a PAN service at all. I haven't tried with the new AWT, but I don't hold much hope.
I've created an update package from CM6.0.0 RC1 with (what I believe to be) all the pertinent Bluetooth files. This will replace your current files when you run this update script.
I'm going to test this using a CM7 nightly, and wholly expect this to fail. This may actually work with CM6, however, but I'm testing CM7 first.
If anyone else tests this, please let me know your results.
Also, if anyone is more tuned in as to what needs to be done/fixed, please let me know that as well. I'm basically treading water in the middle of the pacific, hoping I find an island.
This is appreciated. I stopped using CM because they changed something with bluetooth that would cause my Motorola Rokr headphones to constantly cut in and out. I asked the question over at CM's forums but never received any help there. Before with RC6 the headphones worked flawlessly and I could actually ride my mountain bike on the trails and never have it cut out. Seems they have cut some power out to save battery or something but hey I'm no dev so who knows. Maybe in your quest to get better bluetooth you could figure out if the power can be turned up for those of us that just want a stronger connection.
BuddaBelly said:
This is appreciated. I stopped using CM because they changed something with bluetooth that would cause my Motorola Rokr headphones to constantly cut in and out. I asked the question over at CM's forums but never received any help there. Before with RC6 the headphones worked flawlessly and I could actually ride my mountain bike on the trails and never have it cut out. Seems they have cut some power out to save battery or something but hey I'm no dev so who knows. Maybe in your quest to get better bluetooth you could figure out if the power can be turned up for those of us that just want a stronger connection.
Click to expand...
Click to collapse
+1 I have this same problem. CM has a much weaker bluetooth connection than Sense ROMs. I would love to be able to flash something over CM7 to increase bluetooth reliability, even if it hurts battery life (you could always turn bluetooth off when you need to save battery).
Shidell said:
I've created an update package from CM6.0.0 RC1 with (what I believe to be) all the pertinent Bluetooth files. This will replace your current files when you run this update script.
I'm going to test this using a CM7 nightly, and wholly expect this to fail. This may actually work with CM6, however, but I'm testing CM7 first.
If anyone else tests this, please let me know your results.
Also, if anyone is more tuned in as to what needs to be done/fixed, please let me know that as well. I'm basically treading water in the middle of the pacific, hoping I find an island.
Click to expand...
Click to collapse
ill try this as i have the cutting out issue as well
When I've had problems with audio dropping in and out,it's because my wifi is on at the same time.
You can't have wifi and do a2dp at the same time. I've seen that around,so I think it's a known bug.
The whole reason I switched to cm was because the bitpool is set too low in all the sense roms. From my understanding, it should be set to something in the 50s or 60s (sorry, I haven't looked @ it in a few weeks) and sense roms have it set in the 30s resulting in a lot of high frequency distortion or clipping.
I'm not sure if that's helpful. ..but I wrote some stuff.
Sent from my PC36100 using XDA App
allroy1975 said:
When I've had problems with audio dropping in and out,it's because my wifi is on at the same time.
You can't have wifi and do a2dp at the same time. I've seen that around,so I think it's a known bug.
The whole reason I switched to cm was because the bitpool is set too low in all the sense roms. From my understanding, it should be set to something in the 50s or 60s (sorry, I haven't looked @ it in a few weeks) and sense roms have it set in the 30s resulting in a lot of high frequency distortion or clipping.
I'm not sure if that's helpful. ..but I wrote some stuff.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
my wifi is never on. and even when it is it doesnt do it on sense roms.
zikronix said:
my wifi is never on. and even when it is it doesnt do it on sense roms.
Click to expand...
Click to collapse
Yeah my wifi is not on when Im riding my bike. I do agree sence has a pretty crappy bluetooth stack but the early CM releases were amazing. I could ride even on a open road with no trees to bounce signals of off and never get a signal drop.
Sent from my PC36100 using XDA App
BuddaBelly said:
Yeah my wifi is not on when Im riding my bike. I do agree sence has a pretty crappy bluetooth stack but the early CM releases were amazing. I could ride even on a open road with no trees to bounce signals of off and never get a signal drop.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Well, wouldn't it be easier to look back into the git commits for the CM repository. And see what changed in the bluetooth files after 6.0.0? That way you should be able to drop in the older bluetooth stuff, and have it work. Then you can try to convert that stuff to work in CM7?
timwoj said:
It works fine for other Bluetooth profiles (phonebook, etc) but it doesn't provide a PAN service at all. I haven't tried with the new AWT, but I don't hold much hope.
Click to expand...
Click to collapse
If you use AWT and set it to Bluetooth mode and then turn it on, the PAN service will magically be created, but only while tethering is turned on. However, I still wasn't able to get Bluetooth tether to work because of some kind of IP address error in AWT. I think AWT wasn't able to set an IP address for the Bluetooth PAN adapter. My computer was able to see the Bluetooth PAN but wasn't able to pull an IP address to fully complete the connection.
Hi guys,
I've done some reading on AVRCP and love that I have this feature in teh talon ace beta rom i'm running. I want it in sense roms too, though, because it's a killer feature since I'm always in my car (BT head unit).
Is there any way to implement this feature in sense roms? I know that sense roms use a different bluetooth stack, so it's not the same as google's bluetooth stack in AOSP roms that have working AVRCP. Other than that though, I'm not quite sure of anything else.
Thanks!
nhshah7 said:
Hi guys,
I've done some reading on AVRCP and love that I have this feature in teh talon ace beta rom i'm running. I want it in sense roms too, though, because it's a killer feature since I'm always in my car (BT head unit).
Is there any way to implement this feature in sense roms? I know that sense roms use a different bluetooth stack, so it's not the same as google's bluetooth stack in AOSP roms that have working AVRCP. Other than that though, I'm not quite sure of anything else.
Thanks!
Click to expand...
Click to collapse
Simple answer is that HTC would have to build it in as the BT stack they use is closed source so you really cant edit it to add it in
zelendel said:
Simple answer is that HTC would have to build it in as the BT stack they use is closed source so you really cant edit it to add it in
Click to expand...
Click to collapse
Damn it! Thanks for the quick response.
nhshah7 said:
Damn it! Thanks for the quick response.
Click to expand...
Click to collapse
No prob, Question answered thread closed
Rather than annoy devs on each Sense 4.0 post I thought I'd ask this simple question here as the BT problem is the same on each build.
BT was never working until Mdeejay fixed it (from memory). However, all the builds seem to only have a partially working fix as I cannot get my car to fully connect anymore (fine on Sense 3.6 etc).
My question is...is it a known issue that its a partial fix or do Sense 4.0 BT just not work with all devices. I need my phone to connect to my car and am happy to wait but perhaps I'm waiting for something that'll never happen!
Thanks for any heads-up
jamesbond_28_007 said:
Rather than annoy devs on each Sense 4.0 post I thought I'd ask this simple question here as the BT problem is the same on each build.
BT was never working until Mdeejay fixed it (from memory). However, all the builds seem to only have a partially working fix as I cannot get my car to fully connect anymore (fine on Sense 3.6 etc).
My question is...is it a known issue that its a partial fix or do Sense 4.0 BT just not work with all devices. I need my phone to connect to my car and am happy to wait but perhaps I'm waiting for something that'll never happen!
Thanks for any heads-up
Click to expand...
Click to collapse
Hi,
BT stack is notoriously poor on the Sensation.
I have seen some people using the latest FAUX 005b1 KERNEL on their Sense 4.0 ROMS .
He has had a degree of success in improving the BT stack.
Might be worth a try.
malybru said:
Hi,
BT stack is notoriously poor on the Sensation.
I have seen some people using the latest FAUX 005b1 KERNEL on their Sense 4.0 ROMS .
He has had a degree of success in improving the BT stack.
Might be worth a try.
Click to expand...
Click to collapse
Thanks. Rather embarrassingly I have never swapped the kernel that's already included in the Rom so that might be a challenge. I'll read around and see if I can do it as I like the idea of this kernel having an improved BT stack.
jamesbond_28_007 said:
Thanks. Rather embarrassingly I have never swapped the kernel that's already included in the Rom so that might be a challenge. I'll read around and see if I can do it as I like the idea of this kernel having an improved BT stack.
Click to expand...
Click to collapse
Hi,
Not difficult at all.
MAKE A NANDROID BACKUP.
Wipe cache and dalvik,
Flash kernel like a ROM.
Et voila.
Just worked that out (minus the wiping bit so not sure what I've got now )
jamesbond_28_007 said:
Rather than annoy devs on each Sense 4.0 post I thought I'd ask this simple question here as the BT problem is the same on each build.
BT was never working until Mdeejay fixed it (from memory). However, all the builds seem to only have a partially working fix as I cannot get my car to fully connect anymore (fine on Sense 3.6 etc).
My question is...is it a known issue that its a partial fix or do Sense 4.0 BT just not work with all devices. I need my phone to connect to my car and am happy to wait but perhaps I'm waiting for something that'll never happen!
Thanks for any heads-up
Click to expand...
Click to collapse
Mdeejay only partially fixed Bluetooth - look @rootzwiki it says Bluetooth fix part 1 (media) in changelog
Sent from my HTC Sensation XE with Beats Audio Z715e using xda premium
Jonny said:
Mdeejay only partially fixed Bluetooth - look @rootzwiki it says Bluetooth fix part 1 (media) in changelog
Sent from my HTC Sensation XE with Beats Audio Z715e using xda premium
Click to expand...
Click to collapse
Ahh, I see. The faux kernel made no difference and now I know why. Couldnt find that changelog but at least I know a part 2 is likely!
Has any of the dev's been able to slove the bluetooth issues as yet on sense 4. roms or near to solving the issues.
BT Fix?
Same here, like most Sense 4.0 Roms that I have tried out have been almost near perfection right up until you get to the bluetooth part, like it really bugs me cause i'm normally on my BT majority of the time. Does anyone have any idea of an ETA on the fix? Cause I really would like to go back to Sense 4.0 instead having to use Sense 3.6 still
Anthonyburton100 said:
Same here, like most Sense 4.0 Roms that I have tried out have been almost near perfection right up until you get to the bluetooth part, like it really bugs me cause i'm normally on my BT majority of the time. Does anyone have any idea of an ETA on the fix? Cause I really would like to go back to Sense 4.0 instead having to use Sense 3.6 still
Click to expand...
Click to collapse
One rule of CyanogenMod which probably applies here is don't ask for ETA it is done when its done
Sent from my Sensation using xda premium
Anthonyburton100 said:
Same here, like most Sense 4.0 Roms that I have tried out have been almost near perfection right up until you get to the bluetooth part, like it really bugs me cause i'm normally on my BT majority of the time. Does anyone have any idea of an ETA on the fix? Cause I really would like to go back to Sense 4.0 instead having to use Sense 3.6 still
Click to expand...
Click to collapse
Eta = when it's ready/fixed.
That goes for ANY project on xda/rootzwiki/etc.
It's not like these guys are getting paid to do this, nor is it their job title of "developer".
Sent from my Sensation using Tapatalk 2
Anybody know of a 3.6 rom that has working bluetooth voice dialing?
geoffcorey said:
Eta = when it's ready/fixed.
That goes for ANY project on xda/rootzwiki/etc.
It's not like these guys are getting paid to do this, nor is it their job title of "developer".
Sent from my Sensation using Tapatalk 2
Click to expand...
Click to collapse
I agree. And for clarification, I didnt ask
I know I could just check the change logs on the each Rom but is there anywhere I can go to see progress or updates on this issue? Something about rootwiki but no idea where to look!
Thanks.