Related
I have this problem with my HD2 that i just can't seem to track down on this website just yet, and i have seen one or two persons having the same problem.
when i try taking a picture on my hd2, the picture comes out really sweet i must say, but when taking the pic at night i realise that the dual led's have a lag with the picture actually being taken (about a half second difference), so that the picture is taken AFTER the flash has already stopped, thus leaving the pic as dark as ever, is there any fix for this yet? i'm using mattc Leo + Froyo w/sense 1.8 [kernel: 2.6.32.15 #5] anyone else here having this issue?
i tried out the search but could only find other people having problems with brightness of the flash and other such issues but not the same as mine so i opened a new thread sorry if i didn't enter the correct search criteria and thanks for your time.
That build uses the EVO kernel, the camera flash is a very well known problem right now.
Sent from my HTC HD2 using XDA App
juggs said:
That build uses the EVO kernel, the camera flash is a very well known problem right now.
Sent from my HTC HD2 using XDA App
Click to expand...
Click to collapse
so you mean there's no fix to this and i can't take any photo's at night or in poor lighting? are there any other roms out there that don't have this issue? (and can run as smoothly as this one cuz i find it to be pretty impressive minus the issues i have with the camera flash ofcourse) thanks again!
please people, is there any build out there that doesn't have this issue? are all the builds here created from the Evo kernel, and if not are there any that don't have this issue? i mainly take pictures at night (usual night life activities) and this doesn't help out at all when the camera lags behind the flash.
Not sure if this should be posted here, but considering it needs some development, and it is in the GSM dev forums, I figured it should go here.
Anyway, a couple of days ago I installed V2 and it worked pretty good, but had a few force closes. At that time there was .apk's to install. Now theyre up to V4, and its a flashable zip that doesnt appear to work on our devices. When flashed through recovery, the flash fails at the Model_id check. Not sure if someone here can fix this so its flashable on our phones? seems like a pretty cool camera.
Check it out
http://forum.xda-developers.com/showthread.php?t=1302943
vinscuzzy said:
Not sure if this should be posted here, but considering it needs some development, and it is in the GSM dev forums, I figured it should go here.
Anyway, a couple of days ago I installed V2 and it worked pretty good, but had a few force closes. At that time there was .apk's to install. Now theyre up to V4, and its a flashable zip that doesnt appear to work on our devices. When flashed through recovery, the flash fails at the Model_id check. Not sure if someone here can fix this? seems like a pretty cool camera.
Check it out
http://forum.xda-developers.com/showthread.php?t=1302943
Click to expand...
Click to collapse
Here, try this. I swapped out the model with our version of the Evo3D. I haven't flashed it, but you can test.
Note: Standard disclaimer. I take no responsibility, blah blah blah...
Edit: Updated script
I got pretty much everything working
Sent from my PC36100 using XDA App
sac23 said:
I got pretty much everything working
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Great. Do you have a link?
smw6180 said:
Here, try this. I swapped out the model with our version of the Evo3D. I haven't flashed it, but you can test.
Note: Standard disclaimer. I take no responsibility, blah blah blah...
Click to expand...
Click to collapse
Thanks for fixing! I tried flashing your modified version, it flashed fine,but unfortunately it wiped my device and didnt install the new camera. Also broke the lock screen. No biggie, I got a nandroid backup, so all good! Hopefully sac23 will put up the version he tweaked....
vinscuzzy said:
Thanks for fixing! I tried flashing your modified version, it flashed fine,but unfortunately it wiped my device and didnt install the new camera. Also broke the lock screen. No biggie, I got a nandroid backup, so all good! Hopefully sac23 will put up the version he tweaked....
Click to expand...
Click to collapse
That's what I get for not reading it all the way through, sorry about that. It was supposed to format cache, but the block devices are different so it formatted system. I'll update it and take that one down.
Edit: Fixed, it won't nuke your system now. Not sure if those libs that are included are going to work or not. YMMV.
smw6180 said:
That's what I get for not reading it all the way through, sorry about that. It was supposed to format cache, but the block devices are different so it formatted system. I'll update it and take that one down.
Edit: Fixed, it won't nuke your system now. Not sure if those libs that are included are going to work or not. YMMV.
Click to expand...
Click to collapse
No need to apologize! New version worked great! Well at least I think it did. Not sure about those libs either, guess we'll see!
vinscuzzy said:
No need to apologize! New version worked great! Well at least I think it did. Not sure about those libs either, guess we'll see!
Click to expand...
Click to collapse
My guess is those libs are compiled against the kernel for the GSM version and won't work. But...then again they might. Good luck, sir!
So the only thing that doesn't seem to be working is 3d pics. It takes the picture, but then immediately crashes to the desktop. Along with the issues already posted in the GSM section. So far those libs dont seem to be causing any issues. But then again its 5am, haven't really had a chance to really use anything but the camera.
vinscuzzy said:
So the only thing that doesn't seem to be working is 3d pics. It takes the picture, but then immediately crashes to the desktop. Along with the issues already posted in the GSM section. So far those libs dont seem to be causing any issues. But then again its 5am, haven't really had a chance to really use anything but the camera.
Click to expand...
Click to collapse
It probably has no idea how to use the 2nd camera and gets confuzzled.
smw6180 said:
It probably has no idea how to use the 2nd camera and gets confuzzled.
Click to expand...
Click to collapse
I think the amaze is a 3d camera. You can actually preview the 3d perfectly. Just when you take a pic, it freezes for a few secs and then crashes.
vinscuzzy said:
I think the amaze is a 3d camera. You can actually preview the 3d perfectly. Just when you take a pic, it freezes for a few secs and then crashes.
Click to expand...
Click to collapse
Gotcha. Haven't even seen that phone yet.
Sent from my PG86100 using Tapatalk
Can anyone report on shutter lag? Only thing I find unusable about the Evo 3D camera: shutter lag is at best (with fastest settings, preview off, etc.) 0.5 seconds.
Mike
mikeyxda said:
Can anyone report on shutter lag? Only thing I find unusable about the Evo 3D camera: shutter lag is at best (with fastest settings, preview off, etc.) 0.5 seconds.
Mike
Click to expand...
Click to collapse
From the GSM forum......it seems we need updated kernel with ZERO SHUTTER LAG driver included. So, if HTC doesn't give even kernel src for us we have only choice to wait for new STOCK kernel with ZSL driver.
ZSL means fast speed than galaxy s 2 camera?
Thats one thing I miss
Doesn't work for non rooted evo 3D phone.
Sent from my PG86100 using xda premium
Anybody try on a cdma 3d?
Via My HTC Evo 3D On The Now Network From Sprint.
Rydah805 said:
Anybody try on a cdma 3d?
Via My HTC Evo 3D On The Now Network From Sprint.
Click to expand...
Click to collapse
Yes, the. zip in the 2nd post flashes, and works pretty good, except the camera crashes when taking 3d pics. 2d works great.
Any way to use this without root? And can you install as a separate app? That would be cool.
boom!! from my shooter
Doesnt the MyTouch 4g slide use the same camera? that released right around the time of the E3D too. anyone know if that source got released?
I cant get hdr to work (it takes pic but no different than any other pic), burst wont select, and there were a couple others that didnt work. In 3d mode, in addition to crashing, it doesnt adjust the exposure and alignment is way off so i dont think the amaze has the 3d software programmed.
I was wondering, since there aren't as many roms for the gsm 3vo as I would like, and since the Sensation is very similar to our phone expect the camera, would it be possible to port a sensation rom to the gsm evo 3d? Or even better would it work out of the box(except camera of course) by only flashing an evo kernel?
vipirius said:
I was wondering, since there aren't as many roms for the gsm 3vo as I would like, and since the Sensation is very similar to our phone expect the camera, would it be possible to port a sensation rom to the gsm evo 3d? Or even better would it work out of the box(except camera of course) by only flashing an evo kernel?
Click to expand...
Click to collapse
I wanna know too...
bump.
vipirius said:
I was wondering, since there aren't as many roms for the gsm 3vo as I would like, and since the Sensation is very similar to our phone expect the camera, would it be possible to port a sensation rom to the gsm evo 3d? Or even better would it work out of the box(except camera of course) by only flashing an evo kernel?
Click to expand...
Click to collapse
HMZX said:
I wanna know too...
bump.
Click to expand...
Click to collapse
I think you can definitely test w/o causing permanent damage. For the smoothest test experience, you'll want to be familar with a custom recovery and the backup/restore modes available along with the type of internal memory unlock used on the device (Revolutionary or HTC official method).
Once you're familar with the basics, it would be fairly simple to test. The combinations for testing, off the top of my head, would be:
1) Sensation kernel and EVO 3D ROM.
2) Sensation kernel and Sensation ROM.
3) EVO 3D kernel and Sensation ROM.
Speaking from experience, once you're familar with how to load kernels and ROMs, the process is fairly generic across devices once write access to the internal memory is obtained.
Again, I'll re-iterate the importance of making a proper backup and being familar with the restoration process.
There are only two main hazards which come to mind:
1) Make sure NOT to flash the radio, bootloader, or any other file. ONLY flash kernel/system partitions.
2) Before flashing kernel/system partitions ensure the partition sizes between devices are the same, or EVO 3D is larger. Not sure the device limits and stops partitions from overwriting each other as I know some older devices did not and this caused an unrecoverable damage.
I'm sure if I missed anything, somebody else will post up. Hope that helps provide some technical background and logic to the approach! Keep us updated!
Thanks for the reply. I'm already familiar with flashing kernels/roms and how to make a nandroid backup etc so that isn't a problem. However I have 1 question, how exactly would I find the partition sizes of the sensation, I couldn't find it on the internet and I don't have a sensation that I can check.
Anyways I found a few posts on the forums of people claiming sensation roms work almost flawlessly except for the camera, so the next question would be if there are any apk's/libs etc. I can copy to the sensation rom to get the camera working. I'm no dev myself so I don't have a clue, but if someone could tell me I would appreciate it. Thanks.
Well you can't just flash a sensation ROM out of the box. You would at least need to change the mount points in the updater script otherwise you will get nothing. Regarding the camera, there are libs in /system/lib like liboemcamera.so and such. Not sure fixing the camera would be as simple as copying libs over from our phone though.
Sent from my PG86100 using Tapatalk
EDIT: Well I took a sense 3.6 ICS rom from the sensation forums, changed the mount points, and replaced the boot.img with ours. It boots to the bootanimation and then reboots by itself. So it is possible I may look at it more tonight.
EDIT 2: I just saw you were talking about the gsm 3d, I did this on the CDMA. The process would be the exact same though.
Yeah I have a GSM phone so that's why I said GSM. Also wouldn't porting to the GSM version be easier then to the CDMA version since the sensation is also GSM?
Anyways I'm kinda busy today but I will try to see if it boots on my phone tomorrow and post my results. I'll.also try to get the camera to work by copying libs like you suggested.
Sent from my HTC EVO 3D X515m using XDA App
vipirius said:
Thanks for the reply. However I have 1 question, how exactly would I find the partition sizes of the sensation, I couldn't find it on the internet and I don't have a sensation that I can check.
Anyways I found a few posts on the forums of people claiming sensation roms work almost flawlessly except for the camera, so the next question would be if there are any apk's/libs etc. I can copy to the sensation rom to get the camera working. I'm no dev myself so I don't have a clue, but if someone could tell me I would appreciate it. Thanks.
Click to expand...
Click to collapse
Answer to first question: partition sizes are generally mentioned in a handful of different locations depending on the device: /proc/partition(s), /proc/emmc or /proc/mtd off the top of my head. Since the devices are similar and others have already tried this approach, probably not a concern, but none the less never hurts to learn more!
Answer to second question: the cameras (2 of them for 3D) on this device, along with the 3D display are the two biggest difficulties in porting AOSP such as CM to this device, in my opinion. they use closed source proprietary code from HTC. this requires a bit of reverse engineering and kanging from other random sources in order to get a final working product. personally, i wouldnt invest the time/effort into it, but others might find it a beneficial endeavor for themselves. either way, you're guaranteed to learn a bit about cameras! as stated above, all android libraries are loaded in /system/lib.
For the camera, I view android as having essentially three components contributing to a fully functional camera.
1) Camera drivers in the kernel
2) Camera libraries in /system/lib
3) Camera application apk file for Android UI
These three need to work together to at least some degree in order for there to be some functionality in the camera.
Gumby63 said:
EDIT: Well I took a sense 3.6 ICS rom from the sensation forums, changed the mount points, and replaced the boot.img with ours. It boots to the bootanimation and then reboots by itself. So it is possible I may look at it more tonight.
Click to expand...
Click to collapse
Might be more off topic but could related also to this OP depending on his approach. If you encounter the boot animation this is generally a good sign the kernel has fully loaded and is handing off to the ramdisk/init process.
There are two possible situations at this point
1) If the boot animation loops, i.e. starts over and over, this shows there is an issue with Android/ramdisk init process. Adb has generally been loaded by this point and the issue should be outlined in logcat showing the specific .apk file along with line number which makes for a great starting point in troubleshooting.
2) If the boot animation starts/completes but the device completely reboots back to the splash screen, this is more difficult to troubleshoot. I'm not aware of a great approach to this but I might start by glancing at the /proc/last_kmsg file along with executing adb logcat as soon as I see the boot animation in an attempt to grab the logcat before the device reboots itself.
Good luck and keep us updated!
joeykrim said:
Might be more off topic but could related also to this OP depending on his approach. If you encounter the boot animation this is generally a good sign the kernel has fully loaded and is handing off to the ramdisk/init process.
There are two possible situations at this point
1) If the boot animation loops, i.e. starts over and over, this shows there is an issue with Android/ramdisk init process. Adb has generally been loaded by this point and the issue should be outlined in logcat showing the specific .apk file along with line number which makes for a great starting point in troubleshooting.
2) If the boot animation starts/completes but the device completely reboots back to the splash screen, this is more difficult to troubleshoot. I'm not aware of a great approach to this but I might start by glancing at the /proc/last_kmsg file along with executing adb logcat as soon as I see the boot animation in an attempt to grab the logcat before the device reboots itself.
Good luck and keep us updated!
Click to expand...
Click to collapse
Well yeah it completely reboots back to the splash screen. During the bootanimation, I can't get a logcat and adb says there is no device connected. This isn't my first port but I've never had this happen lol. I'll look into what you said.
Sent from my HTC Flyer P510e using Tapatalk
Well, I successfully installed Android Revoltion HD 3.6.13, It boots, everything seems to work, however I didn't test GPS and BT yet. And the camera is well, half working I guess. The camera app opens, and i can see the controls etc but no image comes, and when I press the capture button the flash pops but the app FC's after that. I'm gonna try flashing [MOD] Camera from HTC Amaze 4G, v0.11 and see if it works. If it doesn't I'll copy over all the camera related libs I can find from my old ROM and see if it works then.
Edit: Hahahaha yessss it works I just flashed the Amaze camera app and now camera works only 2D of course but it's enough for me. I'll keep testing for a few days and of there aren't any serious bugs I can find I'll be using this as my daily driver from now on
Edit2:Audio doesn't seem to work If I can't get that fixed then this ROM will be useless :/
vipirius said:
Edit2:Audio doesn't seem to work If I can't get that fixed then this ROM will be useless :/
Click to expand...
Click to collapse
then move over the proper sound drivers also located in /system/lib, /system/lib/modules and /system/lib/soundfx
t3project said:
then move over the proper sound drivers also located in /system/lib, /system/lib/modules and /system/lib/soundfx
Click to expand...
Click to collapse
Yeah that's what I was going to do, but thanks anyways. I'll report back on my success.
Gumby63 said:
Well you can't just flash a sensation ROM out of the box. You would at least need to change the mount points in the updater script otherwise you will get nothing. Regarding the camera, there are libs in /system/lib like liboemcamera.so and such. Not sure fixing the camera would be as simple as copying libs over from our phone though.
Sent from my PG86100 using Tapatalk
EDIT: Well I took a sense 3.6 ICS rom from the sensation forums, changed the mount points, and replaced the boot.img with ours. It boots to the bootanimation and then reboots by itself. So it is possible I may look at it more tonight.
EDIT 2: I just saw you were talking about the gsm 3d, I did this on the CDMA. The process would be the exact same though.
Click to expand...
Click to collapse
When you say Replaced the Boot.img, How'd you do that? Was it done with a ROM kitchen? Reason I'm asking because I read something saying that a Complete Rom Port could be achieved just with Apps on our phones... Using something like Root Explorer and whatever else (Can't Remember?) But I was wondering is that True?
And as for Extracting the Kernel can that Also be done Without the use of a Computer? In other words straight from a phone?
Thanx in Advance guys!!
PMGRANDS said:
When you say Replaced the Boot.img, How'd you do that? Was it done with a ROM kitchen? Reason I'm asking because I read something saying that a Complete Rom Port could be achieved just with Apps on our phones... Using something like Root Explorer and whatever else (Can't Remember?) But I was wondering is that True?
And as for Extracting the Kernel can that Also be done Without the use of a Computer? In other words straight from a phone?
Thanx in Advance guys!!
Click to expand...
Click to collapse
im not sure what you read but IT WAS WRONG..........
while you can do some of this stuff from your phone, you can not do a complete port properly without a computer
PMGRANDS said:
When you say Replaced the Boot.img, How'd you do that? Was it done with a ROM kitchen? Reason I'm asking because I read something saying that a Complete Rom Port could be achieved just with Apps on our phones... Using something like Root Explorer and whatever else (Can't Remember?) But I was wondering is that True?
And as for Extracting the Kernel can that Also be done Without the use of a Computer? In other words straight from a phone?
Thanx in Advance guys!!
Click to expand...
Click to collapse
Yeah like t3project said, that is wrong.
But anyhow, I replaced the boot.img simply by opening the two ROMs with winrar and then deleting and replacing it. And to extract the kernel, you would need to split the boot.img either using a kitchen or some other tools that do the job.
A little update on my port: I still haven't gotten it to fully boot, it just keeps restarting
Gumby63 said:
A little update on my port: I still haven't gotten it to fully boot, it just keeps restarting
Click to expand...
Click to collapse
Aren't you on the CDMA EVO? If you are wouldn't the radios be completely different since the sensation is a GSM device? So maybe that's what's causing the reboot issues. I mean as far as I know even porting from the CDMA EVO to the GSM EVO is hard so wouldn't porting from the sensation to the CDMA EVO be even harder?
vipirius said:
Aren't you on the CDMA EVO? If you are wouldn't the radios be completely different since the sensation is a GSM device? So maybe that's what's causing the reboot issues. I mean as far as I know even porting from the CDMA EVO to the GSM EVO is hard so wouldn't porting from the sensation to the CDMA EVO be even harder?
Click to expand...
Click to collapse
this is only patrialy the problem. flashing roms doesnt affect the radio so that wouldnt change but i there are some other libs that need to be moved that are associated with communication to the radio. cant remember which off the top of my head
Gumby63 said:
Yeah like t3project said, that is wrong.
But anyhow, I replaced the boot.img simply by opening the two ROMs with winrar and then deleting and replacing it. And to extract the kernel, you would need to split the boot.img either using a kitchen or some other tools that do the job.
A little update on my port: I still haven't gotten it to fully boot, it just keeps restarting
Click to expand...
Click to collapse
Yeah I thought the article I read was Bull****! I wish I could remember where I read it to show you guys what it said but just can't remember for ****... Lol!
Well Thanks for Confirming guys...
Is there any fully functional jelly bean ROMS for evo lte? if so, which ones do you guys recommend? this is my first time rooting ever, so, which backup software should i use? thanks!
There currently is no JB roms for us yet.
Sent from my EVO using xda premium
kushdeck is currently working on one right now as we speak. he actually has a ROM available in IRC, but it isnt quite ready yet.
How do I get to it on IRC
Sent from my EVO using xda premium
zaaye said:
How do I get to it on IRC
Sent from my EVO using xda premium
Click to expand...
Click to collapse
Click this link.
Type in a name for yourself, and fill out the CAPTCHA.
Look for "Decks busted CM10" in the topic near the top of the screen. There will be a link there that will lead you to the download.
There are at least 3 jelly bean roms in the works, but none for a daily driver yet.
Sent from my EVO using Tapatalk 2
Bumping. Because! It has been almost two months since the last reply and I have heard there are some fairly stable Jelly Roms for the Evo LTE now. My question: What are they and how stable are they?
cm10 is very nice...multitask works perfectly...battery life is awesome
HTC EVO LTE
Cm10, paranoid and aokp are the only jb roms that I know of at the moment. All are pretty stable and lots of people are using them as daily drivers. There are still a few issues like phone force closing on boot, flaky mms and weak proximity sensor (there's a separate flash that fixes) but on the whole they are fully functional. Some have reported cell and gps signal issues but everyone's setup is different...YMMV, I suggest giving them all a shot to see which one you like best. Cm10 seems to be the favorite right now, but paranoid has some pretty cool display tweaks. If you're coming from sense and you're s-on with hboot 1.15 or later, make sure to read up on flashing the kernel separately with fastboot.
Sent from my EVO LTE
premo15 said:
Cm10, paranoid and aokp are the only jb roms that I know of at the moment. All are pretty stable and lots of people are using them as daily drivers. There are still a few issues like phone force closing on boot, flaky mms and weak proximity sensor (there's a separate flash that fixes) but on the whole they are fully functional. Some have reported cell and gps signal issues but everyone's setup is different...YMMV, I suggest giving them all a shot to see which one you like best. Cm10 seems to be the favorite right now, but paranoid has some pretty cool display tweaks. If you're coming from sense and you're s-on with hboot 1.15 or later, make sure to read up on flashing the kernel separately with fastboot.
Sent from my EVO LTE
Click to expand...
Click to collapse
Im a completely NOOB when it comes to rooting because I have never done it before, so everything you said might as well be chinese, lol, but no worries, once I pick a ROM, I ll do extensive research on everything you just told me.
My main concern though: My wife's Galaxy SIII sends over track and album art info to our Prius Nav display perfectly. Also, the "reading SMS outloud" feature only works with her phone, and not mine. Will flashing to one of these ROMs add this functionality to my phone? I have heard that the main issue is the version of AVRCP bluetooth profile that HTC uses in sense and also the bluetooth stacks library that Sense uses. I had heard that CM fixed this, but im not sure. And what about the SMS reading thing? what determines that?
Read my guide. It has a lot of info
If you're new to the scene, definitely read om4's guide...it has lots of good info about rooting, flashing, etc. all in one place. Much easier than hours of searching for each topic individually...
http://forum.xda-developers.com/showthread.php?t=1869377
Sent from my EVO LTE
also, read this, it has all the major roms and rooting, including the jb ones. great to compare them all too, plus every guide and walkthrough you could need
http://forum.xda-developers.com/showthread.php?t=1645890
Sent from my EVO using xda app-developers app
Thanks guys! After doing some reading, I will post back on here with more questions.
I have been running paranoid for a while now and have tried going back to sense roms, but love the cm10 jb experience too much to ever go back to sense again. I highly recommend paranoid!
Sent from my EVO using xda premium
Ok guys so I have been reading on the thread you guys recommended, and i still havent pulled the trigger on rooting. I do have a few questions:
-One of the main things I noticed is, if I get CM10, I lose the awesome camera the EVO has. Im assuming if I get a rooted sense based ROM, I would still keep my awesome camera?
-One of the main reasons I am rooting is because I have heard CM10 has a better bluetooth stack built in, and as such it should work much better with my car, sending over track and album artist, as well as the ablity to browse music files via bluetooth through my nav screen. Or at the very least, I want to be able to get back the USB plug in functionality I used to have on the EVO 3D. When i plug in my Evo LTE in my car's USB, nothing happens. So, is there a ROM that allows me to keep the sense camera but also has the bluetooth/USB host capabilities I am looking for?
-When I root, does everything get wiped out and I have to reinstall all my apps, contacts, etc?
I'm on CM10 for the past month and am really liking it. Since I was also disappointed by the camera app I went ahead and tried the Jelly Bean 4.2 camera, and it works wonderfully. It's not 100% as awesome as HTCs, but it's enough for me. Look for the JB 4.2 apps - it's floating around somewhere.
As for BT - I don't think CM10 has APT-X, so audio quality would be lower on compatible devices. I think I notice a difference on my BT stereo headset, but it may be my imagination. Again - small price to pay for using CM10.
gseltzer said:
I'm on CM10 for the past month and am really liking it. Since I was also disappointed by the camera app I went ahead and tried the Jelly Bean 4.2 camera, and it works wonderfully. It's not 100% as awesome as HTCs, but it's enough for me. Look for the JB 4.2 apps - it's floating around somewhere.
As for BT - I don't think CM10 has APT-X, so audio quality would be lower on compatible devices. I think I notice a difference on my BT stereo headset, but it may be my imagination. Again - small price to pay for using CM10.
Click to expand...
Click to collapse
thanks for the reply, but I am not as concerned with audio quality as I am with my track/artist/playlist information showing up on my car's LCD Nav thing. Any ideas on what I can do to get that to happen? Does CM10 have this? And what is APT-X? What I was talking about is AVRCP. Stock sense does not have a high enough level (version) of AVRCP to do what I want. Somewhere on another thread I was told that CM does have this, but I have since been unable to confirm it.
darkleafar said:
thanks for the reply, but I am not as concerned with audio quality as I am with my track/artist/playlist information showing up on my car's LCD Nav thing. Any ideas on what I can do to get that to happen? Does CM10 have this? And what is APT-X? What I was talking about is AVRCP. Stock sense does not have a high enough level (version) of AVRCP to do what I want. Somewhere on another thread I was told that CM does have this, but I have since been unable to confirm it.
Click to expand...
Click to collapse
Your probably better off waiting for the official jelly bean update from HTC which *should* be in the next month or so. It might be included in that. As far as cm10 goes, you have nothing to lose by trying it to see... Just back everything up before you root and then try it to find out.
Sent from my EVO using xda premium
Can I use this http://forum.xda-developers.com/showthread.php?p=26521683 to root and then flash cm10?
Hey guys.
Does anyone know if using an AOSP rom, you loose out on any features, such as hardware camera processing or others by not being on a Sense-based ROM?
Thanks,
Da
You will lose anything related to sense. Widgets, camera software, profile & prl update capabilities, etc.
I would say you definitely lose out on overall stability and also some features. First and foremost you may experience LOS (loss of signal) which can be really crippling and just make the phone unusable. Also, most AOSP seem to have a problem either sending or receiving MMS. Not to mention you can't update profile and prl.
Sent from my EVO using xda premium
It's a matter of opinion HTC does not open source their software, and they wait till the last minute to release kernel sources, as for prl and profile you can't update them via an aosp Rom. But a quick flash or restore to sense and you can as for stability I'd say aosp or stock.
You may miss HTC's applications such as friend stream and others but you can easily find a variant for it.
Sent from my EVO using xda app-developers app
Thanks for the replies.
Understood with the prl update stuff.
I run custom prls atm so I can roam on 3g when desired.
I was mainly asking because I heard there is a processing chip that enables the instant photo shoots, or something similar. Wanted to know definitively if sense drivers were needed for this hardware based functionality and if there was any other loss of hardware features.
Sent from my EVO using Tapatalk 2
As far as I can tell image sense is basically postprocessing but I could be wrong. The libs for image sense were ported to cmx some time ago, not sure about other aosp roms
You win some and you lose some. Multitasking is ornamental in AOSP an fast as hell, but the imagesense hardware and software are unbeatable on sense. I'm running viper4g right now with only the complaint that even the new multitasking "fixes" aren't 100%
om4 said:
As far as I can tell image sense is basically postprocessing but I could be wrong. The libs for image sense were ported to cmx some time ago, not sure about other aosp roms
Click to expand...
Click to collapse
Source on this?
What i miss is the overall integration of my social networks. While you can get apps that help you do it, in sense its already there and works seamlessly. I can see their Facebook and twitter statuses as they call me. But i cant in AOSP from what i have seen. How ever... I like how fast AOSP is, only thing that keeps me away is the sense camera ( its so damn fast ) and the signal stability issue. Once time i walked outside of my workplace and i had signal, just not data. and it stayed that way for about 5 minutes. never happens in sense
Internet passthrough
Sent from my EVO using xda premium
thats actually a good one. useful for when you are at work with no LTE
For me personally no aosp rom has equal battery life to any of our sense based
Sent from my EVO using xda premium
Spyderekz said:
thats actually a good one. useful for when you are at work with no LTE
Click to expand...
Click to collapse
Yup I usr it at my dorm all the time due to their painfully slow WiFi so we use the neighbors Ethernet since mines busted
Sent from my EVO using xda premium