Starting from 4.2, I was stummied whatever the reasons, the Nexus 4, the googliest product, had an imbecile audio driver. The things got worse on 4.3 where they removed that buggy ucm stuff, to replace it with an ever outrageous bs. So, just for testng, I did that codeaurora port and it worked on 4.3! And it's working GREAT, e.g. you can a) <b>record phone calls from line </b>) play compressed audio c) never mind the bollocks d)... Would you try this?
BOARD_USES_QCOM_HARDWARE := true
COMMON_GLOBAL_CFLAGS += -DQCOM_HARDWARE
TARGET_QCOM_AUDIO_VARIANT := caf
TARGET_USES_QCOM_COMPRESSED_AUDIO := true
you know where to find this, and -UQCOM_HARDWARE in cflags in
frameworks/av/services/camera/libcameraservice/Android.mk
frameworks/av/camera/Android.mk
frameworks/native/cmds/surfaceflinger/Android.mk
frameworks/native/services/surfaceflinger/Android.mk
because the surface flinger won't start with qc stuff (needs some adjustment). Here's my built
https://www.dropbox.com/login?cont=https://www.dropbox.com/sm/create/Stuff/rom/update_mako.zip
It's cute. It does record phone calls from the line, if you ask me. Hope you consider this, as that audio_hardware hal is unlikely to be ever upgraded.
UPD: oh yes. forgot that. kernel/lge/mako/sound/soc/msm/msm-pcm-q6.c
#define CAPTURE_NUM_PERIODS_MAX 16
.periods_max = CAPTURE_NUM_PERIODS_MAX,
the camera won't init otherwise
Great idea! Seems promising keep up
Sent from my Nexus 4 using Tapatalk 4
avs333 said:
Starting from 4.2, I was stummied whatever the reasons, the Nexus 4, the googliest product, had an imbecile audio driver. The things got worse on 4.3 where they removed that buggy ucm stuff, to replace it with an ever outrageous bs. So, just for testng, I did that codeaurora port and it worked on 4.3! And it's working GREAT, e.g. you can a) <b>record phone calls from line </b>) play compressed audio c) never mind the bollocks d)... Would you try this?
BOARD_USES_QCOM_HARDWARE := true
COMMON_GLOBAL_CFLAGS += -DQCOM_HARDWARE
TARGET_QCOM_AUDIO_VARIANT := caf
TARGET_USES_QCOM_COMPRESSED_AUDIO := true
you know where to find this, and -UQCOM_HARDWARE in cflags in
frameworks/av/services/camera/libcameraservice/Android.mk
frameworks/av/camera/Android.mk
frameworks/native/cmds/surfaceflinger/Android.mk
frameworks/native/services/surfaceflinger/Android.mk
because the surface flinger won't start with qc stuff (needs some adjustment). Here's my built
https://www.dropbox.com/login?cont=https://www.dropbox.com/sm/create/Stuff/rom/update_mako.zip
It's cute. It does record phone calls from the line, if you ask me. Hope you consider this, as that audio_hardware hal is unlikely to be ever upgraded.
UPD: oh yes. forgot that. kernel/lge/mako/sound/soc/msm/msm-pcm-q6.c
#define CAPTURE_NUM_PERIODS_MAX 16
.periods_max = CAPTURE_NUM_PERIODS_MAX,
the camera won't init otherwise
Click to expand...
Click to collapse
Apart from being able to record phone calls what are the real gains from that on the audio quality front? I don't understand much about audio stuff.
franciscofranco said:
Apart from being able to record phone calls what are the real gains from that on the audio quality front? I don't understand much about audio stuff.
Click to expand...
Click to collapse
Well, I'd expect a better sound quality and battery life (sic) when the phone is used as a media player. In any case, you may tweak that in /etc/snd_soc_msm which is actually unused now (I wonder why they haven't deleted that in their 4.3 roms). And you get the latest codeaurora updates as all qc patches arrive at that branch precisely.
need some mirror, dropbox show 404 now
I'd love to give this a test as I think 4.3 sound quality is absolutely awful on nexus 4. On 4.2 is was always pretty bad but they actually managed to make it worse for 4.3.
Can't download from your drop box.
Great news !
We will finally be able to record 2-way call from phone line instead of mic line on the Nexus 4.
Dropbox link is messed up. Re directs me to login.
Browse to the folder where the zip is and right click and say share link
Merci.
Here is, i think, a little bit older than in topic, but it CM 10.2 with gapps and we can record sound from line tap. In CallRecorder settings set voice uplink+downlink. Author avs333, say thanks for him.
avs333 said:
Starting from 4.2, I was stummied whatever the reasons, the Nexus 4, the googliest product, had an imbecile audio driver. The things got worse on 4.3 where they removed that buggy ucm stuff, to replace it with an ever outrageous bs. So, just for testng, I did that codeaurora port and it worked on 4.3! And it's working GREAT, e.g. you can a) <b>record phone calls from line </b>) play compressed audio c) never mind the bollocks d)... Would you try this?
BOARD_USES_QCOM_HARDWARE := true
COMMON_GLOBAL_CFLAGS += -DQCOM_HARDWARE
TARGET_QCOM_AUDIO_VARIANT := caf
TARGET_USES_QCOM_COMPRESSED_AUDIO := true
you know where to find this, and -UQCOM_HARDWARE in cflags in
frameworks/av/services/camera/libcameraservice/Android.mk
frameworks/av/camera/Android.mk
frameworks/native/cmds/surfaceflinger/Android.mk
frameworks/native/services/surfaceflinger/Android.mk
because the surface flinger won't start with qc stuff (needs some adjustment). Here's my built
https://www.dropbox.com/login?cont=https://www.dropbox.com/sm/create/Stuff/rom/update_mako.zip
It's cute. It does record phone calls from the line, if you ask me. Hope you consider this, as that audio_hardware hal is unlikely to be ever upgraded.
UPD: oh yes. forgot that. kernel/lge/mako/sound/soc/msm/msm-pcm-q6.c
#define CAPTURE_NUM_PERIODS_MAX 16
.periods_max = CAPTURE_NUM_PERIODS_MAX,
the camera won't init otherwise
Click to expand...
Click to collapse
hmm, if you would be so glad and share the adjustments from the surfaceflinger sauce? Oo
i wanna test the qcom stuff on ubuntu touch, maybe its compatible aswell ^^
but nice to see it, any improvemts on the sound quality, audio routing bugs or new deadlocks with the audio driver?
Regards,
OD
avs333 said:
Well, I'd expect a better sound quality and battery life (sic) when the phone is used as a media player. In any case, you may tweak that in /etc/snd_soc_msm which is actually unused now (I wonder why they haven't deleted that in their 4.3 roms). And you get the latest codeaurora updates as all qc patches arrive at that branch precisely.
Click to expand...
Click to collapse
Can you set up a github branch with all the changes you did instead of just pushing the rom .zip? I would like to merge it and test it. Thanks.
So if this will work for the Nexus 4 running 4.3, this will be a kernel side stuff or we can just apply a mod through flash ?
avs333 said:
https://www.dropbox.com/login?cont=https://www.dropbox.com/sm/create/Stuff/rom/update_mako.zip
Click to expand...
Click to collapse
I've seen and read this is devs only, but your link leads to drop box login ,then to a 404 error. Any chance of a link fix? Or is this cause I don't have Dev status or something?
Sent from my Nexus 4 using XDA Premium 4 mobile app
avs333 said:
UPD: oh yes. forgot that. kernel/lge/mako/sound/soc/msm/msm-pcm-q6.c
#define CAPTURE_NUM_PERIODS_MAX 16
.periods_max = CAPTURE_NUM_PERIODS_MAX,
the camera won't init otherwise
Click to expand...
Click to collapse
https://github.com/CyanogenMod/android_device_lge_mako/commit/3034a3419a269f84a110674a33822a5ce37d6682
camera/QCameraParameters.h
OldDroid said:
hmm, if you would be so glad and share the adjustments from the surfaceflinger sauce?
OD
Click to expand...
Click to collapse
No, I didn't touch the surfaceflinger code at all. Instead, you have to compile it with
LOCAL_CFLAGS += -UQCOM_HARDWARE
in those surfaceflinger makefiles I listed (as -DQCOM_HARDWARE is now set in global cflags), just to be able to boot! I haven't tested the audio-caf code much yet, but it looks very promising to me personally as I'm going to add direct 96/24 playback in my AndLess app now.
vitaliy_y, yes, exactly... the mako's camera header too. I'll set up a github branch a bit later this week, as franciscofranco suggests, but no more changes, really!
avs333 said:
No, I didn't touch the surfaceflinger code at all. Instead, you have to compile it with
LOCAL_CFLAGS += -UQCOM_HARDWARE
in those surfaceflinger makefiles I listed (as -DQCOM_HARDWARE is now set in global cflags), just to be able to boot! I haven't tested the audio-caf code much yet, but it looks very promising to me personally as I'm going to add direct 96/24 playback in my AndLess app now.
vitaliy_y, yes, exactly... the mako's camera header too. I'll set up a github branch a bit later this week, as franciscofranco suggests, but no more changes, really!
Click to expand...
Click to collapse
i will try to compile it using aosp, lets see if support has been added to it already
EDIT: not without caf-repos from cm ^^
Great news!
At last some real developers making nexus 4 owners happier
I would like to support this , where i could donate?
Also, is it safe to start using now? Which method to use?
Thanks!
avs333 said:
No, I didn't touch the surfaceflinger code at all. Instead, you have to compile it with
LOCAL_CFLAGS += -UQCOM_HARDWARE
in those surfaceflinger makefiles I listed (as -DQCOM_HARDWARE is now set in global cflags), just to be able to boot! I haven't tested the audio-caf code much yet, but it looks very promising to me personally as I'm going to add direct 96/24 playback in my AndLess app now.
vitaliy_y, yes, exactly... the mako's camera header too. I'll set up a github branch a bit later this week, as franciscofranco suggests, but no more changes, really!
Click to expand...
Click to collapse
ok got it,
from where you get the audio-caf source and the display-caf source?
some provided links would be good ^^
PS: sry im new to n4 development
OldDroid said:
ok got it,
from where you get the audio-caf source and the display-caf source?
some provided links would be good ^^
PS: sry im new to n4 development
Click to expand...
Click to collapse
I used audio-caf from cm10.2 as a base, because new codeaurora ones aren't compatible with libcsd-client for n4 (not a real problem, though).
And I _didn't_ try porting display-caf (no TARGET_QCOM_DISPLAY_VARIANT was set)!!
My tree is in total mess for now, need to tidy up before setting a github branch...
avs333 said:
No, I didn't touch the surfaceflinger code at all. Instead, you have to compile it with
LOCAL_CFLAGS += -UQCOM_HARDWARE
in those surfaceflinger makefiles I listed (as -DQCOM_HARDWARE is now set in global cflags), just to be able to boot! I haven't tested the audio-caf code much yet, but it looks very promising to me personally as I'm going to add direct 96/24 playback in my AndLess app now.
vitaliy_y, yes, exactly... the mako's camera header too. I'll set up a github branch a bit later this week, as franciscofranco suggests, but no more changes, really!
Click to expand...
Click to collapse
Hmm, tried compilling the same with CM10.2 and i get the error :-
'SNDRV_COMPRESS_METADATA_MODE' was not declared in this scope
The SNDRV_COMPRESS_METADATA_MODE is not mentioned in the kernel. It has to be in /include/sound/compress_offload.h
and sound/core/pcm_native.c
How did you get it to compile and which version of kernel did you use, and which Audio-caf did you use ?
Related
It seems that the guys with the Viewsonice G tablet located some issues at wake-up making the CPU run in 216Mhz..
Synopsis of what we learned:
Under certain conditions (LP1 suspend?), when the Tegra 2 was in a suspend state and a driver returned an error on wake-up, there is a step in the resume process where the voltage was supposed to be reset to the CPU, and that step was getting skipped. When the voltage was stuck low, the CPU would get stuck at minimum frequency, 216MHz and couldn't be pushed back to 1GHz or any other setting by the governor. There was a patch from NVidia that fixed this behavior, from a newer branch of the Tegra 2 source code than what Viewsonic used. We integrated this patch and found that indeed, it resolved the problem.
Maybe Teknoraver og badstorm2010 can include the patch those guys found with Nvidia, to fix our kernel too? not sure if Toshiba has the patch included..
or maybe its already in place, but it might be a cause for the wakeup issue we see on our tablet?
I still havent the kernel compile in place, due to a storage crash i lost all changes, so im unable to compile a new version atm..
See this post for alot more details on the problems.
Was messing around with the kernel anyway, so here we go.
I've also included utf8 NLS support (which is also default now) to support mounting NTFS volumes with utf8 charset.
The debug version of the patch sets the following properties
ro.debuggable=1
persist.service.adb.enable=1
This allows debugging/tracing of every (java-)process running on the system, no matter if they have the debuggable attribute set in their manifest.
weeds2000 said:
Was messing around with the kernel anyway, so here we go.
I've also included utf8 NLS support (which is also default now) to support mounting NTFS volumes with utf8 charset.
The debug version of the patch sets the following properties
ro.debuggable=1
persist.service.adb.enable=1
This allows debugging/tracing of every (java-)process running on the system, no matter if they have the debuggable attribute set in their manifest.
Click to expand...
Click to collapse
Thanks weeds! Do you have the original kernel laying around? For rollback purposes...
/Edit: Trying your kernel now, seems the HW buttons react now much better, did you change anything bout this?
weeds2000 said:
Was messing around with the kernel anyway, so here we go.
Click to expand...
Click to collapse
you compiled it with the patches included? right? sounds like the current custom kernel needs to be replaced..
im really hoping it solves some issues...
Did your kernel patch just fix out awake issue? i havent seen it for a while? and im wondering if the patch really was the solution, if so... its sooo great!
ill do some more "sleeping"
edit: ok, 2sec's after i wrote this it happened again, so didnt solve the screen awake issue i think..
I didn't do anything except implementing the patches. No button fixes, no wakeup stuff.
But it seems to be a good idea to get the Nvidia kernel running on the Folio as we then get some patches from Nvidia. Actually this was the "messing around" thing I've mentioned before.
I agree. Porting nvidia kernel might ease development when nvidia comes up with kernel for future android versions. At this point it looks like toshiba is dumping folio 100 for their announced honeycomb tablet. I am about to jump onto the ship and try out folio 100.
This thread is for development of a long-discussed 3.x kernel for encore/nookcolor. The goal is not only to have a modern kernel, but to take advantage of the expected support for hardware accelerated video and such.
TI has released an incomplete 3.x branch which is now being used as a base. The project so far has been about getting stuff ready and working so that as more source comes into omapzoom, it can be readily incorporated into our kernel.
keyodi (with some contributions from me, but mostly keyodi, so thank him below) has been doing the work thusfar for a few days, and there is now a VERY buggy build up-and-running. But since there has been so much discussion in the other cm9 dev thread, we felt maybe moving it here would be a good idea.
Current status:
(updated 5/27/12)
it boots up
accel 2d graphics work
mounting read/writing internal & external SD card
touchscreen (updated 3.4 driver) works but "stutters" (see below)
bluetooth works
adb works
no wifi wifi!
accelerometer works
charger not recognized on boot.
random restarts when sleeping
general sleep issues (pwr_core doesn't enter sleep)
no sound
weirdness where touchscreen is responsive only in short bursts.
no hardware accelerated video (no source for it)
Userland-wise, OMAP_ENHANCEMENT support needs to be added back into ICS, but that's beyond the scope of this thread.
Devs are invited to help. Anyone else should probably stay away, as this is buggy as hell.
To Build:
Add the following local_manifest.xml to ~/android/system/.repo:
--------------------
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<remote name = "gh"
fetch="git://github.com/" />
<remove-project name="CyanogenMod/android_hardware_ti_omap3" />
<project path="device/bn/encore"
name="fat-tire/android_device_bn_encore"
remote="gh"
revision="ics-3.0"/>
<project path="kernel/bn/encore"
name="keyodi/ti-omap-encore-kernel3"
remote="gh"
revision="encore-omap3-3"/>
<project name="platform/hardware/ti/omap3" remote="oz" path="hardware/ti/omap3" revision="ics-mr1" />
</manifest>
--------------------
Then repo sync, and then re-build (doing a make clobber may not be a bad idea to pick up changes to the BoardConfig.mk file). Changes were made to the device on its own branch to turn off audio for now. Also the kernel, using the cm9 conventions, is built along with the rest of CM9.
Try at your own risk. It is truly an unusable, barely completed result at the moment. Kernel devs, meet up on irc.
Also see the NookTablet (OMAP4, but lots of similar hardware) 3.x thread here as well as hashcode's Kindle Fire (OMAP4 also, but with 512MB) 3.x kernel thread here.
reserved
krylon360 said:
I can def confirm the issues that fattire has stated. Touch is VERY sluggish. I'm surprised I haven't broke my screen yet. lol.
I may have figured out wifi though. gotta rebuild to test that out. Had to fix some stuff in the kernel source and device tree just to get it to build the 1st time.
Click to expand...
Click to collapse
I successfully built the compat wifi driver on-the-fly per the NT. Is that what you're doing as well? I kinda only started... Are you still using WPA_SUPPLICANT 6 or are you using 8 now?
If you've got it working, I'll stop, git reset --hard, and wait for your commits
fattire said:
I successfully built the compat wifi driver on-the-fly per the NT. Is that what you're doing as well? I kinda only started... Are you still using WPA_SUPPLICANT 6 or are you using 8 now?
If you've got it working, I'll stop, git reset --hard, and wait for your commits
Click to expand...
Click to collapse
I'm using v8. I added the mac80211 source into kernel/external/wlan and built it with the build. Ill know if my changes worked when I get into the office here in a few.
Sent from my SPH-D710 using XDA
Will this commit help when fixed/merged?
Looks like it activate the hardware decoders , also look at the dependencies
If not , can you please elaborate on this OMAP_ENHANCEMENT? What it triggers?
Couldn't get good info on google
krylon360 said:
I'm using v8. I added the mac80211 source into kernel/external/wlan and built it with the build. Ill know if my changes worked when I get into the office here in a few.
Sent from my SPH-D710 using XDA
Click to expand...
Click to collapse
Yeah I used the mac80211 source from compat... using v8 also... I wasn't seeing a /sys/class/net/wlan0 show up tho... which is where i stopped when I saw your post..
OMAP_ENHANCEMENTS and touchscreen issues...
Dj-Gutz said:
Will this commit help when fixed/merged?
Looks like it activate the hardware decoders , also look at the dependencies
If not , can you please elaborate on this OMAP_ENHANCEMENT? What it triggers?
Couldn't get good info on google
Click to expand...
Click to collapse
OMAP_ENHANCEMENT gets set true for omap devices, and this allows the android build-process to know that it's got an omap device, and so in the frameworks or anywhere else there can be optimizations for that particular architecture added for enhanced performance or offloading calculations or whatever to OMAP-specific subsystems.
It doesn't have much to do with the kernel development except insofar as it needs to be able to support those enhancements. The Android software itself has to have the OMAP_ENHANCEMENT stuff integrated.
You can look at the CM7 code and grep for OMAP_ENHANCEMENT to find places where the omap hardware-supported functions are used instead of the regular android ones to get an idea.
Usually you'll see a check "if OMAP_ENHANCEMENT is set, do such and such instead of the normal way of doing it" and sometimes even a "If the OMAP type is OMAP4, then do this..."... So I don't know what kind of OMAP3 support will be built in or what.
Right now though, there are other issues. like this touchscreen thing. Epsylon3 says Atrix had the same issue but was fixed by Turl. He pointed me to some commits that may fix it... though I think this has to do with touch events being lost somewhere.
Thanks for the detailed response
I actually figured these stuff out before I posted my question , I wanted to focus on what is missing for it to be able to do h/w decoding for youtube hd/netflix
So far I've seen commits ( ics branch , I'll go through gb also later ) involving these files
media/libstagefright/MPEG4Extractor.cpp
media/libstagefright/OMXCodec.cpp
include/media/stagefright/OMXCodec.h
omx/video/src/openmax_il/video_decode/src/OMX_VideoDecoder.c
omx/video/src/openmax_il/video_decode/inc/OMX_VideoDec_Utils.h
original/linux/ion.h
I understand those patches I'm seeing are not completed , and the extent of how they work is questionable
I also know some related to camera recording ( encoding ) , but also decoding
you stated 2d acceleration works , that means hwcomposer is working?
I'll be ok leaving that as it is for now , since you're focusing on different issues now and we need to let you do your thing on the important stuff first - we can get back to that in a later date..
Thanks for the great work!
the patches you are referring to will actually break the framework source..trust me.. I tried. LOL.
the reason being is, you have to code it in manually so it wont break compatibility with QCOM or Samsung devices.
fattire said:
I successfully built the compat wifi driver on-the-fly per the NT. Is that what you're doing as well? I kinda only started... Are you still using WPA_SUPPLICANT 6 or are you using 8 now?
If you've got it working, I'll stop, git reset --hard, and wait for your commits
Click to expand...
Click to collapse
no luck on wifi yet. changed to many things the last build and only got a backlight.
I did notice in the wifi driver source that there is a conf file saying the interface is wlan1. I changed that to wlan0 for this build I'm doing now.
Touch Screen
I discovered something interesting while trying to figure out the issue w/ the touch screen, which was by accident of course. I was running a benchmark on quadrant when i noticed that the responsiveness of touch screen improved dramatically! Once the benchmark finished so did the responsiveness of the touch.
What does this mean? I dunno, but it looks like the issue may be CPU related, not driver.
hmmmm very interesting. I'll have to check this out. Wonder if we are missing a config file?
keyodi said:
What does this mean? I dunno, but it looks like the issue may be CPU related, not driver.
Click to expand...
Click to collapse
Did it get better during one particular test? ie, cpu vs. any particular screen test?
fattire said:
Did it get better during one particular test? ie, cpu vs. any particular screen test?
Click to expand...
Click to collapse
It got better throughout the testing.
Something else to try - start the benchmark, then press home. The touch screen should continue to be lag free even though the benchmarking has stopped, which is weird.
Observation:
cat /dev/zero
Suddenly touchscreen is responsive.
Any thoughts?
fattire said:
Observation:
cat /dev/zero
Suddenly touchscreen is responsive.
Any thoughts?
Click to expand...
Click to collapse
...hum. change your cpu governor setting to see if things get better?
Sent from my A1_07 using xda premium
TippyTurtle said:
...hum. change your cpu governor setting to see if things get better?
Sent from my A1_07 using xda premium
Click to expand...
Click to collapse
New governor has been tried.
New IO scheduler was tried by keyodi.
new task scheduler was tried by me just now. Still has the problem, and cat /dev/zero still makes it run without issue.
keyodi, et al-- here's the BFS commit. Use git am to try it.
Update: One other thought. If someone with a newer nook (and newer touchscreen) could give it a shot, that might help eliminate the driver as the issue (even though I think we can reasonably do that now..). I'd expect the new nooks to have the same issue.
fattire said:
New governor has been tried.
New IO scheduler was tried by keyodi.
new task scheduler was tried by me just now. Still has the problem, and cat /dev/zero still makes it run without issue.
keyodi, et al-- here's the BFS commit. Use git am to try it.
Update: One other thought. If someone with a newer nook (and newer touchscreen) could give it a shot, that might help eliminate the driver as the issue (even though I think we can reasonably do that now..). I'd expect the new nooks to have the same issue.
Click to expand...
Click to collapse
flashing with OnDemand as default right now. Will edit with results.
Edit. No Change.
here's where we are at on wifi
I can get it to read the wpa_supplicant.conf file.
D/wpa_supplicant( 973): wpa_supplicant v0.8.x
D/wpa_supplicant( 973): Initializing interface 'wlan0' conf '/data/misc/wifi/wp
a_supplicant.conf' driver 'nl80211' ctrl_interface 'N/A' bridge 'N/A'
D/wpa_supplicant( 973): Configuration file '/data/misc/wifi/wpa_supplicant.conf
' -> '/data/misc/wifi/wpa_supplicant.conf'
D/wpa_supplicant( 973): Reading configuration file '/data/misc/wifi/wpa_supplic
ant.conf'
D/wpa_supplicant( 973): update_config=1
D/wpa_supplicant( 973): ctrl_interface='wlan0'
D/wpa_supplicant( 973): ap_scan=1
D/wpa_supplicant( 973): fast_reauth=1
D/wpa_supplicant( 973): Could not open file /sys/class/net/wlan0/phy80211/name:
No such file or directory
However, as you can see... the main files for WLAN0 do not exist. There isn't a wlan0 dir, just this:
[email protected]:/sys/class/net # ls
ls
lo
sit0
krylon360 said:
here's where we are at on wifi
I can get it to read the wpa_supplicant.conf file.
D/wpa_supplicant( 973): wpa_supplicant v0.8.x
D/wpa_supplicant( 973): Initializing interface 'wlan0' conf '/data/misc/wifi/wp
a_supplicant.conf' driver 'nl80211' ctrl_interface 'N/A' bridge 'N/A'
D/wpa_supplicant( 973): Configuration file '/data/misc/wifi/wpa_supplicant.conf
' -> '/data/misc/wifi/wpa_supplicant.conf'
D/wpa_supplicant( 973): Reading configuration file '/data/misc/wifi/wpa_supplic
ant.conf'
D/wpa_supplicant( 973): update_config=1
D/wpa_supplicant( 973): ctrl_interface='wlan0'
D/wpa_supplicant( 973): ap_scan=1
D/wpa_supplicant( 973): fast_reauth=1
D/wpa_supplicant( 973): Could not open file /sys/class/net/wlan0/phy80211/name:
No such file or directory
However, as you can see... the main files for WLAN0 do not exist. There isn't a wlan0 dir, just this:
[email protected]:/sys/class/net # ls
ls
lo
sit0
Click to expand...
Click to collapse
Hah. This is EXACTLY where I had gotten stuck as well. No /sys/class/net/wlan0. I couldn't remember if this gets set up in the board file, by the module, or what. although I only had 2 files in /sys/class/net. netcfg also doesn't show anything....
PREFACE: This ROM is not intended for everyday use and posted mainly for experienced users and streak-oriented developerss to evaluate it and collaborate on bug resolution and further development. If you expect it to fit any particular purpose - answer is: "No, not yet."
People who really helped to make this possible:
985hPaKicK - author of original cm9 overlay files and pricey patches for DSC kernel.
Sergei Lyubshin (n0p) - team lead of DSC Phoenix kernel, which is used (in it's ICS-que incarnation) to power up this ROM.
Marc Alexander (marc1706) - original kgsl3.8 backport is taken from his kernel HD2 ics and used to provide support for ICS adreno drivers. Also, Marc's advices on changes in hw init procedures related to new kgsl were priceless. Marc, you're da man!
TeamICS - for excellent guides on installing android build environment.
Team Evervolv and CyanogenMod teams - for their hardware overlays.
Currently working:
Boot
Adeno drivers used to provide hwaccel (for real now, surfaceflinger no longer eats 100% of cpu all the time)
GSM subsystem - rild is partially working (no sim pin prompt)
Bluetooth - seem to work. Phone is able to pair to BT headset and output sound thru it (OP's Nokia's BH-103 - tested)
Wifi - partially. Signal strenght not being displayed at statusbar
Touchscreen - working.
Charging - works partially. Phone charges, reports battery percentage, but not voltages.
Sound output - works (No headset icon in statusbar is normal for stock sources.)
Data usage collecting.
UMS
Known not to work:
Everything that's not listed as working.
Other bugs observed by OP (to be extended with ROM users' feedback):
No mobile data reported by several users. OP is unable to reproduce it, so it's being investigated in "blind" mode at the moment. Currently known rild refuses to establish datacall because it thinks that user has no data subscription. EDIT: there's report that removing PIN makes things to work. Not perfect, yes, but worth a try. Report your results, please.
Scanning for available cellular networks is broken.
Extremely high load average (sometimes, seem to be caused by installed applications)
Development related links:
Kernel source: https://github.com/kibuuka/dsc-team-kernel-project/tree/ics - fork of DSC Phoenix kernel that's being used in this ROM. ics branch will be pulled back to main DSC kernel project source tree after n0p's return from vacation.
Device overlay based on hPa's code, changed to build against AOSP source tree instead of CM9's.
Download links: ROM itself - Updated Jul. 14th 13:53MST (changes: see post #2)
Alternative build - OBSOLETE Updated Jun. 28th 05:16MST. Temoporary solution for webkit rendering glitches.
gapps: update-Gapps-ICS-20710.zip See TheManii's post for details Mirror
root: Superuser.zip recommended way to gain a root on this ROM (By TheManii) Mirror
Screenshots: posted earlier in General forum *click*
Installation precautions: Usual ones. ROM is pre-alpha, so nandroid backup is your natural choice in this case . Factory reset from recovery menu is suggested (dalvik cache deletion is optional but recommended for first boot - caches will be rebuilt anyway).
Updating from previous builds of this ROM:
Flash new version
Flash gapps
Flash Superuser.zip (if applicable)
Last words: Feel free to provide additional details and feedback as you test it out. This project is amied to provide a stable base for future streak development. Once we have stable AOSP with full hw support - we have nice shortcut for porting anything that's not AOSP.
P.S. OP is not really experienced in ROM hacking and modding - all tips related to optimisation are greatly welcomed - for everyone's benefit
Reseved
Changelog (New records are displayed first):
Jul. 14 (built and uploaded for internal testing Jul. 13)
kernel: hPa's "force speaker on" patch.
system: Multiple internal changes in camera-related stuff (just for ther record. camera is still unfunctional)
build.prop: mobiledata.interfaces=ppp0. ro.telephony.ril.v3=datacall,signalstrength,facilitylock,icccardstatus,skipbrokendatacall
Jul. 11
kernel: reverted io scheduler back to cfq.
kernel: default cpu governor: smartass2.
kernel: screen rotation patch from updated Phoenix branch. Credits to hPa and n0p. hw.sw.rotation=180 is obsolete now.
system: *finally* there's working (for OP, please do extensive testing and report back) usb mass storage. Cm9's vold and LegacyUsbSupport (along with messing with rest of source) did a trick.
system: removed BasicSmsReceiver.apk from being built and installed. Double sms notifications should be gone.
Jul. 02
kernel: enabled iptables support (needed for mobile quota setting).
kernel: new cpu governors added. feel free to play with them and share your experience.
kernel: added new io schedulers. new default is sio (matter of change).
system: mobile quota setup is functional as of now.
system: built with BOARD_AAPT_PREF_CONFIG := hdpi mdpi. 160dpi users - please check if dialer problem is still present.
interface: added two previously unincluded LWPs.
Jun. 30
Resolved FCs in kgsl shown in 0630 posted earlier. Please re-download. Filename should read as dell_streak-ota-eng.den.063012-2.zip
kernel - Added support for quota2. Mobile data limits will work in next release (still need to figure if iptables binary is needed for this to function)
OpenGL-disabled build is put on hold and won't be updated since we have figured most of opengl-related problems now.
Fixed webkit rendering issues. (Gmail renders pages correctly but seem to "hide" message content on scroll. Anyone aware of gmail app bugtracker presence? Share a link, please UPDATE: not present at clean install. Please check if dalvik cache fleanup fixes it for you. If not - try factory reset) Please note browser is built with OpenGL rendering disabled by default for OP's testing purposes. This will be changed in next build.
Multimedia libs being built from sources now.
Working video in YouTube as result
Lots of Qualcomm-related patches in OpenGL-subsystem (selected parts of frameworks/base taken from mikegapinski's PolishBlood repo (Great job, Mike), lots of patches are from CAF, source was additionally patched (proper ro.sf.hwrotation=180 support, gradient fix, some more) to work correctly on DS5)
Removed some unfunctional components from being built. Factory reset recommended for full removal if updating from previous builds of this ROM.
Flipped thumbnails in recent apps issue - fixed. Re-enabling...
kernel: re-enabled per-process pages in kgsl (default setup).
kernel: default io governor set to ondemand.
Jun. 28
0627 rebuilt with new flags. no changes in code. hdpi resources are included and used by default.
added debug.egl.swapinterval=0 to build.prop
Added Superuser.apk (non-functional at the moment. Use Superuser.zip from TheManii's thread for now)
Jun. 27
Partial fix for mobile data. Searching for available networks known to fail. EDIT:SIM PIN request - still no love. Please test everything you can and report back.
Data usage logging is working now. Necessary patches applied to kernel source.
Surfaceflinger has dithering enabled by default. Smooth gradients ftw.
Added missing LWPs (requested by TheManii)
Added alternative build (it's being built with USE_OPENGL_RENDERER set to false). It has no webkit rendering bug at cost of lesser interface attractiveness.
Tethering options re-enabled. Check which are worked for you and report back, please.
Jun. 23
Disabled per-process page tables in KGSL driver (for now, matter of reversal on test results)
Surfaceflinger problem resolved. Interface is pretty smooth now
Enabled PF_KEY support in kernel (in resolution of pkoning's bug report)
Jun. 21
new kernel build - ipv6 is enabled - without this google services fail to operate properly
added missing apps (Messaging, Camera (broken) and several others) to build set
added some findings to build.prop, removed libGLES_android.so - overall interface performance is slightly improved, yet we're sure we're running with hwaccel now
Jun. 19
sound is partially working now (speaker and BT headsets. wired headsets/headphones not working yet)
if i not mistaken... there is ICS apps rip/port for messaging... i think i have seen that on market...
No screenshots?
john9 said:
No screenshots?
Click to expand...
Click to collapse
i believe OP already included it on the first post...
This is the Great Start !!!
john9 said:
No screenshots?
Click to expand...
Click to collapse
I think these are the screenshots
http://forum.xda-developers.com/showpost.php?p=27537842&postcount=46
What a great start!
I just tried it for a while. It feels awesome to have gotten this far. The ROM is quite laggy as the OP has already mentioned but I was able to get around. I was unable to make a call got an error about sim card not being there. I didn't have any 3G connectivity either. And didn't have any Wi-Fi to try since I am office right now. Since I did this in a hurry I forgot to factory reset but didn't get any FCs. I am upgrading from CM 7.2. None of the google apps seem to work besides youtube but all other apps started without any issues. Looks very good though it's almost like I can smell ICS now.
I have a spare Streak so am happy to reserve it for testing. Let me know if I can do anything specific.
I can confirm that wifi works.
I have tried setting up my Google account but get "Unfortunately, Exchange Services has stopped"
Browser works after a fashion but is not usable.
I can dial outgoing call and the receiving phone rings but no sound. Likewise for incoming calls, my Streak rings but I can't hear the caller and the caller can't hear me.
I seem to have trouble setting up an APN.
Sorry if all of this is already known. I still can't believe that I am looking at Android 4.04 on my Streak.
omg!
I am so looking forward to this!
Mega-Kudos to everyone involved!
yes, this is a good start for DS5 android 4.0 .
good start！
waiting for your further work,
thanks a lot.
I use this mms.apk (from Evervolv ICS rom), push it to system app and change permission. Sms can send and receive (but it take about 1 minute to send sms). http://db.tt/DTuQO5sS
Maybe this could help, could you check this build prop patch made by @lithid and @the_plattypus to fix the red box screen.
http://db.tt/zAJ04F8a
The build prop is for evo4g sense 4.0 rom.
The camera libs by @rapmv78
http://db.tt/CiZxdJT2
How I wish I have my streak with me.
Sent from my MT27i using xda premium
nom051205 said:
I use this mms.apk (from Evervolv ICS rom), push it to system app and change permission. Sms can send and receive (but it take about 1 minute to send sms). http://db.tt/DTuQO5sS
Maybe this could help, could you check this build prop patch made by @lithid and @the_plattypus to fix the red box screen.
http://db.tt/zAJ04F8a
The build prop is for evo4g sense 4.0 rom.
The camera libs by @rapmv78
http://db.tt/CiZxdJT2
Click to expand...
Click to collapse
Yep, will look further, thanks a lot. Right now i'm trying to figure what causes gralloc to get this mad (almost sure that buffer status errors are the main reason of phone sluggishness).
Oh and btw, could you please post logcat taken while sending sms?
Oh! Yes, Yes, Yes ... =P
Will flash it wright-a-way and give some feedback
Great news ! "You've made my dreams come true" =D
Hope it'll be great and powerfull change for our DS5's =]
---
Ok, so: - WiFi - worsk
My menu LEDs are always on, even after screen time out.
Camera (from lock screen) makes device reset. [there is no camera app i think]
Can't Add any APNs
Sound want work at all
Can make incoming/outgoing call (but with no sound in my earphone/mic)
Web browser cant display pages correcly
Screen brightness want work
Gallery(phonee) want access my SD
Phone correctly downloaded time data from operator.
I would offer every possible assistance in developing the project =P
Great JOB! ...going back to DSC1.1 - ...till now.
kibuuka said:
Yep, will look further, thanks a lot. Right now i'm trying to figure what causes gralloc to get this mad (almost sure that buffer status errors are the main reason of phone sluggishness).
Oh and btw, could you please post logcat taken while sending sms?
Click to expand...
Click to collapse
Kibuuka would you take a look at CM9 for Acer Liquid?
It is almost same as DS 5.
Maybe you can use the necessary libs from that ROM to solve the issues.
Sms send and received work perfect now (maybe last time hv bad network), opera mobile browser work perfect, superuser not work well, can use root explorer but cannot use other root apps.
This is really a good start, I believe we will hv stable version soon.
Sent from my PC36100 using Tapatalk 2
I am getting some offset errors during install, tried some times downloading but still same
Sent from my Dell Streak using Tapatalk
abauer said:
I am getting some offset errors during install, tried some times downloading but still same
Sent from my Dell Streak using Tapatalk
Click to expand...
Click to collapse
These messages are not error ones. Please read this.
Sound output is working now (tested with internal speaker and BT headphones. Wired will be tested tomorrow, don't any of these around at the moment ) EDIT:New download link is live now.
Anyone that has ported a few roms before, specifcally from a similar architecture, in this case from another Qualcomm Snapdragon S4 to our LGOG from Nexus4 and Nexus7 (2013) {edit. or GalaxyS3}. They are both spot on as far as similar but for the life of me every generic porting guide is written with great intentions and horrible follow-through.
What files for our device specifically control each part of our phone in the ROM .Zip? Especially for External SD working, and anything else off hand you feel like mentioning from experience.
Lastly, any differences porting from 4.2.2 to 4.2.2 vs 4.3 to 4.3?
Thank you in advance.
I've been trying push illusion rom over from the nexus 4 source, after 10+ mostly working attempts I started changing multiple variables at once, purposely dirty flashing over slim-bean because it left some residual files, removing the format /sdcard part from the updater-script of illusion to piggy back off of slim. Somewhere in the midst of this I actually had the External SD show up in storage settings, FINALLY. But by that point I started getting lots of FC's on the launchers and just about every app. Prior to that my main bug was that I couldn't control brightness, it was stuck on 100%. Somewhere in the middle of screwing with fstab's and the 4.2 exfat patch I could read the external card from the symlinks but it wouldn't show under storage or MTP/USB, only internal.
I'm going to have another go from 4.3 base to 4.3 from scratch. Feel free to chime in with anything.
It is fairly easy to go from n4 device repo to our repo. If you want to see what others do, just look at someone else's Repo's. I have my tree for aosp here, which is a basic n4 -> lgog fix, with a few hacks for unsupported things in aosp like button backlights: https://github.com/jbott/aosp_android_device_lge_geeb_att_us/commits/jb-mr2-dev
Not the cleanest thing, but shows what basically needs to be done.
I find dvhexer also keeps fairly clean repos that are easy to follow, if you want to check his out.
EDIT: Now I see that you mean literal porting directly. I would recommend building from scratch, even from a device as similar as the n4. It is not hard to do once you understand the basics. I actually find it is often easier than porting manually because the source layout makes sense. I believe the sdcard / mtp stuff is in framework-res as storage_list.xml though. It should match that in the overlay directory of my repo to work correctly.
Sent from my LG Optimus G using xda app-developers app
SnowLeopardJB said:
It is fairly easy to go from n4 device repo to our repo. If you want to see what others do, just look at someone else's Repo's. I have my tree for aosp here, which is a basic n4 -> lgog fix, with a few hacks for unsupported things in aosp like button backlights: https://github.com/jbott/aosp_android_device_lge_geeb_att_us/commits/jb-mr2-dev
Not the cleanest thing, but shows what basically needs to be done.
I find dvhexer also keeps fairly clean repos that are easy to follow, if you want to check his out.
EDIT: Now I see that you mean literal porting directly. I would recommend building from scratch, even from a device as similar as the n4. It is not hard to do once you understand the basics. I actually find it is often easier than porting manually because the source layout makes sense. I believe the sdcard / mtp stuff is in framework-res as storage_list.xml though. It should match that in the overlay directory of my repo to work correctly.
Sent from my LG Optimus G using xda app-developers app
Click to expand...
Click to collapse
I agree, I actually like reading through the source, and I have a good copy of ubuntu plus vm software, or I could dual boot, but unless you have explicit instructions on how to download the absolute minimum amount of data to compile from two different sources, I don't want to attempt it with this free hotel wifi. As it stands now I have more than one wifi card connected at the same time and a python script always running in the background changing the metric for my adapters, as each connection is limited to about 97KB/sec.
Does git know to sync across multiple interfaces? might not be too bad if it does.
Otherwise thanks for the link, reading that side by side with the MAKO source from googlesource.com you are correct about the location in frameworks. I'm pretty sure I can split that apart with an APK explorer and make the adjustments without breaking the rest of the rom(s).
Introduction
VirtualSensor is a module built on Xposed that creates several sensors on devices which do not have them. It does sensor fusion using the values from the accelerometer and the compass which are the two main requirements for this module.
There are currently 5 sensors emulated :
TYPE_ROTATION_VECTOR
TYPE_GYROSCOPE
TYPE_GEOMAGNETIC_ROTATION_VECTOR
TYPE_GRAVITY
TYPE_LINEAR_ACCELERATION
Being the most useful sensor for many applications, the gyroscope is the main sensor this project is about.
This module is born as an answer to personal frustration from not being able to use some applications after updating from my older Moto G (i.e. Photo Sphere) and later also as an answer to this thread.
Changelog
Code:
v1.5.1 - 02/08/2017:
This minor version fixes the module for Nougat devices.
See the changelog of v1.5.1 for the more information on what has changed for the major version 1.5.
v1.5 - 02/08/2017:
Finally a new release after (quite) a while. This release should fix the majority of bugs encountered on current and previous versions of Android.
With the precious help of people on Github, the cardboard hook has been (hopefully) improved.
The overall stability and reliability should be better now.
This release will stay marked as beta until relevant and good feedback is received, to please head over to Github if you can and report issues if any (or add to the exising issues to check wether they still exist)
v1.41 - 01/08/2016:
* Fixed the module, previous version broke it because of proguard minify, do not use version v1.4
v1.4 - 31/07/2016: /!\ This version is broken, avoid it /!\
* Added a check for already existing native sensors so that they don't get overridden by the module
* Now checks the values of the accelerometer and magnetic sensor against their accuracy. This means that the output values contain less noise without loosing too much precision
* Added a simple GUI to quickly get informations about the module. This part also calculates the values the gyroscope should return and compares them against the one the module actually returns
* Some hooks are now made on higher-level API (public available functions for apps), which means that specific device code should no longer break them
* Fixed a recurrent exception (ConcurrentModificationException)
v1.32 - 29/07/2016:
* Fix the mRequiredPermssion field no available on SDK < 20
Hotfix #2 for v1.3
v1.31 - 29/07/2016:
* Fixes the issue with SDK <= 18 where mStringType doesn't exist in the Sensor class
Hotfix for v1.3
v1.3 - 29/07/2016:
* Sensors are now added in a proper way. They should no longer accidentally override existing sensors / cause compatibility issues
* All gyroscope axes are fully functional !
* If it didn't work before for you on JellyBean-Lollipop, try now, it might (fixed the check for initialisation of SystemSensorManager)
* Started to work on a new filter system for the gyroscope mainly
v1.21 - 25/07/2016:
Hotfix for v1.2 to avoid crashes on JB devices.
v1.2 - 26/07/2016:
* Fixed compatibility with SDK18-22 (Android JellyBean 4.3 - Android Lolipop 5.1)
* Added a little more log
* Calculation for the gyroscope is now based on the calculated gravity sensor data, which (should) makes it work as intended in any orientation
* The virtual sensors now have a little more information in the created Sensor class, just to make sure this isn't an issue
v1.11 - 25/07/2016:
Hotfix for v1.1, fixes an exception raised in some cases when trying to get the accelerometer's min delay.
v1.1 - 25/07/2016:
* Added support for all SDK versions from SDK16 to SDK23+, this means all android versions starting from Jelly Bean should be supported
* Added a lot of new sensors : TYPE_ROTATION_VECTOR, TYPE_GEOMAGNETIC_ROTATION_VECTOR, TYPE_GRAVITY and TYPE_LINEAR_ACCELERATION
* Still no support for Pokémon GO though, working on it
* Some exceptions fixed
* Code refactored a lot
v1.0 - 23/07/2016:
Initial release.
Known issues
Right now, the Z-axis is not emulated as it always returned wrong values (Investigating this right now) Fixed
Some applications use the NDK instead of the SDK to access the sensors, the workaround is to hook them seperately, but that isn't done yet
There is some jitter even though the values are smoothed using a lowpass filter and averaged out
Disclaimer
Code:
Though it is unlikely this could happen given the modifications it does, the responsibility is yours for whatever happens after installing and using this module.
Download
Github : https://github.com/Frazew/VirtualSensor/releases/
Xposed Repository : http://repo.xposed.info/module/fr.frazew.virtualgyroscope
Contributing
There is a Github project for this module so please do not hesitate to contribute to it. I'll be glad to share knowledge and code. Please know that I'm not (yet? ) a professional coder and that errors are quite likely to happen.
XDA:DevDB Information
VirtualSensor, Xposed for all devices (see above for details)
Contributors
Frazew
Source Code: https://github.com/Frazew/VirtualSensor
Xposed Package Name: fr.frazew.virtualgyroscope
Version Information
Status: Testing
Current Stable Version: v1.5.1
Stable Release Date: 2017-08-02
Created 2016-07-23
Last Updated 2017-08-02
Reserved
I supposed you tested this with Pokemon GO, as is the reason of so many requests for a virtual gyroscope so I'll suppose is still nor working due my specific device.
Motorola Moto X Play, running CyanogenMod 13.
Thanks for your work!
Thanks for chance to get normal VR experience
Works great with Lenovo Vibe P1 (this device has a jittering problem with its own pseudo-gyro). Tested with Youtube 360 videos. Works great for watching up/down and rotate. As well as you said z-axis is not working at all, so it's impossible to move point of view to the left/right. Can help you with testing on my device, if you want. I have Lenovo Vibe P1 with Android 6.0, TWRP and Root.
P.S. Is there any way to turn on z-axis for testing, for example by using your project at github. I'm not sure if I will understand there something, I was coding before only at C#, but I can try.
OliverG96 said:
I supposed you tested this with Pokemon GO, as is the reason of so many requests for a virtual gyroscope so I'll suppose is still nor working due my specific device.
Motorola Moto X Play, running CyanogenMod 13.
Thanks for your work!
Click to expand...
Click to collapse
I did not test it with Pokémon GO, however I think the hook will have to be made in the app itself. I'll look into it right now
EDIT: Pokémon GO uses the TYPE_ROTATION_VECTOR sensor. This sensor requires data from the gyroscope. I'm working right now on emulating it.
Saratsin said:
Works great with Lenovo Vibe P1 (this device has a jittering problem with its own pseudo-gyro). Tested with Youtube 360 videos. Works great for watching up/down and rotate. As well as you said z-axis is not working at all, so it's impossible to move point of view to the left/right. Can help you with testing on my device, if you want. I have Lenovo Vibe P1 with Android 6.0, TWRP and Root.
P.S. Is there any way to turn on z-axis for testing, for example by using your project at github. I'm not sure if I will understand there something, I was coding before only at C#, but I can try.
Click to expand...
Click to collapse
Glad to see that it works ! I could make another build with the Z axis activated but I really need to look a bit more into it. The problem with it is that it seemed to return higher values than the other axes. This generally broke the calibration many apps do and though the z-axis worked, they would then ignore the small variations of the other axes.
In case you want to build it yourself, it's quite easy, just remove the multiplication by zero here : https://github.com/Frazew/VirtualSensor/blob/master/app/src/main/java/fr/frazew/virtualgyroscope/XposedMod.java#L156
Can't install it on Jelly bean 4.2.2 :/
first a big THANKS!!!!!
I downloaded sensors tests app.before the module,gyroscope test wasn't there!after the module,voilla!!gyroscope test was there!I openned it and tested side by side with my xperia Z3 tablet.But values was muuuch different...It's ok,we all hope for possible future module updates!again THANK YOU!!!
Dant3s said:
Can't install it on Jelly bean 4.2.2 :/
Click to expand...
Click to collapse
Right now the minimum SDK version is KitKat, that's just because the sensor methods are different on Jelly Bean and I haven't worked on it.
Now that there are people who can actually test it on Jelly Bean I'll make an update to add support for it
Frazew said:
Right now the minimum SDK version is KitKat, that's just because the sensor methods are different on Jelly Bean and I haven't worked on it.
Now that there are people who can actually test it on Jelly Bean I'll make an update to add support for it
Click to expand...
Click to collapse
Glad to hear that, thanks
have see this thread : Help module to simulate Gyroscope with Accelerometer and Compass by nicolobos77
Hey, since we've doubled same purpose module I decided to use yours since its clear that you have much more experience than me and your code is much more elegant. (I never used Xposed before)
I built and ran it on my phone, and noticed exception thrown in logs (made pull request with fix at github), this wasnt big deal, but it seems like even though math is correct, sensor behaves wierd. Output is delayed by ~1 sec. There is also wierd "bounce effect" after rotating at ~20degree/sec and stopping velocity goes to ~-20 degree for a moment and drops back to 0.
Also depending on delay set up by application when registering listener some of apps only seem to get any output other than 0 if I like swing phone very hard. So my guess is that you might have more sensitive sensors in your phone and smoothing methods you applied are overkill for mine. I'll look into it closer later today, or tomorrow and see if changing parameters helps.
Thanks you for your work. One question, my phone has this, link to the image: imgur.com/a/lD7Sg Accelerometer it's fine but compass and orientation sensor are the same thing?. I cant find an app that can show me if I have compass sensor. Thanks you again and sorry for my bad english :/
And can you make a guide like "How to Install or what do you need in order to" or something like that? Please?
Maveroik said:
Thanks you for your work. One question, my phone has this, link to the image: imgur.com/a/lD7Sg Accelerometer it's fine but compass and orientation sensor are the same thing?. I cant find an app that can show me if I have compass sensor. Thanks you again and sorry for my bad english :/
And can you make a guide like "How to Install or what do you need in order to" or something like that? Please?
Click to expand...
Click to collapse
Compass means Magnetic Sensor, so yes, you do have one.
Frazew said:
EDIT: Pokémon GO uses the TYPE_ROTATION_VECTOR sensor. This sensor requires data from the gyroscope. I'm working right now on emulating it.
Click to expand...
Click to collapse
I did some reverse engineering on that matter, Pogo uses whole bunch of sensors: TYPE_GRAVITY, TYPE_GYROSCOPE, TYPE_ACCELEROMETER, TYPE_MAGNETIC_FIELD, TYPE_ROTATION_VECTOR and TYPE_LINEAR_ACCELERATION.
Actually I believe that TYPE_ROTATION_VECTOR can be simulated by copying TYPE_GEOMAGNETIC_ROTATION_VECTOR values.
Mourdraug said:
Hey, since we've doubled same purpose module I decided to use yours since its clear that you have much more experience than me and your code is much more elegant. (I never used Xposed before)
I built and ran it on my phone, and noticed exception thrown in logs (made pull request with fix at github), this wasnt big deal, but it seems like even though math is correct, sensor behaves wierd. Output is delayed by ~1 sec. There is also wierd "bounce effect" after rotating at ~20degree/sec and stopping velocity goes to ~-20 degree for a moment and drops back to 0.
Also depending on delay set up by application when registering listener some of apps only seem to get any output other than 0 if I like swing phone very hard. So my guess is that you might have more sensitive sensors in your phone and smoothing methods you applied are overkill for mine. I'll look into it closer later today, or tomorrow and see if changing parameters helps.
Click to expand...
Click to collapse
Thanks for your, I didn't see this exception when I tested it, but now that you bring it up, it seems obvious.
As for the delay you are talking about, the explanation I have for this is that I filter the output using a mean filter that uses the 10 previous values. This has the advantage of reducing the jitter a lot but it also has the huge disadvantage of adding a lot of delay. I will change this as there are better ways to filter the output than using the mean of the previous values. Like I said, I only tested it with my phone and did not take into account the sensitivity of the sensors. This is actually a good idea and I'll have to change that. Feel free to tweak what you want and make pull requests, that's the best way this module can evolve.
Mourdraug said:
I did some reverse engineering on that matter, Pogo uses whole bunch of sensors: TYPE_GRAVITY, TYPE_GYROSCOPE, TYPE_ACCELEROMETER, TYPE_MAGNETIC_FIELD, TYPE_ROTATION_VECTOR and TYPE_LINEAR_ACCELERATION.
Actually I believe that TYPE_ROTATION_VECTOR can be simulated by copying TYPE_GEOMAGNETIC_ROTATION_VECTOR values.
Click to expand...
Click to collapse
I reverse engineered it too and saw these sensors too. The thing is: TYPE_GRAVITY is a virtual sensor created from the accelerometer so no need to simulate it. TYPE_MAGNETIC_FIELD is the compass and TYPE_LINEAR_ACCELERATION is also a virtual sensor created from the accelerometer so no need to simulate it either. I have right now working code to make the TYPE_ROTATION_VECTOR work. I didn't see the TYPE_GEOMAGNETIC_ROTATION_VECTOR so I did the math directly from the rotation matrix values. I guess I'll change to use its values since it's already there, thanks for your help
EDIT: Actually the TYPE_GRAVITY is not a virtual sensor. My bad, I'll see what I can do to simulate it.
EDIT2: Actually TYPE_LINEAR_ACCELERATION is not always present either, I'll simulate it too. I should verify a bit more before posting stuff.
I would donate some cash if you could get the AR function to work in PoGo! That would be awesome!
wktra said:
I would donate some cash if you could get the AR function to work in PoGo! That would be awesome!
Click to expand...
Click to collapse
No need for cash but I'm currently working on it. I implemented a whole new lot of sensors but sadly PoGo doesn't work with them just yet. I'm investigating this and will make an update once it's ready (I play PoGo too so I'd like to see it work too).
Hi , I just registered to thank you a lot for the effort you're doing.
It doesn's seems to work on my LG G3 S, however thank you a lot and hope someone can help you making it through !
Keep the good work.
Dont work on youtube or pokemon Go in motorola moto g 2015(xt1541). Also i installed Cpu Z and it show the virtual gyro sensor ... I dont know why dont work on 360 video on youtube.(sorry for bad english)