Related
-----------8-14-----------
1.Upgrade MIUI to 1.8.12 (130811). No FC anymore! And the internal 2GB mass storage is accessible! This version is great! Unless DO NOT USE BUILD-IN BACKUP, or all your sd-card apps will be unaccessible! (stockwell is working on this)
2.Since I'm kinda like MIUI, and this job is really time consuming, I decided that I'll only update MIUI in the future.
3.Include all the historical data of MIUI in this release, so that you can see MIUI is really improving!
-----------8-7------------
1.Upgrade MIUI to 1.8.5 (070811). Sometimes I found FC quit frequently. Still testing...
2.Upgrade Oxygen to 110805. System benchmark improved!
3.Battery not tested due to time shortage. And I still don't know how to test hardware video acceleration. May anyone help?
-----------8-2------------
1.Upgrade MIUI to 1.7.29 (010811). This ROM fixed the FC problem due to wrong build.prop. The performance looks same.
2.Change the test method of battery. I turn on the phone, turn of WIFI/BT/GPS/APN, and wait for 8 hours (during the night). In the next morning, I record the battery level left. I haven't test HW stock ROM yet. So far, MIUI is better!
-----------7-31-----------
Upgrade MIUI to 1.7.29 (310711). This ROM is GREAT! It not only fixed the bugs (video recording, audio recording, etc), but also improved the performance dramatically! The benchmark of MIUI now is even higher than Oxygen! I think that's due to the latest Android 2.3.5.
But the only problem for MIUI now, is that there are toooooo many FC!
-----------7-30-----------
1.Update battery power consumption, according to Katu2006's opinion and test result. Thanks mate!
2.Upgrade Oxygen to version 110730. It fixed the 720p video recording, and the benchmark seems even better!
-----------7-29-----------
Hi guys!
I just transferred to HW U8800 from SE X1 (WM). Since I've made an X1-ROM benchmark and it was pretty useful for some friends there, I think probably I can do the same thing here as well. So, that's why I make my first post of this.
I'd like to thank the cooks that contributed so much for our U8800. Without your guys, my U8800 is just an ordinary phone.
I'm just using my U8800 for 2 weeks, and still learning Android system. So, if you have any suggestions, please don't hesitate to let me know.
Finally, I'm not a cook or expert on this. Definitely I might make some mistakes, and that means NO offense to any cooks or personnals. I just want to contribute some efforts to someone might in need. I also want to use this for the decision of my U8800 ROM.
Cheers!
China_1 said:
Hi guys!
I just transferred to HW U8800 from SE X1 (WM). Since I've made an X1-ROM benchmark and it was pretty useful for some friends there, I think probably I can do the same thing here as well. So, that's why I make my first post of this.
I'd like to thank the cooks that contributed so much for our U8800. Without your guys, my U8800 is just an ordinary phone.
I'm just using my U8800 for 2 weeks, and still learning Android system. So, if you have any suggestions, please don't hesitate to let me know.
Finally, I'm not a cook or expert on this. Definitely I might make some mistakes, and that means NO offense to any cooks or personnals. I just want to contribute some efforts to someone might in need. I also want to use this for the decision of my U8800 ROM.
Cheers!
Click to expand...
Click to collapse
That's cool to keep a sheet with current roms performance level and stage of usability.
I would want you to continue working on updating as it's hard for some to keep track which rom is up to date and which rom is fastest
It's good to know that my work is useful. I'll try my best. But it's very time consuming, as you can imagine...
Anyway, thanks!
very good really. i saw that you didnt test the battery life, but you cant say nothing about this?
vlc_marcos said:
very good really. i saw that you didnt test the battery life, but you cant say nothing about this?
Click to expand...
Click to collapse
You are right. Battery life (or power consumption) is very important. But I have to find a proper way to do the test! You know, just let the phone wait for a whole day and night is not a effective way (and I myself have to use the phone!). Is there any suggestions?
something like normal use, if you have another phone to use, you can think about a test like 30 sms to your self or another number, 3 or 4 benchs let the music player work during 2 hours and one or 2 youtube movies and the rest left it alone to see how is his behavious on idle
I've been playing gameloft's Dungeon Hunter for a few days now and noticed that it practically sucks the juice out of the phone. So maybe use that game, or one similar? You could monitor battery consumption AND performance. And, it's also entertaining!
Sent from my u8800 using XDA Premium App
Aaaaaaaaand...
And you could run the game while keeping wifi and bluetooth on with max brightness ^^
Ok, I've been testing ALL versions of Roms available at this point and I can tell you that playing a game is not a relevant test, as everybody is interested in power draining during normal daily usage, with Wifi and BT all all the time, 1-2 calls/day, 2 email accounts with push and some browsing (weather/news etc).
What you should do is install each Rom and use it with all options mentioned always on and measure the time it takes to fully discharge.
I've done multiple tests, on B160/B137/Miui/Oxygen etc With all options mentioned above, I NEVER got more than 24h with stock Roms, to be frankly honest, NO FROYO based rom stock/custom has ever gone over the 24h mark for me.
Both Miui and Oxygen have absolutely amazing power drain, over night I lost like 7% of the battery and with everything mention always on, I get at least 40h.
You should correct the statement with the power drain, as Miui and Oxygen have MUCH better power drain if not twice as better compared to stock Roms.
Another thing you got wrong is the hardware acceleration, which is available in Oxygen.
At this point in time, there is nothing better than Oxygen and thank God that is available, cause the Froyo Roms are terrible, especially in terms of power consumption.
I think you are not able to refresh it that fast,because Oxygen is updating every day recently
vlc_marcos said:
something like normal use, if you have another phone to use, you can think about a test like 30 sms to your self or another number, 3 or 4 benchs let the music player work during 2 hours and one or 2 youtube movies and the rest left it alone to see how is his behavious on idle
Click to expand...
Click to collapse
OIC. I think I need to find a more effective way. Is there any battery lasting benchmark software?
Vk_ said:
I've been playing gameloft's Dungeon Hunter for a few days now and noticed that it practically sucks the juice out of the phone. So maybe use that game, or one similar? You could monitor battery consumption AND performance. And, it's also entertaining!
Sent from my u8800 using XDA Premium App
Click to expand...
Click to collapse
Thanks for you advice. I'll try that game!
katu2006 said:
Ok, I've been testing ALL versions of Roms available at this point and I can tell you that playing a game is not a relevant test, as everybody is interested in power draining during normal daily usage, with Wifi and BT all all the time, 1-2 calls/day, 2 email accounts with push and some browsing (weather/news etc).
What you should do is install each Rom and use it with all options mentioned always on and measure the time it takes to fully discharge.
I've done multiple tests, on B160/B137/Miui/Oxygen etc With all options mentioned above, I NEVER got more than 24h with stock Roms, to be frankly honest, NO FROYO based rom stock/custom has ever gone over the 24h mark for me.
Both Miui and Oxygen have absolutely amazing power drain, over night I lost like 7% of the battery and with everything mention always on, I get at least 40h.
You should correct the statement with the power drain, as Miui and Oxygen have MUCH better power drain if not twice as better compared to stock Roms.
Another thing you got wrong is the hardware acceleration, which is available in Oxygen.
At this point in time, there is nothing better than Oxygen and thank God that is available, cause the Froyo Roms are terrible, especially in terms of power consumption.
Click to expand...
Click to collapse
THANKS MATE!
It's good to know that someone is also testing the ROMs, and can share some of the experiences. I think the hardest thing for me is the battery test. I've revised the result, according to your opinion.
And about hardware video acceleration, when I use Mobo player, it seems always very laggy, no matter which ROM I use. So, how to prove that the hardware acceleration is on?
jiangheng90 said:
I think you are not able to refresh it that fast,because Oxygen is updating every day recently
Click to expand...
Click to collapse
I do believe that cooking a ROM is much complex and time consuming than testing one.
Your work is excellent! Thanks !
Escellent overview China_1. Thank you!!
great work m8
ps: I have a doubt, did you put the cpu freq at 800mhz? because both (miui and oxygen) has the cpu at 1ghz per default.
China_1 said:
THANKS MATE!
It's good to know that someone is also testing the ROMs, and can share some of the experiences. I think the hardest thing for me is the battery test. I've revised the result, according to your opinion.
And about hardware video acceleration, when I use Mobo player, it seems always very laggy, no matter which ROM I use. So, how to prove that the hardware acceleration is on?
Click to expand...
Click to collapse
It's hard to tell when GPU is used and when it's not, but in my view, actionscripts (which are used when GPU is not required/unavailable) are sometimes as fast as GPU in rendering simple things.
I may be wrong here, but this is just my understanding...
The best way to tell if GPU is active is by measuring the frames/sec...on action scripts you usually get lower FPS...That's why in testing Quadrant, you get much more points in 3D rendering tests, when having hardware acceleration active.
If you search on the market for "OpenGL Test" or "OpenGL Frame Rate Test", these should test the GPU specifically.
There is an example here:
http://www.yeahbutisitflash.com/?p=2447
d3xtr0 said:
great work m8
ps: I have a doubt, did you put the cpu freq at 800mhz? because both (miui and oxygen) has the cpu at 1ghz per default.
Click to expand...
Click to collapse
Nope. I just used the default CPU setting. So, this might be a reason why Oxygen has such a high CPU score.
katu2006 said:
It's hard to tell when GPU is used and when it's not, but in my view, actionscripts (which are used when GPU is not required/unavailable) are sometimes as fast as GPU in rendering simple things.
I may be wrong here, but this is just my understanding...
The best way to tell if GPU is active is by measuring the frames/sec...on action scripts you usually get lower FPS...That's why in testing Quadrant, you get much more points in 3D rendering tests, when having hardware acceleration active.
If you search on the market for "OpenGL Test" or "OpenGL Frame Rate Test", these should test the GPU specifically.
There is an example here:
http://www.yeahbutisitflash.com/?p=2447
Click to expand...
Click to collapse
I know basically what GPU and hardware acceleration means. And, to turn on hardware acceleration, you need the support of: 1. hardware; 2. O/S and driver; 3. software application. So, to prove that a certain ROM is h/w acceleration supported and measure the performance, we need to find a compatible software.
And, there are usually two kinds of h/w acceleration: 3D animation, and HD video.
U8800's GPU is Adreno 205, shoud be very good at 3D. But the performance is not that good. I think we need more optimization of the O/S and drivers.
Hey guys,
First off, I don't post much on here, but have been doing alot of reading to stay "up-to-date". Yesterday, I just got the Nexus S 4G through Sprint cuz my Epic 4G took a crap and they were backordered so I said sure to the Nexus S.
I spent most the day yesterday looking for ROMs for it and found out about ICS and got all excited for that. So, after looking around I decided on Crossbones 0.1.3 ICS. Overall, I'm liking it but after using it for about a day now, I am noticing the battery life (in comparison to my Epic, which ran the current Legendary ROM with the Samurai Kernel) is HORRIBLE. I don't want to be quick to say it's the phone, ROM, or ICS though. Maybe there's a different way of closing out unused apps that I don't know about? I did just find that you can swipe away unused recent apps. Will that help?
Basically, for a ROM, I look for stability, battery life, speed, and looks. In that order. In GB, I always used Launcher Pro, btw.
So, my question is for those that use or used Crossbones, what are your experiences so far? Also, if it's recommended that I go back to GB for awhile until things get a lil better on ICS (I heard its coming OTA soon), which ROM are people liking? With ICS out now, searching for a good GB ROM has become a lil difficult. So far I read about MUIU (or whatever it is) and CM7, which my gf has on her Dinc2 and her Nook Color. I'm kinda "eh" about CM7. It "just works" imo and I think that's what they are going for. Def not a fan of the looks though. I also miss my power options in my notification pull down too.
PS-
That and I can't get Facebook to add to my account sync. When I go to add it, it does it, goes back to the accounts screen, but its not there. Very strange. Ok, gonna shut up now. this is long enough. lol Thanks in advance.
I've had my Nexus S for a couple of weeks now, I put the stock ICS ROM on the first day and during this time my battery has significantly improved. There are probably three reasons for this, but perhaps not all will apply to you?
1) I've stopped turning everything on, all of the time and constantly tweaking / fiddling / admiring the AMOLED.
2) I've refined how the device uses battery (logged out of Google+).
3) The battery has matured a little.
There's another side effect...
4) I've stopped worrying about the battery so much as I get a day of use from it.
Ice Cream Sandwich and ROMs using it are gonna improve in time. Gingerbread has been out for a year or so and has all this development. So from this there's a lot of potential from ICS...
I'm going to keep my device running the standard ROM for the time being as it's my daily driver, but wanting a device to potentially brick and hack. Thinking about the Galaxy S.
davidsteele1975 said:
I've had my Nexus S for a couple of weeks now, I put the stock ICS ROM on the first day and during this time my battery has significantly improved. There are probably three reasons for this, but perhaps not all will apply to you?
1) I've stopped turning everything on, all of the time and constantly tweaking / fiddling / admiring the AMOLED.
2) I've refined how the device uses battery (logged out of Google+).
3) The battery has matured a little.
There's another side effect...
4) I've stopped worrying about the battery so much as I get a day of use from it.
Ice Cream Sandwich and ROMs using it are gonna improve in time. Gingerbread has been out for a year or so and has all this development. So from this there's a lot of potential from ICS...
I'm going to keep my device running the standard ROM for the time being as it's my daily driver, but wanting a device to potentially brick and hack. Thinking about the Galaxy S.
Click to expand...
Click to collapse
Thanks for the reply. So far in terms of battery saving tricks, I've disabled animations, the screen is set to about 1/4 brightness, only thing that constantly does anything is k9
mail to check my inbox every 15 mins (that I'm aware of lol). So it could be that my battery needs to "mature"? Btw, are there any good themes out yet? I miss my transparent text msg threads and I really miss my power controls on the notification pull down. I'm def not digging the white on the contacts and SMS screens. Lol
::BUMP:: Seriously? No one else?
Well is was getting bad battery and weird force closes on cross bones, i'm on vhgomex(thinks that's right), it's been a lot better for me and it has the notification power widget in it
Sent from my Nexus S 4G using Tapatalk
BrianDigital said:
Well is was getting bad battery and weird force closes on cross bones, i'm on vhgomex(thinks that's right), it's been a lot better for me and it has the notification power widget in it
Sent from my Nexus S 4G using Tapatalk
Click to expand...
Click to collapse
I havent had any issues with the rom running or any FCs... Took a look at gomez. Gonna do a nandroid and give it try. Looks promising, and FB sync is supposed to work. lol
infamshxr said:
::BUMP:: Seriously? No one else?
Click to expand...
Click to collapse
I think you're not getting many answers because your issues have already been addressed. A simple search will find many (most) ROMs with notification toggles and Facebook sync. I personally recommend AOKP.
I'd say it's just the rom. I'm on an ICS rom, everything works great and I have significantly better battery life than before.
I'm on AndroidME with Eugene's speedy-3 kernel. I don't have Facebook sync and power toggles in notification though, but I don't really care for those two features anyway.
Well I'm on Gomez now. Things already seem to be better. Absolutely no issues so far. I'll know for sure in a day or so.
Well I uninstall bloat.sys apps I don't use with root uninstaller
As for Bette battery life. Honestly think. What could someone do to the phone to put out better battery life. Almost nothing but SBC kernels and the CPU speed and goveners. That's it.
Most of you guys don't have battery issues you just play with your phone all day instead of doing your work.
Sent from my Nexus S 4G using XDA App. Developer of brickROM, and OP of XDA Thread of The Year 2011.
Shark_On_Land said:
Well I uninstall bloat.sys apps I don't use with root uninstaller
As for Bette battery life. Honestly think. What could someone do to the phone to put out better battery life. Almost nothing but SBC kernels and the CPU speed and goveners. That's it.
Most of you guys don't have battery issues you just play with your phone all day instead of doing your work.
Sent from my Nexus S 4G using XDA App. Developer of brickROM, and OP of XDA Thread of The Year 2011.
Click to expand...
Click to collapse
A: that was fairly rude. I'm legitimately asking for help and advice. I didn't make the thread to be judged or ridiculed on my phone usage. I don't judge others on how they use they're phone, so why should I be?
B: I'm comparing this all with my epic. I don't over clock or mess with the CPU settings cuz that's beyond my knowledge atm. Like I said, battery seems MUCH better now with this rom . Now my only gripe is volume. Way quieter on this phone which seems to be a known issue. Trying out volume+ soon. Also, at the end of my day, I'll post my battery stats and see what you guys think. But like I said, I think its OK now.
Im on bigxie's rom and icup kernel im getting great battery life with this but thats just me.i dont know whats great for you.try this rom its somewhat minimalist or pure stock with just statusbar widgets and other features.no 'omg' tweaks that cause more harm than good.and it has trebuchet which is perfectly put into the mix.im satisfied with this .been with this rom since build 1 and ive been happy with its consistency.no bugs encountered
Sent from a Nexus S
dark06 said:
Im on bigxie's rom and icup kernel im getting great battery life with this but thats just me.i dont know whats great for you.try this rom its somewhat minimalist or pure stock with just statusbar widgets and other features.no 'omg' tweaks that cause more harm than good.and it has trebuchet which is perfectly put into the mix.im satisfied with this .been with this rom since build 1 and ive been happy with its consistency.no bugs encountered
Sent from a Nexus S
Click to expand...
Click to collapse
Thanks for the opinion. I'll keep that one in mind if this doesn't work out. Sounds a lot like Gomez. Gomez has basically just what you listed. I'd def take stability over extra crap. Lol
Sry for the double post,but to report back, totally forgot to post my battery stats, but they were definitely better. By far. Still not much luck on the sound tho. Got an app the boosts my media volume but my ringer wasn't affected, which sucks. Anything on this that I haven't possibly found?
I'm going back to CM7. 7.2 is out and honesty its just more optimized for this device. CM optimizes their ROMs to very fast high standards and do stuff a lot of you newbies can't even think of. (Yes, these will be implemented in BESTROM.)
So I'm going back. To smoothness.
Sent from my Nexus S 4G using XDA App. Developer of brickROM, and OP of XDA Thread of The Year 2011.
Shark_On_Land said:
I'm going back to CM7. 7.2 is out and honesty its just more optimized for this device. CM optimizes their ROMs to very fast high standards and do stuff a lot of you newbies can't even think of. (Yes, these will be implemented in BESTROM.)
So I'm going back. To smoothness.
Sent from my Nexus S 4G using XDA App. Developer of brickROM, and OP of XDA Thread of The Year 2011.
Click to expand...
Click to collapse
You really shouldn't be so rude and demean other members of this forum like that. Frankly, no one cares if you're going back to CM7 or not. But thank you for your belittling feedback.
To the original poster, I'm running Pete Alfonso's nightlies along with Mathkid's Matrix CFS kernel. With a bit of overclock and tweaking of the kernel settings, I get great smoothness, stability, and decent battery life. To me, any battery life that gets me from "up in the morning" to "home at night" is fine, because I have my charger at my desk. But typically, I can survive a full 24 hours on one charge.
Who knows, though. Maybe I'm just too much of a newbie to realize the full potential of what my device can do and therefore it's my fault that the battery life is as good as it is.
Hey! I've just recently switched to my Galaxy Nexus, but was a Crespo owner since it came out. Been reading your post but I would agree that you should try out the AOKP rom along with a custom undervolted kernel for longer battery life.
I haven't really tinkered with my Nexus S in awhile (I gave it to my gf when I got the Galaxy Nexus) but the last thing I remembered was either installing aokp or cm9. In due time the custom ics roms will improve and the power widgets in the notification bar will be brought back, but they usually want to focus on stability then add new features little by little. Hope you are having fun your Crespo!
Sent from my Galaxy Nexus using xda premium
So far I'm still rocking gomez's. Really loving the battery life. Only issue I've had is 3g doesn't always come back after using wifi. Not a big deal tho I guess. Really stable too. I was thinking of using mathkidskernel but don't wanna possibly screw up what I got now. I'm backed up so maybe one of these days. Heard alotof good things about mathkids kernel. Heard good things about aopk too, so that's my other go to. Lol
kto_matchu said:
You really shouldn't be so rude and demean other members of this forum like that. Frankly, no one cares if you're going back to CM7 or not. But thank you for your belittling feedback.
To the original poster, I'm running Pete Alfonso's nightlies along with Mathkid's Matrix CFS kernel. With a bit of overclock and tweaking of the kernel settings, I get great smoothness, stability, and decent battery life. To me, any battery life that gets me from "up in the morning" to "home at night" is fine, because I have my charger at my desk. But typically, I can survive a full 24 hours on one charge.
Who knows, though. Maybe I'm just too much of a newbie to realize the full potential of what my device can do and therefore it's my fault that the battery life is as good as it is.
Click to expand...
Click to collapse
sorry if that was rude but you have to take in count that
I myself is using modified CM7.1RC0AOSP2.3.7GB as base. But far as CM9AOSP4.0.3ICS goes its still not ready for folks like me for DD yet.
As I described below how extensively its optimized and most of it is outside the scope of current XDA.
What you have to understand is performance is not measured via synthetic benchmarks (ex: Quadrant). The biggest issue with people is that they don't know enough to know that they don't know, so they compare it with silly numbers (ex: score) they can't comprehend what they see, much less put numbers behind real life activities that's not applicable in controlled environment.
OS development which eliminates most of it but on software level custom base rom (ex: CyanogenMod) is highly optimized and tweaked to run on optimal performance. Mostly, but not all. But does it mean it can't be tweaked any further? (Rhetorical) No. How do I know? We (scope outside of XDA) tweaked it to the next level. How you ask?
1) Optimized ext4fs: reduced r/w rate (healthy NAND lifespan), improved journaling (corrupted data writeback integrity) = Which improves the IOPs and performance access rate.
2) HC3.x fugu binaries, patched sqlite libraries, mSD read ahead buffer fix.
3) Modified VM: OOM (Out Of Memory), LMK (Low Memory Killer), VM heap (Virtual Machine), DRA (Dirty Ratio), DBR (Dirty Background Ratio), DWC (Dirty Writeback Centisecs), DEC (Dirty Expired Centisecs), SWP (Swap), VCP (VFS Cache Pressure).
4) Increased minfree value: Background, Foreground, Empty, Hidden, Visible, Secondary, Content.
5) Optimized cache: File and Drop cache, Forced cache (resident loop).
6) Custom kernel: OC/UC, UV/SVS/VDD, BFS/CFS, RSU/NP/VR/SP supported.
7) Custom ROM: Optimized Rom script and props (ex: CyanogenMod).
this as its tweaked to THE next level. I'll stick with AOSP2.3.7GB until ICS4.X is more stable and we understand more as most memory grouping and adjustments might be changed.
I bet most of you only do 2 of those thing (6&7)
i suggest you try androiduser aosp rom with icup kernel. you dont have to do anything else and with normal usage you'll get 24+ hours
We all know that the GNote Yamaha DAC= fail.
We also know that A2DP on samsung-based devices = fail, because of the abnormally low bitpool- this is the subject of this thread.
Has anyone raised the bitpool issue to Samsung?
Might be a good idea before they release Touchwiz ICS, to make sure that they fix their @#$& kernel.
Otherwise we will have no choice but to use AOSP kernels, or heavily modify the Samsung kernel to completely bypass the Samsung bluetooth stack and use an AOSP version with a higher bitpool instead.
guitarplayerone said:
Ordering a Gnote no matter what, but we all know that the Yamaha DAC= fail.
We also know that A2DP= fail, unless we are running 128kbps files which might not cause issues with the extremely low, stock, closed bitpool issue.
Has anyone raised the bitpool issue to Samsung?
Might be a good idea before they release Touchwiz ICS, to make sure that they fix their @#$& kernel.
(Yes, we could use CM9, which would hopefully fix the bitpool issue, but it is not yet clear if all the nice Spen features will be integrated... probably at least part of the reason any of us purchased Gnotes to begin with)
Click to expand...
Click to collapse
Honestly, CM sucks for me. I know it may be useful for some people to have as AOSP as possible, but stock Android builds still leave a lot to be desired and they never include special characteristics of the device. Look at the Atrix... 9 months to get the fingerprint sensor working, and webtop is still out.
However, other devs could mod this on their ROMs. Is it possible to do so? That's my question here.
guitarplayerone said:
We also know that A2DP= fail, unless we are running 128kbps files which might not cause issues with the extremely low, stock, closed bitpool issue.
Click to expand...
Click to collapse
Could you describe this issue? I use A2DP every day and I haven't noticed any problems.
PickleHead said:
Could you describe this issue? I use A2DP every day and I haven't noticed any problems.
Click to expand...
Click to collapse
Which device is it on? The bitpool set by Samsung on the GSII and GNote, from what I understand, is ~30 (units?). Apparently, to be able to properly stream A2DP media with higher bitrates, a higher bitpool is required.
This is not a problem with stock droid builds or CM9, because they use an open-sourced version of the bluetooth stack, which can be edited relatively easily.
It has been an issue on the most recent gingerbread touchwiz roms
guitarplayerone said:
Which device is it on? The bitpool set by Samsung on the GSII and GNote, from what I understand, is ~30 (units?). Apparently, to be able to properly stream A2DP media with higher bitrates, a higher bitpool is required.
This is not a problem with stock droid builds or CM9, because they use an open-sourced version of the bluetooth stack, which can be edited relatively easily.
It has been an issue on the most recent gingerbread touchwiz roms
Click to expand...
Click to collapse
I was using A2DP on the Note stock rom and I moved to Cassie's rom, I don't notice a problem. I know I'm not an audiophile but I think I can tell between 128k and higher. Is there a more precise way to tell if I'm using the higher bitrates?
My impression was that it ran both cores simultaneously already as needed...which with me would be most of the time.
I guess this just has em on all the time.
rockky said:
My impression was that it ran both cores simultaneously already as needed...which with me would be most of the time.
I guess this just has em on all the time.
Click to expand...
Click to collapse
Just to be clear, this thread is about the bitpool value in the closed-source Samsung bluetooth stack.
What does this have to do with cores?
Don't know HOW the hell this response got on this thread....!
PickleHead said:
I was using A2DP on the Note stock rom and I moved to Cassie's rom, I don't notice a problem. I know I'm not an audiophile but I think I can tell between 128k and higher. Is there a more precise way to tell if I'm using the higher bitrates?
Click to expand...
Click to collapse
If you are using windows, you can just look under the properties of the MP3 file on your computer, and it should have the bitrate on there.
No idea how to do it on android though, as the device has not yet arrived ;-)
A bitrate of 320 kb/s should cause increased chances of stuttering.
Also, could you share which headset you are using? It seems that some have more trouble than others.
Edit: it appears that the stock player doesn't show the bitrate of the file, at least according to Androidcentral
guitarplayerone said:
If you are using windows, you can just look under the properties of the MP3 file on your computer, and it should have the bitrate on there.
No idea how to do it on android though, as the device has not yet arrived ;-)
A bitrate of 320 kb/s should cause increased chances of stuttering.
Also, could you share which headset you are using? It seems that some have more trouble than others.
Edit: it appears that the stock player doesn't show the bitrate of the file, at least according to Androidcentral
Click to expand...
Click to collapse
I didn't know you meant the bitrate of the actual audio files. I use subsonic which downconverts audio to 256 kbps on wifi, or 192 kbps when I'm running on data. I still don't notice any issues. I used to have CRAZY stuttering on my captivate and this is one of the big reasons I upgraded to the note.
I use a Nokia BH-905i.
Ya i can fell that the audio quality over the bluetooth is low compared to other phones...
I searched for a couple minutes and didn't find what I was looking for.
I've been out of the Vibrant scene for about 6 months now but I was looking to turn my Vibrant into a media player so I can just leave it in my car. If I recall correctly, there was a rom that disabled all cellular capabilities on the phone and made it just a touch screen media player.
My questions are:
1. Is there any benefit to using this rom as opposed to a regular rom and just using flight mode?
2. How is the battery life on ICS roms? Last time I had the vibrant I was using the latest Bionix.
Thanks for the help!
1. I'm not sure which ROM you're talking about but I think it was developed by Jellette.
2. ICS ROMS have come a LONG way since then. Battery life depends on your usage, but it is still par on with any other Froyo/GB ROM i've ever used. I use Miui V4 (ICS)
xriderx66 said:
1. I'm not sure which ROM you're talking about but I think it was developed by Jellette.
2. ICS ROMS have come a LONG way since then. Battery life depends on your usage, but it is still par on with any other Froyo/GB ROM i've ever used. I use Miui V4 (ICS)
Click to expand...
Click to collapse
Sounds good, I'll go take a look around the development section.
Thanks!
Is this what you are looking for?
http://forum.xda-developers.com/showthread.php?t=1566651
sahil04 said:
I searched for a couple minutes and didn't find what I was looking for.
I've been out of the Vibrant scene for about 6 months now but I was looking to turn my Vibrant into a media player so I can just leave it in my car. If I recall correctly, there was a rom that disabled all cellular capabilities on the phone and made it just a touch screen media player.
My questions are:
1. Is there any benefit to using this rom as opposed to a regular rom and just using flight mode?
2. How is the battery life on ICS roms? Last time I had the vibrant I was using the latest Bionix.
Thanks for the help!
Click to expand...
Click to collapse
You know. This is kinda funny. I accidentally nicked a transistor when I was playing with my Vibrant and now the SIM is not working at all on my phone so all I can use it for is as a Media Player. And my daughter plays games on it as well. So I can tell you which one to nick and you don't ever have to worry about the SIM card.
As the title says?. I listen to a lot of music via my headphones. Also is there any roms that improve battery life even further?.
Cheers guys
Sent from my iPhone using Tapatalk
These kinds of threads generally don't go far. Everyone uses their device differently, and thus battery will be different for everyone.
As for music, roms won't generally make a difference in audio quality. Some may include Viper4Android, some kernels may have audio level tweaks, but those can both be installed on any rom.
Sent from my Nexus 6P using Tapatalk
What he said. Battery performance depends solely on you and how you use your phone, two people using the exact same ROM can have wildly different experiences with battery. As for which ROMs may have audio tweaks, the answer to your question is as simple as looking at them to find out.
dont expect high fidelity music out of a phone (especially this one), get a portable amp/dac... as far rom and battery life all of them more or less the same, the only way to extend battery life is be on wifi and have your screen constantly at 25% brightness or less
@gibbo82 Any one you want for sound just add this http://forum.xda-developers.com/showthread.php?t=2952137 and you'll be good to go. ? I personally use Dirty Unicorns rom and ak kernel and its my favorite setup but you gotta find what's best for you. That's the beauty of android. Choices.... We have many. Good luck.
Sent from a Di®tY ?
+1 to what most people have said. Rom won't make a difference that much. Definitely check out Viper4Android. Not sure how much of an audiophile you are but like someone already said a dac/amp will also open up new avenues.