There is better gapps package for non-neon devices like glide
http://goo.im/devs/tonyp/non-neon-gapps
Full details could be found: http://forum.xda-developers.com/showthread.php?p=39022876&postcount=2
I have made for cm10.1, but it should work with any 4.2 base rom.
Problem:
Glide has tegra 2, witch doesnt support neon instructions, google dropped support non-neon library.
Change
initial:
start with gapps-20130301-signed.zip
replaced:libpatts_engine_jni_api.so, libfacelock_jni.so
removed:libjni_latinime.so
2013.04.22.
Fix google videochat: Add libvideochat_stabilize.so and replace libgtalk_jni.so
Download
Use that: http://goo.im/devs/tonyp/non-neon-gapps Credit for tonyp
My old one could be found here : http://dualhoki.vim.hu/gapps-20130301-i927.zip
Issue
talkback doesnt work, you need to install from google play
Credits
Adam77Root for FaceUnlock fix.
Face unlock can be fixed by replacing libfacelock_jni.so from HOX+. Here is the lib: http://forum.xda-developers.com/showpost.php?p=38946152&postcount=254
great! Thanks
bubor said:
I have made for cm10.1, but it should work with any 4.2 base rom.
Problem:
Glide has tegra 2, witch doesnt support neon instructions, google dropped support non-neon library.
Change
start with gapps-20130301-signed.zip
replaced:libpatts_engine_jni_api.so, libfacelock_jni.so
removed:libjni_latinime.so
Download
http://dualhoki.vim.hu/gapps-20130301-i927.zip
Issue
talkback doesnt work, you need to install from google play
Credits
Adam77Root for FaceUnlock fix.
Click to expand...
Click to collapse
sorry for the noob question but what does it differ exactly from the original gapps? apart from faceunlock fix, I got that, and that's cool (thanks Adam )
soadzoor said:
sorry for the noob question but what does it differ exactly from the original gapps? apart from faceunlock fix, I got that, and that's cool (thanks Adam )
Click to expand...
Click to collapse
removed one file, and replace 2 with non-noen one.
I can replace all 3, but cm10.1 has own libjni_latinime.so
bubor said:
removed one file, and replace 2 with non-noen one.
I can replace all 3, but cm10.1 has own libjni_latinime.so
Click to expand...
Click to collapse
Okay I got that you removed/replaced some files, but what does it effect? how can someone experience the difference? I dont want to be rude, I'm just curious
soadzoor said:
Okay I got that you removed/replaced some files, but what does it effect? how can someone experience the difference? I dont want to be rude, I'm just curious
Click to expand...
Click to collapse
those 3 library dont compatible with tegra 2, because tegra 2 has no neon. You shouldnt experience any difference, only it fixes some apps.
Replacing the libjni_latinime.so fixes auto correction and word prediction at the cost of swype function.
Adam77Root said:
Replacing the libjni_latinime.so fixes auto correction and word prediction at the cost of swype function.
Click to expand...
Click to collapse
swype function has never been working on the cappy glide, so I guess it's just fixes the auto correction and word prediction?
soadzoor said:
swype function has never been working on the cappy glide, so I guess it's just fixes the auto correction and word prediction?
Click to expand...
Click to collapse
Well, then yes.
I have opened a thread about non-neon gapps a while ago:
Non-neon Gapps (Android 4.2) dev-discussion thread
Feel free to join in, I were terribly busy fixing other bugs on my phone (bluetooth, WifiAP etc.) so I didn't yet have time to look into it closer.
As all Tegra2 / armv6 etc. devices are suffering from the same issues it might be interesting for more people.
Please note that it's (on purpose) a thread in the development discussion section, I will delete noobish posts.
Although I think the package here from the OP is already pretty complete - I got some additional gtalk non-neon libs which fix the gtalk videochat, will post them later today or tomorrow in the thread above.
I'm not aware of any other neon related bugs (but as I said, I didn't spent a lot of time, yet).
Adam77Root said:
Well, then yes.
Click to expand...
Click to collapse
Adam,
How did you guys end up fixing the picture rotatation when they are taken in portrait mode ?
kick buttowski said:
How did you guys end up fixing the picture rotatation when they are taken in portrait mode ?
Click to expand...
Click to collapse
It isn't fixed yet. There are still some issues with the camera. This can be fixed in a camera wrapper which can also fix ISO modes and exposure compensation. Unfortunately, camera wrapper causes lockups sometimes.
Sent from my CM10.1-powered GT-I9103
I finally found some time to work further on the non neon gapps package.
All details here:
http://forum.xda-developers.com/showthread.php?p=39022876&postcount=2
It should fix pretty much all remaining issues the old one had
Thanks
Related
Due to conflicts between Color Calibration and the camera/video playback overlays, I would recommend not to do these modifications. If it was the case, just restore your nandroid backup.
Sorry for the inconvenience.
I'll try to improve the compatibility with our devices.
Hello everyone,
I just wanted to share some knowledge about a discovery I've made today.
Just like a lot of our Galaxy S community members, my screen was way too blueish (temperature "over 9000" kelvin).
However, by googling a few keywords around, I saw that a fix by storm9999 was available for the droid, N1, and even desire xx phones.
Basically I just tried to do the modifications on my Galaxy S with the Darky's 6.0 Gingerbread edition rom. And it works!
Here is a screenshot of the application:
http://img600.imageshack.us/i/uicolor.jpg
Requirements:
- Rooted phone
- Clockworkmod
- An Android 2.2[+] ROM (successfully tested on Darky's 6.0)
Installation:
- Make an nandroid backup just to be safe (français, english)
- Put the under-attached zip and apk files into the root folder of your internal sdcard
- Restart your phone in recovery mode
- Choose "install zip from sdcard", "choose zip from sdcard", and select the "calibrated-signed..." zip file
- Reboot your phone. Note: At first reboot, sim card may not be functional. Just reboot, and the issue should be gone
- Install the "calibrator-5.1" apk file with Astro or else
- Enjoy!
Please if you try this fix with another froyo rom, tell us if it works or not. I'll put a compatibility list here!
ROM compatibility:
- Darky's v6.0 Gingerbread ed. JPX => OK
- Stock JPU with CF-root => OK
Known bugs:
- If calibration is enabled, Spare Parts will crash when Render Settings is opened.
- When you tune your colors, the overlay appears over the sliders, and not over the calibration field at the top
- Camera and video playback lose their overlay
Credits
- Storm9999 for the apk and certificate
- Cyanogen and his team for the source files
- RixKliq for the icon making
- Xenio2000 for the UI improvements
- Supercurio for not integrating his awesome voodoo colorfix in JPU and JPX versions Sans rancune l'ami!
eruur said:
- Supercurio for not integrating his awesome voodoo colorfix in JPU and JPX versions Sans rancune l'ami!
Click to expand...
Click to collapse
Lol yeah it's a good alternative and don't require recompiled kernel !
Limitation is that it lower the final brightness and reduce the color-resolution (something like 18 or 20 bits depending the adjustment you apply - very rough estimation)
but hey, it works !
Thank you eruur
Just installed, but i noticed no differencies, droid calibrator has red blue and green at 1000 is it ok?
Working in stock JPU with CF-root
but is the color overlay really supposed to appear over the sliders? shouldn't it be covering the calibration field at the top?
looks like this here:
Razer(x) said:
Just installed, but i noticed no differencies, droid calibrator has red blue and green at 1000
Click to expand...
Click to collapse
You need to click on "User 1", then tune your colors. If your screen is a little blue, just decrease its value to something like 960.
Then save your settings.
At first I thought it wasn't working too, but if I put my blue value to 500, my screen is all yellow :d So it is actually working
I also recommend to do your calibration with the maximum brightness in order to be accurate!
@supercurio: De rien! lol
XlAfbk said:
Working in stock JPU with CF-root
but is the color overlay really supposed to appear over the sliders? shouldn't it be covering the calibration field at the top?
Click to expand...
Click to collapse
Indeed, I've noticed that also. You need to save, quit, and relaunch the calibrator to see the effect on the top field. I will try to fix the overlay position!
Does it make you lose overlays in camera and video player like it used to do before? Ie. is it modified in some way to be more compatible with stock Galaxy Froyo or is it just the unmodified files from stormy?
works with darky's rom 6.0 JPX + speedmod kernel K11C
Case_ said:
Does it make you lose overlays in camera and video player like it used to do before? Ie. is it modified in some way to be more compatible with stock Galaxy Froyo or is it just the unmodified files from stormy?
Click to expand...
Click to collapse
I searched and did not find any info about galaxy compatibility. You're right, the overlays do not work anymore in camera and video player.
Sorry about that, hadn't noticed. I guess it doesn't work that well afterall :/
I'll look into that.
Wowww ! work very good
eruur said:
You need to click on "User 1", then tune your colors. If your screen is a little blue, just decrease its value to something like 960.
Then save your settings.
At first I thought it wasn't working too, but if I put my blue value to 500, my screen is all yellow :d So it is actually working
I also recommend to do your calibration with the maximum brightness in order to be accurate!
@supercurio: De rien! lol
Click to expand...
Click to collapse
Thanks, mine seems to be good with no changes
nesquix said:
Wowww ! work very good
Click to expand...
Click to collapse
Does your camera still work good?
i can confirm the camera issues. had to restore libsurfaceflinger.so
XlAfbk said:
i can confirm the camera issues. had to restore libsurfaceflinger.so
Click to expand...
Click to collapse
Where to find it?
in your nandroid backup or an extracted factoryfs.rfs
XlAfbk said:
in your nandroid backup or an extracted factoryfs.rfs
Click to expand...
Click to collapse
Yeah, but where? (path)
eruur said:
I searched and did not find any info about galaxy compatibility. You're right, the overlays do not work anymore in camera and video player.
Sorry about that, hadn't noticed. I guess it doesn't work that well afterall :/
I'll look into that.
Click to expand...
Click to collapse
I think I've posted about that in the original thread quite some time ago and I'm fairly certain I've mentioned this option in some Galaxy S threads either here in Development or in General. But that was most likely sometime in August or September, so it's long forgotten.
I guess it makes sense that the overlays stop working, given that you need to replace the libsurfaceflinger.so for this to work.
Too bad, I was quite excited that someone finally managed to get it to work on stock Galaxy ROM. I'd love to have the option to calibrate my screen to 6500K properly to match my PC screen and I thought someone finally made it possible without the need to use CyanogenMod (not that I have anything against CM, it's just it isn't all that stable/usable just yet).
Anyway, if anybody is interesting in using this even in this state, my screen is pretty close to 6500K when using these settings:
R: 965 G: 740 B: 720
Of course every screen is a bit different and the color temperature of SAMOLED screens changes with time, so no guarantees that this will work for you as well.
Case_ said:
I think I've posted about that in the original thread quite some time ago and I'm fairly certain I've mentioned this option in some Galaxy S threads either here in Development or in General. But that was most likely sometime in August or September, so it's long forgotten.
I guess it makes sense that the overlays stop working, given that you need to replace the libsurfaceflinger.so for this to work.
Too bad, I was quite excited that someone finally managed to get it to work on stock Galaxy ROM. I'd love to have the option to calibrate my screen to 6500K properly to match my PC screen and I thought someone finally made it possible without the need to use CyanogenMod (not that I have anything against CM, it's just it isn't all that stable/usable just yet).
Anyway, if anybody is interesting in using this even in this state, my screen is pretty close to 6500K when using these settings:
R: 965 G: 740 B: 720
Of course every screen is a bit different and the color temperature of SAMOLED screens changes with time, so no guarantees that this will work for you as well.
Click to expand...
Click to collapse
Sorry for the false joy.. I was also disappointed!
Anyway, I'll play with the modified libsurfaceflinger to see if I can come up with something.
Oh and for Razer: path /root/system/lib
I think you need to put a DEV tag on the title. Good threads have been tossed to general becuse of this.
Sent from my GT-I9000 using XDA App
oh ****ttttt camera don't work too on JPX
Just get better keyboard, Battery life 24H!!
http://files.xdandroid.com/
Hi
It's very fine and usable but i can't find the live wallpaper function.
Do you know what can i do ???
PANCIO said:
Hi
It's very fine and usable but i can't find the live wallpaper function.
Do you know what can i do ???
Click to expand...
Click to collapse
It has no Live Wallpaper support because it's still alpha release.
And this feature has lower priority than other stuff that have to be fixed.
PANCIO said:
Hi
It's very fine and usable but i can't find the live wallpaper function.
Do you know what can i do ???
Click to expand...
Click to collapse
It won't have live wallpaper anytime soon. They are not worth fixing because they drain battery crazy fast and are darn slow on our devices. I think they were disabled on purpose in FroYo.
hi, can you tell us, what is working and what no in this build?
I refer about the bluetooth, camera, wifi...
Thanks
dedalum said:
hi, can you tell us, what is working and what no in this build?
I refer about the bluetooth, camera, wifi...
Thanks
Click to expand...
Click to collapse
Hi, dedalum!
On Blackstone BT does not work, wifi and data works, camera.... I'll test it! (I think it wont work) --Tested, but the news are bad!
The old kernels does not work with Gingerbread, so camera does not work, yet!
I tried two different kernels, for the camera testing and for the anti-audio stuttering MOD, in the both cases it cant reach the homescreen.
As nasko_spasko mentioned, camera seems out of reach for the moment...
I also asked in VirusCrazy's camera testing thread, and he also gives Gingerbread "low chance", something for the future...
But I should add that there is (probably more than one) kernel out here that fixes audio stuttering, I'm using Gingerbread with a modified 1253 kernel from http://forum.xda-developers.com/showpost.php?p=11169582&postcount=76
Audio and Wifi great, battery life ~ 20-30 hours (using periodic data for ClockSynch and some weather sync, but nothing else)
Cheers,
Robbert
nasko_spasko said:
Hi, dedalum!
On Blackstone BT does not work, wifi and data works, camera.... I'll test it! (I think it wont work) --Tested, but the news are bad!
The old kernels does not work with Gingerbread, so camera does not work, yet!
I tried two different kernels, for the camera testing and for the anti-audio stuttering MOD, in the both cases it cant reach the homescreen.
Click to expand...
Click to collapse
nasko_spasko said:
Hi, dedalum!
On Blackstone BT does not work, wifi and data works, camera.... I'll test it! (I think it wont work) --Tested, but the news are bad!
The old kernels does not work with Gingerbread, so camera does not work, yet!
I tried two different kernels, for the camera testing and for the anti-audio stuttering MOD, in the both cases it cant reach the homescreen.
Click to expand...
Click to collapse
The audio is the most important issue for me.
I have GBX0A running with 1255 kernel. It's the only one that doesn't give me audio-stuttering since Gingerbread won't boot with the 1498 kernel.
The latest kernels 1260/1262 both work but give audio-stutter.
Only thing i'd like is a new rootfs with keymapping for Blackstone like in the rootfs from 2011-01-31.
very nice build. i have one question though... why is the clock lazy?
it is like the android minute is a second short. is there a fix for this?
had the same problem. search market for time sync apps..
5zeci said:
very nice build. i have one question though... why is the clock lazy?
it is like the android minute is a second short. is there a fix for this?
Click to expand...
Click to collapse
Do as d.weiss says. Clocksync works perfectly.
5zeci said:
very nice build. i have one question though... why is the clock lazy?
it is like the android minute is a second short. is there a fix for this?
Click to expand...
Click to collapse
just get clocksync from market
Am i the only one having trouble with the keyboard not showing up properly? it's only about 20px high and it's impossible to see there are different keys but if you drag your finger around the popup with the different characters show up so it works but seem to be scaled incorrectly...
I tried long pressing on a text field to switch keyboard and the chineese keyboard works just fine but that doesn't really help me...
zagitta said:
Am i the only one having trouble with the keyboard not showing up properly? it's only about 20px high and it's impossible to see there are different keys but if you drag your finger around the popup with the different characters show up so it works but seem to be scaled incorrectly...
I tried long pressing on a text field to switch keyboard and the chineese keyboard works just fine but that doesn't really help me...
Click to expand...
Click to collapse
same problem.
and i had during the initial boot that the alignmet squares disapeared (the 4/5 blocks to align the touch screen)
zagitta said:
Am i the only one having trouble with the keyboard not showing up properly? it's only about 20px high...
Click to expand...
Click to collapse
SmokeMasta said:
same problem.
and i had during the initial boot that the alignmet squares disapeared (the 4/5 blocks to align the touch screen)
Click to expand...
Click to collapse
Keyboard is a known issue.
Recommendation: get Thumb keyboard from Market. It's free and has different layouts and looks.
Fix for alignment squares: use old ts-calibration file from another build, or use the one attached below. Just remove the extension and put it in the same folder as haret and startup.
hrk7474 said:
Keyboard is a known issue.
Recommendation: get Thumb keyboard from Market. It's free and has different layouts and looks.
Fix for alignment squares: use old ts-calibration file from another build, or use the one attached below. Just remove the extension and put it in the same folder as haret and startup.
Click to expand...
Click to collapse
How exactly am i supposed to get on the market in the first place when i can't write my email? I've put the apk onto the sd card but there's not even a file manager included so that's not possible either :<
zagitta said:
How exactly am i supposed to get on the market in the first place when i can't write my email? I've put the apk onto the sd card but there's not even a file manager included so that's not possible either :<
Click to expand...
Click to collapse
Use build in Japan IME. It has Latin characters on the numeric keyboard (like in non touchscreen phones). Should be enough to log into market and download gingerbread keyboard.
zagitta said:
How exactly am i supposed to get on the market in the first place when i can't write my email? I've put the apk onto the sd card but there's not even a file manager included so that's not possible either :<
Click to expand...
Click to collapse
Or just put the apk inside the AndroidApps folder (it's inside the andboot one). It will auto-install at boot.
I like the app "Gingerbread keyboard" though. I use it in froyo too.
g3rm0 said:
Use build in Japan IME.
Click to expand...
Click to collapse
Thanks so much for that, I owe you a huge beer!
Yes this version is working like a charm !
Its very fast and stable
Hi everybody!
You might already know me. I develop CM for the SGR. Here I give you my builds of CyanogenMod 10.1 (based on Android 4.2.1 Jelly Bean) for the Samsung Captivate Glide (SGH-I927).
As I do not own the device, I need some testers first to confirm! Do have a backup!
For general discussion and Q&A: head to this thread.
What works:
Mobile network (2G/3G switch and network selection as well)
Data connection
Data usage statistics
Audio
Wi-Fi
Wi-Fi Direct (P2P)
Bluetooth
Video player
Accelerometer, orientation, magnetic field, light, proximity, battery temperature sensors, gyroscope
BLN feature (you need either the free or the paid version of BLN Control from Play Store)
Auto brightness
USB On-The-Go
Moving apps to SD card
Camera (single and panorama pictures)
Video recording (480p SD and 720p HD as well)
Full HW acceleration with Nvidia and Samsung codecs
Wireless tethering
Keyboard rotation and key fixes (thx thegreatergood)
What doesn't work:
USB Mass Storage only works manually
Stock sound recorder app (use an external, like MIUI Sound Recorder instead)
Maybe bluetooth A2DP (I couldn't test)
Maybe bluetooth tethering (I couldn't test)
A more detailed bug list and possible solutions can be found here. There may be other bugs, feel free to report them.
Link: Not available.
Get Google apps here: http://goo.im/gapps/gapps-jb-20121212-signed.zip
Installation method:
Flash CM.
Flash this kernel to fix vibration issue.
Flash Google apps. (It is not optional anymore!)
Do 'Wipe data/factory reset' in recovery.
Reboot & enjoy.
Every custom modification to devices have risks. Flash this at your own risk!
Have fun and enjoy!
Thread cleaned
The bickering ends now. There is room for creativity from many members. Continuation of the deleted discussion will result in an infraction against the user's account.
Thanks MOD. Love ur presence here.
Sent from my GT-I9103 using Tapatalk 2
don't know what happend but if staring from scratch why not building 4.2.1 instead?
He has to understand your device first, once it is stable he will release for 10.1... He already release for Galaxy R and it is Beta...
So don't worry guys, Please download, test and provide the logcat for him... he will fix as earliest..
I noticed that the bugs from dman's build aren't the same ones listed. Does that mean the keyboard works now?
Sent from my myTouch_4G_Slide using Tapatalk 2
gtmaster303 said:
I noticed that the bugs from dman's build aren't the same ones listed. Does that mean the keyboard works now?
Sent from my myTouch_4G_Slide using Tapatalk 2
Click to expand...
Click to collapse
He doesn't have the phone that's why we he wants us to test it
i cannot install it. cwmr says: installation aborted.. I thought it might be a result of a bad downloading, so I downloaded it again, but the result is the same
soadzoor said:
i cannot install it. cwmr says: installation aborted.. I thought it might be a result of a bad downloading, so I downloaded it again, but the result is the same
Click to expand...
Click to collapse
Does it say anything more?
well, I made a picture of it, dont know if it makes anything clear..
this is error
This is assertion error. Just wondering if dman has opened all of his zips and removed these lines. Will post a new zip tomorrow with the assertion check removed then will examine your CWM builds.
Adam77Root said:
This is assertion error. Just wondering if dman has opened all of his zips and removed these lines. Will post a new zip tomorrow with the assertion check removed then will examine your CWM builds.
Click to expand...
Click to collapse
so i have a paper weight until tomorrow
smutta said:
so i have a paper weight until tomorrow
Click to expand...
Click to collapse
Should be able to mount USB and transfer a working ROM to the phone for flashing.
smutta said:
so i have a paper weight until tomorrow
Click to expand...
Click to collapse
Dude you chose to test this, he clearly said to make a backup so,
Adam77Root said:
This is assertion error. Just wondering if dman has opened all of his zips and removed these lines. Will post a new zip tomorrow with the assertion check removed then will examine your CWM builds.
Click to expand...
Click to collapse
Should be assert i927, SGH-I927, SGH-I927R, SGHI927,SGHI927R, n1. That's what all my updaters run....
Sent from my SGH-I927 using xda premium
And this will fix keyboard lights in lights.c
char const*const BUTTON_FILE="/sys/class/sec/sec_stempe_bl/backlight"
But you probably already knew that..
Sent from my SGH-I927 using xda premium
dman3285 said:
And this will fix keyboard lights in lights.c
char const*const BUTTON_FILE="/sys/class/sec/sec_stempe_bl/backlight"
But you probably already knew that..
Sent from my SGH-I927 using xda premium
Click to expand...
Click to collapse
Thanks !!!
dman3285 said:
And this will fix keyboard lights in lights.c
char const*const BUTTON_FILE="/sys/class/sec/sec_stempe_bl/backlight"
But you probably already knew that..
Sent from my SGH-I927 using xda premium
Click to expand...
Click to collapse
I end up getting char: not found...
Has anyone else noticed that the Home button doesn't actually function as a home button (the capacitive button, not the keyboard one.)
Installed by edited installer script.
According to the QUALCOMM: Snapdragon camera app is designed to make it easier than ever to capture, edit, and share the moments that make life so special, which works with Qualcomm® Snapdragon™ 800 series processors.
We have a powerful processor in OnePlus X, so we can benefit from this great Camera application. For extended details on the Snapdragon Camera, features and some samples please visit the official blog post here
How to install
>> A flashable zip for automatic installation is here
Thanks to @Einstein67
Manually:
Step 1:
Download required files
- Snapdragon Camera v2.1
- Snapcamtinyplanet.so
- Snapcammosaic.so
Step 2:
» Download the camera apk and lib.files [Snapcammosaic.so , Snapcamtinyplanet.so] into your device.
» Open any root explorer app and navigate to device/internal storage>system>lib>place the two lib files downloaded above{cut/paste}. Also change permissions to each lib to 0644 (-rw-r--r--).
» Similarly, place the snapdragon camera app [apk.file] in device/internal storage>system>app and again change permissions to apk to 0644 (-rw-r--r--).
» Now, reboot your device to activate the changes and enjoy! :victory:
any sample shot comparisons?
Root needed ?
Radzioo85 said:
Root needed ?
Click to expand...
Click to collapse
Yeah I guess because you have to cut/paste the needed libs in the "system" folder..
ckret said:
any sample shot comparisons?
Click to expand...
Click to collapse
Maybe later, dont have much time now, but until then just try it and see for yourself! It's a super easy procedure! :laugh:
Excellent! Thanks! Camera is lightning fast! No more delay after taking a pic
Lots of options, but can't save to SD card. It will save to USB OTG though, I clicked on this even though I had no USB plugged in and it gave me a toast of couldn't locate SD card, which won't go away now. It works nicely though and some will find it useful.
@jackshot you've forgotten a very important point. The permissions have to be changed on both the libs and on the apk too.
parasthakur37 said:
@jackshot you've forgotten a very important point. The permissions have to be changed on both the libs and on the apk too.
Click to expand...
Click to collapse
Will that change the quality of the pics too? I know it sounds silly to ask, but I installed it yday, it worked but photos looked worse (much, much brighter) than on stock app. Also, after using this app the normal camera apk wouldn't boot.
parasthakur37 said:
@jackshot you've forgotten a very important point. The permissions have to be changed on both the libs and on the apk too.
Click to expand...
Click to collapse
Oh, my bad.. Actually a friend asked me to try it and I decided to share it with the community.. What permissions should we set on libs and apk? If you know, I will add it to instructions..
jackshot said:
Oh, my bad.. Actually a friend asked me to try it and I decided to share it with the community.. What permissions should we set on libs and apk? If you know, I will add it to instructions..
Click to expand...
Click to collapse
apk and lib files should be with permissions 0644 (-rw-r--r--)..
charliebigpot said:
Will that change the quality of the pics too? I know it sounds silly to ask, but I installed it yday, it worked but photos looked worse (much, much brighter) than on stock app. Also, after using this app the normal camera apk wouldn't boot.
Click to expand...
Click to collapse
Thanks for the review, can you post same sample too?
StraightEdgeKid said:
Thanks for the review, can you post same sample too?
Click to expand...
Click to collapse
Right after trying this camera I tried the battery mod posted in the other sub-forum and unfortunately turned my phone into a brick. I solved it now but the photos are lost Not going to install it again, at the end of the day I realised that the oneplus app is the fastest and the google photo app will do the job too.
charliebigpot said:
Right after trying this camera I tried the battery mod posted in the other sub-forum and unfortunately turned my phone into a brick. I solved it now but the photos are lost Not going to install it again, at the end of the day I realised that the oneplus app is the fastest and the google photo app will do the job too.
Click to expand...
Click to collapse
It was real help mate, thanks. (Pulled thanks trigger too )
charliebigpot said:
Right after trying this camera I tried the battery mod posted in the other sub-forum and unfortunately turned my phone into a brick. I solved it now but the photos are lost Not going to install it again, at the end of the day I realised that the oneplus app is the fastest and the google photo app will do the job too.
Click to expand...
Click to collapse
Well maybe it was battery mod's fault then?
I use Snapdragon Camera and I never had a problem or conflict with anything I flashed since then..
jackshot said:
Well maybe it was battery mod's fault then?
I use Snapdragon Camera and I never had a problem or conflict with anything I flashed since then..
Click to expand...
Click to collapse
I'm almost sure it was the battery mod's fault, but I don't want to try it again
This camera worked, the only issue I had was that any other camera wouldn't open afterwards (had to fc the snapdragon camera), but maybe that's related to the missing permissions, that info came after I tried it.
Where's this app taken from? I also saw this post but they doesn't mention any source.
raulx222 said:
Where's this app taken from? I also saw this post but they doesn't mention any source.
Click to expand...
Click to collapse
The files were sent to me by a friend in order to test them in my OPX.. I just shared them here with the community.
I guess he got it from Oneplus One's thread..
Working perfect! I was using it with Sultanxda CAF ROM in my Oneplus One and love it. Best camera App IMHO.
Thanks dude!
Enviado desde mi Oneplus X
Followed steps exactly but it's not working. The app just starts goes to a black screen and closes
Sent from my ONE E1003 using Tapatalk
Hello guys and girls,
As some of you already know Android 8.1 suffers from a severe Multi-Touch Issue. This issues makes the smartphone randomly jumping between the two touching points on the screen when touching with two or more fingers.
The issue is known to google since the preview of 8.1. It isn´t only affecting pixel but most probably all devices running 8.1. The issue is also present on P.
An issue got created here: https://issuetracker.google.com/issues/70344455
There is a fix since mid march in review on google gerrit. But that didn´t make it into the april release, obviously.
To visualize the issue refer to the following videos:
https://youtu.be/wgYN5GwIgIc
https://youtu.be/2Vv584tvVyg
https://www.youtube.com/watch?v=4dnIk_5qdK8&feature=youtu.be
This is especially bad for gamers. With the recent release of PUBG this issues seems dramatic to some, less to others.
I´m no gamer but I noticed the issue on the google foto app.
This issue has nothing to do with the corners badly reacting to touches, or touch sensitivity etc.
So but now to the fix. It seems the issues is only related to resampling but not to touching specific points of the screen ( not related to crossing x and y axis).
That also explains why the issue wasn´t happening when using the touch tracking tool in dev settings but on various multi touch test apps.
The fix is on google gerrit currently under review here:
https://android-review.googlesource.com/c/platform/frameworks/native/+/640605
https://android-review.googlesource.com/c/platform/frameworks/native/+/640606
Last week I compiled myself a DU build with the changes included and I couldn´t trigger the issue at all. I found no other side effects caused by the two patches.
For now I decided to provide a Magisk Module which replaces the changed libs that fixes the issue.
I compiled the libs while doing my april build of DU. The magisk module can be found on the link a little bit down.
The download is here:
https://www.androidfilehost.com/?fid=890129502657595755
A few disclaimers here.
1. That fix should in theory work for most 8.1 devices, including the likes of pixel 1st gen, pixel 2nd gen, one plus, xiaomi which suffer from this severe issue.
It seems devices with oos on 8.1 ( op5/t) cannot use this mod.
AOSP and LOS roms should be okay.
2. I didn´t fix this, I just compiled the libs with the fix found on google gerrit.
3. Rom devs you are very welcome to include this fix. I found no ill consequences as of yet but I can understand google taking it slow and reviewing it longer. Maybe they will find a better fix, but as of now this is the best thing we have.
Donations:
Donations are not mandatory but very welcome.
If you like my work: http://paypal.me/freak07
@calebcabob
@Myself5
@BDogg718
@sixohtew
@nitin.chobhe
@auras76
you may want to look at this and include it in your april releases.
If not users can just make use of the magisk module.
This causes a bootloop on P DP1.
iaTa said:
This causes a bootloop on P DP1.
Click to expand...
Click to collapse
Thanks for the report.
can anyone confirm this?
In the meantime i removed the p tag from the thread title.
Could be That there are additional changes in p that make this libs unusable and only workable on 8.1.
Unfortunately there is afaik no complete source for p yet. So I can’t compile them specifically for p.
Fixed for me!! I only ever noticed the issue when pinch/zooming images on Instagram.. it's gone! Using the April update of 8.1 ... Thanks!!!
jbarcus81 said:
Fixed for me!! I only ever noticed the issue when pinch/zooming images on Instagram.. it's gone! Using the April update of 8.1 ... Thanks!!!
Click to expand...
Click to collapse
Same with me on google fotos!
Glad it’s fixed for you.
Freak07 said:
Same with me on google fotos!
Glad it’s fixed for you.
Click to expand...
Click to collapse
Also fixed for me, thanks for solving this problem!
I can't replicate this problem, but good to know that there's a fix if I ever experience it.
I'm a beginner at this.But when I tried to install it via magisk manager,I get this error.What are the correct installation steps to flash a magisk module?
Thanks
I never had this issue but it's good to know there's a fix..I'm on the p preview so I'm not sure if I will ever have this issue and no one reported it in my builds but I will include the fix anyways that way no one has to do anything. Good catch
Prey521 said:
I can't replicate this problem, but good to know that there's a fix if I ever experience it.
Click to expand...
Click to collapse
sixohtew said:
I never had this issue but it's good to know there's a fix..I'm on the p preview so I'm not sure if I will ever have this issue and no one reported it in my builds but I will include the fix anyways that way no one has to do anything. Good catch
Click to expand...
Click to collapse
I also thought at first I didn’t have this issue at all.
But once I triggered it accidentally I experienced it many times. Maybe I just learnt what to look for.
Another fun thing is. A friend of mine also got the pixel XL 2 and I could reproduce it right away on his locked phone which is stock 8.1.
I can also trigger it on my pixel C tablet.
ReapinDevil said:
I'm a beginner at this.But when I tried to install it via magisk manager,I get this error.What are the correct installation steps to flash a magisk module?
Thanks
Click to expand...
Click to collapse
Either try flashing it in recovery or use the latest magisk?
Freak07 said:
@calebcabob
@Myself5
@BDogg718
@sixohtew
@nitin.chobhe
@auras76
you may want to look at this and include it in your april releases.
If not users can just make use of the magisk module.
Click to expand...
Click to collapse
The mention for the last dev didn't work for some reason, so:
@auras76
mistermojorizin said:
The mention for the last dev didn't work for some reason, so:
@auras76
Click to expand...
Click to collapse
Thanks in the quote from your post of my post it worked tough
Freak07 said:
Thanks in the quote from your post of my post it worked tough
Click to expand...
Click to collapse
That is really weird, because even when I quoted you, then hit "preview post" to see what it would look like, it still didn't work inside the quote.
Kudos to you,
Previosly my device has a bad touch pressure sensitivity along the edge, and in certain spot, it wont even register the touch,
Now it all fixed.
The corner two still has less sensitivity, but previously all edge zone were patchy, full of red zone.
And considering am using full cover glass protector. This is amazing work !
What app did you use for that test?
I've experienced lack of touch response quite often. It's weird and seemingly random. I just flashed this on 8.1 with magisk. I don't have any results yet, but based on what everyone else is saying, this is a solid fix. Thanks for your work!
Do we have to worry about removing this in the future if google updates fix the issue too? Will this being on the system cause conflicts and issues?
mistermojorizin said:
That is really weird, because even when I quoted you, then hit "preview post" to see what it would look like, it still didn't work inside the Autor.
Click to expand...
Click to collapse
That’s just xda bring xda.
I had this problem a few times when updating the OP for a new release. Sometimes the OP won’t update at all...
otonieru said:
Kudos to you,
Previosly my device has a bad touch pressure sensitivity along the edge, and in certain spot, it wont even register the touch,
Now it all fixed.
The corner two still has less sensitivity, but previously all edge zone were patchy, full of red zone.
And considering am using full cover glass protector. This is amazing work !
Click to expand...
Click to collapse
Glad it works out for you!
Enjoy your phone