Related
mattc's EvoLeo v1.0
Note: 1.0.1 is the same as 1.0 except using older kernel to prevent blue screens and other startup issues.
This is a brand new build. I have based it on the official HTC EVO rom and tweaked it for the HD2. The rootfs will create a 1GB data image.
The EVO base is friendlier to the non-trackball phones.
Important note: after booting Haret you will notice strange lines on the screen. This is normal, be patient and it will boot. Also, you will probably need to manually enter your APN information for MMS/Mobile Data to work.
Instructions on APN settings:
1. Settings > Wireless & Networks > Mobile Networks > Access Point Names
2. Push 'Windows' button, choose 'New APN'
3. Enter all relevant information for your specific provider, you can likely google it.
4. When everything is entered, push 'Windows' key again, then 'Save'.
5. Push on the radius button next to the new APN you created, it should turn green.
What's Added that you won't get in my other build:
EVO keyboard with directional buttons
Proper HTC camera interface with working previews
Additional downloadable sense Widgets are working
Ringtones, notifications, etc. work without additional media folder (no more ringtones with your music!!)
What is working:
Louder sound over speakerphone and headset
Very stable and fast internet over PPP. Hard freezes are completely eliminated
Light sensor
Touchscreen/Gsensor Freezes Eliminated
Bluetooth Streaming Media/Phone
Wifi
Wifi/USB tethering
USB transfers
EDGE/3G/HSDPA Internet
Camera (flash is buggy)
Standard Definition Camcorder w/flash
LED Keypad Lights and Charging Indicator
No more green line in HQ YouTube
All other items working on other builds, too many to list
Known Issues:
The camera flash is premature causing dark photos in low light
You may need to enter a manual DNS address when using WIFI tethering
There are menu items for 4G. The hardware doesn't support 4G, they will fail.
Notification led is flaky, works at times, not at others. Don't rely on it.
Tips:
Use SetCPU for better battery life.
Turn off live wallpaper for better performance and battery life.
I have included a Task Manager. Learn to use it religiously to improve battery life.
Other Notes:
CPU scaling is enable by default without SetCPU. This kernel cannot be overclocked.
I have included Astro File Manager as well as a Task Killer.
Installation Instructions:
Unzip the contents to your SD card. All of the files should extract into a folder named "Android".
Use an autoloader or, in Windows Mobile, browse to the Android folder on your SD card and run CLRCAD.exe, then Haret.exe.
Let Android boot. The first boot is always the longest and larger data sizes require longer times.
Enjoy Android.
DOWNLOADS: http://www.multiupload.com/2OG2HRRB8S
V1.0.1
If you don't have any ringtones or notifications, download this: http://www.megaupload.com/?d=ZZBUXPK2
Unzip it into your Android folder.
Kernel Sources (note: nothing below is required for you to run Android. Everything listed here is already included in the download).
The latest kernels and modules can always be found here: http://oe.netripper.com/files/htcleo_autobuild_evo_tree/
The autobuild dated 20.9 was used in this build.
Thanks to all of the devs working on kernel - Cotulla, dcordes, gauner1986, markinus, ElBartoME, etc. Also, thanks to Darkstone, Cass, and many others for their great support.
Also, thanks to all the folks on #htc-linux and #htc-linux-chat!
As always, donations are appreciated but not required.
Reserved for change log...
Thanks for ur effort, downloading now!
and time to get a new rom =)
Awesome!!!
Can't wait to try this!!
Thanks, trying this build out and will report back
been waiting for this for 20 days thanks man, you rock!
Iguess I'm the first to download and comment.luv your work
Sent from my Desire HD using XDA App
thx u i think ur bulid is stablest
edit 21.9.10
Quadrant score - 1350 after few tweaks
stablest i ever see so far
battery - 1.5%ph screen off [4 hours test] setcpu profile
very responsive no lags [ changing between apps + load cpu nothing stop it ]
thank you will try when get home. Finally Light Sensor <--have been waited for long time.
dlding hope it works as good as hd build... or better
Thanks a lot... downloading now!
Touchscreen/Gsensor Freezes Eliminated
Click to expand...
Click to collapse
I require a dose of this instantly, just for that 1 point alone
Thank you very much for you efforts
Battery
Is there Extended battery support. Didn't say there was so assuming no.
And if I use michy R11 will I lose other features?
BTW MattC has alot of manfection friends around here. Great Builds!
Jwatt0918 said:
Is there Extended battery support. Didn't say there was so assuming no.
And if I use michy R11 will I lose other features?
BTW MattC has alot of manfection friends around here. Great Builds!
Click to expand...
Click to collapse
The kernel is from GIT so no ext batteries. Michy's EVO kernel should work, not sure about the Desire kernel though.
Thank you so much.I'll trying your build out this week and response result.
Thanks again your hard working.
Forgot to note, you will need to enter APN info manually for MMS/Mobile data to work. Sorry for the inconvenience
getting a blue screen on boot up, is this normal for the build?
you said
"You may need to enter a manual DNS address when using WIFI tethering"
Where do you enter this DNS? and what dns numbers to put in?
caliente said:
getting a blue screen on boot up, is this normal for the build?
Click to expand...
Click to collapse
Oh yeah, it is. Keep trying, it will boot.
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.
Similar to my TWRP / Multirom thread, this is temporary until xda decides to add this device to the dev db list. A few comments and a known issues list will be all in this post. Please report any and all problems you find. This is still very early in the development process.
NOTES:
This will only install using my TWRP build here because I'm have to do some hacky things to support a unified build. I may eventually find a cleaner method.
This doesn't yet contain my attempt at controller pairing. The framework patches are there, but not the apk. It will be tested and included in later builds. Wifi doesn't work, so pairing wouldn't work anyways.
I had to use aosp libs to make this boot, which is different from my Portable and Tablet releases. The hdcp libs seems to be very different, so I have no idea if 4k works at all and I seriously doubt youtube and netflix drm will verify correctly.
You will have to wipe data to install this, make a backup first. Do note this is just /data, not the entire internal sd.
KNOWN ISSUES:
Wireless controller pairing not implemented
No audio over hdmi (so, no audio at all)
SOURCE:
device
kernel
vendor
CURRENT RELEASE:
cm-13.0-20160224-UNOFFICIAL-foster.zip
OLD RELEASES:
cm-12.1-20150819-UNOFFICIAL-foster.zip
cm-12.1-20150720-UNOFFICIAL-foster.zip
cm-12.1-20150709-UNOFFICIAL-foster.zip
missing default android keyboard?
installs fine boots into CM - displaying in 1080p on my monitor just fine.
missing android keyboard.
works fine with usb keyboard (logitech k400r)
amazon app store installs fine, recognizes all apps - minecraft PE crashes on start
touch pad / mouse freezes intermittently
netflix installs but does not play
great start, looking good.
I'm finding all kinds of interesting things working on this... Well, I got the stock libs 'working'. HDCP (or something in the graphics stack) locks up the system on boot when using a custom built kernel. From within CM or even from Nvidia's aosp tree. It will only boot with the kernel pulled out of an official boot image. I compared the ikconfig out of the official kernel with what I'm building in CM and they match. So, I'm kinda lost as to what black magic is at work here... Is something doing a crc check? Is there black box GPL violations in the stock kernel? I don't know. And I had a custom kernel booting stock when I was first trying multirom stuff. So that makes me *really* confused. For the moment, I've disabled kernel compiles in my device tree and I'm shipping a blob kernel. And I hate doing that.
Haven't looked at the missing keyboard yet.
Wifi is closer, but still not there. The wlan0 interface seems to init, but the p2p interface fails and brings it immediately back down. I'll do some more research into that over the weekend.
The screen flickers at times. Don't know why, but I think I saw some system props that affects the screen drawing on stock, once I find those again I should be able to fix that.
The OMX libs work now. Which means game streaming works. I tested a grid game already. Don't have Windows, so I can't test local streaming. And theoretically the aforementioned Netflix problem should be fixed by this as well.
I'm kicking off a build to run overnight (takes 4+ hours for a clean release build [on a AMD FX 9370, no less]), so I should have this stuff up first thing tomorrow morning (pending life (r)).
Edit: And... build failed. Starting over... So, looking at this afternoon now.
Edit 2: Well... I can make it boot when I tinker with it manually, but I'm not having much luck making a reproducible build from source. So... I'll have a release eventually, but with 4 hour rebuilds, I can't say when at this rate.
Steel01 said:
Similar to my TWRP / Multirom thread, this is temporary until xda decides to add this device to the dev db list. A few comments and a known issues list will be all in this post. Please report any and all problems you find. This is still very early in the development process.
NOTES:
This will only install using my TWRP build here because I'm have to do some hacky things to support a unified build. I may eventually find a cleaner method.
This doesn't yet contain my attempt at controller pairing. The framework patches are there, but not the apk. It will be tested and included in later builds. Wifi doesn't work, so pairing wouldn't work anyways.
I had to use aosp libs to make this boot, which is different from my Portable and Tablet releases. The hdcp libs seems to be very different, so I have no idea if 4k works at all and I seriously doubt youtube and netflix drm will verify correctly.
You will have to wipe data to install this, make a backup first. Do note this is just /data, not the entire internal sd.
KNOWN ISSUES:
Wifi doesn't enable. (ethernet works fine, though)
Keyboard not installed
SOURCE:
device
kernel
vendor
CURRENT RELEASE:
cm-12.1-20150709-UNOFFICIAL-foster.zip
Click to expand...
Click to collapse
screenshots ?
Glad to see ATV gettin some action ... ooooo hel I'm excited. I've been fastbooting your twrp img. for a few things and its working quite nicely on my pro model. BIG BIG thanks for that @Steel01 Does it look like there will be any issues reguarding which version console its running?
@aniel300: Screenshots? It's Cyanogenmod. The same Cyanogenmod as on any other device...
@ElwOOd_CbGp: Like mentioned in the OP, I do a hacky thing or two to support unified builds. It have the pro version myself, so that's what I test on. I'm pretty sure it will work with no extra problems on the 16 GB model, however.
Alright, I *think* I finally ironed my build problems (all related to using a prebuilt kernel... got to figure out a way to not have to do that), so theoretically I'll have a build out tomorrow. Probably won't be able to test much until the afternoon, so I doubt it'll be out bright and early.
yey! please keep going! AOSP + Kodi + Support for official remotes would be awesome!
Steel01 said:
@aniel300: Screenshots? It's Cyanogenmod. The same Cyanogenmod as on any other device...
@ElwOOd_CbGp: Like mentioned in the OP, I do a hacky thing or two to support unified builds. It have the pro version myself, so that's what I test on. I'm pretty sure it will work with no extra problems on the 16 GB model, however.
Alright, I *think* I finally ironed my build problems (all related to using a prebuilt kernel... got to figure out a way to not have to do that), so theoretically I'll have a build out tomorrow. Probably won't be able to test much until the afternoon, so I doubt it'll be out bright and early.
Click to expand...
Click to collapse
is it a hybrid rom ?
@[email protected]: Kodi is of great interest to me as well, so I'll work to make sure works well.
@aniel300: No, it's pure CM. I plan to make the TV stuff accessible, but it won't be there by default.
I finally got a bootable build, but it does show more problems. The launcher and some programs lag terribly. Not locking up, but slow enough to trigger ANRs. Netflix does still crash when loading a video, hopefully that won't be hard to fix once I can read the logs. The interface still flickers, but only the interface, not videos or games or such. I'll do some more testing this afternoon and unless an even worse problem shows up, I'll release.
New build is up. It appears the netflix bug affects others things too, like youtube. Appears to be audio related, but I don't have time right away to try and track down the root cause. So, consider this another bug hunting build and not truly usable.
I've fixed an audio problem, so sound and YouTube and all that works again. Netflix is still confusing me a bit, though. It appears to be a problem with the OMX libs, but not one seen on any other Shield device. Haven't spent too much time looking the last few days.
I'm in the process of restructuring the build setup on my dev machine. Like moving the build trees to a faster spinny disk and ccache to a ssd. That should get builds going a lot faster. 4 hours per build gets old real fast. And 45 minutes for a one package change. I plan to release a new build once I get that all sorted out.
what about you try to port android m tv developer preview instead or at least cm but with all the good stuff from android tv.
It seems Forge has unlockable bootloader they posted instructions also for home images so it's a start it should be easy to flash recovery if there was one. Sorry for going little off topic but this seems more active here
New build up. Seems the OMX libs are only partially working. Youtube works, but mxplayer and kodi fall back to their software decoders. Wireless appears to finally work, but logcat messages lead me to believe it's still not completely there. Oh, and the UI flickering is still there.
So, I loaded this build up and promptly installed HALauncher and Kodi. With the controller wired in, this seems to be a pretty usable setup. As things begin to stabalize, I'll probably start to recommend that launcher as a replacement for leanback. Now if only I can find a replacement for the leanback keyboard, I won't have to include any Google blobs... Suggestions are welcome for a free and preferably open source dpad enabled keyboard.
Really good progress tonight. Barring something patentably bad happening, I should be releasing a new build tomorrow. List of progress:
1. Interface flickering is way down. Don't know if it was something I did or if upstream CM tweaked stuff. Either way, it's bearable now. I only notice it on some transitions, whereas before it was all the time on builtin android interface stuff.
2. OMX libs work. Hardware accelerated video and movies, plus game streaming and grid works now.
3. Leanback IME (controller enabled keyboard) is part of the build. It's smaller than on stock, but still usable.
Some things still need work, though:
1. Netflix still fails to play a video. At least it doesn't crash to desktop anymore...
2. Wireless controller pairing fails. The app runs and it tries to set stuff up, but seems to hit the same problem the Portable does most times. I have got the Portable to pair once or twice, though, so some people might be more lucky than me and it'll actually work.
All in all, this looks like a very usable test build, if not a daily driver for some use cases.
Hi steel01
I am planning to buy this device, pro version, but its true that the SSD storage drive has some problems about performance and response, speed, looking all around for a good review about this and nothing found yet,unbelievable, I want to be sure the 16 GB or pro version.
Counting on you,like you doing on the shield tablet,interesting approach with CM,look forward, when I get it I will install the Zulu99 full android ROM first and them....cm
Good luck on this, thank for you hard work
I haven't had any lag problem with the Pro edition, but I also haven't done anything IO intensive. So, I'm not really a good yardstick for that. However, the pro edition does have the 16GB hardware, just needs some tweaking to be able to access it. Probably could do some boot image trickery to get /system on that device. Haven't looked at that yet since CM and multirom are higher priority in that order.
Other stuff came up today, so I didn't get to test the new build. As soon as I drag it back across the house to reflash it, I'll verify the build and upload. Maybe tomorrow afternoon.
I am just a thinker, its possible to use all the best feature of CM and put it in android tv or viceversa.
I dont own yet a android tv device, but is like no to manny peoples like it, may restrictions from google, its entirely new or old UI, developers needs to port their apps to android tv platform, maybe we like the custom launcher or just the regular launcher, well its until everybodys decision.
Multirom sound good, but i like the basic and fast, what about if we can have two launcher in the GUI or UI, can be possible, there is a really need an apps to be ported to android tv platform, why google put restriction, we can sideload to get what we want, i think this is confusing android OS is android.
I think the best thing to do its going back to the basic.
Well, I didn't get to testing today either. I think I'll run another build tonight and try to get to a test tomorrow night.
@duanim: That is my end goal for my device. The Shield TV running CM with a 10 foot launcher (that isn't leanback) and everything accessible from the controller. The current build isn't too bad for that, but not all the way there. CM and HALauncher works pretty well. But the controller still needs help wirelessly.
There's one major problem with running android and android tv simultaneously. It seems the play stores are different. You either get the TV apps or the normal apps, not both. If someone knows different or a way to work around this, I'd love to hear it.
Still can't get the dumb wireless controller libs to package the way I want. So the latest build is missing some, causing the app to continuously force close, making the build unusable. I'll split it like I didn't want to and should have a releasable build tomorrow.
EDIT: Please direct any development questions, queries, etc. to the new thread in the Development Forum, concerning all development-y things.
http://forum.xda-developers.com/grand-prime/development/unofficial-cyanogenmod-12-1-g530w-t3424761
============================================================
I've recently started working on a custom ROM for the Samsung Grand Prime G530W [gprimeltevl/gprimeltecan], and so far I have built a somewhat working ROM (without any radio/wireless capability or audio for now).
If there is interest in this project (which I think there is; the lack of any kind of love shown for the G530W is annoying), I'll continue hacking away at it until I (hopefully) have a working ROM.
I'm new to Android ROM building in general, and there have been several bumps along the way, so any help would be appreciated.
Thanks.
I will be uploading images daily to my Drive storage, in folders named by date (if the date today is not there, then the image had not been built or uploaded yet), and will be compressing the system.tar images with either gzip or xz to reduce the image size.
I will also be updating this area with issues and fixes as necessary.
What I have managed to get working so far (23/07/2016)
Limited mobile connectivity [ sending/receiving texts ].
- Calls can be received or made but there is no audio (speaker or microphone).
- Mobile data is not working.
- Currently the system does not show the mobile connection as active, but texts can still be sent and received.
Bluetooth is working
Audio is working (microphone, speaker)
Multimedia playback working
GPS is working
Wifi is working
Screen brightness controls working
Sensors are working (magnetic, rotation/gyro,proximity)
App installation is now working
Camera is kinda working - only back camera works, and the image is distorted.
Issues
Radio [ modem ] is not working properly
NFC is not working
MTP is not working
Cameras are not working
Here is a link to the system.tar, boot.tar and recovery.tar flashable by ODIN or fastboot (when unpacked).
https://drive.google.com/open?id=0B-bYwctD_MoDaWJGcUQ4eWtzRTQ
Project GitHub Repositories:
https://github.com/vince2678/android_device_samsung_gprimeltecan
https://github.com/vince2678/android_vendor_samsung_gprimeltecan
If there are any other issues I missed, let me know.
Great effort
vince2678 said:
I managed to compile and get an image working for the G530W.
What I have managed to get working so far
Bluetooth is working
Audio is working (microphone, speaker)
Multimedia playback working
GPS is working
Sensors are working (magnetic, rotation/gyro,proximity)
Issues
Device fails to unlock and heats up [only once, so far]
Wifi is not working
Radio [ modem ] is not working
User interface crashes periodically
Screen brightness controls not working
MTP is not working
Cameras are not working
Here is a link to the system.tar, boot.tar and recovery.tar flashable by ODIN or fastboot (when unpacked).
https://drive.google.com/folderview?id=0B-bYwctD_MoDVzd0eS1aaDV6RW8&usp=sharing
I'll be working at it to get at least the Wifi working, if there are any other issues I missed, let me know.
Click to expand...
Click to collapse
Good work so far!
I recently purchased a g530w and I would love to boot the stock ROM.
However, I am still busy researching and reading up on this device before I attempt to flash anything. Actually, I did create an update zip file to remove Skype and tried applying it while not rooted but it failed because it was not properly signed.
Anyway, I will watch your progress with keen interest!
Zippy Dufus said:
Good work so far!
I recently purchased a g530w and I would love to boot the stock ROM.
However, I am still busy researching and reading up on this device before I attempt to flash anything. Actually, I did create an update zip file to remove Skype and tried applying it while not rooted but it failed because it was not properly signed.
Anyway, I will watch your progress with keen interest!
Click to expand...
Click to collapse
Sounds interesting. Did you try rooting your phone and using Link2SSD to remove the app(s)? It works pretty well, and you don't have to go through the whole effort of packing and unpacking the ROM.
vince2678 said:
Sounds interesting. Did you try rooting your phone and using Link2SSD to remove the app(s)? It works pretty well, and you don't have to go through the whole effort of packing and unpacking the ROM.
Click to expand...
Click to collapse
Here's my plan for my new phone:
Reading and research (in progress)
Setting up Odin on a virtual machine (I am a Linux user) and testing a restore of the stock ROM. Do you have a good link to such a ROM? I briefly looked at http://www.sammobile.com/firmwares/ and this site looks a little sketchy to me.
Root the device. I believe the method described in this G530T thread has worked for our G530W.
Debloat the crapware. Surprisingly, there is not all that much on the device - mostly some Micro$oft crap, Skype, and an old, old version of Chrome which I cannot uninstall. As root, I'll just go in and delete the unwanted stuff from /system/app using a terminal emulator.
Once it get this far, I can probably live with stock Lollipop. Question, if you are learning how to port a ROM, have you considered starting with Marshmallow? I'm keen to move up.
Build the ROM myself and then attempt to build it with my Linaro toolchain which I built from scratch myself.
Questions, with what you know so far, will the G530H ROM in this thread work on our phone? Is this what you started from? What differences between the 2 devices what preclude it from working on ours - different hardware? software - i.e. different bootloader?, etc?
Zippy Dufus said:
Here's my plan for my new phone:
Reading and research (in progress)
Setting up Odin on a virtual machine (I am a Linux user) and testing a restore of the stock ROM. Do you have a good link to such a ROM? I briefly looked at http://www.sammobile.com/firmwares/ and this site looks a little sketchy to me.
Root the device. I believe the method described in this G530T thread has worked for our G530W.
Debloat the crapware. Surprisingly, there is not all that much on the device - mostly some Micro$oft crap, Skype, and an old, old version of Chrome which I cannot uninstall. As root, I'll just go in and delete the unwanted stuff from /system/app using a terminal emulator.
Once it get this far, I can probably live with stock Lollipop. Question, if you are learning how to port a ROM, have you considered starting with Marshmallow? I'm keen to move up.
Build the ROM myself and then attempt to build it with my Linaro toolchain which I built from scratch myself.
Questions, with what you know so far, will the G530H ROM in this thread work on our phone? Is this what you started from? What differences between the 2 devices what preclude it from working on ours - different hardware? software - i.e. different bootloader?, etc?
Click to expand...
Click to collapse
Hey Zippy,
That sounds like a good idea.
That website does seem kinda sketchy, and their downloads take millenia, but it's the only option available and their images actually work (just make sure to get the correct one).
Setting up a virtual machine is a good idea, because heimdall doesn't work with this device and I'm not keen on bricking my device trying to force it.
Rebooting between builds to test firmwares because of a lack of a good recovery was becoming a pain. (CyanogenMod Recovery is still missing critical features but it's better than stock).
You can use CF-Auto-Root to root the device (so simple) at:
https://download.chainfire.eu/774/C...uto-Root-gprimeltecan-gprimeltevl-smg530w.zip
Yup, debloating is good, i wanted to do so at first but I wanted to be done away with KNOX and have an su binary which worked flawlessly for good so I decided to start from scratch.
I've considered starting from M, but that will be a task for later. It is troublesome to start from a fimware above what your device is at when you're porting, because the vendor libraries and binaries you copy might not work in the newer version of Android because of linking errors.
You can copy the binaries fine but obscure errors due to missing references will pop up in the logs which will stop the modules from loading or binaries from running.
I'm having these issues with a build ID that is just a few apart from the one used on the stock ROM - LMY49J on the cm build versus LMY47X on the stock).
My Git repos are above - you can get yourself a cm12.1 source tree, pull my device_ and vendor_ trees, pull proprietary files using the scripts in the vendor tree, build from source and then flash the resultant images to your device.
The G530H ROM might, in theory flash without issue and actually boot, but whether it will be usable is another thing.
The thing that differs between the devices, as far as I'm aware, is mostly the baseband, some other device hardware (e.g the G530W has 1.5GB RAM instead of 1GB as most G530 devices), and the device bootloader. As such, the kernels and modules used might differ slightly in terms of modules compiled in, even though they're built from the same kernel source.
And yes, indeed, I started from a G530 device and vendor tree, though whether it was that one, or perhaps one for the G530FZ, I don't remember (though I think it's the G530FZ, it's the device closest to the G530W).
Finally something for this variant, I've been waiting for ages. Huge thumbs up dude, from a thankful Canadian. I don't use this phone as my daily driver so I'll be flashing this without delay. Mind if I trouble you for the order of operations? I've never used Odin to flash a custom ROM before.
Some more questions ...
Hi again @vince2678, I have more questions:
Do you have a local_manifest.xml that drives your build? ... I have a single-purpose Fedora24 virtual machine which I use to build android ROMs.
Does your build actually produce a CM12.1 zip installation package? ... And do you simply harvest the system.img, etc afterwards to put into a flashable this tar file?
What is the command line that do you use to create the flashable tar files? ... I'm just curious.
What version of the firmware does your device have? ... Mine has G530WVLU1AOFB. Apparently, this is the Tanzanian version! WTF? I purchased my phone from a Costco in Oakville, Ontario, Canada. It was purported to be unlocked for all Canadian carriers. My carrier is Virgin Mobile (owned by Bell) and it works fine. But, my understanding is that device actually locks to your SIM card upon first use so you can't use it for other SIM cards, but I haven't proven this yet. BTW, I got over half of the stock ROM DL'ed from SamMobile before it stopped due to a "network error". Yeah right! I'll try again later.
Have you (or are you) cherry-picking patches from the G530H CM12.1 ROM? ... android_device_samsung_fortuna3g I suggest DL'ing their key files and comparing them to yours. They appear to be in the final exhilarating phase of perfecting their ROM.
So you have totally removed the KNOX software without in deleterious consequences? ... I thought that I read in an XDA thread where somebody did this and then had issues such as connecting to WIFI, etc. It appeared that there may be a dependency in the BIOS.
Did you trip the KNOX e-fuse hence void the warranty? ... Not that I care about the warranty, I only worry about bricking the device.
Unlike @Pbotelho, this is my daily driver so I will be proceeding slowly and cautiously and look forward to his experience flashing it.
Pbotelho said:
Finally something for this variant, I've been waiting for ages. Huge thumbs up dude, from a thankful Canadian. I don't use this phone as my daily driver so I'll be flashing this without delay. Mind if I trouble you for the order of operations? I've never used Odin to flash a custom ROM before.
Click to expand...
Click to collapse
Hi Pbotelho, thanks man. You will have to enable Developer Mode on your phone and unlock the bootloader from the settings. I don't remember what exactly in the settings that option is, but it should be in the Debugging area for sure.
Once done, reboot into Download Mode [Press Power+Volume Down+Home].
Once you've done that, grab the boot.tar, system.tar.xz and recovery.tar from the links above. Extract the system.tar.xz with 7zip or `xz -d system.tar.xz` if under Linux to get a system.tar file, and flash the recovery, boot, and system, one after the other, in whatever order, by booting into download mode as soon as it is done flashing a file.
You will need to wipe your cache and data partitions, which can be done by rebooting into recovery [Power+Volume Up+Home].
The button options are built into the hardware so they can be used at any point after the phone is on.
When all that is done, you can report any problems here [or on the github page] and post logcats and I'll look at them if there's any issue I've missed.
Zippy Dufus said:
Hi again @vince2678, I have more questions:
Do you have a local_manifest.xml that drives your build? ... I have a single-purpose Fedora24 virtual machine which I use to build android ROMs.
Does your build actually produce a CM12.1 zip installation package? ... And do you simply harvest the system.img, etc afterwards to put into a flashable this tar file?
What is the command line that do you use to create the flashable tar files? ... I'm just curious.
What version of the firmware does your device have? ... Mine has G530WVLU1AOFB. Apparently, this is the Tanzanian version! WTF? I purchased my phone from a Costco in Oakville, Ontario, Canada. It was purported to be unlocked for all Canadian carriers. My carrier is Virgin Mobile (owned by Bell) and it works fine. But, my understanding is that device actually locks to your SIM card upon first use so you can't use it for other SIM cards, but I haven't proven this yet. BTW, I got over half of the stock ROM DL'ed from SamMobile before it stopped due to a "network error". Yeah right! I'll try again later.
Have you (or are you) cherry-picking patches from the G530H CM12.1 ROM? ... android_device_samsung_fortuna3g I suggest DL'ing their key files and comparing them to yours. They appear to be in the final exhilarating phase of perfecting their ROM.
So you have totally removed the KNOX software without in deleterious consequences? ... I thought that I read in an XDA thread where somebody did this and then had issues such as connecting to WIFI, etc. It appeared that there may be a dependency in the BIOS.
Did you trip the KNOX e-fuse hence void the warranty? ... Not that I care about the warranty, I only worry about bricking the device.
Unlike @Pbotelho, this is my daily driver so I will be proceeding slowly and cautiously and look forward to his experience flashing it.
Click to expand...
Click to collapse
Hi Zippy,
I do not have a local_manifest, if you want you can just manually pull the device and vendor trees into your build area, or you can make one yourself if you wish.
I will probably make one though, because the build has dependencies on some qcom sources.
I just use 'make -j8' to build everything, though you can use 'make otapackage' to build a flashable zip [You'll need the CMR recovery from here though, the images can't be flashed by stock recovery]
For creating flashable tar files, you can just use `tar`. You don't need to make .md5 verifiable archives, those are just to ensure a download wasn't corrupted [I provide md5sums for checking].
The system.img in the output directory will have to be renamed to 'system.img.ext4' and then archived, as so:
Code:
cd out/target/product/gprimeltecan
ln system.img system.img.ext4
tar cf system.tar system.img.ext4
tar cf boot.tar boot.img
tar cf recovery.tar recovery.img
Then you can move the files wherever and flash them with Odin.
Yes the gprimeltevl/gprimeltecan baseband is indeed G530WVLU1AOFB, though this should work with all G530WXXXXXXXs (not sure how many different ones are out there].
I'm not sure about the SIM locking thing, I cannot confirm this, someone might have to try to check.
I did consider sourcing from that repository, though ultimately i ended up using another one [I don't remember the name]. I might take a look at their source to see what I can do about mine though.
I did trip KNOX, though that was back when I was still trying to root my phone with CF-Root, so I'm not sure if flashing this will trip KNOX. And yes, KNOX is completely gone from this device, with no problems from the phone.
vince2678 said:
Hi Pbotelho, thanks man. You will have to enable Developer Mode on your phone and unlock the bootloader from the settings. I don't remember what exactly in the settings that option is, but it should be in the Debugging area for sure.
Once done, reboot into Download Mode [Press Power+Volume Down+Home].
Once you've done that, grab the boot.tar, system.tar.xz and recovery.tar from the links above. Extract the system.tar.xz with 7zip or `xz -d system.tar.xz` if under Linux to get a system.tar file, and flash the recovery, boot, and system, one after the other, in whatever order, by booting into download mode as soon as it is done flashing a file.
You will need to wipe your cache and data partitions, which can be done by rebooting into recovery [Power+Volume Up+Home].
The button options are built into the hardware so they can be used at any point after the phone is on.
When all that is done, you can report any problems here [or on the github page] and post logcats and I'll look at them if there's any issue I've missed.
Click to expand...
Click to collapse
I got impatient with it so I took a gamble and inferred with some background knowledge. Got it up and running several hours ago. Performance wise, it seems dead on perfect. There's no lag, no force closing of apps. Everything runs as snappy as it should. Its fast as f***. Now I even installed xposed framework and added in a few modules, one of those being the Android N-ify project, and it works really well with it, so kudos on this area. I'll be sure to uninstall xposed when it comes to error reporting and logcats.
The only issues I'm seeing besides the ones you've already outlined are graphical in nature. I'm not home at the moment but I'll upload some logcats when I get the chance.
1) What I'm seeing is a blackout out lock screen. I have a theme installed and used it to apply a custom lock wallpaper to test this out. The wallpaper only shows once you've accessed the Pattern input by swiping up. Haven't tried it with a pin. If you're only using swipe, it'll stay black until unlocked.
2) When unlocked and swiping down to access the notifications panel and quick settings, the same blackout effect is present. This is present only while you're looking at your notifications or tiles, and returns to normal when swiped back up.
3) The first half of this part is only noticed when using the material glass theme. When swiping down to access the notification panel without notifications, the "no notifications" text will be present as it should be, however, when swiped down again to access the quicksettings tiles, the "no notifications" text isn't cleared away. It sits behind the brightness slider. This isn't noticeable on the stock theme because its opaque, while material glass features transparency as their main selling card. If using the battery saver, the text from this persistent notification will appear instead.
Edit: Upon further analysis, it seems that the notification content is linked to the bottom of the header instead of the bottom of the quicksettings tiles, and that's why it works this way. When expanding or shrinking the header, the notification also moves directly with it.
Second half: whether on the stock theme or not, the "no notifications" text will continue to stick and be viewable on the lockscreen, retaining its position that is viewed in the notification panel. It sits directly above the clock. The persistent battery saver notification works the same way. I'm no expert, but I believe that since the notification panel and lockscreen both go to black, that this might be linked in some way.
4) Sometimes when using the stock theme and toggling options in the quick settings tiles, it'll glitch out and turn into what I can only describe as a zombie menu. The pixels of the status bar are replaced by that proportionate area of the quick settings menu, and when swiping down to use the menu, access is disabled (it can't be touched) and it closes itself when attempted. Only way I've been able to fix it was to toggle the theme to material glass and all was restored, still subject to the above three points.
Edit: 5) when using kernel adiutor to try to adjust the CPU frequencies, the only option that comes up for both minimum and maximum is 0MHz. The button seems to work as well, bringing the clock max speed down to 0 for a split second before it reverts to a a maximum of 200MHz. Adjusting the governor after the fact won't restore the maximum, seems only a reboot will get it done. I'm slightly amazed to be honest as before on Touchwiz, it was impossible to get it to hold onto a lower maximum. It would jump all over the place as it pleased.
Edit: 6) The recents hardware button is disabled. Touching it, holding it, nor double tapping brings up a function. It also isn't present in settings when trying to map the button functions. Its the only one that's missing. Power, home, back, and volume are all there.
That's all I got for the moment, I tried to be as descriptive as possible as I won't be able to get the logcats up for awhile. Let me know if you have any questions about what I've said here.
And also, are you taking feature requests?
Pbotelho said:
I got impatient with it so I took a gamble and inferred with some background knowledge. Got it up and running several hours ago. Performance wise, it seems dead on perfect. There's no lag, no force closing of apps. Everything runs as snappy as it should. Its fast as f***. Now I even installed xposed framework and added in a few modules, one of those being the Android N-ify project, and it works really well with it, so kudos on this area. I'll be sure to uninstall xposed when it comes to error reporting and logcats.
The only issues I'm seeing besides the ones you've already outlined are graphical in nature. I'm not home at the moment but I'll upload some logcats when I get the chance.
1) What I'm seeing is a blackout out lock screen. I have a theme installed and used it to apply a custom lock wallpaper to test this out. The wallpaper only shows once you've accessed the Pattern input by swiping up. Haven't tried it with a pin. If you're only using swipe, it'll stay black until unlocked.
2) When unlocked and swiping down to access the notifications panel and quick settings, the same blackout effect is present. This is present only while you're looking at your notifications or tiles, and returns to normal when swiped back up.
3) The first half of this part is only noticed when using the material glass theme. When swiping down to access the notification panel without notifications, the "no notifications" text will be present as it should be, however, when swiped down again to access the quicksettings tiles, the "no notifications" text isn't cleared away. It sits behind the brightness slider. This isn't noticeable on the stock theme because its opaque, while material glass features transparency as their main selling card. If using the battery saver, the text from this persistent notification will appear instead.
Click to expand...
Click to collapse
Hi Pbotelho,
I'll try to answer everything as completely as I can.
The blackout lock screen thing seems to be an issue with Trebuchet. I found that using a different lock screen app solves this issue.
As for the blackout on the notification area, I'm not sure what exactly is causing this, though I think this may be a problem with the cm-12.1 source and not necessarily the device port itself.
Second half: whether on the stock theme or not, the "no notifications" text will continue to stick and be viewable on the lockscreen, retaining its position that is viewed in the notification panel. It sits directly above the clock. The persistent battery saver notification works the same way. I'm no expert, but I believe that since the notification panel and lockscreen both go to black, that this might be linked in some way.
Click to expand...
Click to collapse
This seems to be an issue with Trebuchet again, and using a different lock application fixes this.
Sometimes when using the stock theme and toggling options in the quick settings tiles, it'll glitch out and turn into what I can only describe as a zombie menu. The pixels of the status bar are replaced by that proportionate area of the quick settings menu, and when swiping down to use the menu, access is disabled (it can't be touched) and it closes itself when attempted. Only way I've been able to fix it was to toggle the theme to material glass and all was restored, still subject to the above three points.
Click to expand...
Click to collapse
I'm aware of this one, for now you can fix this by disabling Brightness Control in the settings ( Settings->Status Bar->Brightness Control).
This again might be an issue with the cm-12.1 source, though it'll need some checking to confirm.
Edit: when using kernel adiutor to try to adjust the CPU frequencies, the only option that comes up for both minimum and maximum is 0MHz. The button seems to work as well, bringing the clock max speed down to 0 for a split second before it reverts to a a maximum of 200MHz. Adjusting the governor after the fact won't restore the maximum, seems only a reboot will get it done. I'm slightly amazed to be honest as before on Touchwiz, it was impossible to get it to hold onto a lower maximum. It would jump all over the place as it pleased.
Click to expand...
Click to collapse
I'm using Kernel Adiutor and frequency setting is fine. Did you try using a tunable governor like interactive? That may be the issue.
Edit: 6) The recents hardware button is disabled. Touching it, holding it, nor double tapping brings up a function. It also isn't present in settings when trying to map the button functions. Its the only one that's missing. Power, home, back, and volume are all there.
Click to expand...
Click to collapse
I'm aware of this, you can blame this on my bad arithmetic skills . I had set the wrong bit field mask for the button settings in the device frameworks.
I'll be pushing a fix addressing this shortly.
And also, are you taking feature requests?
Click to expand...
Click to collapse
That depends on what the features are, if they're reasonable and within my capabilities, then yeah .
PS: I would appreciate any help I can get, and if you have any coding skills and time to compile builds, you can help me polish up the device port.
Thanks!
vince2678 said:
Hi Pbotelho,
I'll try to answer everything as completely as I can.
The blackout lock screen thing seems to be an issue with Trebuchet. I found that using a different lock screen app solves this issue.
As for the blackout on the notification area, I'm not sure what exactly is causing this, though I think this may be a problem with the cm-12.1 source and not necessarily the device port itself.
This seems to be an issue with Trebuchet again, and using a different lock application fixes this.
I'm aware of this one, for now you can fix this by disabling Brightness Control in the settings ( Settings->Status Bar->Brightness Control).
This again might be an issue with the cm-12.1 source, though it'll need some checking to confirm.
I'm using Kernel Adiutor and frequency setting is fine. Did you try using a tunable governor like interactive? That may be the issue.
I'm aware of this, you can blame this on my bad arithmetic skills . I had set the wrong bit field mask for the button settings in the device frameworks.
I'll be pushing a fix addressing this shortly.
That depends on what the features are, if they're reasonable and within my capabilities, then yeah .
PS: I would appreciate any help I can get, and if you have any coding skills and time to compile builds, you can help me polish up the device port.
Thanks!
Click to expand...
Click to collapse
1) Aww man I love using Trebuchet, I like to keep my install as small as possible so I'm not one for installing additional apps. I'm a resource junkie though, so its just a matter of personal preference.
2) Again, I'm not an expert, but I suspect it might be the device port. Previously, I've had an unofficial version of CM12.1 installed on a Galaxy Tab 3 as well as a CM12.1 based Pac-rom installed on a Galaxy S4. I'm not sure if this is something those developers corrected on their own or not when building their ROMs, so it could be the source. That's the best of my knowledge on the topic.
3) Will do for the brightness slider, but again, it isn't something I experienced on the other devices with CM12.1 and the sister project.
4) Yeah I played around with the governors and tried all of them. They all list 0MHz as the only option. Maybe its a CPU hotplug issue? I didn't try playing around with those so I'll have to get back to you on that one.
5) Look forward to the update I have a question regarding it though. I'm really familiar with updating custom ROMs through recovery using the zip file format, but this is the first time I'm using Odin to do the job. Will flashing an update with Odin this way cause a factory reset? Or will it update as expected?
6) A couple more graphical hiccups I remembered. The blackout also happens when going to About Phone>Status. In About Phone, the device field says unknown (doesn't bother me, I just don't know if its significant or not), the illumination for the hardware buttons isn't working (I usually keep them off to save battery anyways, but someone out there probably uses it). And finally, when switching recents by holding the home button, only the title bars of the individual apps are viewable. The content of the windows themselves is completely transparent so it looks like a series of floating title bars.
(Apologies if some of these features are already included, I didn't get the opportunity to check, I just think they're awesome)
Feature requests:
1) When phone is off and charging, percentage is displayed inside battery symbol.
2) CPU and GPU undervolting built into the kernel. These custom ROMs are much better than the stock ROM in terms of functionality, but the battery life on the stock Samsung experience is no joke.
3) If possible, more steps for CPU frequency adjustments, every 100MHz or so. I remember the stock ROM had limited options. My S4 is the example I'm going to use here, it has a step for every 108MHz.
4) USB fast charging, aka setting USB to "charge only".
5) Wakelock Blocker. Its built into the latest Resurrection Remix for the S4, not sure if that could be of viable use to you. It'll certainly help out with battery improvements.
6) Boot Manager. Decide which apps get to start at boot. Its built into Marshmallow and an xposed module also exists for this purpose, so really low priority on this one, for me at least.
7) This one is a doozy. Absolutely the one I care most about, but most likely asking for too much. USB tethering. Already exists, I know, but not the way I hope it to. I have an old WRT54G router with DD-WRT installed. My goal is basically this: Phone's network connection>USB Tether>Micro-USB-LAN adapter>WAN port of router. In this sense, the phone would be acting as the modem in a regular home network. I know its possible to do this if the router has a USB port, but mine doesn't, and I also know its possible if you have an intermediate device that bridges the connections for you. Like a laptop, PC, or raspberry pi. Cost efficiency as a student is what I'm working towards though, so this one is a wishlist request.
Ps. The only coding skills I have are from high school's Visual Basic and HTML, truly beginner stuff, and that was about 10 years ago. I'm running Ubuntu on a core i5-2500k with 16GB of RAM and about a terabyte of space though, so compiling is definitely a possibility with some instructions.
Pbotelho said:
5) Look forward to the update I have a question regarding it though. I'm really familiar with updating custom ROMs through recovery using the zip file format, but this is the first time I'm using Odin to do the job. Will flashing an update with Odin this way cause a factory reset? Or will it update as expected?
Click to expand...
Click to collapse
Nope, this should be pretty much the same as flashing a zip from recovery. If you modified the system partition though (like by flashing GApps for example) your changes will be lost.
Pbotelho said:
6) A couple more graphical hiccups I remembered. The blackout also happens when going to About Phone>Status. In About Phone, the device field says unknown (doesn't bother me, I just don't know if its significant or not), the illumination for the hardware buttons isn't working (I usually keep them off to save battery anyways, but someone out there probably uses it). And finally, when switching recents by holding the home button, only the title bars of the individual apps are viewable. The content of the windows themselves is completely transparent so it looks like a series of floating title bars.
Click to expand...
Click to collapse
I fixed this in the device tree, once I've built a new image this should be corrected.
Pbotelho said:
(Apologies if some of these features are already included, I didn't get the opportunity to check, I just think they're awesome)
Feature requests:
1) When phone is off and charging, percentage is displayed inside battery symbol.
Click to expand...
Click to collapse
I'll be looking into this one.
Pbotelho said:
2) CPU and GPU undervolting built into the kernel. These custom ROMs are much better than the stock ROM in terms of functionality, but the battery life on the stock Samsung experience is no joke.
Click to expand...
Click to collapse
I'm still using the stock kernel in my builds, once the builds are stable I'll start compiling the kernel from source and I'll see if I can do something about this.
Pbotelho said:
3) If possible, more steps for CPU frequency adjustments, every 100MHz or so. I remember the stock ROM had limited options. My S4 is the example I'm going to use here, it has a step for every 108MHz.
Click to expand...
Click to collapse
According to the configurations, this is already how it is.
PS: I changed the governor under Kernel Adiutor to performance from interactive and switched back, and became unable to change the frequencies (like you were experiencing). I'll need to play around more with this to see why.
Pbotelho said:
4) USB fast charging, aka setting USB to "charge only".
Click to expand...
Click to collapse
This is already available under the Settings->Storage->USB Computer Connection menu
Pbotelho said:
5) Wakelock Blocker. Its built into the latest Resurrection Remix for the S4, not sure if that could be of viable use to you. It'll certainly help out with battery improvements.
6) Boot Manager. Decide which apps get to start at boot. Its built into Marshmallow and an xposed module also exists for this purpose, so really low priority on this one, for me at least.
Click to expand...
Click to collapse
Not sure I could do this, I'll check.
Pbotelho said:
7) This one is a doozy. Absolutely the one I care most about, but most likely asking for too much. USB tethering. Already exists, I know, but not the way I hope it to. I have an old WRT54G router with DD-WRT installed. My goal is basically this: Phone's network connection>USB Tether>Micro-USB-LAN adapter>WAN port of router. In this sense, the phone would be acting as the modem in a regular home network. I know its possible to do this if the router has a USB port, but mine doesn't, and I also know its possible if you have an intermediate device that bridges the connections for you. Like a laptop, PC, or raspberry pi. Cost efficiency as a student is what I'm working towards though, so this one is a wishlist request.
Click to expand...
Click to collapse
I don't quite understand what you mean by this, how does it differ from the normal USB tethering?
Pbotelho said:
Ps. The only coding skills I have are from high school's Visual Basic and HTML, truly beginner stuff, and that was about 10 years ago. I'm running Ubuntu on a core i5-2500k with 16GB of RAM and about a terabyte of space though, so compiling is definitely a possibility with some instructions.
Click to expand...
Click to collapse
If you can't code, that's fine, you could set up a build environment on your computer for creating images from the source.
vince2678 said:
Nope, this should be pretty much the same as flashing a zip from recovery. If you modified the system partition though (like by flashing GApps for example) your changes will be lost.
I fixed this in the device tree, once I've built a new image this should be corrected.
I'll be looking into this one.
I'm still using the stock kernel in my builds, once the builds are stable I'll start compiling the kernel from source and I'll see if I can do something about this.
According to the configurations, this is already how it is.
PS: I changed the governor under Kernel Adiutor to performance from interactive and switched back, and became unable to change the frequencies (like you were experiencing). I'll need to play around more with this to see why.
This is already available under the Settings->Storage->USB Computer Connection menu
Not sure I could do this, I'll check.
I don't quite understand what you mean by this, how does it differ from the normal USB tethering?
If you can't code, that's fine, you could set up a build environment on your computer for creating images from the source.
Click to expand...
Click to collapse
Sounds awesome, I'll flash it as soon as possible and continue testing it for you.
I uploaded a logcat to the other thread in development. The performance governor is set up as the default for me so I'm set up with that situation from the get go.
It technically isn't different from regular USB tethering, but it seems that no one has done it successfully before. There are adapters that you can use to provide a wired Ethernet connection to an android device over micro USB, but no one has been able to do it the other way around. Google results don't turn up any answers.
And I'm willing to learn how to code, but I fear that I may slow you down with this project as I get past the learning curve. That being said, I can definitely set up a build environment and compile it from source for you. That'll be a learning experience on its own. Just point me towards a noob guide and I'll get it done.
Pbotelho said:
Sounds awesome, I'll flash it as soon as possible and continue testing it for you.
I uploaded a logcat to the other thread in development. The performance governor is set up as the default for me so I'm set up with that situation from the get go.
It technically isn't different from regular USB tethering, but it seems that no one has done it successfully before. There are adapters that you can use to provide a wired Ethernet connection to an android device over micro USB, but no one has been able to do it the other way around. Google results don't turn up any answers.
And I'm willing to learn how to code, but I fear that I may slow you down with this project as I get past the learning curve. That being said, I can definitely set up a build environment and compile it from source for you. That'll be a learning experience on its own. Just point me towards a noob guide and I'll get it done.
Click to expand...
Click to collapse
The USB tethering thing sounds interesting, though I would need to have one of the adapters to test that, and time at hand as well.
As for the build environment, the best source of information is the CM wiki. You can look at these links below on how to get started:
https://wiki.cyanogenmod.org/w/Development#Learning_To_Build_CM
https://wiki.cyanogenmod.org/w/Doc:_Building_Basics
https://docs.omnirom.org/Setting_Up_A_Compile_Environment
https://wiki.cyanogenmod.org/w/Build_for_captivatemtd
http://jira.omnirom.org/browse/OMNI-1263
http://forum.xda-developers.com/showthread.php?t=2329228
The guides above are just outlines to detail the general build process - you will need to do things slightly differently from the steps above to get the proper source and device trees.
The attached local_manifest can be used with repo when obtaining the cm-12.1 source.
Remember you'll be getting the cm-12.1 source - not anything else.
vince2678 said:
The attached local_manifest can be used with repo when obtaining the cm-12.1 source.
Remember you'll be getting the cm-12.1 source - not anything else.
Click to expand...
Click to collapse
So if I add in your device tree and provide a toolchain, I should be good to go? (I think so.)
Thanks!!
EDIT: Not so fast! I'll have to find a kernel as well.
Pbotelho said:
Edit: 5) when using kernel adiutor to try to adjust the CPU frequencies, the only option that comes up for both minimum and maximum is 0MHz. The button seems to work as well, bringing the clock max speed down to 0 for a split second before it reverts to a a maximum of 200MHz. Adjusting the governor after the fact won't restore the maximum, seems only a reboot will get it done. I'm slightly amazed to be honest as before on Touchwiz, it was impossible to get it to hold onto a lower maximum. It would jump all over the place as it pleased.
Click to expand...
Click to collapse
I've test Kernel Adiutor and I too got the O MHz only window for both as the only option. Though Now I wonder if it is because I used the latest beta Kernel Adiutor, I'll further check with the normal stable version. Pretty sure it'll fix it if it worked normally for Vinc. --- Update; As strange as it might look while re opening kernel adi to take a screenshot, the list of normal MHz values is there and working properly.. Strange.. Magic? Huh technology, you're so unpredictable.
Zippy Dufus said:
So if I add in your device tree and provide a toolchain, I should be good to go? (I think so.)
Thanks!!
EDIT: Not so fast! I'll have to find a kernel as well.
Click to expand...
Click to collapse
Hi Zippy,
The kernel source was included there as well (it's just a dummy source so that the build can get the necessary source files for libraries which need them). The build still uses the default prebuilt kernel though.
vince2678 said:
Hi Zippy,
The kernel source was included there as well (it's just a dummy source so that the build can get the necessary source files for libraries which need them). The build still uses the default prebuilt kernel though.
Click to expand...
Click to collapse
As an experiment, why don't you try downloading the G530H ROM, unzip, take the boot.img, and flash it over top of your stock kernel? See if it boots and how it performs.
Meanwhile, I plan to hack at putting together complete manifest, possibly with the G530H kernel and my Linaro 4.9 toolchain and see if I can build a complete ROM.
Have you extracted the firmware?
However, I don't want to flash anything until I see your ROM's modem working because it is my daily driver. But I'm keen though!!
I've managed to download the stock ROM from SamMobile but I'm now thinking of going straight to your ROM once it is a bit more complete and stable.
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)