Related
As a lot of other persons I have the "screen lag" issue. After reading several posts I have found a way to fix it : I've just removed the back cover and I check the battery position, then I put back the back cover.
Now the big lag disappeared.....
No need to add a paper between the battery and the back cover in my case.
I hope it will help others.
Well, another thing that worked for me was tighten all screws a tiny bit.
Worked like charm ^^
I opened d battery twice since i bought my folio. Lagging issue oni several times for me. Is it really should do this i don know.
Should give a try bcoz it is no need to pay for opening d battery
I still believe that must of the lag is caused by bad software, though i also notice that screen is kind of lose.
bastospn said:
I still believe that must of the lag is caused by bad software
Click to expand...
Click to collapse
i do believe too, no prove but have the feeling that some app crashed behind the screen and make the folio lag or freezed.
somebody can confirm that?
waii69 said:
i do believe too, no prove but have the feeling that some app crashed behind the screen and make the folio lag or freezed.
somebody can confirm that?
Click to expand...
Click to collapse
using dev tools, u can monitor the cpu usage values. if it get above 2.0( except for the first 2/3 minutes when booting and when connecting to wifi), then some app is causing it to lag. if values are still below that number for a long time and still there is screen lag issue, then its definitely a hardware issue.
use an app called aLogCat to see what's happening during an error. Pretty handy errorlog tool
thanks guys, i will try and see what is happen.
This is what i get when i clear the log, then shut the screen and wait till it pops open.
Code:
D/WindowManager( 1081): I'm tired mEndcallBehavior=0x2
I/power ( 1081): *** set_screen_state 0
E/Sensors ( 1081): mask[0x0]
D/RemoteCtrlManager( 1081): ACTION_SCREEN_OFF
D/UpdateReceiver:( 1081): HDMI_UNPLUG
D/UpdateReceiver:( 1081): false
D/RemoteCtrlManager( 1081): initHDMIfalse
V/alogcat (12698): save instance
V/alogcat (12698): paused
D/JuicePlotter.CollectService( 1583): battery:81, plugged:1, screen:0, wifi:false,apn:false,bluetooth:false
D/ ( 976): NVRM_DAEMON(985): pm_notifier_thread: calling power_displays(false)
D/ ( 976): NVRM_DAEMON(988): pm_notifier_thread: returned from power_displays(false)
D/JuicePlotter.CollectService( 1583): battery:81, plugged:1, screen:0, wifi:false,apn:false,bluetooth:false
D/JuicePlotter.CollectService( 1583): battery:81, plugged:1, screen:0, wifi:false,apn:false,bluetooth:false
D/dalvikvm( 1178): GC_EXPLICIT freed 546 objects / 124312 bytes in 74ms
I/AKMD2 ( 930): akmd2 : Compass Closed.
D/dalvikvm( 5555): GC_EXPLICIT freed 2696 objects / 169120 bytes in 70ms
D/dalvikvm( 5835): GC_EXPLICIT freed 3104 objects / 113848 bytes in 93ms
D/ ( 976): NVRM_DAEMON(974): pm_notifier_thread: calling power NvddkAudioFxSuspend(true)
I/AKMD2 ( 930): akmd2 : Suspended.
W/EventHub( 1081): could not get event (errno=19)
I/EventHub( 1081): Removed device: path=/dev/input/event8 name=USB2.0 UVC 1.3M WebCam id=0x380008 (of 0x9) index=10 fd=328 classes=0x1
D/org.jraf.android.nolock.NoLockService( 1479): onStartCommand
D/org.jraf.android.nolock.NoLockService( 1479): handleStart locking=false (nolock ENABLED)
D/org.jraf.android.nolock.NoLockService( 1479): handleStart mKeyguardLock != null: reenabling keyguard
I/power ( 1081): *** set_screen_state 1
D/ ( 976): NVRM_DAEMON(980): pm_notifier_thread: calling power NvddkAudioFxSuspend(false)
D/ ( 976): NVRM_DAEMON(991): pm_notifier_thread: calling power_displays(true)
W/ResourceType( 1081): Invalid package identifier when getting bag for resource number 0x00000000
D/GoogleLoginService( 1178): onBind: Intent { act=android.accounts.AccountAuthenticator cmp=com.google.android.gsf/.loginservice.GoogleLoginService }
E/Sensors ( 1081): mask[0x0]
D/RemoteCtrlManager( 1081): ACTION_SCREEN_ON
D/UpdateReceiver:( 1081): HDMI_UNPLUG
D/UpdateReceiver:( 1081): false
D/RemoteCtrlManager( 1081): initHDMIfalse
V/alogcat (12698): resumed
D/ ( 976): NVRM_DAEMON(994): pm_notifier_thread: returned from power_displays(true)
Some unrelated stuff there too like juice plotter and no lock...sorry.
‘Life’, as per John Horton Conway’s original creation. It simulates the existence of a two dimensional array of cells which will continue, or not, into the next generation based on a few simple rules. Which are:
If a cell has two or three neighbours, it will continue into the next generation. If an empty square is surrounded by three neighbours, then a new cell will be ‘born’ into it on the next generation. In all other cases which is where a cell has less than two or more than three neighbours, then the cell will die, simulating a lack of breedable neighbours, or lack of food due to overcrowding, respectively.
These simple rules create a complex world, where order and chaos reign, and quite often change places with each other, before finally settling down to a stable or completely static state, sometimes after hundreds, if not thousands, of generations.
The program is a Win32 C++ implementation in an executable of only 13Kb in size, although it consumes around 200Kb of memory when running. It uses basic GDI drawing functions so it will run on any ARM powered Pocket PC or Smartphone, from WM2003 onwards. Just drop the executable on your device and run it. It will also run on any sized screen up to 1024x1024 pixels, so that should take care of all current devices. It matches the grid size to the screen size. Cell populations cycle every half a second.
The original population is a randomly generated, with a one in four chance of a cell being present, after that the above rules take over.
MENU OPTIONS:
Restart will regenerate another random selection.
Auto Restart will make an intelligent guess that the population has reached a stable or static situation and will automatically restart after around 20 seconds of such a situation being reached. It has a reasonable attempt, but it cannot spot all possible stable or static situations.
Start Edit: Stops the generation and allows you to edit the cell pattern.
Pocket PC: - Tap the screen to create or remove a cell.
Smartphone:- Use the D-Pad to move the inverted cursor to the required square and press the centre Enter button.
Clear will erase all cells.
Run restarts the generations.
Wraparound removes the bounding effects of the edges of the display. When selected, cells' affects are allowed to roll over, left/right and up/down. The display, in effect, then becomes part of an infinitely repeating pattern.
Pressing the OK button does not terminate the program. Select End Program to close it completely.
If you have a Wizard, Kaiser or similar device, where the display can be switched from portrait to landscape, and if you do so, the program will continue, but you may invoke a near catastrophic extinction, as the display gets realigned to the new layout.
For a more complete article on this topic, have a look at:-
http://en.wikipedia.org/wiki/Conway's_Game_of_Life
The samples image shows a few shapes to try. They are the glider, the R pentamino, the spinner and the 10 consecutive cells. The R Pentamino generates a chaotic pattern of many cycles before it settles down, all the others are static/cyclical patterns. Auto Restart cannot detect the 10 consecutive cells, the repeating pattern is too complex for it to spot.
Update: 17/06/2011 Version 1.1 fixes the Embedded C++/WinMo 6.5.3 Dialog Box issue mentioned in
http://forum.xda-developers.com/showthread.php?t=635063
If you are running Winmo 6.5.3 and you downloaded this before 17/07/2011, you will need version 1.1 in the zip file below.
UPDATE: CE Version added.
If you have bought an ARM powered Windows CE device and are thinking
"What the hell do I do with this?!!"
try the CE version, then you can think,
"What the hell does this do?!!!"
Do not run the CE version on your SmartPhone or PPC device, the display will look awful. The same applies to running the Mobile version on a CE device, but try it if you must. An extra caveat is that your CE device should be running a version backwardly compatable with the Embedded C++ 4.0 'Standard' SDK
P.S. I wrote this program originally to run under DOS, over twenty years ago. It was written in 8086 assembly language, as it was the only way to get it run fast enough on a 12Mhz 80286, and drive an 640x480 mono VGA screen fast enough for it not to look awful. These days, on a current Intel Core class processor, the same program now runs through hundreds of generations per second, rendering it almost useless. Even though the program is now ported to C++ under a completely different platform, some of the original code optimization methodologies remain. They still work!
Thanks a lot.
Updated to 1.2
On Pocket PC/WinMo Professional/Windows CE platforms only:-
During 'Edit' mode, click and drag to set or erase a series of consecutive cells. Set or erase depends on whether the first cell clicked was empty or occupied, respectively, and will continue in the same mode until the mouse or stylus is lifted.
This makes it much easier to create the 10 cell line pattern as mentioned above.
None of this applies if the program is running on Smartphone or WinMo Standard platforms.
Hello.
So I've been tampering with the android SDK and made an app for practice. However, while trying to stick to my basic level goals, it seemed like I was going against the grain of how stuff seemed to work. I'm gonna read up on theory now, but it'd be a real help if you could tell me if there were any glaring dumb/broken/bad things there.
Anyway, the general idea was to have a reverse-stopwatch that I could populate with types of laps with custom durations. So I'd have, for example, WALK 10sec, RUN 30sec JOG 15sec *10 times. I wanted the app to vibrate every time one of these laps ended (no matter what, even in screen lock) but I also wanted those laps and their duration-countdowns to be dynamically shown in a ListView inside the main Activity.
In order to do that, I populated an Object that extended Application with my dataset, plugged it into an Adapter to update the ListView with, then when I had a populated list, I'd invoke an IntentService which would make a deep copy of the data and do countdowns inside logic loops. That IntentService also periodically sent messages to a BroadcastReceiver, who would update durations and remove expired laps on the Original List (linked to the Adapter) and handle vibrations. The intentService could be aborted prematurely , I haven't been able to think of a way to pause it.
Well, it works if you don't ever let it re-orient screens and while phonecalls don't break it, some of the listview data appearance was corrupt after one (the timers were fine tho which is weird).
**** THIS PROJECT IS NO LONGER MAINTAINED ****
Force Touch Detector
Force Touch Detector (FTD) is a Xposed module to detect Force Touch and switch touch action. FTD assigns seven force actions:
Tap
Double Tap
Long Press
Flick Left
Flick Right
Flick Up
Flick Down
Of course FTD doesn't bother normal operation by the threshold of pressure.
Introduction
Android reports pressure of your touch when you tap, press, swipe, and so on. However the pressure is different from Apple's Force Touch Technology. (It is mechanical implementation, isn't it?) Android's pressure is depending on touch area of your finger, not strength. But the touch area provides us new UI.
Force Touch on Android
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If you touch with the ball of your finger, the touch area increases. Call this "Force Touch" in this project. It is possible to distinguish ordinary touch operation from deliberately Force Touch because there is a distinct difference between these touch area. By checking whether a touch event is started from Force Touch, you can change the action of the touch.
Example:
Open floating launcher when you do force tap that is a tap started from Force Touch.
Go back by performing force flick to right that is a flick started from Force Touch.
Expand notifications by performing force flick to bottom anywhere.
Getting Started
At first, check your hardware supports FTD functions or not. Open a threshold screen, Pressure -> Threshold, and then test tap and force touch with two buttons. If Max, Pressure and Ave are changed by each touch, your touch screen supports the pressure parameter, you can use FTD by pressure. If not so, your phone doesn't support pressure, next try Size -> Threshold screen.
Note that some smartphones don't support both the pressure and the size parameter. FTD doesn't work on such a device.
After checking the capability of your touch screen, practice and adjust Force Touch with Threshold screen. Tap small button and do force touch on large button 5 times or more respectively, you'll get a Max value for normal tap and an Ave value for force touch. The Ave value must be higher than the Max value, you should practice force touch until so.
Finally, input a number between the Ave and the Max, and turn Master Switch on.
Adjustment
There are 3 parameters to adjust sensitivity for force touch.
Threshold
When pressure or size of your touch exceed this value, it is recognized as a force touch.Detection Window
The length of time FTD waits for force touch. If zero, FTD checks only the beginning of your touch stroke.Detection Sensitivity
The sensitivity for force tap and flick. If zero, Force Touch is always interpreted as a flick. If too high value, it is always tap. The range is 0 to about 20, depends on hardware.
I propose two strategies for adjustment.
Long detection window and high threshold value
Short detection window and mid threshold value
Maybe the experience of the former is near to Apple's Force Touch, squashing. However Android devices detect the pressure of touch by touch area even if you enable Pressure Threshold. In the other words, FTD's Force Touch based on Android API and Apple's one are fundamentally different. So I recommend to try both strategies.
Pressure vs. Size
These touch parameter depend on your hardware. Some phones report both parameters, some phones report only one parameter, and there may be some phones that don't report neither.
Reported Devices (shared/editable spreadsheet)
Compatibility
I tested on Nexus 4 running AOSP 5.1.1.
Q&A
Q. Does this mod work on my phone?
Activate the pointer location in dev options to see your touch pressure and size. If they are always same value, your hardware doesn't support them.
Download
Xposed Module Repository
XDA:DevDB Information
Force Touch Detector, Xposed for all devices (see above for details)
Contributors
tkgktyk
Source Code: https://github.com/tkgktyk/ForceTouch
Xposed Package Name: jp.tkgktyk.xposed.forcetouchdetector
Version Information
Status: Stable
Stable Release Date: 2015-07-28
Created 2015-06-08
Last Updated 2016-10-25
can you make how to video?? cant seem to get it work.
I dont really get what is the advantages of this module.. ?
Interesting.
Love to see a video too.
Very interesting concept! Love to see more information about how to "properly" use this module.
By the way dev, isn't there already a thread for this module earlier? Have you upgrade the module so a new thread is open as well?
Great job! Will give it a try now~
Vídeo for us
Works with CM12.1 ?
HGT - S5 G900F - Oneplus One - Tesla TTL7
I found out how it works on my z3 running Android 5.0.2.
What the developer means with his explanations is that you don't use the tip of your thumb but instead you place the thumb flat on the screen. You press or long press or swipe as usual, except you do it with the thumb flat on the screen. Don't press harder or in any different way then usual except of the thumb being flat.
Open the app, forget about half the settings and all the explanations and simply put "pressure threshold" to 0.7 and assign desired actions to the different commands. For example: click on the action "tap", chose "apps" and chose "YouTube". Then go to your homescreen (or into any other app) to test. You can not test while the module itself is in the foreground.
If you do it right, the "press with flat thumb" doesn't count as a normal press. This means you can press anywhere to execute the command, without ab care for what would happened if you pressed normally at same spot.
It takes some practice but once you got it, you got it. A good module with potential.
set to 0.8 on the OnePlus One (CM 12.1)
https://youtu.be/Xj0AMN5lHD0
Moto g LTE with 5.1
Works fine, set up to 0.6
I think that would be great to limit the area where we input a force touch, maybe in the bottom area of the screen.
Everyone, I apologize for any confusion.
#8 posted by @android404 and #10 posted by @k0sTi are great helpful. Thanks a lot!
@android404;
Many thanks! "press with flat thumb", yes, that's all!
I wanted to explain as you said. I'm going to simplify Pressure Threshold screen.
sclcn12 said:
Moto g LTE with 5.1
Works fine, set up to 0.6
I think that would be great to limit the area where we input a force touch, maybe in the bottom area of the screen.
Click to expand...
Click to collapse
The implementation is easy probably. I try to append your suggestion.
Thanks!
Looks like it's not working for me. Used 0.75 and rebooted, all touches are reported as "force touch" in a toast. Tried 0.95 same ****. I had to delete apk using twrp as normal touch wasn't working.
Blisspop 5.1.1
( back now, but still no reply ?)
andreasf93 said:
Is there a chance you can do mine as well?
Click to expand...
Click to collapse
Oh, I was overlooking your post. It's my fault, sorry.
I'm sure simulating taps is OK, but I need time for long press. Simulating one tap is unnecessary, isn't it? I'll focus dtap and long press.
Need help, this module is not working for me. wherever i click on the screen a toast appears telling the force touch pressure. I can unlock the phone but that is as far as it goes, unable to access xposed module or any other app. How do i uninstall or access this module, please help.
I get touch pressure of 1 no matter what i do . Any value below one , all touches are considered forced. However it works perfectly with my s pen.
andreasf93 said:
Great module, seems to be working fine so far (Nexus 5, set at 0.7500). I have a request tho, can you make an action (tap/dtap/long press) simulate another action? For example, I would like a tap to simulate a long press.
EDIT: Btw this is very similar to Mohammad's one (http://repo.xposed.info/module/com.mohammadag.systemwideforcetouch) but his module doesn't work on 5.1 while this one does.
Click to expand...
Click to collapse
I would be a great improvement if it could implement these actions. I would like it to simulate long press.
Hi, tkgktyk.
Constant force close. Here is the xposed log, I hope it helps. http://pastebin.com/0tz04TcN
P. S. : Can't a arch log, please, use pastebin to get it.
Sent from my Galaxy Note III LTE
v0.1.3
I uploaded wrong apk as v0.1.2.
Please skip v0.1.2 and update to v0.1.3.
** WARNING **
(SOFT)REBOOT IMMEDIATELY AFTER UPDATING
+ Master Switch
+ Notification to disable while running
+ Limit detection area on screen
+ Force touch effect
> Remade "Pressure Threshold" screen
> Added double tap and long press action
>>> but only interface
mobihack said:
Looks like it's not working for me. Used 0.75 and rebooted, all touches are reported as "force touch" in a toast. Tried 0.95 same ****. I had to delete apk using twrp as normal touch wasn't working.
Blisspop 5.1.1
( back now, but still no reply ?)
Click to expand...
Click to collapse
I remade "Pressure Threshold" screen to practice Force Touch. Please try this.
satanoncrack said:
Need help, this module is not working for me. wherever i click on the screen a toast appears telling the force touch pressure. I can unlock the phone but that is as far as it goes, unable to access xposed module or any other app. How do i uninstall or access this module, please help.
Click to expand...
Click to collapse
The solution is the same as during bootloop. Flash Xposed-Disabler-Recovery.zip to disable Xposed framework at recovery. or refer to http://forum.xda-developers.com/xposed/xposed-lollipop-stuck-bootloop-t3055816 for lollipop.
Added notification to disable this mod in v0.1.3!
j-a-c-k said:
Hi, tkgktyk.
Constant force close. Here is the xposed log, I hope it helps. http://pastebin.com/0tz04TcN
P. S. : Can't a arch log, please, use pastebin to get it.
Sent from my Galaxy Note III LTE
Click to expand...
Click to collapse
I'm sorry to trouble you, I uploaded wrong apk as v0.1.2. I forgot to rebuild apk at last after modifying.
I uploaded next apk v0.1.3 rebuilt surely.
After updating, please clear data of FTD before launching it.
Ok managed to download the latest version by accessing the website since going to xposed app shows only the old version. Gonna try the new one and report back.
Ok latest version installed , soft rebooted as instructed , dalvik cache got wiped after soft reboot, however the same issue is there , no matter how I touch The screen the pressure is always 1. Any value below 1 all touches are considered forces touches. Note edge running Resurrection remix 5.4.7.
Instead of putting everything in DEV forum, lets talk about the problems in this thread. So far I can confirm the following issues.
[*]In Call Volume - Not able to reduce it ( 5.0s )
[*]Radio is missing ( 5.0s )
[*]On screen navigation bar is missing in options - but can be enabled using setting/console ( 3.0/4.0s )
[*]Tri-state keys: If you switch from the very top to the very bottom quickly, the notification mode gets stuck at "priority" when it should be "all notifications".
[*]Hardware buttons: Haptic feedback does not work ( 2.0s )
[*]GPS ( for some users )( 2.0s )
[*]Notification LED always on upon notification.( 2.0s )
[*] No Charging LED ( 3.0s )
[*]Disable the "Swap Buttons" and enable "Double Tap yo wake" etc gestures, after a reboot they all change back to default.( 3.0s )
[*]After every reboot Time and Date is reset, but as I have auto update enabled, it resolves itself in about 10-15 secs
[*]SD card doesn't show on PC while connected by MTP( 5.0s )
[*]Speakerphone during calls do not work. No sound received going to the other line. However, once speakerphone is disabled everything works through the earpiece and microphone( 8.0s ) with Speaker Volume Fix Zip
[*]802.1x-EAP bug ( 8.0s )
[*]Call recording not working ( functionality as per @No-New-Phone - Instead use this http://repo.xposed.info/module/com.pyler.enablecmcallrec) or capps by cyanogen
[*]Speaker during call (11.0s)
[*]echo during call (11.0s)
[*] Google Voice Search & Commands [Workaround] - delete ro.product.brand from build.prop
[*] USSD doesn't show up after calls or messages - This is random only reported not working for Airtel India - Workaround http://forum.xda-developers.com/showpost.php?p=65002497&postcount=1988
Tristate keys are not stable
There are two more minor bugs I noticed:
4. Tri-state keys: If you switch from the very top to the very bottom quickly, the notification mode gets stuck at "priority" when it should be "all notifications".
5. Hardware buttons: Haptic feedback does not work.
Keep up the awesome work.
6. GPS (LocationServices)
Can confirm 4.
6 works for me, but many others seems to have problems.
7. BankID and swish (scandinavian banking apps) force closes when trying to start. They do work on other rooted phones and roms and on OPX with oxygenOS.
Should the build number be included in these bug reports ?
Things are moving forward so fast that it is difficult to track which bugs are still valid...
PWMx said:
Things are moving forward so fast that it is difficult to track which bugs are still valid...
Click to expand...
Click to collapse
And it's great
8. Recents key is stuck on menu for short tap and recents app for long tap. Changing action in settings doesn't do anything.
Sent from my ONE E1005 using Tapatalk
NAVIGON crashes upon opening. (GPS issue?)
Notification LED always on upon notification.
9. LED notification light stays solid white and does not blink (I saw a post about this in the dev thread.. is this fixed already?)
logock said:
NAVIGON crashes upon opening. (GPS issue?)
Notification LED always on upon notification.
Click to expand...
Click to collapse
MrKhozam said:
9. LED notification light stays solid white and does not blink (I saw a post about this in the dev thread.. is this fixed already?)
Click to expand...
Click to collapse
Yes, both GPS and notification light have been fixed, but the new build is not online yet.
There seems to be something wrong with microphones and/or noise cancellation.
Some people here reported that other persons can hear an echo in calls.
And google voice search and voice recognition don't work...
I have spoken to two persons since installing the rom and one was complaining about high volume from my end and the other about sound quality.
mawells787 said:
8. Recents key is stuck on menu for short tap and recents app for long tap. Changing action in settings doesn't do anything.
Sent from my ONE E1005 using Tapatalk
Click to expand...
Click to collapse
I can confirm. Also, long pressing the recent key brings up the recent list.
Sound is distorted. When changing governors i get reboots. It had no temp limit by default. My play store had transparent upper bar. Chrome had red bars around the screen sometimes. All and all it is not stable.
Date still resets to 1970 on reboot if automatic date & time (use network-provided time) is disabled.
(MA-12.1-20151212-onyx.zip)
Problem should probably be caused by the time_daemon in /system/bin/
Older CM12 builds for the klte (galaxy S5) had this problem also and there was a "manual" fix before it was included into official CM builds: http://forum.cyanogenmod.org/topic/105008-wrong-date-and-time-at-every-reboot/#entry504187
The official oxygen os does not suffer from this problem.
It's annoying to set correct date & time after every reboot. Hope this can get fixed.
fblaese said:
There seems to be something wrong with microphones and/or noise cancellation.
Some people here reported that other persons can hear an echo in calls.
And google voice search and voice recognition don't work...
Click to expand...
Click to collapse
I can confirm this. Another thing is: the microphone seems not to work if i use the speakers (hands free), i hope you understand what i mean.
br
For me the following is broken,
1. GPS
2. Google Voice Search & Commands
3. Notification LED is Static
4. After every reboot Time and Date is reset, but as I have auto update enabled, it resolves itself in about 10-15 secs
5. If I disable the "Swap Buttons" and enable "Double Tap yo wake" etc gestures, after a reboot they all change back to default.
6. SD card doesn't show on PC while connected by MTP
7. In-Call volume cannot be changed and person at the other end says sound is distorted.
That's all I have encountered as of now but I can't help but marvel at how smooth this thing is, I salute MasterAwesome for his work. And trust that he will fixx all these petty things, all in good time
Model - E1003
Flashed ROM by CM recovery AND by TWRP by eng.stk. issues remain the same.
Gapps used - open_gapps-arm-5.1-nano-20151212 (from opengapps.org )
Thanks
~Tapatalk'd v¡a my One Plus X
OK. Same issue here, led notification, in call volume, and Goole voice search. Also data and time auto fix after 30 seconds.
GPS WORKS like a charm.
My onyx is E003
---------- Post added at 08:26 AM ---------- Previous post was at 08:24 AM ----------
For everyone: I can't restore OnePlus Radio from titanium. I downloaded Spirit2 app from play store and radio FM works perfect with a lot of sfuff to manege eg. Equalizer, band, ui, etc
Same Issues With E1001
joshwin_aranha said:
For me the following is broken,
1. GPS
2. Google Voice Search & Commands
3. Notification LED is Static
4. After every reboot Time and Date is reset, but as I have auto update enabled, it resolves itself in about 10-15 secs
5. If I disable the "Swap Buttons" and enable "Double Tap yo wake" etc gestures, after a reboot they all change back to default.
6. SD card doesn't show on PC while connected by MTP
7. In-Call volume cannot be changed and person at the other end says sound is distorted.
That's all I have encountered as of now but I can't help but marvel at how smooth this thing is, I salute MasterAwesome for his work. And trust that he will fixx all these petty things, all in good time
Model - E1003
Flashed ROM by CM recovery AND by TWRP by eng.stk. issues remain the same.
Gapps used - open_gapps-arm-5.1-nano-20151212 (from opengapps.org )
Thanks
~Tapatalk'd v¡a my One Plus X
Click to expand...
Click to collapse
Hi!
I am too facing the same issues with the same flashing scenario with this build. I'm also having problems with
- tri-state-keys being stuck at priority and "none" not working
Admittedly, this is the best rom for 1+X atm but hoping these can be addressed at your earliest convenience @MasterAwesome. Btw, I'm using E1001. Everything else work like a dream.
TIA.
p/s: fyi, Cortana works flawlessly!
Settings crash when trying to connect to 802.1.x/EAP authenticated Wifi networks (WPA2 Enterprise).
Seems to be an issue with EAP-SIM...
logcat:
Code:
E/WifiStateMachine( 880): Exception: EAP-SIM not supported
D/AndroidRuntime(14031): Shutting down VM
E/AndroidRuntime(14031): FATAL EXCEPTION: main
E/AndroidRuntime(14031): Process: com.android.settings, PID: 14031
E/AndroidRuntime(14031): java.lang.NullPointerException: Attempt to read from field 'int android.net.wifi.WifiEapSimInfo.mNumOfSims' on a null object reference
E/AndroidRuntime(14031): at com.android.settings.wifi.WifiConfigController.checkEapSimInfo(WifiConfigController.java:825)
E/AndroidRuntime(14031): at com.android.settings.wifi.WifiConfigController.showSecurityFields(WifiConfigController.java:752)
E/AndroidRuntime(14031): at com.android.settings.wifi.WifiConfigController.<init>(WifiConfigController.java:334)
E/AndroidRuntime(14031): at com.android.settings.wifi.WifiDialog.onCreate(WifiDialog.java:68)
E/AndroidRuntime(14031): at android.app.Dialog.dispatchOnCreate(Dialog.java:373)
E/AndroidRuntime(14031): at android.app.Dialog.show(Dialog.java:274)
E/AndroidRuntime(14031): at android.app.DialogFragment.onStart(DialogFragment.java:490)
E/AndroidRuntime(14031): at com.android.settings.SettingsPreferenceFragment$SettingsDialogFragment.onStart(SettingsPreferenceFragment.java:590)
E/AndroidRuntime(14031): at android.app.Fragment.performStart(Fragment.java:2077)
E/AndroidRuntime(14031): at android.app.FragmentManagerImpl.moveToState(FragmentManager.java:922)
E/AndroidRuntime(14031): at android.app.FragmentManagerImpl.moveToState(FragmentManager.java:1067)
E/AndroidRuntime(14031): at android.app.BackStackRecord.run(BackStackRecord.java:834)
E/AndroidRuntime(14031): at android.app.FragmentManagerImpl.execPendingActions(FragmentManager.java:1452)
E/AndroidRuntime(14031): at android.app.FragmentManagerImpl$1.run(FragmentManager.java:447)
E/AndroidRuntime(14031): at android.os.Handler.handleCallback(Handler.java:739)
E/AndroidRuntime(14031): at android.os.Handler.dispatchMessage(Handler.java:95)
E/AndroidRuntime(14031): at android.os.Looper.loop(Looper.java:135)
E/AndroidRuntime(14031): at android.app.ActivityThread.main(ActivityThread.java:5294)
E/AndroidRuntime(14031): at java.lang.reflect.Method.invoke(Native Method)
E/AndroidRuntime(14031): at java.lang.reflect.Method.invoke(Method.java:372)
E/AndroidRuntime(14031): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:904)
E/AndroidRuntime(14031): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:699)
W/ActivityManager( 880): Force finishing activity 1 com.android.settings/.Settings$WifiSettingsActivity