Related
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.
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.
i very like learn to mod the apps or a rom with my device, but i can't know which way is easy, i think i or new member like me will aslo like to do this work. Give me to advice. Thanks all you.
keveinee said:
i very like learn to mod the apps or a rom with my device, but i can't know which way is easy, i think i or new member like me will aslo like to do this work. Give me to advice. Thanks all you.
Click to expand...
Click to collapse
There is no easy way. First you have to learn Linux (ROM building) or learn to decompile the apps and look threw thousands of files. Alot of which are xmls and smali code.
^ true
Also depends which device you have
Mtk or snapdragon
zelendel said:
There is no easy way. First you have to learn Linux (ROM building) or learn to decompile the apps and look threw thousands of files. Alot of which are xmls and smali code.
Click to expand...
Click to collapse
i knew it, but i have one question that im using my device with snapdragon chip, but i don't understand that why some app, when i get from the other devices then some app, i can use, but something some app i can't use to my device? But all app from google play, the alls that can use to setup to my device, all things what is the different?
Ok first your chip has very little to do with what apps will or will not work on your device. Those are concidered by many other factors. Like screen res, ram, and in some very rare cases gpu. Others are OEM dependent. Some are dependent in if your rooted or not.
I would advise putting any development ideas on hold while you go back and do alot of research.
zelendel said:
Ok first your chip has very little to do with what apps will or will not work on your device. Those are concidered by many other factors. Like screen res, ram, and in some very rare cases gpu. Others are OEM dependent. Some are dependent in if your rooted or not.
I would advise putting any development ideas on hold while you go back and do alot of research.
Click to expand...
Click to collapse
thanks about your advice!!! First, my device had been rooted (my device is LG) then i can setup the apps from outside, and i see that when the modders decompile or rebuild a app, they also had added lge-res.apk, lge-res.odex, lge-framework.apk with command ' if ' in apktool like that 'apktool if lge-res.apk.....'
why did they do that?
I already have found very things from google search, but i could not find what things i need, cause be able to my english level is not good. im very exciting to do anything about that.
IF you be modder, professional in the modifier work. Can you help me to do that? Again that i thanks about your advice.
keveinee said:
thanks about your advice!!! First, my device had been rooted (my device is LG) then i can setup the apps from outside, and i see that when the modders decompile or rebuild a app, they also had added lge-res.apk, lge-res.odex, lge-framework.apk with command ' if ' in apktool like that 'apktool if lge-res.apk.....'
why did they do that?
I already have found very things from google search, but i could not find what things i need, cause be able to my english level is not good. im very exciting to do anything about that.
IF you be modder, professional in the modifier work. Can you help me to do that? Again that i thanks about your advice.
Click to expand...
Click to collapse
I am not an expert modder but I can try and point you in the right direction, those files are framework files that are required by the LG framework to function correctly, essentially they are extra resources that are required for the app to work correctly based on the changes LG made. Samsung, HTC, Motorola, etc. all have similar files that are required when working on any of there apk's (For example S Note is a Samsung specific app I would first have to input "if" the touchwiz framework for the app to compile and re-compile successfully in order to make any modifications to it). What other resources where you looking for?
shimp208 said:
I am not an expert modder but I can try and point you in the right direction, those files are framework files that are required by the LG framework to function correctly, essentially they are extra resources that are required for the app to work correctly based on the changes LG made. Samsung, HTC, Motorola, etc. all have similar files that are required when working on any of there apk's (For example S Note is a Samsung specific app I would first have to input "if" the touchwiz framework for the app to compile and re-compile successfully in order to make any modifications to it). What other resources where you looking for?
Click to expand...
Click to collapse
thanks your answer, you're so right. I would to be a really modder, i've just been learnt about electrical technology in my school, but i very exciting be become modder. Sure i will find additional to adding my leaked knowledge. Thank alot.
Hi all,
First off, I'm an experienced developer, but new to building Android. I'm looking to create my own personal ROM for my Nexus 4, stock AOSP but including root and App Ops. However, I have a couple of questions and clarity issues:
1) What is the proper way to fork AOSP so as I make my changes, they can be saved long term?
I've followed threads like this for setting up and looked into this to try to figure out the most efficient way, but it's not sinking in, so I guess I need a bit of hand holding.
2) Is it possible to enable App Ops in Lollipop pre-compilation?
I see tons of threads on enabling App Ops in JellyBean after compilation by modifying the Settings.apk, but I can't seem to find a way to enable it in the actual source code. Can anyone point me in the right direction? If anyone has guides for adding root and/or the battery percentage hack, that would be helpful as well, but admittedly I haven't done my due diligence searching those on my own yet.
Thanks in advance,
B.
i hope you get what your after.. missing AppOpps / privacy guard is what is preventing me from moving to Lollipop.
Sage said:
i hope you get what your after.. missing AppOpps / privacy guard is what is preventing me from moving to Lollipop.
Click to expand...
Click to collapse
I'm sure there are lots of other ROMs that have this out by now already, but if you want something that's 99.9% factory, mine is compiling now. Assuming my testing works, it will be bone stock LRX21T with a few minor modifications:
Enabled App Ops
Root friendly
Full rotation (including 180 degrees)
I'll let you know how it goes.
Thanks,
Ben
thanks Ben. I actually found an AppOps app in Google Play which works on Lollipop!
Sage said:
thanks Ben. I actually found an AppOps app in Google Play which works on Lollipop!
Click to expand...
Click to collapse
Could you reply here with a link to the App you located for anyone else who may be looking for this?
I just finished up my ROM actually. It's a base AOSP compilation for the Nexus 4 that is:
Root friendly
Has Busybox (for root backups)
AppOps
180 degree screen rotation
Modifications/Fixes to enable GApp support
That last one took a while, as location doesn't work out of the box with Google Location Services. It turned out to be a tiny tweak in the compile signing. Anyway, I just need to add the su binary into the ROM and it's done if you want it.
https://play.google.com/store/apps/details?id=com.findsdk.apppermission
This appopps is working on LP
Thanks sage. I'll likely continue to use my own ROM since future updates won't break my changes or lose root, but that will help many people out who find this thread.
Hello guys,
i want to share my experience about games on MIUI Rom.. Maybe you know, Some of games are not smooth on Miui with this Phone Specs. i tried some Magisk mode and now i have a perfect phone for the games.
After root my phone which magisk modes i used;
-NFS-INJECTOR 7.0 by K1ks (GAME MODE !)
-GPU Turbo Boost 3.0 by EmperorEye1993
-Ram Management fixez by crok
-Improve Game Xperience by mifansLA
i tested on those games.. CT Dream Team , MCOC, Perfect Mobile, Asphalt 9, Mobile Legend, Black Desert Online (KR).
For the installation..
You need to root your phone with Magisk and Add those modes on Magisk or TWRP at the Attached.
All the best. Good luck
How has this affected battery life IMO?
Great post but NFS is apparently a copycat and things which three other Devs hate and they work separately but one is working with another and one of them makes sure their mod are compatible with the other two.
I have probably confused you so let me list the names
FDE: app will be released very soon to allow user to control some things. Compatible with the following two. Maybe not all three at the same time lol.
LKT: has an app manager which the Dev of the mod below helped make.
Lspeed: first one to have an actual app, LKT had terminal commands to control some things (not hating on that just pointing out).
However if you have tried them and done your testing or simply do not want to change your setup then that's fine.
Whatever works:victory:
i've tested RAM_management_fixes_by_crok-v0.0.4.zip and it freezes the phone sometimes.
Sarcasm-Sunday-Pro-Tip:
If you're using the famous "GPU Turbo Boost 3.0 by EmperorEye1993" Magisk Module (and therefore didn't check its "source-code") - I strongly suggest also adding:
debug.fairydust=true
ro.vendor.outdated.cmds=enable
sys.activate.hidden.extra.gpu=1
to your system.prop - or any other file.
PS: don't
Windroid-user said:
How has this affected battery life IMO?
Great post but NFS is apparently a copycat and things which three other Devs hate and they work separately but one is working with another and one of them makes sure their mod are compatible with the other two.
I have probably confused you so let me list the names
FDE: app will be released very soon to allow user to control some things. Compatible with the following two. Maybe not all three at the same time lol.
LKT: has an app manager which the Dev of the mod below helped make.
Lspeed: first one to have an actual app, LKT had terminal commands to control some things (not hating on that just pointing out).
However if you have tried them and done your testing or simply do not want to change your setup then that's fine.
Whatever works:victory:
Click to expand...
Click to collapse
Im new on this phone.. so this is my first experience now im trying LKT and FDE, i will tell you result with Performance, Heating, and Battery Life.
JonasVFC said:
i've tested RAM_management_fixes_by_crok-v0.0.4.zip and it freezes the phone sometimes.
Click to expand...
Click to collapse
which rom are you using it? im using 10.3.15 and i dont have any problem..
callmeWhiskers said:
Sarcasm-Sunday-Pro-Tip:
If you're using the famous "GPU Turbo Boost 3.0 by EmperorEye1993" Magisk Module (and therefore didn't check its "source-code") - I strongly suggest also adding:
debug.fairydust=true
ro.vendor.outdated.cmds=enable
sys.activate.hidden.extra.gpu=1
to your system.prop - or any other file.
PS: don't
Click to expand...
Click to collapse
i dont understand what do you mean? shall i change that lines or not ?
Imyeltekin said:
i dont understand what do you mean? shall i change that lines or not ?
Click to expand...
Click to collapse
No - sorry for replying so late - this was supposed to be a joke.
I came across this module more than a year ago, immediately had doubts after reading its description ("...aims to increase Snapdragon powered devices by up to 75% but at the same time reduces power consumption by up to 25% seamlessly."), read through a lengthy thread about it here on XDA (mainly featuring people with little experience reporting back, that they "think" it works - and others reporting, that it's definitely not working and/or breaking things - and also some experienced devs chipping in to explain why... )
My conclusion (after also googling some of the tweaks, found in the source code): it was a collection of either non-functional, outdated or (very) device-specific tweaks - basically, hocus-pocus.
How to remove gpu turbo boost cause its not showing in magisk modules list
Where should i flash Improve Game Xpirience in Magisk or Custom Recov ? Cause i flash it in Magisk and take reboot.. but he's not showing in the magisk module, is it fine ?.. please help..
Stop installing crap on your phones instead to cry here...
Buy gaming PC, console - phone is not for serious games