So I bought this OTG cable because I didn't do much research and saw that it worked with the Evo LTE. Problem is, all videos were of AOSP. Is there a Sense Rom/kernel that supports OTG? I want to have a bigger screen to work my camera with for video. This seemed like the cheapest way to do so. Any info would be great. Thanks
I'm pretty sure that all the sense ROMs will support this feature.
a senile fungus said:
I'm pretty sure that all the sense ROMs will support this feature.
Click to expand...
Click to collapse
Thanks for the reply. I can get certain USB devices like flash drives to work. So maybe I am doing something wrong with my camera.
I've always just used this. Download the modules to and put them where the rest of ur modules are with root explorer.
https://play.google.com/store/apps/details?id=net.shajul.usbotg
Swyped from my eVo
ryanalan82 said:
I've always just used this. Download the modules to and put them where the rest of ur modules are with root explorer.
https://play.google.com/store/apps/details?id=net.shajul.usbotg
Swyped from my eVo
Click to expand...
Click to collapse
I did get that working. I've been researching a little more, and it looks like OTG host controller needs to be active? I think this is something in the kernel, and I haven't found much for Sense roms. I tried AOSP earlier, and cm10.1 didn't work either. I'm still pretty confused what exactly needs to be activated
edit: got it working with cm10.1 unofficial. Going to play around and see how many diff AOSP roms work. Still would love to be able to use a Sense rom
southernstyle said:
I did get that working. I've been researching a little more, and it looks like OTG host controller needs to be active? I think this is something in the kernel, and I haven't found much for Sense roms. I tried AOSP earlier, and cm10.1 didn't work either. I'm still pretty confused what exactly needs to be activated
edit: got it working with cm10.1 unofficial. Going to play around and see how many diff AOSP roms work. Still would love to be able to use a Sense rom
Click to expand...
Click to collapse
Have you tried a custom kernel yet?
I use my OTG cable to connect my ps3 controller to phone and play games on Sense.
I hope you get this figured out...
southernstyle said:
I did get that working. I've been researching a little more, and it looks like OTG host controller needs to be active? I think this is something in the kernel, and I haven't found much for Sense roms. I tried AOSP earlier, and cm10.1 didn't work either. I'm still pretty confused what exactly needs to be activated
edit: got it working with cm10.1 unofficial. Going to play around and see how many diff AOSP roms work. Still would love to be able to use a Sense rom
Click to expand...
Click to collapse
You are correct. I tried messing with it a little bit too, but I didn't try any of the custom Kernels. You can check a couple of them to see it they work. When I checked the threads I couldn't find any info about the host controller being enabled, so I didn't even mess with it. Plus I have a Nexus 7 that it does work on, so I use that instead.
Meanbean has the option to activate a Xbox controller using the otg, you have to enable it with the sticky settings zip... It might help with what you are trying to do...
Sent from my EVO using xda app-developers app
Thanks for all the replies. What I've found, for AOSP, is Deck's CM10.1 kernel works perfect. All the other tangents of CM10.1 have modified kernels or different ones, and those don't seem to work. I don't know how to extract his kernel and flash over other roms, but I think that might work. I'm not really sure how kernels work other than for OC and UV.
Sense roms allow OTG with everything except the DSLR thing. I think it's due to not having host controller abilities. I gave up on Sense Roms after seeing that CM had this working. I guess I'm stuck now with CM10.1. It's not terrible, but I like the AOKP and Paranoid tweaks if I'm on AOSP. For now, I will survive. Anyone who knows about kernels could probably help figure out what's in Deck's kernel that's not in other variations.
Thanks again everyone
Ok so I'm back after digging more. It looks like they got this feature working via http://forum.xda-developers.com/showthread.php?t=2244620&highlight=dslr on the HTC One. The kernel removes the whitelist for OTG and that allows more devices to be connected. I compared the code to the ElementalX and saw it was exactly the same code. While comparing them, I noticed one difference.
ElementalX has:
drivers/usb/core/otg_whitelist.h
arch/xtensa/configs/iss_defconfig
tbaldens kernel3.6:
drivers/usb/core/otg_whitelist.h
arch/xtensa/configs/iss_defconfig
AND
arch/arm/configs/m7_defconfig
I don't know much about how kernels work, but I compared the source for both and they were identical except for not having that last file. Maybe someone who does can help? I figured the 2 devices are similar enough to compare, should I maybe ask flar2 or TeaMSeven?
Just wanted to give an update. I've found a solution to the problems and actually got a solid ROM and the features i needed.
The problem is the 3.14 cm kernel that everything is based off of, at least for our device. I'm currently on PAC v22 rom , which is 3.07 based. The otg works properly and everything runs smooth. Of course its not latest and greatest, but works.
I have another thread about gif MMS on aosp ROMs. I also got that working now via hand cent and quick pic. So anyone trying to switch to aosp from sense, there are ways to get the features, just gotta do a lot of trial and error.
Thanks again to all the advice. I cant remember who suggested mean ROM, but the Xbox setting didn't work. Seems sense ROMs don't play well with anything other than USB flash drives and mouse/keyboards.
Related
I am looking for something on the HTC Thunderbolt that has the look and feel of ICS but without all the buggy issues. I tried several 4.0 versions from different sights but stuff like data does not work reliably or mms does not work at all. So I am willing to try out any GB rom or ICS rom or ICS hybrid rom that has all the basic working features as a stock rom would. Also what I am looking for is something that has USB tethering built in as I never could get the downloadable apps for USB tethering to work. I do not require Wifi tethering simply because its too slow for gaming and is unreliable. Lastly if you can recommend a rom with good battery life.
driodman98 said:
I am looking for something on the HTC Thunderbolt that has the look and feel of ICS but without all the buggy issues. I tried several 4.0 versions from different sights but stuff like data does not work reliably or mms does not work at all. So I am willing to try out any GB rom or ICS rom or ICS hybrid rom that has all the basic working features as a stock rom would. Also what I am looking for is something that has USB tethering built in as I never could get the downloadable apps for USB tethering to work. I do not require Wifi tethering simply because its too slow for gaming and is unreliable. Lastly if you can recommend a rom with good battery life.
Click to expand...
Click to collapse
Wow, alot to ask for, but ill try. I think if you need tethering built in, you need something aosp, like thundershed. There are ics themes for aosp scattered in market or in theme section i believe. You probably just need to read here, rootzwiki, and any other place that has rom development, and then start flashing. Everyone has different tastes. Oh, an my experience with aosp is bad battry life, just my $.02. Good luck dude. I use eternity and ginger bread rock.
Sent from my ADR6400L using XDA App
I am used to modding android devices. I might be looking to get a touchpad for my mother depending on how stable an android rom is for it.
Is there a stable CM7?
What are the features that DO-NOT work? (that way I can assume everything else works?)
Front camera, skype support?
Again I would be looking for the most stable and bug free ROM that I would not have to constantly flash updates for her. Thanks!!
I have never used CM7 since I just got my Touchpad a few weeks ago when CM9 was out. But CM9 is stable. Just doesnt have camera or mic working. I dont know if these issues are the same with CM7. But if your mom has no need for all the apps android has to offer, she can just use webOS which is more stable than both CM7 and CM9.
Wond3r said:
I am used to modding android devices. I might be looking to get a touchpad for my mother depending on how stable an android rom is for it.
Is there a stable CM7?
What are the features that DO-NOT work? (that way I can assume everything else works?)
Front camera, skype support?
Again I would be looking for the most stable and bug free ROM that I would not have to constantly flash updates for her. Thanks!!
Click to expand...
Click to collapse
Dont bother at all with CM7. CM9 and other ICS roms are far more stable. Pretty much everything works except for the camera and microphone. Battery life is nowhere near as good as in webOS, expect about 2 days of standby or about 5 hours of constant usage. Some people have wifi issues, but they're more often than not fixed by setting the router to avoid higher channels (keep it on 6 or below). The vibrate motor also for some reason stops working after the device goes into sleep, and the only way to get it going again is to reboot but I dont think that's a big issue for anyone.
As for a ROM, I'd recommend CM9 not because its the best but because its the one I'm most familiar with, and I can say its fairly stable. Sometimes it will randomly reboot, but never while actively using it. I'm using a nightly, but since you're giving this to a family member you might be better off with the better tested Alpha 2.
Stable Rom: Classicnerd
For me the most stable rom has been classicnerd's latest version. I have been using it and donot get any force closes or reboots. You can find the latest version at classicnerd.net/Betas/
as far as CM9 and the camera/mic issues, I think she would want to use skype to video chat with family members, so that would be a problem.
Does classicnerd have that issue?
Wond3r said:
as far as CM9 and the camera/mic issues, I think she would want to use skype to video chat with family members, so that would be a problem.
Does classicnerd have that issue?
Click to expand...
Click to collapse
All CM9 ROMs have that issue. Again, she can use webOS for that though.
jsgraphicart said:
All CM9 ROMs have that issue. Again, she can use webOS for that though.
Click to expand...
Click to collapse
webos does not have a lot of the banking and other apps she may find useful. Although is it easy to dual boot webOS and android? I'm thinking maybe its useful to boot to webOS just for skype and Android for everything else. That is, if its easy to switch between them.
Wond3r said:
webos does not have a lot of the banking and other apps she may find useful. Although is it easy to dual boot webOS and android? I'm thinking maybe its useful to boot to webOS just for skype and Android for everything else. That is, if its easy to switch between them.
Click to expand...
Click to collapse
Dual booting is the only way to do it. As far as I know, you cant replace webOS. When you follow the instructions to install android, you also install what is called a moboot that lets you select which operating system to boot into when starting the device. Switching between the two is easy and is just a matter of restarting your device.
Wond3r said:
I am used to modding android devices. I might be looking to get a touchpad for my mother depending on how stable an android rom is for it.
Is there a stable CM7?
What are the features that DO-NOT work? (that way I can assume everything else works?)
Front camera, skype support?
Again I would be looking for the most stable and bug free ROM that I would not have to constantly flash updates for her. Thanks!!
Click to expand...
Click to collapse
CM7, yes.
Personally, I prefer AOKP.
Sent from my Galaxy Nexus using Tapatalk 2
Just depends on how adept she is at technology. If she can decently run a computer and text, she should be mostly okay. The one thing I would highly recommend is to make sure she can fix the wifi authentication problem. Basically, every now and then, wifi will have an authentication problem. When this happens, she needs to go to wifi settings, forget the router, toggle wifi off/on, and sign back into the router. This problem usually occurs for me when I leave wifi on and then reboot or get a random reboot. Takes maybe a minute to fix. As far as ROM, I like oat's light and tasty, although they're all pretty good, as they have the same base.
Sorry, I have to get this out of my system, then I'll be back to polite nice Canadian. In short, try one and see.
<rant mode on>
One of these days, people will actually glance through the forums as opposed to posting a new thread. This thread has been duplicated many other times before now.
In the end, again, just grab one, take it for a spin, and try it. Start with the more official ones, and work out from there until you find something you like. If nothing suits your fancy, take the source and make your own. It's pretty simple. So please stop spamming the boards with "Which ROM should I use" threads. </rant mode off>
MikeyCriggz said:
Personally, I prefer AOKP.
Click to expand...
Click to collapse
+1
I have tried CN and others but, I think that Oat's light n' tasty is the best so far. All my games run great and so does netflix and YouTube. But, a Rom is only good if it runs the apps you like. You I'll have to find the one that works best for you. I still think webOS is still good. Just my $0.02
I figured one more opinion can't hurt.
I've been using AOKP on my touchpad ever since I found out that they build roms for hp touchpads. It's great, so is CM9 but for some reason my touchpad refuses to behave with CM9, I'm talking random reboots, wifi issues, SOD (screen of death), and so on. ClassicNerd is also great too but I fell in love with the ROM control options available with AOKP.
Either way, one of the earlier posts mentioned that battery life is weak with ICS which is NOT the case for me, I always have wifi on, with my CPU overclocked to the maximum available frequency and get about 7 days, yes 7 DAYS, of standby and at least a full day of constant use.
As for skype, it is not fully functional with all android devices, just the few that the skype people officially support, I've tried it on my phone and it gave me a lot of issues, so even if the mic and cam were working I doubt skype would work well enough on the TP.
Obviously as others have mentioned earlier ICS is much better on the TP than GB, plus you have the great option of dual booting so you could always use WebOS which is pretty decent itself.
All in all, the TP was a great $100 investment and has a lot of support from some great devs out there. My almost 3 years old nephew has one and he loves it too lol
if you install one of the current nightlys, unofficial or official, she should be running just fine until you come over and install the one of the newer ones for her
the nightlys seem to be running great, even without the supreme mods.
can anyone tell me if the supreme mods are still worth installing?
mes0suave said:
if you install one of the current nightlys, unofficial or official, she should be running just fine until you come over and install the one of the newer ones for her
the nightlys seem to be running great, even without the supreme mods.
can anyone tell me if the supreme mods are still worth installing?
Click to expand...
Click to collapse
I found your answer on another thread:
cdzo72 said:
I read somewhere that the tweaks were in one way or another no longer relevant or in some form had been incorporated into Android starting with Gingerbread... I think the post is actually in this thread. I myself was using it for a while but after reading that I stopped flashing it and haven't missed it
Sent from my cm_tenderloin using Tapatalk 2
Click to expand...
Click to collapse
I have tried several versions CM9, CM10 and Paranoid ROMs but do not have dock audio working properly with any of them. I am specifically referring to the Samsung dash mount for the Galaxy Note. I am currently running CM10 from H0tW1r3 08.03.12 and when I go into settings/dock the option for routing the audio is greyed out. I am able to plug into the audio jack on the phone and it always works when I do that but would like to just plug into the dock and go and skip this setup if possible. Am I missing an APK?
Any help is appreciated, yes I searched and searched again. Thanks in advanced for your help!
Feeling your pain...but....
Wilarico said:
I have tried several versions CM9, CM10 and Paranoid ROMs but do not have dock audio working properly with any of them. I am specifically referring to the Samsung dash mount for the Galaxy Note. I am currently running CM10 from H0tW1r3 08.03.12 and when I go into settings/dock the option for routing the audio is greyed out. I am able to plug into the audio jack on the phone and it always works when I do that but would like to just plug into the dock and go and skip this setup if possible. Am I missing an APK?
Any help is appreciated, yes I searched and searched again. Thanks in advanced for your help!
Click to expand...
Click to collapse
I have the same dock and the same problem...my solution was to remove the headphone cord from the dock and plug it into the phone directly. Sorry, but that's the only way I've been able to enjoy custom ROMs and music from my phone in my car. BTW, same thing in my house on the Samsung dock
Wilarico said:
I have tried several versions CM9, CM10 and Paranoid ROMs but do not have dock audio working properly with any of them. I am specifically referring to the Samsung dash mount for the Galaxy Note. I am currently running CM10 from H0tW1r3 08.03.12 and when I go into settings/dock the option for routing the audio is greyed out. I am able to plug into the audio jack on the phone and it always works when I do that but would like to just plug into the dock and go and skip this setup if possible. Am I missing an APK?
Any help is appreciated, yes I searched and searched again. Thanks in advanced for your help!
Click to expand...
Click to collapse
CM9 has options for this in the settings, but support needs to be added in the kernel. At this point we have to wait for a dev to make it happen.
Calling all DEVs!
borgib said:
CM9 has options for this in the settings, but support needs to be added in the kernel. At this point we have to wait for a dev to make it happen.
Click to expand...
Click to collapse
I'm ready to donate to this! If anyone is able to work on it let me know, I'm lazy and want to avoid plugging in the cable if that is feasible!
Thanks!
hi! the solution for now is to flash custom rom based on stock firmware. i'm gonna make something like this for galaxy note next week, but if you flash a rom like that you still have touchwiz. i'll try to put the gs3 touchwiz version for cooler aspect note my name and visit my profile next week
bye
Sent from my Galaxy Nexus using xda app-developers app
CM10 - Dock Audio Please
BigBrother1984 said:
hi! the solution for now is to flash custom rom based on stock firmware. i'm gonna make something like this for galaxy note next week, but if you flash a rom like that you still have touchwiz. i'll try to put the gs3 touchwiz version for cooler aspect note my name and visit my profile next week
bye
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
I'd like to stay on CM10 and get dock audio working... a man can dream can't he? I don't really want to go to a stock based rom since they are always so behind.
I am also desperately looking for a solution with custom ROM and dock audio.
Currently I run Omega which is Sammy based. I'd rather use a custom ROM with AOSP and AOKP mix. Tried several but neither worked in the dock. Is there any chance to build one which includes USB audio?
Any news on this issue
Muenchen04 said:
I am also desperately looking for a solution with custom ROM and dock audio.
Currently I run Omega which is Sammy based. I'd rather use a custom ROM with AOSP and AOKP mix. Tried several but neither worked in the dock. Is there any chance to build one which includes USB audio?
Click to expand...
Click to collapse
I'm using a samsung galaxy SII, I've tried the CM 10.2, but the dock audio does not work on that one. Any ROM that has this great feature? Unless I can find something real soon, I'll revert to stock, which i sad since samsung has dropped S2 support.
I know this is kind of old but i'm stuck here on the same issue. Seems like Samsung and other manufacturers(Motorola does so definitely) have USB audio solutions or the like built into their docking stations. If your Kernel/ROM does not recognize the chip used or does not have the appropriate routines, modules and drivers, you're out of luck.
I'm also having a Samsung P1000 and a docking station for it. It also does not work with anything else but stok or modded stock, even though the audio connection to the dock is purely analog and the HDMI out is plain&simple MHL.
I absolutely thick, this should be doable but i'm more of the hardware guy. If someone with interest to this matter requires some info on hardware like docks for Samsung Galaxy Note(v2 and upwards)/Galaxy Tab(any version)/Galaxy S(v2 and upwards) or for Motorola Atrix 4G i'm more than happy to tear these docks apart and dig deep for the info you need.
Hi!
Same problem here, with P1000 as a car tablet.
Dock audio works (only) on the newest HumberOS, but otherwise quite buggy rom. Youtube, HomeDJ, Spotify does´t work. Maps is laggy.... Not great for a car tablet.
AND Humber has stopped developing it.
But this meas, that it is doable, and I really hope, that someone would make this works.
Hello. I'm relatively new to the Cyanogenmod scene in general, so forgive me if I'm a bit ignorant. I looked through the official CM10.1 threads and didn't see much in the way of actually fixing MHL/HDMI not working. I think I read that the last snapshot that had MHL working was back in February or so, but I don't remember exactly.
I'm currently running cm-10.1-20130304-EXPERIMENTAL-jewel-M2 and have no MHL/HDMI at all. The phone doesn't seem to notice I've plugged in the adapter (except for it notices it's being charged, since the adapter is connected to an AC adapter).
Could someone inform me if there's been developments to fix this issue? Any insight is appreciated!
I had the same issue with my before car wrecked EVO LTE. I ran CM and many sense roms before basically giving up on it. Went through 2 cheap eBay adapters that worked for a bit then stopped altogether. Then the mhl/hdmi wouldn't work at all, not on any adapter or tv.
I asked a lot of other users if they had the same issue, even tried to pay a dev to look into it and was basically told it was a hardware issue.
My solution was to usb phone to Xbox for movies and use bluestacks on my pc for games/apps. Haven't yet tried my replacement EVO LTE. My original was a pre-order held up @ customs, so maybe it was faulty workmanship just bc it was new.
Hope u come up w a solution.
RudyH246 said:
Hello. I'm relatively new to the Cyanogenmod scene in general, so forgive me if I'm a bit ignorant. I looked through the official CM10.1 threads and didn't see much in the way of actually fixing MHL/HDMI not working. I think I read that the last snapshot that had MHL working was back in February or so, but I don't remember exactly.
I'm currently running cm-10.1-20130304-EXPERIMENTAL-jewel-M2 and have no MHL/HDMI at all. The phone doesn't seem to notice I've plugged in the adapter (except for it notices it's being charged, since the adapter is connected to an AC adapter).
Could someone inform me if there's been developments to fix this issue? Any insight is appreciated!
Click to expand...
Click to collapse
Mine works fine on aosp or sense roms, is a rocket fish mhl adapter, try to flash komodo kernel which I think it supports tv out, that's what I'm using with cm 10.1
Sent from my EVO using xda app-developers app
jocarog said:
Mine works fine on aosp or sense roms, is a rocket fish mhl adapter, try to flash komodo kernel which I think it supports tv out, that's what I'm using with cm 10.1
Click to expand...
Click to collapse
Are there any large differences between running CM10.1's stock kernel and Komodo Kernel? I am not entirely sure what exactly different kernels entail.
Yes with Komodo you can use swipe gestures to wake your phone or put it to sleep, also lover/increase the volume and advance power menu, etc, plus you can overclock and increase zram, etc etc etc... make a nand and flash komodo... good luck!
RudyH246 said:
Are there any large differences between running CM10.1's stock kernel and Komodo Kernel? I am not entirely sure what exactly different kernels entail.
Click to expand...
Click to collapse
Here's a good reading about kernels and schedulers:
http://forum.xda-developers.com/showthread.php?t=1369817
jocarog said:
Here's a good reading about kernels and schedulers:
http://forum.xda-developers.com/showthread.php?t=1369817
Click to expand...
Click to collapse
Thanks a bunch! I'll give it a read.
So with Android version 4.4 KitKat being able to run on devices with as low as 512 MB of RAM comfortably, will this allow rom developers to further develop/improve custom roms for the Amaze with Android 4.4 with little to no bugs in the future? Let the speculation begin...:fingers-crossed:
I wish they would develop that for this device, but I'm not so certain that they will because we don't even have an unofficial 4.3 port as yet (well, as far as I've looked. Only 4.0, 4.1, 4.2.......)
Darian_A said:
So with Android version 4.4 KitKat being able to run on devices with as low as 512 MB of RAM comfortably, will this allow rom developers to further develop/improve custom roms for the Amaze with Android 4.4 with little to no bugs in the future? Let the speculation begin...:fingers-crossed:
Click to expand...
Click to collapse
Only if HTC, Qualcomm, and Texas Instruments provide the corresponding updated sources for development. Otherwise what few developers that are left here will still be banging their heads against the wall to port it.
Darin_Ram said:
I wish they would develop that for this device, but I'm not so certain that they will because we don't even have an unofficial 4.3 port as yet (well, as far as I've looked. Only 4.0, 4.1, 4.2.......)
Click to expand...
Click to collapse
We do have 4.3.
http://forum.xda-developers.com/showthread.php?t=2423642
KT-82166 said:
We do have 4.3.
http://forum.xda-developers.com/showthread.php?t=2423642
Click to expand...
Click to collapse
Ooohh I had forgot about this!!
My bad, we do have a 4.3
It was buggy for me, so I went back to tmobile ICS
Idk, I like the sense and sense keyboard more than CM keyboard.
Roms
Darin_Ram said:
Ooohh I had forgot about this!!
My bad, we do have a 4.3
It was buggy for me, so I went back to tmobile ICS
Idk, I like the sense and sense keyboard more than CM keyboard.
Click to expand...
Click to collapse
I prefer the old Sense Keyboard. how can I get it back on my CM 10 rom ?
so far I managed to install CM10 rom
updated the contact manager to get it to synchronize with Facebook
but what it lacks is the snapshot ability using power + home button which doesnt work on CM10 rom
and the filp to silent the phone... also the volume controls are not so good during calls.
the volume is always at its highest even if I lower it. also the speaker is not as high as it used to be on the ICS rom
but I have to say CM10 is a better battery saver
runs smoother then ICS stock
and looks good
Sense Jellybean...
Once we have sense Jellybean, the next working will be KitKat.
We are very close to having the very first Sense jellybean rom
4.3 roms
The evervolv rom is currently the best "4.3" rom for the Amaze. Found here: evervolv.com/devices/ruby.
Although, the mobile data is very choppy. It will connect but it's seems to when it wants. Not sure about the intricacies of that. But, a bit of a dealbreaker for me at this point. The good news is evervolv has been updating this rom with
tweaks and bug fixes everyday. So, it looks very promising. Also note, I have found an "unofficial" cm10.2
build by sportsstar89 but the sound does not work. If you search 'ruby' on goo.im you will find it. I would post a link
but the site seems to be down atm. I am currently running cm10/1006-nightly, what i've found to be the best jelly bean
rom at this point. There is also an unofficial cm10.1 build that is pretty good as well. It can be found here: droidfirmwares.com/cm10-1-android-4-2-2-jelly-bean-custom-firmware-for-htc-amaze-4g.html/2. I ran it for quite a while w/o any noticeable
trouble. I just prefer official cm builds i guess.
Fadiayad said:
I prefer the old Sense Keyboard. how can I get it back on my CM 10 rom ?
so far I managed to install CM10 rom
updated the contact manager to get it to synchronize with Facebook
but what it lacks is the snapshot ability using power + home button which doesnt work on CM10 rom
and the filp to silent the phone... also the volume controls are not so good during calls.
the volume is always at its highest even if I lower it. also the speaker is not as high as it used to be on the ICS rom
but I have to say CM10 is a better battery saver
runs smoother then ICS stock
and looks good
Click to expand...
Click to collapse
I don't think you can get the keyboard on CM10 unless there's an app or someone made a port or something.
The snapshot feature works differently with Cyanogenmod cause they use the long press power button then selecting screenshot, though you'll have to enable the feature in the system settings.
Flip to silent the phone? Must be a feature I don't use lol
Idk, I liked the ICS stock tmobile (I de-bloated it myself using root uninstaller. Got rid of anything pertaining to t-mobile and it runs like a dream.)
Nenamark2 benchmark averages at 47 fps.
Antutu results are a little over 9000 (Let the Dragon Ball Z jokes start now lmao)
Overclocking is something that I would have loved to do on this stock rom, but I'll just run V6 Supercharger script instead.
Though pushing min. clock to about 1.2ghz gives a slight difference in benchmarks.
Hmmmmmm.......
It would take a lot of developer skills to get it on this device. CM said if they didn't officially support the device before, they won't start now regardless of ram specs. The s4 has it, but even better there is a dev for the international s4 that has made a 4.3.1 ROM which is made up of 85% straight Google source with 15% cm commits to get it to work on our device. And IMO, aosp is better and more stable than cm10.2 and has way less lag.
Sent from my GT-I9505 using Tapatalk
Thanks to jeepers007 and Evervolv we're getting ourselves some KitKat- http://forum.xda-developers.com/showthread.php?t=2524691
It's only a matter before the bugs are worked out. So nice to see the Amaze still getting some love. :good:
from what i have seen and heard kit kat will be better on amaze
Darian_A said:
Thanks to jeepers007 and Evervolv we're getting ourselves some KitKat- http://forum.xda-developers.com/showthread.php?t=2524691
It's only a matter before the bugs are worked out. So nice to see the Amaze still getting some love. :good:
Click to expand...
Click to collapse
Unfortunatelly jeepers007 bricked his device
The problem is with mounting the sdcards. Google changed how the cards are mounted and we don't know how to get both cards to mount while the phone isn't connected to the computer.
And exactly what happened to Ravike is what happened to jeepers.
Sent from my HTC_Amaze_4G using xda app-developers app
I want to ask here in general that is porting risky??
Because it lookin that jeepers007 bricked his phone...
What one should not do while porting Roms...!??
Any.suggestions
Sent from my Amaze 4G using xda app-developers app
chevycowboyusa said:
The problem is with mounting the sdcards. Google changed how the cards are mounted and we don't know how to get both cards to mount while the phone isn't connected to the computer.
And exactly what happened to Ravike is what happened to jeepers.
Sent from my HTC_Amaze_4G using xda app-developers app
Click to expand...
Click to collapse
Chevy perhaps you guys are going about things the wrong way. Instead of putting so much energy into getting a 3.4 kernel up and running maybe its better to stay with 3.0 and work around it. This is what the most successful developers have been doing on other legacy devices. For example, Tytung is still using basically the same kernel 2.6.29 for every version of Android since Froyo and his version of JellyBean-4.3 / CM-10.2 is much further along than anyone here is. He has faced the same issue of not having updated sources that everyone here has. In discussions on his board he's mentioned that it was easier to modify elements which require ion to pmem than developing an ion kernel from scratch to fully support that device. Perhaps our Amaze would be better served if developers here take the same approach. Use what we already have and just workaround it.
Now as to the mounting issue, the fact that both internal and external SD-cards are recognized and can be mounted via adb suggests that It's a configuration problem. Perhaps init scripts need slight modification or symbolic links created to get them mounted correctly. Again I hate to keep bringing up Tytung, but he worked around MTP issues by simply not implementing it in his newer ROMs. The old method of accessing the SD storage worked well with our devices, why must we reinvent the wheel? Yes MTP is more secure which is the primary reason for its adoption, but really, do we need it if implementing it correctly is only bringing about more problems?
Edit: Another thing to consider is Jellybean-4.3 introduced SELinux in permissive mode which means potential security risks are only logged, but nothing is done about it. KitKat incorporates SELinux in enforcing mode which introduces a whole range of new issues I'm sure developers here have never had to deal with before. I know from my experience with Gentoo that SELinux can be a royal pain in the ass to administer. Which is why I don't use it in my rig. I can't tell you how many times I've seen bug reports where a package fails on an SELinux install that works as expected for everyone else. I also can't tell you how many times I've seen packages pushed into the stable repository only to be moved back into unstable when SELinux users complain about it not working for them. It truly is a ***** to setup and have running correctly. To me this is just another reason to get out a stable fully functioning Jellybean-4.3 in which to build off of before trying to tackle KitKat-4.4 which is going to be a far more difficult nut to crack.
Just my 2 cents
Odysseus1962 said:
Chevy perhaps you guys are going about things the wrong way. Instead of putting so much energy into getting a 3.4 kernel up and running maybe its better to stay with 3.0 and work around it. This is what the most successful developers have been doing on other legacy devices. For example, Tytung is still using basically the same kernel 2.6.29 for every version of Android since Froyo and his version of JellyBean-4.3 / CM-10.2 is much further along than anyone here is. He has faced the same issue of not having updated sources that everyone here has. In discussions on his board he's mentioned that it was easier to modify elements which require ion to pmem than developing an ion kernel from scratch to fully support that device. Perhaps our Amaze would be better served if developers here take the same approach. Use what we already have and just workaround it.
Now as to the mounting issue, the fact that both internal and external SD-cards are recognized and can be mounted via adb suggests that It's a configuration problem. Perhaps init scripts need slight modification or symbolic links created to get them mounted correctly. Again I hate to keep bringing up Tytung, but he worked around MTP issues by simply not implementing it in his newer ROMs. The old method of accessing the SD storage worked well with our devices, why must we reinvent the wheel? Yes MTP is more secure which is the primary reason for its adoption, but really, do we need it if implementing it correctly is only bringing about more problems?
Edit: Another thing to consider is Jellybean-4.3 introduced SELinux in permissive mode which means potential security risks are only logged, but nothing is done about it. KitKat incorporates SELinux in enforcing mode which introduces a whole range of new issues I'm sure developers here have never had to deal with before. I know from my experience with Gentoo that SELinux can be a royal pain in the ass to administer. Which is why I don't use it in my rig. I can't tell you how many times I've seen bug reports where a package fails on an SELinux install that works as expected for everyone else. I also can't tell you how many times I've seen packages pushed into the stable repository only to be moved back into unstable when SELinux users complain about it not working for them. It truly is a ***** to setup and have running correctly. To me this is just another reason to get out a stable fully functioning Jellybean-4.3 in which to build off of before trying to tackle KitKat-4.4 which is going to be a far more difficult nut to crack.
Just my 2 cents
Click to expand...
Click to collapse
Well I tried what you said thing is sense is entirely different than CM or aosp the sources are there for public in both of them... But sense is a closed source and sense jb rom libs are compiled according to 3.4 kernel by HTC.. If we want to update the 3.0.16 kernel we have to enable ion with it then have to make the necessary libs along with it as well according to sense source, also must make ion enabled libs we have to make them all according to sense source.. Even the simple fixes of sense is really hard cuz HTC Sense is a complicated system :/... Tytong and almost all the cm devices lower than villec2 still use pmem kernels not ion... Not even cm team making ion enable kernels and ion enabled roms for us cuz it's a lot of work even tho its basically aosp..
Sent from my HTC_Amaze_4G using XDA Premium 4 mobile app
ravike14 said:
Well I tried what you said thing is sense is entirely different than CM or aosp the sources are there for public in both of them... But sense is a closed source and sense jb rom libs are compiled according to 3.4 kernel by HTC.. If we want to update the 3.0.16 kernel we have to enable ion with it then have to make the necessary libs along with it as well according to sense source, also must make ion enabled libs we have to make them all according to sense source.. Even the simple fixes of sense is really hard cuz HTC Sense is a complicated system :/... Tytong and almost all the cm devices lower than villec2 still use pmem kernels not ion... Not even cm team making ion enable kernels and ion enabled roms for us cuz it's a lot of work even tho its basically aosp..
Sent from my HTC_Amaze_4G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks for you comments, now I fully understand your dilemma. The issue isn't just getting a working JB ROM, it's getting a working JB/sense ROM. You see I'm sense agnostic. My HD2 had sense with windows, but all of the best android ROMs for it were aosp or cm based, so I got used to not having it. Now I've got it again with the nrg ROM so I use it. When I ran Tytung's cm ROMs I always customize anyway. To me cm or aosp is like having a blank canvas to paint on. You have the basic features, but It's infinitely customizable to taste. Sense gives a different platform. You can still customize, but It's not as flexible to customize as aosp or cm. In a way it's factory customized. Either way I'd just love to see a fully functioning JB on our devices. Please keep up the good work!
Ciao
I've asked somthing in above post..
Can anyone reply please... I want to start my work though....
Sent from my Amaze 4G using xda app-developers app
shubham211995 said:
I want to ask here in general that is porting risky??
Because it lookin that jeepers007 bricked his phone...
What one should not do while porting Roms...!??
Any.suggestions
Sent from my Amaze 4G using xda app-developers app
Click to expand...
Click to collapse
I'm not the most experienced but from my knowleged you should be ok as long as you watch what partitions you format.
Sent from my HTC_Amaze_4G using xda app-developers app