Hi Guys,
Looking for a clue here, because I clearly don't have one...
Obviously, moving from sense to something Sense Free (I've just switched to SinLess to be rid of BlinkFeed), is there any way to get some of the additional functionality of the device back?
The main think I'm looking for is the ability to use the IR blaster. I understand this was launched from the 'TV' app provided in Sense. Has anybody managed to break this out into an APK?
Alternatively, any thoughts/experiences with this, specifically with sense-free roms? https://play.google.com/store/apps/details?id=com.remotefairy2
It's an expensive app, and I'd prefer to only throw money at it in the event it'll actually work.
Haioken said:
Hi Guys,
Looking for a clue here, because I clearly don't have one...
Obviously, moving from sense to something Sense Free (I've just switched to SinLess to be rid of BlinkFeed), is there any way to get some of the additional functionality of the device back?
The main think I'm looking for is the ability to use the IR blaster. I understand this was launched from the 'TV' app provided in Sense. Has anybody managed to break this out into an APK?
Alternatively, any thoughts/experiences with this, specifically with sense-free roms? https://play.google.com/store/apps/details?id=com.remotefairy2
It's an expensive app, and I'd prefer to only throw money at it in the event it'll actually work.
Click to expand...
Click to collapse
Need the IR libs which aren't available at the moment
Prompt reply, awesome!
Being a bit green to the idea of Android development, Are we unable to pinch these from the original firmware?
Related
Hi there,
I don't know if this is possible, so the first part of this thread is a question. The second part is an idea, that only works if the answer is yes.
1. Is it possible to dismount the current camera in the Tattoo and replace it with a different camera?
2. If so, we should try to find a camera which has accessible drivers, a low price tag, autofocus and maybe even flash(which would require a bit of casemodding). That way we could have new ROMs with working cameras and the crappy original camera would be replaced. That way we could kill two birds with one stone.
We could find several possible candidates, have a poll in the forum and then add tutorials for new users, so they know where to get the camera and how to put it in the device.
What do you think? And more importantly - Would it even work?
4 said:
Hi there,
I don't know if this is possible, so the first part of this thread is a question. The second part is an idea, that only works if the answer is yes.
1. Is it possible to dismount the current camera in the Tattoo and replace it with a different camera?
2. If so, we should try to find a camera which has accessible drivers, a low price tag, autofocus and maybe even flash(which would require a bit of casemodding). That way we could have new ROMs with working cameras and the crappy original camera would be replaced. That way we could kill two birds with one stone.
We could find several possible candidates, have a poll in the forum and then add tutorials for new users, so they know where to get the camera and how to put it in the device.
What do you think? And more importantly - Would it even work?
Click to expand...
Click to collapse
Nah, near impossible.
Actually a nice idea but VERY difficult. Only a small number of users would be possible to actually mod there devices, if this is possible in the first place...
Sent from my Tattoo using Tapatalk
And what about copy the stock camera app and driver for rooted android phons
Sent from my Tattoo using XDA App
mlkabdullah said:
And what about copy the stock camera app and driver for rooted android phons
Sent from my Tattoo using XDA App
Click to expand...
Click to collapse
Lol you think nobody tried?
Anyway its a cool idea but its hard for a regular user to do something like that...
Maybe rather a USB connected camera. The built-in will not work, so when we need a camera, we pull this mini-camera out of our pocket and connect it to the USB-port.
Someone who want starting a new firm? It's gonna sell!!
Ihaveatattoo said:
Maybe rather a USB connected camera. The built-in will not work, so when we need a camera, we pull this mini-camera out of our pocket and connect it to the USB-port.
Someone who want starting a new firm? It's gonna sell!!
Click to expand...
Click to collapse
yeea but nothing bellow 12mp
It is interesting idea, but i don't believe a lot of people would spend money on tattoo - i'd rather buy a new android phone with better camera
Anyway, we now have almost fully workable camera, thanks to all developers!
For all ppl who are also annoyed by missing MP3-tags over bluetooth.
Please star following issue on code.google.com:
http://code.google.com/p/android/is...id&colspec=ID Type Status Owner Summary Stars
Thanks!
AOSP doesn't support AVRCP 1.13 which is the version that introduced metadata support. Until it does, custom ROMs the devs have added it to are the only one's that'll display song/album/artist.
Audio/Video Remote Control Profile (AVRCP)
This profile is designed to provide a standard interface to control TVs, Hi-fi equipment, etc. to allow a single remote control (or other device) to control all of the A/V equipment to which a user has access. It may be used in concert with A2DP or VDP.
It has the possibility for vendor-dependent extensions.
AVRCP has several versions with significantly increasing functionality:
1.0—Basic remote control commands (play/pause/stop, etc.)
1.3—all of 1.0 plus metadata and media-player state support The status of the music source (playing, stopped, etc.)
Metadata information on the track itself (artist, track name, etc.).
1.4—all of 1.0, 1.3, plus media browsing capabilities for multiple media players Browsing and manipulation of multiple players
Browsing of media metadata per media player, including a "Now Playing" list
Basic search capabilitieshttp://en.wikipedia.org/wiki/Bluetooth_profile
https://www.bluetooth.org/Building/HowTechnologyWorks/ProfilesAndProtocols/AVRCP.htm
As far as I know, no n4 custom rom supports it until today. Google will most likely never update it, don't know what the heck they are thinking.
it's such an elementary feature. Can't believe it's not integrated....This really makes me mad.
Lownita said:
As far as I know, no n4 custom rom supports it until today. Google will most likely never update it, don't know what the heck they are thinking.
Click to expand...
Click to collapse
What do you mean no custom ROM supports it?
I was waiting for someone to confirm if AVRCP 1.3 was going to be added in android 4.2.2 but now I'm planning on rooting and getting a ROM that does support this...
This is my most wanted bug fix for android 4.2.2, and I can't believe they missed it. Shame on Google.
jc monkeyballs said:
This is my most wanted bug fix for android 4.2.2, and I can't believe they missed it. Shame on Google.
Click to expand...
Click to collapse
I completely agree
Does anyone know of a stable mod that does have AVRCP 1.3?
I'm glad that I am not the only one^^
Please share this bug report as often as possible in other forums. Maybe if enough ppl will star this google will react - MAYBE^^
main reason
This was the main reason I was looking forward to the update...now, I'm sad. Guess I'm going to be forced to root now...anyone know when any of the ROMs will add this much needed feature?
alternetconcept said:
What do you mean no custom ROM supports it?
I was waiting for someone to confirm if AVRCP 1.3 was going to be added in android 4.2.2 but now I'm planning on rooting and getting a ROM that does support this...
Click to expand...
Click to collapse
There is no rom that supports it! If you find one, let me know
sarasotaguy said:
This was the main reason I was looking forward to the update...now, I'm sad. Guess I'm going to be forced to root now...anyone know when any of the ROMs will add this much needed feature?
Click to expand...
Click to collapse
That's all I was looking forward to also.
Its no wonder companies ignore their users when they needlessly and wrongly report bugs for something which is clearly not a bug.
If I was Google I'd ignore every single bug report which was actually reporting a missing feature.
For whatever reason, Google left it out, probably because its a niche requirement. It's not a bug.
thank god ur not google
maybe it's not the right category but at least I did something to point out that there's a problem and gave other ppl the chance to express their madness about this problem aswell.
And a niche? C'mon this is absolute standard nowadays and we can expect this from a 2012 smartphone when even my 2010 i9000 had it!
Lownita said:
There is no rom that supports it! If you find one, let me know
Click to expand...
Click to collapse
cm10 has it.
AnonymousPenguin said:
cm10 has it.
Click to expand...
Click to collapse
Is it possible for anyone to confirm this?
I was about to root when looking at CM but thought they didn't have it?
alternetconcept said:
Is it possible for anyone to confirm this?
I was about to root when looking at CM but thought they didn't have it?
Click to expand...
Click to collapse
I dont have NEXUS but CM10 M2 for Galaxy S III has it. 100% working. keep in mind, its 4.1.2 though !
It is funny how google is missing this very important feature.
bump. Which ROM has it?
Bump Anyone know if any of the custom ROMs for Nexus are putting this feature in? I've search...but didn't see a mention. Please link. Thanks!
sarasotaguy said:
Bump Anyone know if any of the custom ROMs for Nexus are putting this feature in? I've search...but didn't see a mention. Please link. Thanks!
Click to expand...
Click to collapse
Same here, don't understand it
i can confirm it works in cm 10. i use it on my car all the time. the cover art doesnt work but the tags work perfect.
Which ROM?
Sent from my Nexus 4 using Tapatalk 2
I find the Zoe function of the Camera very interesting. Don't know yet, if I am going to go for the HTC One so I wonder if the function is portable to other devices (by some crafty XDA-dev)?
take55 said:
I find the Zoe function of the Camera very interesting. Don't know yet, if I am going to go for the HTC One so I wonder if the function is portable to other devices (by some crafty XDA-dev)?
Click to expand...
Click to collapse
Since it is a HTC function, it will probably require the HTC framework etc so I would say unlikely. No one has ever successfully ported the HTC rosie or any HTC app to another ROM without porting the whole thing.
I am sure someone will come up with something similar one day
Sorry to ruin your hope
Having virtual buttons has been excellent, both for a sensible button layout and because it puts the three-dot overflow menu into a consistent, intelligent location. I know you can get it on AOSP-based ROMs, but I'd be curious to try it with one of the Google Edition variants. Is there one which supports the virtual buttons?
Have you tried adding qemu.hw.mainkeys = 0 to your build.prop? I'm not sure if it'll work, but it's worth a try.
wtfismdna said:
Have you tried adding qemu.hw.mainkeys = 0 to your build.prop? I'm not sure if it'll work, but it's worth a try.
Click to expand...
Click to collapse
I'm actually such a noob that I don't even know what the build.prop is...
If you go to /system/, there's a file called build.prop. If you open the file, you can add "qemu.hw.mainkeys=0" to the end, which should enable software keys. I'm not sure if it'll work on Sense/GE ROMs, but there's no harm in trying. Just make a backup before you do any editing!
Sent from my HTC One using Tapatalk 4 Beta
To my super limited background, that looks like it should just disable hardware keys, but I'll give it a shot. Thanks!
Also if anyone knows of a GE ROM with such an option built in, I'd appreciate it.
Sent from my One using Tapatalk 2
wtfismdna said:
If you go to /system/app, there's a file called build.prop. If you open the file, you can add "qemu.hw.mainkeys=0" to the end, which should enable software keys. I'm not sure if it'll work on Sense/GE ROMs, but there's no harm in trying. Just make a backup before you do any editing!
Sent from my HTC One using Tapatalk 4 Beta
Click to expand...
Click to collapse
Build prop is usually in /system.
Sent from my HTC One
Simba501 said:
Build prop is usually in /system.
Sent from my HTC One
Click to expand...
Click to collapse
Yeah, that's what I meant to say, unfortunately not what I typed.
Fixed now.
Were you ever able to get it to work? I did try adding that command to the stock touchwiz on my GS4, but it never worked. GUI froze and restarted all the time. Having the nexus virtual buttons on the GE HTC & GE GS4 roms would be excellent. Please help anyone! =)
Whach said:
Were you ever able to get it to work? I did try adding that command to the stock touchwiz on my GS4, but it never worked. GUI froze and restarted all the time. Having the nexus virtual buttons on the GE GS4 rom would be excellent. Please help anyone! =)
Click to expand...
Click to collapse
Why are you asking here ... You might want to ask in a Samsung thread because I can't see why you'd ask in a HTC Forum
AllAboutTheCore said:
Why are you asking here ... You might want to ask in a Samsung thread because I can't see why you'd ask in a HTC Forum
Click to expand...
Click to collapse
Thought it was pertinent to any GE Edition Rom - HTC, Samsung, whatever. I'd assume enabling software keys would not be device specific in a GE ROM? (well, at least I hope it is) Just saying......
Whach said:
Thought it was pertinent to any GE Edition Rom - HTC, Samsung, whatever. I'd assume enabling software keys would not be device specific in a GE ROM? (well, at least I hope it is) Just saying......
Click to expand...
Click to collapse
If that's the case then why bother having device specific forums? May aswell just have one forum where people post anything ... If I wanted to ask a question about the HTC One, I wouldn't be asking it in the Samsung section, what's the point?
AllAboutTheCore said:
If that's the case then why bother having device specific forums? May as well just have one forum where people post anything ... If I wanted to ask a question about the HTC One, I wouldn't be asking it in the Samsung section, what's the point?
Click to expand...
Click to collapse
The point being the question was more about enabling the virtual keys in relation to the GE software only. The thread title & discussion was more relevant.
I've now been able to get the virtual keys for both GE edition phones working using the same build.prop command. The command applied to both devices since it concerned the software rather than the hardware....... whether I posted here or in the Samsung forum (which I did) didn't really make a difference did it?......the outcome was the same.
Of course posting in a device specific section is best when the discussion is about the specific hardware, that's obvious. This thread could have easily been located in the Android Dev and Hacking section, but it wasn't and so I just made do with it.
Hope that is a satisfactory enough explanation for this storm in a teacup....if not, have an apology for your appeasement
I really dislike the fact that the Note for has a very cool (I mean, it makes my slightly cool iPad look warm..) screen calibration. Is there anyone who'd even know how to add this to a Kernel for CM12? (not stock touchwiz) would be cool to warm it up a touch and get that eye hurting blue under control (I know it's not that bad for most, but I'm really sensitive to minute details like that.) Figured I'd at least ask. Also, I'm working on my first "custom" ROM. Essentially I want to bring back some of the helpful features that touchwiz offers within CM12. QUICK SOMEOME SCREAM! Haha I know the point of CM12 is to get rid of that, but the point of AOSP is to enjoy open source freedoms. So far I've gotten a few stock apps running as well as some other customisations
Alcor10 said:
I really dislike the fact that the Note for has a very cool (I mean, it makes my slightly cool iPad look warm..) screen calibration. Is there anyone who'd even know how to add this to a Kernel for CM12? (not stock touchwiz) would be cool to warm it up a touch and get that eye hurting blue under control (I know it's not that bad for most, but I'm really sensitive to minute details like that.) Figured I'd at least ask. Also, I'm working on my first "custom" ROM. Essentially I want to bring back some of the helpful features that touchwiz offers within CM12. QUICK SOMEOME SCREAM! Haha I know the point of CM12 is to get rid of that, but the point of AOSP is to enjoy open source freedoms. So far I've gotten a few stock apps running as well as some other customisations
Click to expand...
Click to collapse
Check out CF Lumen on the play store.
Sent from my SM-N910T using XDA Free mobile app
I know of many apps for that. The issues with apps is that they run on top of the system. A kernel tweak would give you optimized adjustments. Essentially setting the display natively vs actively updating it. I hope this makes sense. I had an app that did that, but the constant running meant that it inherently caused the system to be stressed more. (Now this app could do much better, and please let me know if it does, but the app I had used an unnecessarily high amount of RAM for what little it was doing.) In my mind it would be simpler to just warm the display up natively from the kernel. Also (Full credit to whoever did it) I would be able to post the ROM file already modified like that without needing to make that app a system app.
look in the cm remix thread
wase4711 said:
look in the cm remix thread
Click to expand...
Click to collapse
Thank you for the suggestion, but in this case a link would help. Searching for it leads to MANY results, haha
ok, here is the thread
http://forum.xda-developers.com/note-4-tmobile/development/rom-cmremix-rom-v2-5-12-23-14-t2981479
wase4711 said:
ok, here is the thread
http://forum.xda-developers.com/note-4-tmobile/development/rom-cmremix-rom-v2-5-12-23-14-t2981479
Click to expand...
Click to collapse
Thank you sir!! I made a quick little post in there to ask them what's up, shall see if that already does it, or if it can be added.