Wow, I'm speechless, thousand thanks, I will organize a device this week and will be finally able to test GPS, RIL etc
Wow, I'm speechless, thousand thanks, I will organize a device this week and will be finally able to test GPS, RIL etc
So i'd like to get my own build running, however on the github page i couldn't find a matching device_n7100 with lineage-18.1 branch.
So i wonder how did you built this rom?
Everything except boeffla audio is included in the kernel, I've reverted these things because of a real low audio volume and other issues.However i'm missing all the boeffla tweaks which could be accessed by tweaks.rc in /vendor/etc/init/
Hmm if it's empty, then it may not be a kernel crash.So far, i experienced random reboots from time to time (mostly when screen is off)
last_kmsg is invalid, shows only initial bootup but no crash messages. (may try again grabbing directly from twrp)
Because it's disabled by default in the settings, just enable itS Pen works, however the small cursor (circle) isn´t showing up onscreen.
Camera takes pictures, video capture is crashing the media server (can´t connect to camera).
I will re-fix the microphone recording today, this fix got lost with my last sycn...Built in recorder crashes when trying to record audio, maybe video capture has the same issue.
Yep:All animations are disabled in dev settings by default. (for a reason?)
These things are kown, but thanks for your report.GPS, compass is broken
Orientation sensor doesn´t respond (auto rotation works though)
Magnetic sensor doesn´t respond.
There are a few n7100 on ebay.de. The prices are around 40 eur. There are cheaper options, but my German is non-existent to understand the nuance....
I wasn't able to buy a device so far, so it's not easy to fix GPS, but it should work already on LOS 19.0.
I'm searching in austria and try again to buy one, I will keep you updated.There are a few n7100 on ebay.de. The prices are around 40 eur. There are cheaper options, but my German is non-existent to understand the nuance.
GPS somewhat works in LOS-18 (it found a satellite, but no fix), I reported this before. It was later when I tried LOS-19, I found that GPS works better with the old API set in the developer options and in GPStest app. So, try fiddling with the options and also try it outside.
Sorry, Austria of course!
Since I can test GPS by my own, I've recognized the same behaviour.- GPS & compass works, but after ~15 mins did lost satellites and only able to fix with reboot. Not sure yet if this happens constantly so will continue tests.
Did you enable the s-pen hovering in the settings?- there is no cursor of spen, but itself hover works (i think this was reported already)
I've only tested to read and write nfc tags, which worked fine. I'm not sure what gpay exactly needs.- there is no NFC option in "connected device" settings, but can turn on/off in main menu, while i'm not yet sure if it works at all - gpay says "touch payment not available", i do PASS all safetynet tests + have all possible GPAY fixes and even certified device in google play market, seems like it just cannot detect NFC module. I'll try to find a way to test NFC later - using some NFC marker so will know if it actually works in this ROM or it just do nothing, but i'm 100% sure it did worked in past on stock 4.4 android.
Someone reported a similar issue in an other thread (other device), this may be an issue which will be fixed with the next sync.EDIT: can't choose wallpaper using settings - it just reloads after selecting proper file in "my files", can setup those using gallery but then its same for lock & home screen. want to setup different ones. This thing worked just fine in 12 rom
Ok thanks, hopefully this will be fixed later.Since I can test GPS by my own, I've recognized the same behaviour.
Hmm, where exactly located this setting? Can't find it seems, or its named somehow weird in my language.
Well, i have feeling that there is still some missing part of api or something, since there is no proper settings option etc. Also just saw this is logs:I've only tested to read and write nfc tags, which worked fine. I'm not sure what gpay exactly needs.
02-07 14:25:13.684 5925 17504 W TapAndPay: platformSupportsGooglePay: true [CONTEXT service_id=79 ]
02-07 14:25:13.685 5925 17504 W TapAndPay: hasManagedProfile: false [CONTEXT service_id=79 ]
02-07 14:25:13.686 5925 17504 W TapAndPay: isChromeOsDevice: false [CONTEXT service_id=79 ]
02-07 14:25:13.686 5925 17504 W TapAndPay: isUncertifiedDevice: false [CONTEXT service_id=79 ]
02-07 14:25:13.686 5925 17504 W TapAndPay: deviceSupportsTokenization: true [CONTEXT service_id=79 ]
02-07 14:25:13.687 5925 17504 W TapAndPay: isGooglePayEnabled: true [CONTEXT service_id=79 ]
02-07 14:25:13.693 5925 17504 E CardEmulation: This device does not support card emulation
02-07 14:25:13.693 5925 17504 W TapAndPay: Getting CardEmulation instance failed. [CONTEXT service_id=79 ]
02-07 14:25:13.693 5925 17504 W TapAndPay: java.lang.UnsupportedOperationException
02-07 14:25:13.693 5925 17504 W TapAndPay: at android.nfc.cardemulation.CardEmulation.getInstance(CardEmulation.java:165)
02-07 14:25:13.693 5925 17504 W TapAndPay: at bcul.<init>(:[email protected]@21.48.16 (150300-420364950):0)
02-07 14:25:13.693 5925 17504 W TapAndPay: at com.google.android.gms.tapandpay.hce.task.TapAndPayAidRegistrationTaskOperation.a(:[email protected]@21.48.16 (150300-420364950):5)
02-07 14:25:13.693 5925 17504 W TapAndPay: at com.google.android.gms.tapandpay.gcmtask.TapAndPayGcmTaskChimeraService.a(:[email protected]@21.48.16 (150300-420364950):4)
02-07 14:25:13.693 5925 17504 W TapAndPay: at ajyg.call(:[email protected]@21.48.16 (150300-420364950):4)
02-07 14:25:13.693 5925 17504 W TapAndPay: at java.util.concurrent.FutureTask.run(FutureTask.java:266)
02-07 14:25:13.693 5925 17504 W TapAndPay: at voc.c(:[email protected]@21.48.16 (150300-420364950):6)
02-07 14:25:13.693 5925 17504 W TapAndPay: at voc.run(:[email protected]@21.48.16 (150300-420364950):7)
02-07 14:25:13.693 5925 17504 W TapAndPay: at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
02-07 14:25:13.693 5925 17504 W TapAndPay: at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
02-07 14:25:13.693 5925 17504 W TapAndPay: at vub.run(:[email protected]@21.48.16 (150300-420364950):0)
02-07 14:25:13.693 5925 17504 W TapAndPay: at java.lang.Thread.run(Thread.java:923)
02-07 14:25:13.702 5925 24143 I NetworkScheduler.Stats: Task com.google.android.gms/com.google.android.gms.tapandpay.gcmtask.TapAndPayGcmTaskService finished executing. cause:4 result: 3 elapsed_millis: 55 uptime_millis: 56 exec_start_elapsed_seconds: 31718 [CONTEXT service_id=218 ]
K, thanks.Someone reported a similar issue in an other thread (other device), this may be an issue which will be fixed with the next sync.
GPay needs special functionality, called NFC-HCE or host based card emulation which in fact doesn´t work on most devices/ROMs as far as i know.Did you enable the s-pen hovering in the settings?
I've only tested to read and write nfc tags, which worked fine. I'm not sure what gpay exactly needs.
Thanks, never spend any time for gpay, because I'm not that guy who would use it.GPay needs special functionality, called NFC-HCE or host based card emulation which in fact doesn´t work on most devices/ROMs as far as i know.
And gpay also requires SafetyNet to pass and SELinux enforcing aswell.
So it probably only works in stock, dunno if this is a requirement for official lineage but i think even officially supported devices may not support NFC-HCE while running lineage.
Btw. i couldn´t find any S-Pen related settings.
Where is it supposed to be located at?
SafetyNet test and SELinux enforcing is not a problem at all, since i already can pass it. So yeah its something else...GPay needs special functionality, called NFC-HCE or host based card emulation which in fact doesn´t work on most devices/ROMs as far as i know.
And gpay also requires SafetyNet to pass and SELinux enforcing aswell.
So it probably only works in stock, dunno if this is a requirement for official lineage but i think even officially supported devices may not support NFC-HCE while running lineage.
Btw. i couldn´t find any S-Pen related settings.
Where is it supposed to be located at?
Have no idea, because i did switch from stock 4.4.2 to this roms (12 and 11 now) after got most of apps not working because of outdated version.
Hmm.. don't see option for enable cursor here. But thanks)
Because this setting is in the language part.
Oh, works! Big thanks! But location of this settings is way deep to find it myselfBecause this setting is in the language part.
Settings->Sytem->Languages and Input->Show icon when using stylus
Thanks man, in logs i can see that system_server and com.google.android.gms eat cpu a lot, so lags because of this guess. but don't know why.Ok that's crazy, I will check this tomorrow, there were nor RIL relevant changes,
Go to settings -> Screen -> Styles and wallpaper -> first tab (wallpaper) -> click on "my photos" (gallery popup) -> choose any file -> after that getting crash.What do I have to try, to use an image out of the gallery or what?
Sorry, I have so much work todo at the moment, that I've forgot to check this,Any news on this? since its way critical issue, must reboot each time after phone call.
Works for me on n7100, are you sure updated properly?I downloaded the last update. everything is fine but mobile data is not working. can you please fix it?
Thanks a lot! While we have still tons of issues but most of them are minor and this rom is pretty usable for most cases. And i did bought your app as small support as well)
yes I tried your lineage os 18.1 and 19.1, but mobile data is not working. what is the solution for this?
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
*/
This thread has 65 posts. 39 of them is from you (60%). Approximately 1 of those is somewhat helpful to the development of the rom, the other 38 is comprised of asking questions and making demands.