[Wip] Hdmi On Non-Moto Based Roms - Motorola Droid RAZR

NOTE: A lot of this info is duplicated from a post i had made on droidrzr a while ago. I'm adding it here because i'm actively looking into getting this working once again and I would love any input/thoughts that other devs have on this topic.
Ok, so i've been poking around trying to get HDMI support working in non moto-based ROMs (basically anything that would be using kexec or an AOSP base like CM). It's not complete but i figure it's better to have more eyes on this than just mine. Apologies ahead of time if this post turns into a big info-dump, but here's what i have so far. Also, this is HDMI only, not webtop related.
Initial research:
My previous phone was a Droid X and there were similar issues relating to HDMI on non-stock roms. So my first inclination was to look into how that was fixed.
Here's the post in question: http://rootzwiki.com...m-audio-solved/
Basically, there are some required framework files that are needed for detecting an HDMI cable, notifying the system that it exists and enabling the output. There were also some permissions files and an APK that needed to be copied as well. The big issue with this is that the APK needed to be signed with a signature that matched the one that the ROM was built with (and since a lot of devs use the default android test/build keys, this wasn't all that difficult).
Now, keep in mind that the HDMI on the droid X wasn't mirror mode and operated VERY differently. However, it gave me a good place to start looking on the razr.
Some digging:
First, after looking through system/app i found this apk: ExtDispService.apk. As with the DX, this file is definitely going to be needed. This was where i started digging. I re-signed it and added it to the CM install zip, and put it on my phone. Now, of course it immediately crashed, but at least i had some logs to help me determine why.
Tools:
As a small note, I was using Virtuous Ten Studio to do a lot of this editing. I can't stress enough how awesome this program is for things like this. I had been doing it all manually at the start and making ONE change to that APK would take me close to 15 minutes. With VTS, i could do it in 5 or less. So from here on out, if you're following along, be sure to have the APK and JAR files mentioned added to a project in VTS and de-compiled so that you can see the smali code.
The roadblocks:
So once i had the logs, i was able to see where the APK was crashing. I knew that I would need to include some items from the framework, but i just wasn't sure what yet.
The first hiccup was in ExtDispService$HandleInitAutoDetectSetting.
Code:
const-string v3, "hdmi_autodetection"
invoke-static {v1, v3}, Lcom/motorola/android/provider/MotorolaSettings;->getInt(Landroid/content/ContentResolver;Ljava/lang/String;)I
So, from looking at this, you can see that it's trying to access a Moto utility that allows programs access to information from the settings menu. In this particular instance, it's the on/off switch for HDMI autodetect. This opened up a whole new can of worms. How would we add these items back to the settings menu? How would we fake the overscan setting?
My first inclination was to look for the MotorolaSettings class and include that into the package. However, this could potentially lead us down a very dark path of dependency hell. Worst case scenario: we have to include a lot of moto's framework to get this working (and isn't the whole point of this to get away from moto's code?!). I attempted to remove the references to the settings menu in the smali code and replace them with hardcoded values. This was EXTREMELY hackey but it was more of a proof of concept at this point anyway. I was able to get the phone to boot and not have ExtDispService crash on me, however there was also no response when I plugged in the HDMI cable (nothing at all in the logs).
List of files needed:
Here are a list of some files that i know are required to get this working:
system/app/ExtDispService.apk
system/framework/framework-ext.jar
system/lib/libextdispjni.so
system/lib/libhdmi.so
system/lib/libhdcp.so
Some final thoughts:
I realize that there isn't too much concrete info here, but I wanted to share what progress I had made so that maybe someone else could either pick up from where i've left off, or make some suggestions on how to proceed.
EDIT: I wasn't sure if this belonged in the Android Development sub-forum or not, but i put it here just to be safe. If a mod sees this and think's thats a better place, please feel free to move it.

HDMI is mostly related to the kernel (for kexec at least). But currently there is a new kernel and a workaround for kexec in development, 3.0.31 / 3.0.88 Kernel. Two of the main goals are Full HD video recoding and HDMI.
The apks only will not work as there are complete different drivers in the kexec kernel. I guess we would have it working already if this could have been fixed by app side.
However, maybe I'm wrong
Hash told me about the current development, you can see it in their repo of course. Maybe we should wait a little more..
Gesendet von meinem XT910 mit Tapatalk 4

Ah, wonderful! I just read through your thread. Thanks for posting here about it. I'll be keeping an eye on the new kernel. If there's anything i can do to help out, be sure to let me know.

djuniah said:
Ah, wonderful! I just read through your thread. Thanks for posting here about it. I'll be keeping an eye on the new kernel. If there's anything i can do to help out, be sure to let me know.
Click to expand...
Click to collapse
Help is always appreciated! Are you familiar with C coding?
Gesendet von meinem XT910 mit Tapatalk 4

Yup, I am quite familiar with C.

djuniah said:
Yup, I am quite familiar with C.
Click to expand...
Click to collapse
Nice! If you would like to join kernel development, let me kow.

This had been one of the first things that never worked with our custom roms. Your reasearch and approach for solving this damned bug make good sense. I hope you can succeed for all of us and solve the DROID RAZR HDMI MYTH. Thank you.

Related

[Q] android kitchen

hello guys just set up dxsidia android kitchen not sure if anyone uses this but i have a few questions and since dxsidia does not support this anymore was hoping someone could answer them for me...
1. is the major obvious one does it work on the photon in the thread it does say unconfirmed for atrix but nothing on photon?
2.after creating the work folder i go into advanced options and start editing? i realize since there is nothing on the photon most of my answers are probably going to be try and see but no harm in asking right...
3.it has a set of pluign scripts labeled sgs2/ sgs these are for samsung galaxy s right so i dont want to use any of them?
4. there is a task killer tweak you can add from it what exactly is this?
5. add data/app functionality??? lets you add or remove apps??? not sure is why im asking
there are more q's but i figured if i can get these answered im doing good
ive read the thread for a few days now and seems simple but confusing at same time seems like its a one click type thing but if you dont know for sure what you are clicking can really screw up and have to start from scratch... anywho trying to do more around here and would appreciate any help anyone has thanks a ton
1) Yes in terms of an apk is an apk. No in terms of the updater script (IIRC)
2) Yes, assuming theres options in the advanced menu you'd like to impliment
3) You don't need the Samsung plugins.
4) Changes minfree settings in the boot image. Be aware the ICS impliments memory handling differently than previous versions.
5) Adds a script and folder for data/app partition so you can include optional apps. Optional apks (things like nascar for example) could be placed in here and would be installed on flash. But because they are in /data, the user has the option to uninstall through manage apps.
Personal Opinion: While the kitchen may be a convienient way to do things, it leaves little (Read: No) room for learning. Assuming you'd like to create a body of work to be publically distributed and not just for personal use, it might be worth the upfront investment in figuring out how to do/script this stuff yourself. That's not me trying to be an elite a-hole, that's me giving solid advice.
Cheers!
Yeah im a trying to learn as much as i can ive been reading and reading and reading have always known about the kitchen just never tried it thanks for the response you didnt come off as elitest is all good i find its easier for me to learn by trying things while reading about it granted i do research in great lengths not just in xda but other forums, blogs, links so on and so on before even downloading these tools but as i said it seems to sink in better when i can go ok i use this option this what it means thats what it did this what its supposed to do/look like
Sent from my MB855 using xda premium
So ive been trying all day to spit out a rom with the kitchen and no matter what i do it doesnt install either get status 7 or 0 says was looking for 4agrs but only found 3 and sometimes says 3args but only found 2 ive tried using a rom i know flashes and just running it through the kitchen and flashing the output... idk what im doing wrong but starting to think it is not photon compatible any insider tips? i know i already asked this but not quite ready to surrender to defeat on this yet and i REALLY dont want to install linux or ubuntu on my computer would have to partition it and just not to keen on doing that to the family computer my kids and wife play on it almost more than i do

update beta2 release(app) FLIPBOARD (official beta)

Found this application which was once only on i-application(iphone) working fine on our touchpad and yes it also plays good on my LG optimus one too. It is like google currents but a little different in work around. Enjoy the port.
Here is the app
Press thanks if I helped.........
no offense but I'm pretty sure i've seen this posted somewhere else..u might wanna give credit to the original poster who yanked this from the sg III launch event..
Should be this http://forum.xda-developers.com/showthread.php?t=1644212
it doesn't look that great on the touchpad....very pixelated
ace9988 said:
it doesn't look that great on the touchpad....very pixelated
Click to expand...
Click to collapse
yes you are right but most of the posts and topics look nice, neat and clean.
and I think something is still better than nothing....
what do you say?
compared to the browser....you'd have to argue the need for this, it was designed for the phone (GS3) and all that's been done is ported from there. If they developer made a bespoke tablet version then it'd be nice. but hey, thats my beef with ICS at the moment, many apps are stretched and look wrong
I like it alot.... Thanks for sharing,I hadn't seen the other thread so glad to have the app on my og evo and touchpad
Sent from my cm_tenderloin using Tapatalk 2
Thanks
HP Touchpad CM9
I think an update came out for this today. Of anyone can pull the updated app it would be greatly appreciated! Thanks
HP Touchpad CM9
Someone was working on a version where they adjusted the fonts to make them look better on a tablet but I never saw the actual package posted.
famewolf said:
Someone was working on a version where they adjusted the fonts to make them look better on a tablet but I never saw the actual package posted.
Click to expand...
Click to collapse
I was working on it.... Never got it right, as it appears I was only able to change the UI fonts. The article fonts themselves appear to be set remotely and just displayed locally. So it didn't even fix the biggest issue with the fonts which is in the articles themselves. It only fixed the UI and header fonts. I was going to post the APK anyway, but I found a force close error when trying to add new feeds, so that made things not so nice. Add to that the fact that for some reason, the APK wasn't installable unless I re-signed it, that makes it difficult to switch between versions without uninstalling/reinstalling, I decided not to post the modified APK.
If a developer type wants, I can send the modified APK directly. I'm not going to post it here because it's A) not stable and B) didn't achieve the intended purpose anyway, and C) I don't want to have to support something that's broken/unfinished.
Anyone that knows how to decompile/recompile an APK can do the same thing I did. All I did was reduce the font sizes in the XML layout and values files. As I said though, that didn't have any effect on the actual article content, which appeared to be defined remotely.

[Discussion][4.0, 5.0 US+INTL]Enabling handsfree calling

First of all - sorry for posting it here, i don't mean to be in your face, it's just all discussions about this topic in other threads or posts went nowhere and i also think it didn't get enough attention from the developers. So, i just wanted to start a new thread dedicated to just this feature, since i believe this is one of the most useful features which is somehow got missed in these devices.
I'm talking about the ability to use GP5 to make calls though and answer calls from other devices through bluetooth. I think it's nuts that Samsung didn't implement this feature in these players, since most if not all top range mp3 and media players from this manufacturer in the last 5-6 years have had this feature (my pretty basic 4 year old samsung mp3 player can do this easily). Some people wonder why i care about this, but in my opinion it is a killer feature, which really opens up so many different possibilities to these devices. Tablets with 3g and 4g are reasonably cheap these days, so more and more people buy them. When you have one of them, you naturally think about a possibility of making calls through it. I'm one of such people, i have a 10" 3g tablet and i would like to be able to call through it using my GP5.
I participate in 5-6 different forums dedicated to these devices (mostly european sites) and i see requests and questions from people about this feature almost on daily basis. I think there are hundreds of people out there who would love to have it in their GPs. What i know is that the new GP 3.6 and 4.2 have it and the older ones 4.0 and 5.0 don't. So, i'm begging you, somebody, please make a ROM with this feature! I have no experience in programming for Android, but i think it should be very easy to take code or a library or whatever it is from one device and put it into another, since all these players have pretty much the same hardware (to my knowledge).
Thank you for your attention.
I you can link to a 3.6 or 4.2 rom that I can pull from (can be stock, custom or whatever), I can possibly integrate it into my next release, although I give no promises. Also, as this is development, and this is slightly off topic, I recommend that you change your post tags to [Discussion][4.0, 5.0 US+INTL]Enabling handsfree calling, so that people understand that this is a discussion, not some random person begging for a feature.
Thanks for your reply, i'll have a look for such rom.
Ok, i've changed the tags of this thread. Thanks.
Thanks! I also meant the tags in the thread name, not the actual thread tags. I never use them, so I forgot .
Right, that's what i thought at first, but i see no way to change the name of the thread, unfortunately.
Right, that's what i thought at first, but i see no way to change the name of the thread, unfortunately.
Click to expand...
Click to collapse
Edit the first post and click on the button called go advanced. Its at the top of the page
Sent by my Robot Butler
ok, Mars11_ on this forum pointed me here ->source codes for samsung players, plus he also offered to get any files from his unrooted GP 3.6. Would any of this be of any help?
Supermaster34 said:
Edit the first post and click on the button called go advanced. Its at the top of the page
Sent by my Robot Butler
Click to expand...
Click to collapse
great, thanks for the tip, done.
Thanks for the link! I will try and play around with some of the stuff included and see if I can come up with something. It may be just as simple as installing an apk...
Or maybe swapping bt libs would be all it takes.
Sent using Tapatalk
hanthesolo said:
Thanks for the link! I will try and play around with some of the stuff included and see if I can come up with something. It may be just as simple as installing an apk...
Click to expand...
Click to collapse
oh, sweet, i'm all itching in anticipation! thanks mate!
this means the phone features also needs to be activated because it goes hand in hand im not a dev but im sure its more than installing an apk. i think this will also require some framework changes. also activating the sip calling feature will be very exciting as our SGP can sync contacts as well this can be done in galaxy note by just adb pushing some files to system dir and activating the hands free profile in htc flyer is as simple as editing the build.prop so im sure this is doable but we need to call in the attention of devs :good:
Bad news guys, the uncompiled image didn't help, and I was unable to open the .img that I pulled from a 3.6 rom. Could someone pull their entire /system directory (apply this terminal command: dd if=/dev/block/systemname of=/sdcard/factoryfs.rfs), and then pull it off their sdcard (internal) and upload it here (tar or zip it if you need to). I do not believe root is required for that, and I am able to access .rfs files to edit them. You can find the name of your system partition by punching in "mount" in the terminal and then finding /system in the output, and recording the partition name that follows (eg. my system partition on my 4.0 is /dev/block/stl9).
I was tinkering with my sgp amd found this if this might be of any help
Sent from my YP-G70 using xda app-developers app
Ok, I've just sent an email to Mars11_, who's recently offered his help with extracting files from his SGP 3.6 in this thread: http://forum.xda-developers.com/showthread.php?p=28558588#post28558588
I asked him to come here and follow your instructions. He's our only hope right now.
Got responce from Mars11_ that's what he said: "Okay, so I've run the commands Hanthesolo had, but I didn't have read access to /dev/block/mmcblk0p8 . So I need root, and second, I can't post in the Android Dev yet, as I don't have 10 or more posts. "
Well, hat pretty much means that I can't pull anything together untilthe 3.6 gets root (I guess I could create a guide for that, but I don't have a 3.6, and I cannot exract anything from it's .img images). Sorry about that, but as soon as a /systm dump is uploaded, I will get on it. A last ditch attempt may be to use adb, but I think that you must have root to get su access from it as well. Perhaps you can boot into stock recovery and adb push the superuser binary and apk, that is, if the stock recovery supports adb, as I believe /system is mounted as rw in recovery. Perhaps a signed update.zip that only has superuser? I dunno, just some theories for 3.6 devs.
Mate, you have absolutely nothing to appologise for, you've done everything you could. I'm grateful for you desire to work on this. I guess we'll just have to be patient and wait for the 3.6 to be rooted Thank you.
Well, thanks for giving me a project to work on, because my sumer has just about fizzled out! I look forward to working on this while I wait for my Nexus 7 to arrive, and with it some more time-consuming hobbies .
hanthesolo said:
Well, hat pretty much means that I can't pull anything together untilthe 3.6 gets root (I guess I could create a guide for that, but I don't have a 3.6, and I cannot exract anything from it's .img images). Sorry about that, but as soon as a /systm dump is uploaded, I will get on it. A last ditch attempt may be to use adb, but I think that you must have root to get su access from it as well. Perhaps you can boot into stock recovery and adb push the superuser binary and apk, that is, if the stock recovery supports adb, as I believe /system is mounted as rw in recovery. Perhaps a signed update.zip that only has superuser? I dunno, just some theories for 3.6 devs.
Click to expand...
Click to collapse
You can always try the korean system dump and see what it gives.

[Users][4.0]ICS 4.0.4 support/discussion thread

Well, that time has come. I feel like our ROM is stable enough that I can finally proide support for it without you guys (unintentionally) clogging up the dev thread.
If you have a question, POST IT HERE. If you want to ask about install issues, how to get into devving, or rabid toasters, POST IT HERE. I am closing off the dev thread now that this is created. If you post there without a constructive helpful comment (I will put up criteria there), you will get yelled at, beaten, and sent to slink back to your hole from whence you came.
Okay, now that that's over, I will be providing support in this thread. I am not mean, scary, nasty, or like to drown puppies for fun, despite what the impression the above may give you. I am actually a very helpful person (as most pre-existing members here will agree), and will try to help you, even if you think it's a stupid question.
One rule here: Search first!
I cannot emphasize how important this is. As I said, I am more than happy to answer questions, but for the love of god please don't post something like "wherez the ICS guyzz, I don;t see it in this thrad, this forum sukks". Please use search first before posting. Thank you, and have a nice day.
Well, have fun, and I will answer any questions you have (even if they don't directly relate to ICS).
Install instructions:
Special thanks to daniel644 for the video and his high praises of me .
Guides (thanks to goldflame for these):
Drm manager
YOU MUST HAVE ROOT IN ORDER TO DO THIS!!!!
http://forum.xda-developers.com/showthread.php?p=31201787
Run this in terminal with su permissions
Open terminal Type su Accept the superuser request Follow the code from the post One condition if you reboot you have to repeat the third line of code.
This will fix the market
Here is rooting:
Download tsparky root on your computer from here: http://forum.xda-developers.com/showthread.php?p=31067529
Extract the zip plug in your Samsung, turn on USB debugging which can be found in settings-devoloper-usb debugging and run the bat file.
For those of you like me that when you open super user it fcs, here is a guide on how to fix that:
I have rooted, super user won't open now
OK follow theses steps
1) download and install Android commander (Google it)
1a) plug in your device and make sure USB debugging is on
2) open android commander
3) on the right panel go to /system/app and delete super user.apk
4) then go to /system/xbin and delete busybox and su
5) reboot and root again
Worked for me and two other people so it should work for you.
This is a good idea ... hopefully we will see more people pop in here than the dev thread, like to see you guys progress whenever possible and not so much "I need help installing this". I read a few posts of one of your guys requesting people to PM for help but maybe this thread will alleviate that "burden"...
da1writer said:
This is a good idea ... hopefully we will see more people pop in here than the dev thread, like to see you guys progress whenever possible and not so much "I need help installing this". I read a few posts of one of your guys requesting people to PM for help but maybe this thread will alleviate that "burden"...
Click to expand...
Click to collapse
Well, answering questions is not a "burden" more than it is something not 100% relevent to our dev thread, which (unfortunately) sometimes gets us off on a tangent. This way, I can help you guys, and we can still be productive in the original thread. Even if your question isn't relevant, pop me a PM, and I will be happy to help you, as long as you have researched first (meaning not stuff like "where's the stock rom"?).
hanthesolo said:
Well, answering questions is not a "burden" more than it is something not 100% relevent to our dev thread, which (unfortunately) sometimes gets us off on a tangent. This way, I can help you guys, and we can still be productive in the original thread. Even if your question isn't relevant, pop me a PM, and I will be happy to help you, as long as you have researched first (meaning not stuff like "where's the stock rom"?).
Click to expand...
Click to collapse
This is simply a suggestion, but maybe you guys could make a skype group, if you guys don't do that already. I guess it's a good thing to post in the dev thread the little updates, but I think a skype may be more convenient.
euphoriaflow said:
This is simply a suggestion, but maybe you guys could make a skype group, if you guys don't do that already. I guess it's a good thing to post in the dev thread the little updates, but I think a skype may be more convenient.
Click to expand...
Click to collapse
Between devs yes, we use Gtalk on a daily basis, and has been invaluable in getting work done quickly. It would be interesting to use skype and/or Gtalk for support, although we would need a dedicated account for that (and we are currently locked out of our Nova Gmail account, because we forgot the password ).
Not trolling here, but just wondering. Since when did discussion become development? Shouldn't this be in general?
In our one s forums all discussion threads are in the general section.
Sent from my HTC One S using Tapatalk 2
Same at the epic 4g touch forums, but to be honest, I don't mind it being here at all. Not too late to move this over there, though.
Sent from my SPH-D710 using xda app-developers app
hanthesolo said:
Between devs yes, we use Gtalk on a daily basis, and has been invaluable in getting work done quickly. It would be interesting to use skype and/or Gtalk for support, although we would need a dedicated account for that (and we are currently locked out of our Nova Gmail account, because we forgot the password ).
Click to expand...
Click to collapse
I do have the pass (I saved them in case we forget it). Also klin, it is considered for general but can be considered like dev too (in the sense of error reporting).
klin1344 said:
Not trolling here, but just wondering. Since when did discussion become development? Shouldn't this be in general?
In our one s forums all discussion threads are in the general section.
Sent from my HTC One S using Tapatalk 2
Click to expand...
Click to collapse
This is a subsection of our development thread, and while it may be better placed in general, it is best here, as we remove the chance of people who create accounts just to complain, and we obtain easier access for users. Plus, I believe I may have an idea to put the community to work, I just need to polish it a bit more.
hanthesolo said:
Between devs yes, we use Gtalk on a daily basis, and has been invaluable in getting work done quickly. It would be interesting to use skype and/or Gtalk for support, although we would need a dedicated account for that (and we are currently locked out of our Nova Gmail account, because we forgot the password ).
Click to expand...
Click to collapse
Can't you reset it. Should be easy if you put a recovery email
Sent From My YP-G1 running ICS build 3.5
is this version (3.5) already better than the GB Roms out there? or is it better for domeone like me who likes gaming and music to stay on my current rom until HW and such things are fixed?
btw im using dream Ultra right now because my device makes weird noises when im using other roms
crancpiti said:
is this version (3.5) already better than the GB Roms out there? or is it better for domeone like me who likes gaming and music to stay on my current rom until HW and such things are fixed?
btw im using dream Ultra right now because my device makes weird noises when im using other roms
Click to expand...
Click to collapse
I would hold off, but only for a little while longer, there are a few details (market download fix and proper sdcard support) that need to be added into the next ROM build so you don't have to ADB push things or use terminal to enter code after every boot, once those issues are fixed then it should be a good daily. But, if your comfortable and know how to ADB push files and stuff like that then go for it, just remember you WILL be charging it EVERY night due to the deep sleep bug inherited from the CM7 kernel that was used as the base for our CM9 kernel.
daniel644 said:
I would hold off, but only for a little while longer, there are a few details (market download fix and proper sdcard support) that need to be added into the next ROM build so you don't have to ADB push things or use terminal to enter code after every boot, once those issues are fixed then it should be a good daily. But, if your comfortable and know how to ADB push files and stuff like that then go for it, just remember you WILL be charging it EVERY night due to the deep sleep bug inherited from the CM7 kernel that was used as the base for our CM9 kernel.
Click to expand...
Click to collapse
Is it possible to fix that deep sleep bug?
My milestones that need to be crossed for daily usage would be:
H/W Acceleration
SD Card fixed (internal and external)
Deep Sleep
Everything else either has already been added/fixed (Voodoo!!! Beats removed and optional ) or I could wait for (bluetooth, camera, gps).
You guys are doing a great job though, can't wait for the next build to see how you guys are doing.
da1writer said:
Is it possible to fix that deep sleep bug?
My milestones that need to be crossed for daily usage would be:
H/W Acceleration
SD Card fixed (internal and external)
Deep Sleep
Everything else either has already been added/fixed (Voodoo!!! Beats removed and optional ) or I could wait for (bluetooth, camera, gps).
You guys are doing a great job though, can't wait for the next build to see how you guys are doing.
Click to expand...
Click to collapse
once oisis gets his sgp 4.0, he can port a 3.0.x kernal and all these will will be fixed.
da1writer said:
Is it possible to fix that deep sleep bug?
My milestones that need to be crossed for daily usage would be:
H/W Acceleration
SD Card fixed (internal and external)
Deep Sleep
Everything else either has already been added/fixed (Voodoo!!! Beats removed and optional ) or I could wait for (bluetooth, camera, gps).
You guys are doing a great job though, can't wait for the next build to see how you guys are doing.
Click to expand...
Click to collapse
if/when Oisis gets a 3.0.x kernel up and going (after he gets his player) hopefully the deep sleep bug will be no more, since its a carry over from the CM7 base kernel and if we have a new kernel that should solve that issue, and should get us to where bluetooth, camera and H/W acceleration could all be possible aswell.
Han, while we wait for Oisis to get his player and do his magic can we get one more build that has the fixed vold.fstab to have both internal and external memory working normally without having to ADB push files to the player and the market fix (if there's an easy way to do it)?
daniel644 said:
if/when Oisis gets a 3.0.x kernel up and going (after he gets his player) hopefully the deep sleep bug will be no more, since its a carry over from the CM7 base kernel and if we have a new kernel that should solve that issue, and should get us to where bluetooth, camera and H/W acceleration could all be possible aswell.
Han, while we wait for Oisis to get his player and do his magic can we get one more build that has the fixed vold.fstab to have both internal and external memory working normally without having to ADB push files to the player and the market fix (if there's an easy way to do it)?
Click to expand...
Click to collapse
A build with a fixed vold.fstab is possible but for the market fix, this is something related to the initrd that actually needs one more line of code for it to be activated lool.
goldflame09 said:
once oisis gets his sgp 4.0, he can port a 3.0.x kernal and all these will will be fixed.
Click to expand...
Click to collapse
Hold up a sec, I'm unsure of the situation a bit here... does oisis HAVE a Samsung Galaxy 4.0?
If not, I'm willing to toss a couple Tens his way (won't mention how much here) with a stipulation. I'm talking about Amazon Credit (which I have alot of) here... An Amazon gift card (via email) would have to be used as Amazon being the purchase website. PM me if there is an interest oisis if this is the case of you not having an actual SGP 4.0 ...
Edit: Ok, I just read that oisis actually did order one from China (?) but if it takes too long I'm still willing to help money wise if needed for any of these great 4.0 devs here developing the ICS rom
zaclimon said:
A build with a fixed vold.fstab is possible but for the market fix, this is something related to the initrd that actually needs one more line of code for it to be activated lool.
Click to expand...
Click to collapse
OK then, a build with fixed vold.fstab and a file browser like the free ES File explorer so I can sideload my apps.
daniel644 said:
OK then, a build with fixed vold.fstab and a file browser like the free ES File explorer so I can sideload my apps.
Click to expand...
Click to collapse
A file explorer? I think I will just fix the kernel so that the drmserver can work on boot. As for the vold.fstab, I cleaned all my repo so it will take a long time before I can get one, I will get it more presumably on the weekend.
zaclimon said:
A file explorer? I think I will just fix the kernel so that the drmserver can work on boot. As for the vold.fstab, I cleaned all my repo so it will take a long time before I can get one, I will get it more presumably on the weekend.
Click to expand...
Click to collapse
Yeah a file explorer (file browser) so I can access the LEGALLY obtained .apk's I've collected from the developers websites, to install them. for whatever reason there is NO file browser app in this CM9.

[Q] Capture Stylus hover events before they get to apps

I'm trying to work with a custom build of Android based on KitKat to incorporate a stylus, copying some of the functionality (though not code) from Samsung which sells Android-with-stylus builds for e.g. the Note 3. I'm not including details of the specific device because right now I am working on a custom dev device and my aim is to write code which is generic enough to be usable from any Android (based on KitKat). The build (written by others) already incorporates drivers and sends stylus events correctly as motion events etc. Programming at the app level I can receive onHover, ontouch, onClick etc
The specific functionality I am trying to achieve is to pick up a stylus-button-click while hovering. It's perfectly possible to do this in any app, using an onGenericMotion Listener.
However, I want to make my "stylus-action" have system-wide effect - so that anywhere (in any other app, or in the launcher or whatever) I will pick up the event (prior to any other app) and bring up my custom menu. (just like AirCommand in Samsung Note 3) I guess in my custom Android this would then make that particular action somewhat protected or unusable for other users, but I'm ok with that.
In older Android (prior to ICS) you could try something by putting up a System Overlay (i.e in regular app code, without hacking the ROM at all), but this is no longer possible.
This is not an attempt to tapjack or whatever, I understand why this functionality has been removed from the domain of the regular programmer, and I don't want to regress my ROM back to pre-ICS behaviour by allowing the System Overlay hack. Now I am programming the system (if my change is good enough I'd like to submit it back to AOSP) so I would like to know the best method to address this. Since Samsung have already done this, it must be legal (using legal in the terms of "Android will allow it"), and I want to do it right.
Is it possible to write something similar to the System Overlay when you are running from a system service? Or is there a good choke-point to capture events before they are broadcast to the current running apps?
I was looking at (sorry, not allowed to post links) AndroidXRef /frameworks/base/core/java/android/view/View.java specifically in the function dispatchHoverEvent() which looks like a promising place. My naive idea is that I would place code here checking the MotionEvent to see if the button is pressed and if it is, don't call any listeners and instead call my little menu app (or broadcast a custom message, or something anyway). However, I've never written code on the ROM level before (LOTS of experience writing app code) so I don't know if this is a really bad point or a good point to add in code. Should I be putting things at a higher level or a lower one? Will this capture all events or not? Is it all just trial and error?
If this is the wrong place to ask questions like this, please tell me where on XDA I should be asking it. If it's the right place - please answer
Thanks
Kibi
Crickets....
Is this the wrong forum to ask? Anyone able to clue me in on where i should be asking?
Thanks
Last try
Bumping one more time for good luck.
if this is the wrong forum, please can someone point the way to the right forum for me
Thanks
Kibi
kibi1 said:
Bumping one more time for good luck.
if this is the wrong forum, please can someone point the way to the right forum for me
Thanks
Kibi
Click to expand...
Click to collapse
this is not a wrong section but your post is too long so no one intrested to wasting time to read whole post.even i haven't read the post
kibi1 said:
Bumping one more time for good luck.
if this is the wrong forum, please can someone point the way to the right forum for me
Thanks
Kibi
Click to expand...
Click to collapse
The guy above me is a ****. I stumbled across this post looking for something completely unrelated (title interested me). Five words in I knew this was something completely out of my league, but I still read the entire post. If I may offer you some probably useless advice, I would talk to the devs in the note forums. The only problem I could see is that the AOSP guys don't have this function in their roms because it's locked up Samsung code and the guys modding the stock roms leave it alone for the same reason. I could also be completely wrong. Like I said completely out of my league.

Categories

Resources