[Q] Basebands, what do they do and why do they matter? - XPERIA X10 Q&A, Help & Troubleshooting

Yes, the title sounds like a seminar, but I really wanted to understand a bit more about what makes a device (specifically SE's X10) work and why different ROMs are tied to different basebands.
I successfully flashed the latest baseband; 2.1.55 through the Roger's leaked ROM. On top of that, I flashed FreeX10b4 into my devices about a month ago. So far the device works without a hitch. I'm really happy and have tweaked and personalized the phone in different ways. Overall I'm happy with what the hardware allows once you remove the general bloatware from the stock ROM (I'm looking at you Timescape and Mediascape).
I'm considering trying out 2.3.3 on my x10 and see how it behaves. Mostly, I want to see improved performance and how, in general terms, Gingerbread is better than Froyo. For me, this means installing a fully functional, stable ROM.
I use:
the stock Contacts apps for dialing, call history, favorites,
Dolphin HD to browse,
Touchdown 2.0 for Emails,
Tweetdeck for social,
Google's Listen for Podcast
Google's Reader for RSS
Waze for maps
I pretty much use most of the phone's functionality, leaving out --specifically--the camera; which is why I'm so comfortable with FreeX10b4.
I wanted to try out Cyanogen CM7.0 RC1 v007, but I feel it's too early into development. Is this true, or am I just reading too much into the "what's working / what isn't" list?
tl;dr
Why are some ROMs dependant on specific basebands, like Cyanogen CM7.0 RC1 v007 appears to be?
What determines or what needs to be tweaked in order to make ROMs oblivious to the baseband you have installed?
sorry for the long post, I'm very curious and just starting out.

Baseband or radio are the same (as far as i know)
"The Radio is the Firmware that works between the Operating System and the Cellular Hardware. It handles the Sound, Camera, GPS, Phone Calls, etc. The Radio must be compatable with the ROM's Operating System or you may experience problems with your sound and camera."
As far as the 2.3.3 you want to try. I did try it, and I'm sorry to say that it messed up my phone. It kept having random reboots after using certain apps (facebook, gmail, browser, etc...).. which i by now realize are all 'internet apps'.
After a day of using it, it wouldn't boot at all anymore. Just stuck at the white sony erricson. (Wouldn't even load xrecovery). Had to flash the stock SE firmware to get it back up running.
I am using the [Cyanogen6.1.3]gingerbread theme[v01] (2.2.1) now
http://forum.xda-developers.com/showthread.php?t=947613
These sudden shift of 3 ROMS gave me a little insight in their speed.
The stock one is just horribly slow, even after i removed all the nonsense.
The CM7.0 was incredibly fast and smooth, too bad it kept crashing (for me).
The CM6.1.3 is stable (no FC or any other problems for an active day of trying all kind of stuff, and its fast and smooth as well, just less options (CM wise).

Thanks for the detailed explanation. It really helped.
Would it be safe to say that "baseband" is another way to say kernel?
I don't want turn this thread into a tutorial, God knows there's many laying around; it's just that I feel that there's so much terminology to learn...
Anyway, I'll stick with FreeX10 for a bit until I read more about CM.
Thanks again,
Xperia x10i
FreeX10b4|BB:2.1.55|K:2.6.29

You would say its safe to say, because i just explained that baseband/radio controls the hardware and communicates with the software.. but its not quite that.
a kernel is the core piece of software that runs an os, its responsible for many things including data processing at a h/w level, memory, cpu and power management. the radio/baseband, controls not just the radio stack (network.bluetooth,wifi,gps) but it also works like a massive driver pack for the device.... now a kernel is not that important, if you flash a bad or wrong kernel its easy to recover, the radio tho, is one of the deepest levels of software on your device, flashing a bad or wrong radio will brick your device.
On the ROM suggestion, CM is really an improvement, and the one i use is very safe.

Let me excuse myself to Hobbes first as I hope im not trashing this thread, I just feel my question is a little associated with it, and dont wanna start a whole new thread:
As Pierre was saying, the basband is basically the "drivers" for all of the hardware a phone has, my question is this then....has anyone developed a way to increase the stock sound level on the X10?? This phone for me has been the best in all aspects as I use it for everything it does: camera, music player, web browsing, video capture, portable game piece, etc....
I ask this question because I use to have a Samsung Impression, and i found a website of a guy that has hact it at the time down to the "kernal" if you will. What do I mean? He had a way where you can go into what would be the equivalent of the "dos" part of the phone, where you can change the values of the decibel levels for each volume, which in the case of the Impression, it had seven preset volume settings. I believe the X10 has like 10 or 12, wateva, doesn't matter. point is, can we change these levels? Cause this is my ONLY gripe about the phone. It really isn't as loud as others. I came from a Blackberry Bold 9000 to the x10, and that phone is much louder in the aspect of the ringtome and alarm sound volume...hope someone can give me a good answer to this one.......

Does the custom rom have to have the same baseband as your existing rom,or i can install any rom i choose,sorry noob at this.

What? The baseband is not the drivers at all....
You guys have NO idea what you're talking about.
The baseband and kernel are not even close to the same either.
The baseband controls the frequency of the radio in your device.

this is kernel or even hardware related (as far as i know), and we can't modify the kernel without cracking the bootloader. (be my guest and work on that )
and mm, i find it weird that ppl say that the x10 aint so loud.. it sometimes scares the hell out of me when i get a txt. And i got a hearing problem

read... http://www.tech-faq.com/baseband.html

Ok then fiscidtex, if you don't mind please enlighten our curiosity and clear our confusion. Or any other info another vested member of this great forum can share with us.
Sent from my X10i using XDA App

im_iceman said:
read... http://www.tech-faq.com/baseband.html
Click to expand...
Click to collapse
sure, i know the term baseband, ive studied as well and it was my first thought, to what they mean with 'baseband' here.
but, im pretty sure the terminology is a little different when it comes to firmware/roms in combination with baseband. Little over 12mb packed sounds a bit much to just be a little code to control a radiofreq, don't you think?

kevace1 said:
has anyone developed a way to increase the stock sound level on the X10?? This phone for me has been the best in all aspects as I use it for everything it does: camera, music player, web browsing, video capture, portable game piece, etc....
Click to expand...
Click to collapse
In the CM settings there is an option to increase the stock volume of alarm, notifications and ring tones. Try using that..

Pierre Duc said:
sure, i know the term baseband, ive studied as well and it was my first thought, to what they mean with 'baseband' here.
but, im pretty sure the terminology is a little different when it comes to firmware/roms in combination with baseband. Little over 12mb packed sounds a bit much to just be a little code to control a radiofreq, don't you think?
Click to expand...
Click to collapse
No, what he posted is EXACTLY what the baseband is... The width of the range of theoretical frequencies your phone can operate on.
The kernel is like dos on a pc, the backbone of the computer/os... It is the deeper level that to some degree controls the os. So when we change os, but still use same kernel this is where problems arise.

fiscidtox said:
No, what he posted is EXACTLY what the baseband is... The width of the range of theoretical frequencies your phone can operate on.
The kernel is like dos on a pc, the backbone of the computer/os... It is the deeper level that to some degree controls the os. So when we change os, but still use same kernel this is where problems arise.
Click to expand...
Click to collapse
Mhm, like i said, i know the term baseband. and kernel.. but I was confused when i read that a ROM is so baseband dependant on wether it works or not.
and if baseband is just the width of range of the theoretical frequencies, why does it take 12mb to flash sounds like there is more to it

Pierre Duc said:
Mhm, like i said, i know the term baseband. and kernel.. but I was confused when i read that a ROM is so baseband dependant on wether it works or not.
and if baseband is just the width of range of the theoretical frequencies, why does it take 12mb to flash sounds like there is more to it
Click to expand...
Click to collapse
Well think whatever you want...
I'm an electrical engineer and I KNOW what it is.
It would be a decent size as it would have to edit various things in your phone in order for the frequencies to work as well..

fiscidtox said:
Well think whatever you want...
I'm an electrical engineer and I KNOW what it is.
It would be a decent size as it would have to edit various things in your phone in order for the frequencies to work as well..
Click to expand...
Click to collapse
I understand, I studied information technology, and as I said. I'm familiar with the term Baseband. And you are right about its definition.. but when it comes to 'baseband version' implemented in a smartphone, it seems like there is just more to it. I would like to see a dev's opinion on this one
Sent from my X10i using XDA App

Related

Wll we ever be "stable"

I am starting to think that we will never have a fully funtional device.
Are there any examples of xdandroid having an almost perfect port?
Sent from my MSM using Tapatalk
bijan588 said:
I am starting to think that we will never have a fully funtional device.
Are there any examples of xdandroid having an almost perfect port?
Click to expand...
Click to collapse
Devs are making leaps and bounds recently... the list of bugs is just so high, there's a lot of little things to squash - with the addition of pieces of hardware still not being functional.
So have a little patience, and show a little respect. We'll get there eventually - and as always, patches welcome - if you think you've got the talent to fix things fix them and give us patches! Don't sit on the sidelines and ***** about how stuff doesn't work. Doesn't do anyone a damned bit of good.
bijan588 said:
I am starting to think that we will never have a fully funtional device.
Are there any examples of xdandroid having an almost perfect port?
Sent from my MSM using Tapatalk
Click to expand...
Click to collapse
we are "stable" look at Arrrghs post below
BUILD] **Complete Froyo Bundle!!** FRX06 - "Stable" - Minor Fixes
Originally Posted By: arrrghhh
I was running this bundle for a while and in the begining I did have some issues but that's cause I didnt know crap. but now that I have learned a litle about each bundle and how they work and how to make it run better, I said good bye to windows and hello droid.
I'm testing another bundle and so far its prettty good.
THANKS TO ALL DEVS, ARRRGH PLEASE EXCUSE THOSE WHO COMPLAIN BUT DONT DO ANYTHING TO FIX THINGS. THANKS ARRGH FOR ALL YOUR WORK AND I AM SCREAMING DAMN IT!!!!!
bijan588 said:
I am starting to think that we will never have a fully funtional device.
Are there any examples of xdandroid having an almost perfect port?
Sent from my MSM using Tapatalk
Click to expand...
Click to collapse
It really depends, partially on usage scenarios. xdandroid FRX05/06 on RHOD300 is close to what many WinMo ROMs achieved in terms of general stability. It's actually better than the old version of Energy I was using (which hung on boot 50% of the time, but would be fine after that.) I'm using the xdandroid source tree myself as my daily phone with lots of success.
Power management issues are getting knocked down pretty fast (major focus right now for the devs, primarily being worked by WisTilt2)
RIL issues are on the way to resolution, thanks to independent efforts by highlandsun and WisTilt2. I'm personally hoping to maybe see WisTilt2 hand off his work to highlandsun so WisTilt2 can resume working the kernel PM stuff
Bluetooth is in progress - sounds like we're close, but it's lower priority. Unfortunately the Bluetooth commits and WisTilt2's latest PM work are conflicting, so there isn't a kernel that includes both the improved PM and the improved BT support. I suspect this will change in a week or two.
GPS - It's functional enough for most people, so currently is very low priority. I've done a little work here since I'm not really qualified to work some of the other stuff. Ideally the GPS will get cleaned up so it doesn't wakelock us (we have an easy workaround for that), and time/loc injection can be implemented for faster locking (This requires a significant reverse engineering effort though - Qualcomm changed the interface enough with newer gpsOne solutions that I don't think we can use the code/documentation from the cyanogenMod and AOSP GIT trees.). Lack of XTRA isn't a priority at all for those running from SD, it's a big issue for NAND though.
The progress made in the last several months has been significant. Back near the beginning of the year I was having to delete my data.img and restore from backups every few days. The latest kernels and system releases have solved a ton of issues.
Bluetooth and ril fixes are all that's needed to make me completely forget about Windows mobile on this phone.
toadlife said:
The progress made in the last several months has been significant. Back near the beginning of the year I was having to delete my data.img and restore from backups every few days. The latest kernels and system releases have solved a ton of issues.
Bluetooth and ril fixes are all that's needed to make me completely forget about Windows mobile on this phone.
Click to expand...
Click to collapse
I already forgot about windows. I use droid daily. it's stable enough for me
arrrghhh said:
Devs are making leaps and bounds recently... the list of bugs is just so high, there's a lot of little things to squash - with the addition of pieces of hardware still not being functional.
So have a little patience, and show a little respect. We'll get there eventually - and as always, patches welcome - if you think you've got the talent to fix things fix them and give us patches! Don't sit on the sidelines and ***** about how stuff doesn't work. Doesn't do anyone a damned bit of good.
Click to expand...
Click to collapse
Sorry, I'm not tryin to complain.
I was just thinking "has ther ever been a 100% port of android to a windowss phone"
I dident intend to sound like a spoiled brat, and I understand a ton of work goes into this project.
Sadly I only know java and am of no use to you guys, if I tried to help I would end up being anotheeeeeeeeeeeeeeeeer tiad 8.
Oh look! The famus key stuck bug
Sent from my MSM using Tapatalk
bijan588 said:
Sorry, I'm not tryin to complain.
I was just thinking "has ther ever been a 100% port of android to a windowss phone"
I dident intend to sound like a spoiled brat, and I understand a ton of work goes into this project.
Sadly I only know java and am of no use to you guys, if I tried to help I would end up being anotheeeeeeeeeeeeeeeeer tiad 8.
Oh look! The famus key stuck bug
Click to expand...
Click to collapse
Yes, there are still bugs out there.
There are two WinMo phones that I'd say have a 'complete' port - HD2 and Vogue. Now I don't think every single feature has been matched, but they're considered stable and almost every feature has been ported over to Android.
I'm on FRX05 with the 3/11 wistilt2 kernal and this thing is heaven. I don't get any lagging unless I run a crap ton of apps at once or try and download a ton of programs off the market at once (that would slow down any phone). I get through the day with about 40% battery still left. Bluetooth isn't completely working but I don't use that. What more are you looking for in terms of stability? Android can be even less buggy/laggy than some Winmo Cookie 2.0 ROMs in my opinion.
Wow, this is pretty impressive.
I'm an old TP2 (VZW) user, got a Droid X in October as a replacement.
I saw a video for the HD2 and figured I'd check out my old phone and see how Android development is going. I've kept my TP2 in case I ever did any world travel, so this is definitely something I'm going to start watching.
Just a few questions.
1) How does touching work as opposed to the stylus? I know WinMo was VERY stylus heavy and often finger presses would miss because they weren't exact enough. I was always under the impression that was hardware config. Since Android is working on these WinMo devices, I'll presume the stylus is useless now. Confirm / Deny?
2) What's not working exactly? I've gathered BT and GPS (but not sure exactly what doesn't work with GPS), but I'm sure there is more.
3) Can this be flashed as the default OS, or does it need to be launched as an EXE from the SD card?
4) Can someone guide me to the best install guide? I'm considering popping this on to my TP2 and playing around with it (via WiFi).
5) How well does WiFi hotspot work?
6) Are all builds rooted by default?
7) Recommendations for which ROM to use?
arrrghhh said:
Yes, there are still bugs out there.
There are two WinMo phones that I'd say have a 'complete' port - HD2 and Vogue. Now I don't think every single feature has been matched, but they're considered stable and almost every feature has been ported over to Android.
Click to expand...
Click to collapse
Yeah, my wife has the HD2 and *everything* (that I know of) works.
EtherBoo said:
Wow, this is pretty impressive.
I'm an old TP2 (VZW) user, got a Droid X in October as a replacement.
I saw a video for the HD2 and figured I'd check out my old phone and see how Android development is going. I've kept my TP2 in case I ever did any world travel, so this is definitely something I'm going to start watching.
Just a few questions.
1) How does touching work as opposed to the stylus? I know WinMo was VERY stylus heavy and often finger presses would miss because they weren't exact enough. I was always under the impression that was hardware config. Since Android is working on these WinMo devices, I'll presume the stylus is useless now. Confirm / Deny?
2) What's not working exactly? I've gathered BT and GPS (but not sure exactly what doesn't work with GPS), but I'm sure there is more.
3) Can this be flashed as the default OS, or does it need to be launched as an EXE from the SD card?
4) Can someone guide me to the best install guide? I'm considering popping this on to my TP2 and playing around with it (via WiFi).
5) How well does WiFi hotspot work?
6) Are all builds rooted by default?
7) Recommendations for which ROM to use?
Click to expand...
Click to collapse
1) All UI elements are large enough that I've never had a need for the stylus in Android. However, since it is a resistive touchscreen, often "fingertip" dragging isn't so hot (single-presses OK, dragging less so) - Fingernails are great for this. I'd say it's about on par with my Huawei S7 in terms of touchability.
2) 3.5mm jack is completely nonfunctional on devices that have it
Headset via ExtUSB is flaky - few people use it so it doesn't get much testing/dev attention
BT is nonfunctional right now, I'd say it's the biggest "missing" item
GPS is usable but has performance issues in terms of initial lock times. Once locked it works great. There are two issues - Ephemeride preloading (XTRA, or in terminology more familiar on the WinMo side, QuickGPS) is not implemented. Fortunately XTRA loading can be done from WinMo prior to booting Android. There's also GPS time/location injection used to "warm start" the GPS - also not implemented.
Camera is a little flaky, but there have been major strides in that in the past month
Power management is still a little flaky, but I think WisTilt2's kernel work is nearly complete
Our RIL has definite known issues, esp. on CDMA phones. WisTilt2 was working it a bit, and highlandsun has made MAJOR improvements in just the past week
bijan588 said:
Sorry, I'm not tryin to complain.
I was just thinking "has ther ever been a 100% port of android to a windowss phone"
I dident intend to sound like a spoiled brat, and I understand a ton of work goes into this project.
Sadly I only know java and am of no use to you guys, if I tried to help I would end up being anotheeeeeeeeeeeeeeeeer tiad 8.
Oh look! The famus key stuck bug
Sent from my MSM using Tapatalk
Click to expand...
Click to collapse
The HD2 has a pretty close to 100% port of android... the HD2 is even starting to get it's own CM7 build... not a port, a build made specifically for it. I think it was easier porting android to the HD2, though, because there are many similar android devices that use similar hardware. Also the HD2 seemed to have a lot more devs working on the project.
I love my HD2... it's my main phone and will be for at least another 6 months. Currently running WP7 on NAND and running a CM7 build from my SD card, and even running from SD card, it runs about as well as a native android device. It's going to be hard to move on to a new phone when I'm used to being able to run both WP7 and Android.
Anyways, sorry for the HD2 talk in the Rhodium forum. I'm new in this section... just got myself a T-Mobile Touch Pro 2 to play with and use as spare phone, so I'll be around these parts more from now on.
Is cotulla still working on magldr for the rhodium? Any recent news on that. Having magldr can make the rhodium much more like a native android phone, especially if he has recovery support.
absolutely, magldr 113 is phenominal on my hd2, i'd never go back to windows again, i've been using frx06 with different highlandsun's ril and arrrghhh's kernel for a few days with verrry few problems. i can't wait to get it on nand and have a clockwork mod system
As to the HD2 - As I understand it, there seems to be far fewer variations between Snapdragon configurations as there were for MSM7k configurations.
As a result, it's a lot easier to target one of the rare non-Android Snapdragons when so many Snapdragons ran Android.
EtherBoo said:
1) How does touching work as opposed to the stylus? I know WinMo was VERY stylus heavy and often finger presses would miss because they weren't exact enough. I was always under the impression that was hardware config. Since Android is working on these WinMo devices, I'll presume the stylus is useless now. Confirm / Deny?
7) Recommendations for which ROM to use?
Click to expand...
Click to collapse
1 Winmo is much better for fingers. I can not use fingers for soft keyboard on Android. Seem to me that WM has a lot of filtering, that is missing in Android. Using my nails work pretty well though.
7 I recommend you try them all. All of them have issues. Find one you can live with
Many people has had success with Huawei, its pretty easy to install, so I would start with that. Does not work for me though.
FRX05/06 are easy ready-to-go-bundles as well.
EtherBoo said:
Just a few questions.
1) How does touching work as opposed to the stylus? I know WinMo was VERY stylus heavy and often finger presses would miss because they weren't exact enough. I was always under the impression that was hardware config. Since Android is working on these WinMo devices, I'll presume the stylus is useless now. Confirm / Deny?
2) What's not working exactly? I've gathered BT and GPS (but not sure exactly what doesn't work with GPS), but I'm sure there is more.
3) Can this be flashed as the default OS, or does it need to be launched as an EXE from the SD card?
6) Are all builds rooted by default?
7) Recommendations for which ROM to use?
Click to expand...
Click to collapse
1.) I much prefer androids UI to that of winmo, stylus is needed less but I still use it occasionly . But I didn't use it much in winmo eithar as iv grown good at precise use of the touchscreen But android is still a lot less fiddly
2.)Most of these have already been pointed out but as usual I'm adding in my own personally annoyance Idv3 tags in mp3s are not being read. So you can listen to your music, but album/artist/album art/ and da rest of it won't be seen in most mp3s.
3.) Great progress is being made. . . . .but atm its still reccomended to boot using HARET on sd
6.) Yes afaik the builds are rooted because root is access to /system . . .which seeing as its on the sd card it can be accesed/edited. (Btw can only onfirm for certain that root apps and exploring of root in android in neopeek builds . . . Havnt tried on an xda build as of yet)
7.)well first of all you need to decide wether you want to run a partition(neopeek) build , or a system.ext2 file (xda) build . . . . .you being new id recommend a build here on xda as setup is easier, that does leav you with less choices though but The latest FRX0- build should satify your craving for android . Arrrghhh has made a thread with the build and instructions.
Jandyman said:
2.)Most of these have already been pointed out but as usual I'm adding in my own personally annoyance Idv3 tags in mp3s are not being read. So you can listen to your music, but album/artist/album art/ and da rest of it won't be seen in most mp3s.
Click to expand...
Click to collapse
I'd like to address this issue.
I think this is simply an issue with ID3v1 and v2 tags. Have you made sure both tags are populated on your music?
If it's not this issue, then I'm not sure. I've only tried streaming music, haven't tried playing it locally yet...
teemo said:
1 Winmo is much better for fingers. I can not use fingers for soft keyboard on Android. Seem to me that WM has a lot of filtering, that is missing in Android. Using my nails work pretty well though.
Click to expand...
Click to collapse
I had this problem too but you can simply fix it by downloading a keyboard app from the market (like 'Gingerbread Keyboard' or 'SwiftKey').
I am using Gingerbread Keyboard and that is working much more exactly than the standard keyboard for me.
One more questi.
Is it possibe to make the browser scroll faster. And less choppy?
Sent from my MSM using Tapatalk

[Q] Need advice

Hello,
a friend of mine just got an Xperia X10, and since she doesn't understand a thing abou technology or smartphones, she asked me to help her with it. I was wondering which ROM I should flash. She doesn't need something fast but buggy nor complicated, she needs something simple (I know, she needs an Iphone) and she doesn't need something that needs to be updated. So I was wondering, should she stick with the stock ROM or is there on I can flash for her? (Of course I'd prefer if she had Gingerbread but if it's too buggy, the stock ROM it will be). I'm asking for advice because I own an HD2 so I don't have a clue about X10 roms!
Thank you
Hello all,
I have a quite similar question.. i didnt flash my phone for the last 2,5 months since i use a quite stable rom now (only barcode scanner and video recording dont work).
I still use a stock kernel.
Now my question is, what rom is recommended at this moment that is:
1. stable (no rebooting etc)
2. can use a custom kernel (i like to have the 32fps cap removed)
3. is froyo or higher (i need adobe flash for my football stream watching)
4. has working wifi, bluetooth, gps, 3g, proximity sensor
there are so many rom varieties, that i dont know what to flash.
(in dutch we say: door de bomen het bos niet meer zien )
I think me and the above poster are looking for the same awnser (sorry for highjacking the thead buddy )
greets!!
Use freex10 beta 4 its the most stablest rom very good battery life i never had a single fc or bug nothing to say else then its running.froyo 2.2 and so far its the best out of the 10 roms i tried very simple nothing fancy
Sent from my X10i using XDA Premium App
Read the threads, look at the screenshots and decide for yourself. FreeX10 is the base that all the 2.2 roms are built on, WB's 6.1.3 is a tweaked 2.2 with CyanogenMod settings and lots of tweaks already built in, MiUi roms are made to look like an iPhone without the normal android launchers, the CM7 and gingerbread ROMs are still missing some functionality. Its all just preference at this point, speed wise theyre all similar, most are relatively stable, it just depends what features and style you want. You could try a bunch of them and just make lots of backups and switch between all of them if you have a decent SD card.
Sent From My *Super Fly X10*
If I (or anyone for that matter!) help you, dont be afraid to press THANKS!
You could also do this: http://forum.xda-developers.com/showthread.php?t=934486
clixt said:
You could also do this: http://forum.xda-developers.com/showthread.php?t=934486
Click to expand...
Click to collapse
It looks like you're the only one who actually read my post ^^ thanks I'm gonna try this
She could use the MIUI ROM of Trip, it's iPhonish and has some little bugs. (Very little) (Not the Gingerbread version since it's not as stable as Froyo)
ROM looks very sexy, fast, smooth etc... Easy to put some girly theme on.
Id suggest not flashing it. I've jailbroken friends iPod before and if anything goes wrong they come to me to fix it and they dont even appreciate the added functionality or use it. Chances are someone with little tech skills will appreciate the change. And if anything goes wrong you'll have to fix it. Unless there complaining about the phone I wouldn't flash it.
Sent from my X10a using XDA App

Looking for as close to stock Kernel as possible with an updated BT bitrate

Sooo.. I'm not a fan of the crazy supermod kernels that add "tweaks" that improve only synthetic scores but kill your battery and are actually worse performing in real-world apps and cause other issues.
But damn, HTC has a HORRIBLE Bluetooth bitrate on A2DP. It's not the phone because one time I had a random ROM that had it sounding perfect, but whatever crap HTC has in there stock is awful.
Can anyone recommend one that doesn't do all the crazy stuff like SD/RAM "tweaks" but maybe only has things like dimmed capacatative buttons and the updated BT A2DP bitrate?
Or if I have to do this myself, what's a good way to get started?
Come on, no one?
Answer: Do it your self. Brah
Sent from my PG86100 using XDA App
southern87 said:
Answer: Do it your self. Brah
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
He wasn't asking someone to developed a kernel, he was simply asking if one exists. Way to be a ****. I seriously have a hard time dealing with all the bull**** in the 3D forums.
Sent from my HTC Evo 3D using XDA App
Saneless One said:
Can anyone recommend one that doesn't do all the crazy stuff like SD/RAM "tweaks" but maybe only has things like dimmed capacatative buttons and the updated BT A2DP bitrate?
Or if I have to do this myself, what's a good way to get started?
Click to expand...
Click to collapse
I compiled a stock kernel with only dim leds and notification light blinking changed. If you tell me exactly what to change for the BT A2DP bitrate (or point to a kernel that has that change as a commit on github, etc), I'll do it for you.
wrapkgb said:
He wasn't asking someone to developed a kernel, he was simply asking if one exists. Way to be a ****. I seriously have a hard time dealing with all the bull**** in the 3D forums.
Sent from my HTC Evo 3D using XDA App
Click to expand...
Click to collapse
Read the last sentence. Kthxbye lol
Sent from my PG86100 using XDA App
ANYWAY.
Thanks mwalt. I'm actually using your kernel now with Clean/Senseless ROMs. I prefer no crazy crap in there, so I appreciate changing a few things that make sense and aren't experimental theoretical improvements.
My request is real though
Here's a big long thread about it, actually, to show I'm not crazy
http://forum.xda-developers.com/archive/index.php/t-708685.html
Now.. to answer your question on where or what to change, after reading all that, I'm not sure I have an answer for you.
I know that the ROM in this thread works just fine:
http://forum.xda-developers.com/showthread.php?t=1316039
But of course, being CM7 based, it's still missing many things I need. Oddly though, unlike CM7 alpha, the BT audio worked just fine.
Saneless One said:
I know that the ROM in this thread works just fine:
http://forum.xda-developers.com/showthread.php?t=1316039
But of course, being CM7 based, it's still missing many things I need. Oddly though, unlike CM7 alpha, the BT audio worked just fine.
Click to expand...
Click to collapse
Do you happen to know what kernel empiire's rom is running? He doesn't say or give a source that I saw by quickly looking. I don't know enough to dig through the code myself and find it.
all my kernels have new / faster BT drivers...
GSM AOSP - pending
GSM SENSE - DONE
CDMA SENSE - DONE
CDMA AOSP = done
http://forum.xda-developers.com/showthread.php?t=1318005
chad.goodman knows what he is doing!
I use the stockAnthraX kernel and it has just the right amount of tweaks that I need. Actually, I don't even think of them as tweaks...just making the phone do what it was designed to do.
Flash it...you won't regret it!
Just noticed mwalt had posted in here....his kernels were going to be my other suggestion! Both of them do quality work.
mwalt: The kernel for empires says it's from toastcfh, evo 3d #25 dirty. Something like that. I'm going from memory since I only flashed it to see if Bluetooth sounded good. And it sure did sound good. I have a few songs that are always an issue with HTCs settings and they were perfect.
I'll try out Chad's kernel to see if it's a kernel or other settings issue. If it's kernel, I'll have to research, hopefully with some help, where the setting truly is.
I've yet to check out how chad's performs in the car, but I have zero interest in overclocking anything. FSB, CPU, GPU, anything. This phone doesn't get the best battery life in general, and I have zero issues with 1.2ghz, so I see no reason to go higher. I use apps instead of just benchmarking, and those all work just great. In fact, some ROMS even set things back with tweaks that look good on paper (benchmarks) but actually break things like SD card read/write latency.
I personally recommend chad.goodman's kernals. I have flashed different kernals and different roms, testing each rom with each kernal. His always gave a better benchmark score, while remaining the most stable. I know that's not what your looking for however. Since that "phase" that I was going through flashing 4-6 roms a day, I have since stuck with flashing a new rom every few days to try them out. But I always, ONLY, flash his stock kernal, because it seems to me to make the phone run exactly as it should. I don't overclock or tweak it in any way, or use any apps to do so.
So basically I would say flash his stock kernal, don't worry about overclocking it or doing anything to change it, and try it out for a few days. I think you'll be pretty happy with the outcome.
Edit: I play games for 1-3 hours a day on my phone, text constantly and use the phone for everything it has, and I get 18-26 hours per charge. The rom I had stuck with mostly(Or always go back to) is CleanROM DE with his kernal, which now includes it.
I'd prefer not to OC, but the kernel has it set for 1.5 by default.
CleanROM DE isn't bad, but some of the tweaks cause real-world issues despite possible score gains. For instance, the SD Card speed fix actually slows down read/write rates in any real-world usages and even makes songs skip. The latency is horrible with that script in particular.
I have played multiple albums without running into any problems myself. All of my music is 320 CBR, and I use the stock music player. As far as score gains, I haven't ran a benchmark on this rom. I've gotten to where I just want a good stable rom, regardless of the benchmark scores, and of course one that works for me. I'm not saying it's your phone or SD Card, but honestly I haven't ran into any issues with the read or writing of my card. I'm also using the SD Card that came with the phone which I believe is class 4. I'm getting out of where I "know what I'm talking about" but it could also be the process you follow when flashing. I feel like I go through alot of un-needed steps while flashing roms/kernals. I flash a combination of different Wiping tools that format and optimize(Synergy Wipe for example) the partitions in EXT4. I'm not sure if that has anything to do with it, but I can honestly say I haven't ran into any latency issues and especially no song skipping, even with the phone under heavy load(Music+Games/3DGames+Sometimes an open web tab or two and texting).
It could all just come down to each phone is different, even though they have the same hardware. Just like with PCs.
As far as OCing, I may not be correct(I'm probably not), but from what I read on chad.goodmans post along with others, the processor is approved/supported to run up to 1.512 by QUALCOMM, although it seems HTC says 1.188.
I'm not an expert on this at all, and if this isn't correct let me know. I'm just talking from experience and from my understandings of reading around on the forums.
Trust me, I try multiple things multiple times so I can single out the source of issues
Without SD Card tweak init.d scripts everything is fine. Introduce them into the mix, songs, album art, and the phone in general runs slow as it waits to build up the buffer before reading/writing. Now, benchmarks don't show this because during that buffer time there's no reading/writing so it's not measuring it. Once it actually writes it's slightly faster, but you can clearly see that the test is stalling out and it takes a LOT longer to complete.
As for chad's OC, I realize he's just doing what the chip is rated at, I'm not worried that he's got things set to some bad level, I just also realize that the chip is underclocked probably to save battery, and I'm fine with that speed so I'll take the power savings.
And finally.. the Anthrax kernel has the same A2DP issues as stock, so the bitpool setting is either not changed in it or the setting is elsewhere. I need to flash the other kernel I had from empire's rom to see if that alone can fix it.
Post your results once you finish testing it out, I'd like to know what they are haha!
Like I said I'm not into pushing my phone anymore, just looking for the best overall experience as possible with complete stability. However once in a great while I decide to flash some stuff and tweak it around to see how far my phone will go before freaking out ha.
Ok.. after another round of testing.
Looks like it's NOT a kernel thing after all. If I use Chad's anthrax kernel in a Sense ROM it doesn't change the quality of the BT A2DP streaming. But in an AOSP ROM, where the audio sounds good, using Chad's AOSP kernel still sounds good.
So it looks like there's some file/setting somewhere else that determines the bitrate or the BT drivers. Guess this isn't going to be as easy as I hoped.
Well at least you got that figured out haha. I'm still very interested in your findings so keep us updated! ^.^
I've always found that AOSP run better anyways, but I like Sense too much to get rid of it haha! However I'm looking forward to the bugs in the XPLOD ROM to be worked out, I flashed that one when it was released a few days ago and it seems pretty sick.
I would love to have an AOSP rom, but at this point the phone is missing functionality. I'll deal with Sense, so long as I can play music over BT and not cringe.
BT is important for the car because I can use steering controls

New to Fascinate, coming from Incredible forums and have a few questions.

I have had an Incredible since about October of 2010 and it finally bit the dust and I have moved to the Fascinate because of the price and awesome reviews the phone has received.
I have a few questions about the Fascinate.
What known bugs does this phone have? Are the bugs specific to Froyo, Gingerbread or both?
Which stock ROM is better for this device, Froyo or Gingerbread? (I prefer Froyo for the Incredible)
Is there a mostly stock ROM for this phone that is completely stable, zero bugs and zippy?
What is the best and easiest root method?
Is there anything I need to do before I root?
Thanks for any help.
Take a look at my guide in the general section. Section 1 has i.structions for flashing imo one of the best froyo roms...its just a enhanced version of stock froyo that yields awsome battery life. I also have a section (5) on rooting, but its not needed if your flashing a custom rom. Pretty much all of the latest roms for the fascinate are pre rooted.
Thanks a lot! I will check this out over the weekend.
ejdavis72 said:
I have had an Incredible since about October of 2010 and it finally bit the dust and I have moved to the Fascinate because of the price and awesome reviews the phone has received.
I have a few questions about the Fascinate.
What known bugs does this phone have? Are the bugs specific to Froyo, Gingerbread or both?
Which stock ROM is better for this device, Froyo or Gingerbread? (I prefer Froyo for the Incredible)
Is there a mostly stock ROM for this phone that is completely stable, zero bugs and zippy?
What is the best and easiest root method?
Is there anything I need to do before I root?
Thanks for any help.
Click to expand...
Click to collapse
Welcome to the fascinate forums ej, I too came from an incredible not too long ago so here's a couple things that should help you out.
First, you do not need to root to flash a rom/recovery/whatever. Samsung apparently leaves the security pretty wide open so you're free to flash an alternate recovery in odin then flash the rom of your choice from there. This was a weird concept for me coming from the incredible, and I think a lot of people just assume that you need to root before flashing roms (as that's how it is with moto, HTC, etc) but that's not the case.
I don't know if you prefer stock or AOSP roms, on the stock front, I think there's Superclean, Geewhiz, and TSM resurrection. These should be quite stable stock-ish roms that don't have the bugs that AOSP roms do. AOSP roms (ICS/MIUI/CM7/TSM PoolParty) on the fascinate use a different and faster filesystem (MTD). I can't really comment on any roms but MIUI/CM7/ICS as that's all I've ever used personally. The AOSP bugs that I've run into (currently on CM7) are data issues - data will occasionally drop out requiring airplane mode toggle, or will get stuck on 1x after sending/receiving SMS. Also there's a weird thing where the earpiece volume during calls will default to a high volume (just requires a quick volume adjustment or tasker script). I don't always notice this happening though.
I'll probably think of more later on, those are just the ones that come to mind at the moment. Hope this helps.
k_nivesout said:
Welcome to the fascinate forums ej, I too came from an incredible not too long ago so here's a couple things that should help you out.
First, you do not need to root to flash a rom/recovery/whatever. Samsung apparently leaves the security pretty wide open so you're free to flash an alternate recovery in odin then flash the rom of your choice from there. This was a weird concept for me coming from the incredible, and I think a lot of people just assume that you need to root before flashing roms (as that's how it is with moto, HTC, etc) but that's not the case.
I don't know if you prefer stock or AOSP roms, on the stock front, I think there's Superclean, Geewhiz, and TSM resurrection. These should be quite stable stock-ish roms that don't have the bugs that AOSP roms do. AOSP roms (ICS/MIUI/CM7/TSM PoolParty) on the fascinate use a different and faster filesystem (MTD). I can't really comment on any roms but MIUI/CM7/ICS as that's all I've ever used personally. The AOSP bugs that I've run into (currently on CM7) are data issues - data will occasionally drop out requiring airplane mode toggle, or will get stuck on 1x after sending/receiving SMS. Also there's a weird thing where the earpiece volume during calls will default to a high volume (just requires a quick volume adjustment or tasker script). I don't always notice this happening though.
I'll probably think of more later on, those are just the ones that come to mind at the moment. Hope this helps.
Click to expand...
Click to collapse
I saw you on these forums earlier and recognized you right away, I remember you from the Incredible forums for sure.
Thanks for the help, you answered many of my questions! A few more though...
Is the volume bug with all ROM's or just with certain ones?
How would you rate this phone against the Incredible, and can I use Mesmerize ROM's too? Would you recommend Froyo for this phone or Gingerbread?
ejdavis72 said:
I saw you on these forums earlier and recognized you right away, I remember you from the Incredible forums for sure.
Thanks for the help, you answered many of my questions! A few more though...
Is the volume bug with all ROM's or just with certain ones?
How would you rate this phone against the Incredible, and can I use Mesmerize ROM's too? Would you recommend Froyo for this phone or Gingerbread?
Click to expand...
Click to collapse
The volume bug is something that I've read is an issue with all MTD roms (CM7/MIUI/ICS), but in my experience, I've only noticed it a couple times, and I've only been on MTD roms since I got this phone a month or two ago. What I'm trying to say is, it's a pretty minor concern for me, but I don't actually talk on the phone all that much.
IMO, this phone is a nice upgrade coming from the incredible. Not galaxy nexus-like nice upgrade, but still, considering I sold my incredible for what I paid for the fascinate, it was totally worth it. One of the big things you'll notice coming from the incredible is the screen. I had an AMOLED incredible, and the SAMOLED on the fascinate is *much* better. You get a little more screen real estate (3.7" vs 4") and the display itself is just much more vibrant and closer to the actual glass part of the touchscreen that you interact with. Also, with voodoo color, you can tweak the display exactly to your liking, which is something I've definitely enjoyed being able to do.
Also, if you use your phone as a media player, you will love the WM8994 DAC used in the Galaxy S line. It sounds absolutely amazing paired with the voodoo control (app that lets you tweak sound and display) - considerably better than any ipod I've tested it side-by-side against. The audio quality alone will make it hard for me to upgrade, considering the DACs used in the newer generation devices like the Nexus or Galaxy SII are actually inferior to the one used in the original Galaxy S phones.
There is one downgrade coming from the incredible though, and that's the RAM (384MB vs 512MB), but I haven't run into any situation yet where the RAM was insufficient to do what I wanted to do. Also, if you're in to tweaking kernel things, you can do MUCH more with the kernels on this device compared to the incredible.
I'm not sure about mesmerize roms, I don't think you could use them on the fascinate unless they were modified. Are there any mes-specific roms you've seen that aren't available on the fascinate? As far as froyo vs GB, I can't really comment on that either since I've only used GB/ICS. Now that I think of it, aside from stock roms, I haven't seen any froyo roms around. But that's probably because I got the phone right around when GB finally officially came out for it.
k_nivesout said:
The volume bug is something that I've read is an issue with all MTD roms (CM7/MIUI/ICS), but in my experience, I've only noticed it a couple times, and I've only been on MTD roms since I got this phone a month or two ago. What I'm trying to say is, it's a pretty minor concern for me, but I don't actually talk on the phone all that much.
IMO, this phone is a nice upgrade coming from the incredible. Not galaxy nexus-like nice upgrade, but still, considering I sold my incredible for what I paid for the fascinate, it was totally worth it. One of the big things you'll notice coming from the incredible is the screen. I had an AMOLED incredible, and the SAMOLED on the fascinate is *much* better. You get a little more screen real estate (3.7" vs 4") and the display itself is just much more vibrant and closer to the actual glass part of the touchscreen that you interact with. Also, with voodoo color, you can tweak the display exactly to your liking, which is something I've definitely enjoyed being able to do.
Also, if you use your phone as a media player, you will love the WM8994 DAC used in the Galaxy S line. It sounds absolutely amazing paired with the voodoo control (app that lets you tweak sound and display) - considerably better than any ipod I've tested it side-by-side against. The audio quality alone will make it hard for me to upgrade, considering the DACs used in the newer generation devices like the Nexus or Galaxy SII are actually inferior to the one used in the original Galaxy S phones.
There is one downgrade coming from the incredible though, and that's the RAM (384MB vs 512MB), but I haven't run into any situation yet where the RAM was insufficient to do what I wanted to do. Also, if you're in to tweaking kernel things, you can do MUCH more with the kernels on this device compared to the incredible.
I'm not sure about mesmerize roms, I don't think you could use them on the fascinate unless they were modified. Are there any mes-specific roms you've seen that aren't available on the fascinate? As far as froyo vs GB, I can't really comment on that either since I've only used GB/ICS. Now that I think of it, aside from stock roms, I haven't seen any froyo roms around. But that's probably because I got the phone right around when GB finally officially came out for it.
Click to expand...
Click to collapse
After spending some time with this phone I have some issues with it...
1. Lowest in-call volume is TOO HIGH!
2. Headset buttons don't work other than pause, play, answer, and end. (GAY!)
3. When I end a call and hit the power button to turn the screen off, it comes back on! (with Widget Locker) regular lock works fine to keep the screen off after a call. Hmm
4. Music playback doesn't seem to sound right. (sounds tinny)
5. Volume buttons turn the screen on! (What the hell?)
ejdavis72 said:
After spending some time with this phone I have some issues with it...
1. Lowest in-call volume is TOO HIGH!
2. Headset buttons don't work other than pause, play, answer, and end. (GAY!)
3. When I end a call and hit the power button to turn the screen off, it comes back on! (with Widget Locker) regular lock works fine to keep the screen off after a call. Hmm
4. Music playback doesn't seem to sound right. (sounds tinny)
5. Volume buttons turn the screen on! (What the hell?)
Click to expand...
Click to collapse
.
try flashing the glitch v13.1 kernel, should help with in call volume...thats if your currently on a mtd rom. If your running a TW rom, then use the kgb kernel and use terminal to adjust call volume settings.
ejdavis72 said:
After spending some time with this phone I have some issues with it...
1. Lowest in-call volume is TOO HIGH!
2. Headset buttons don't work other than pause, play, answer, and end. (GAY!)
3. When I end a call and hit the power button to turn the screen off, it comes back on! (with Widget Locker) regular lock works fine to keep the screen off after a call. Hmm
4. Music playback doesn't seem to sound right. (sounds tinny)
5. Volume buttons turn the screen on! (What the hell?)
Click to expand...
Click to collapse
1. I'm on glitch kernel and it's fine for me. You can also customize all sorts of volumes but I've just left em at the default.
2. What other functions are besides play, pause, answer/end aren't working? Track skipping? I have a pair of headphones with inline controls and nothing works on MTD roms for me, so your already a bit ahead of the curve in comparison.
3. Sounds like something with widgetlocker, not necessarily the phone.
4. Adjust settings in Voodoo control if you need. Music sounds *amazing* with my setup. I personally delete DSPmanager and just use VC.
5. This is something that can be turned on or off with CM7/MIUI. You didn't say what rom or kernel you're using so it's kinda hard to help.
k_nivesout said:
1. I'm on glitch kernel and it's fine for me. You can also customize all sorts of volumes but I've just left em at the default.
2. What other functions are besides play, pause, answer/end aren't working? Track skipping? I have a pair of headphones with inline controls and nothing works on MTD roms for me, so your already a bit ahead of the curve in comparison.
3. Sounds like something with widgetlocker, not necessarily the phone.
4. Adjust settings in Voodoo control if you need. Music sounds *amazing* with my setup. I personally delete DSPmanager and just use VC.
5. This is something that can be turned on or off with CM7/MIUI. You didn't say what rom or kernel you're using so it's kinda hard to help.
Click to expand...
Click to collapse
Oh yeah, I totally forgot to tell you what ROM I'm using.
I'm on the Geewiz 2.3 Gingerbread ROM and kernel because I always like some goodies but I try to stay as close to stock as possible for stability reasons. I know the volume issue is with Widgetlocker but it didn't do that on the Dinc so, I have to have something to blame right? Ha...
Do the US Cellular Mesmerize phones have the same issues as our phones? Ya know like the headset control, in-call volume too high and all that?
Oh I gotcha, does the kernel you're using support voodoo sound? If not, I'd try out another one that does and then check out your music. And yes, I think the issues that are common to the phone affect the fascinate/mesmerize/showcase since they're essentially the same phone. I don't know much about touchwiz roms, but I'd suggest looking into a kernel with more features, you might be able to tweak those things that you're having an issue with.
Sent from my SCH-I500 using Tapatalk
I have a guide to kernels for eh03 here http://forum.xda-developers.com/showthread.php?t=1459905 all 3 tw kernels have voodoo sound as of latest updates iirc
Sent from my SCH-I500 using XDA App
I tried the KGB kernel and it has an option to boost in-call volume but nothing to lower it. The tinny sound issue was my inline remote I use for the headphones, it had a faulty volume slider that needed some cleaning. Thanks for all your help!
k_nivesout said:
Oh I gotcha, does the kernel you're using support voodoo sound? If not, I'd try out another one that does and then check out your music. And yes, I think the issues that are common to the phone affect the fascinate/mesmerize/showcase since they're essentially the same phone. I don't know much about touchwiz roms, but I'd suggest looking into a kernel with more features, you might be able to tweak those things that you're having an issue with.
Sent from my SCH-I500 using Tapatalk
Click to expand...
Click to collapse
Oh okay, I thought all theses issues were probably software issues with Verizon's ROM/kernel. Yes, Geewiz kernel supports voodoo.
Droid Razr Maxx
Well I guess this is my goodbye... I scored an awesome deal on a Motorola Droid Razr Maxx off of Craigslist and it's time for me to move on.. Thanks for all your help and I hope to see you all sometime in other forums.

[Q] Some questions

1) Knowing what ROM is the best is kind of subjective, so it's a silly question to ask without clarification. Perhaps if one gives some perspective, that might help?
I used the stock ROM until the built-in browser refused to work in https, and some of the things just bugged me in that version. Some extra bulk in that ROM. That for one, and the fact one couldn't tether easily for fre with it aswell. So, I am now running miniCM7. It's miles and miles better than the 2.1 or whatever it was that was the last stock android. Still, it seems kind of bulky for my taste at times. All these silly (built-in)apps I don't really even want. With this in mind, what ROM would you recommend for someone who:
-wants a functional internet/phone/camera/best performance
-wants the lightest OS possible that can do this
If it's ugly, I don't care. If it doesn't have a sound recorder or some car app, I don't care.
I have to add though, that I really love CM7. The only times it fails me is when there's some serious stress regarding the phone use. If there's a way to modify CM7 (and it's legal to do so), that would help too if you can help me out by pointing towards the instructions
2)This is a bit out there I guess, but is it possible to actually upgrade x10 minipro hardware? I guess the phone is getting too old and I really love everything else about it.
Delete unwanted apps by browsing to system / apps by rootexplorer.
Sent from my E10i using xda app-developers app

Categories

Resources