Closed Spookcity closed 4 years ago
@HaxXorHardy Beanstalk updated. Have a look at the main post on XDA for some important details. XDA
@Spookcity The calm before the storm? What awaits us in the new test version of the kernel?)
@Oleggluk Yes, I have just spent my rather limited free time the last little while trying to help out as much as I'm able with some LOS 15 issues. I was actually going to release a test build today. I built it,but it throws an error while flashing about the image being too large for the boot partition. Which is strange,but I've obviously messed something up. I will try my best to look into it and hopefully get it sorted in the next few days.
Sent from my Samsung SM-G800F using FastHub
Spookcity_Kernel-N - Test v5.1
Changes:
There are other features that I have already added (CPU gov's etc) that are currently partially broken,so they are not included in this build. I will hopefully have more time in the near future to work on this kernel.
Download Spookcity_Kernel-N_v5.1 Download Spookcity_Kernel-N_v5.1-1500mhz (untested)
here and problem with Spookcity_Kernel-N_v5.1-1500mhz tension on 1500mhz isn't regulated (( help please, I thanks
@hard-sat Ugg,sorry about that. This is the same problem as with the last 1500mhz version. Hopefully I can remember how I fixed it. I have been pretty busy,but will look into it and release a fixed version as soon as I have some time.
Edit: @hard-sat I think I have fixed this issue. The new build is in the same post above. Hope it works now.
Sent from my Samsung SM-G800F using FastHub
this problem is solved, we wait for updates, I thank ))
@spookcity With 5.1, still Crashes within minutes :( I really think it's a F2FS problem, can you / somone try to use this kernel with data and cache as F2FS? Thx
@friedensfurz Hmm,that's a shame. Thanks for letting me know. I have been really busy lately with real life things and the limited free time I've had has been spent trying to sort out some audio issues with LOS 15. I'm not really sure what I would have done to cause this problem. Particularly with F2FS. I will need to have a look into. Which I will when I have the time.
Sent from my Samsung SM-G800F using FastHub
@Spookcity Los15 is interesting. Calls already working? I tested the prealph version a little. And what are the problems with sound? I remember there the music played well. I also noticed a lot of settings for bluetooth in the developer parameters, but there was no way to check it.
@Oleggluk Yes,Tobias fixed the ril problem,so calls work now. Sound was working fine,but something has changed and no longer works. I've tried many things to try to figure this out (reverting things,applying found patches etc.) with no luck so far. It's very confusing. I'm sure Tobias will figure it out though when he has the time.
Sent from my Samsung SM-G800F using FastHub
so what is working and what isn't now in LOS 15? I have a bit of free time and I could install again Linux and try to build to see what's (not) working now
@vonico The only thing that doesn't work in my testing and useage is audio (ringtones, music player,etc) Phone calls work fine now. Audio worked before,but no longer does for some reason. I've given myself a headache trying to sort that out,so I've taken a break. I'm sure its something simple that I'm just overlooking. Tobias is away,but I'm sure he'll figure it out when's he's back if I'm unable.
Edit: Some things I've not used,but just thought about and am pretty sure still don't work are GPS and NFC. Camera does now though.
Sent from my Samsung SM-G800F using FastHub
@Spookcity great! Can somebody build LOS 15? I am too busy to do it myself this weekend and would like to at least try it out!
@vonico I've built LOS15 many times in the last few days. Luckily I have sorted out the audio problem and have built yet again. You can test it out no prob: lineage-15.0-20171006-UNOFFICIAL-kminilte
Edit: I also applied a patch for home button wake as it was driving me insane hah
@Spookcity already downloading Thank you very much! 😊😊
@Spookcity @vonico Does anyone have problems with memory on los15? Applications do not see memory and a memory card. The camera also does not see the memory.
@Oleggluk Interesting. The camera, you are right,has a problem with picking it up. The camera still needs more work. My internal and external card are picked up fine though other than the camera.
Edit: I need to test more. I've not tried many apps. I now understand what you're saying. I will test this out later as I'm currently away,so I'm using another ROM. Feedback like this is very good though and will help in fixing things.
Sent from my Samsung SM-G800F using FastHub
@Spookcity My any installed applications do not see memory and a memory card.
Редактировать: I'll now try to make a complete format with the removal of all files
@Oleggluk Yeah,I realized that's what you meant after I read your post better. I don't think I tested this,so this may indeed be an issue. I'll flash it later,test and grab a log and go from there. Thanks for reporting
Sent from my Samsung SM-G800F using FastHub
@Spookcity A complete deletion of all files from the phone does not help. Applications do not see memory or write that there is no access.
@Oleggluk OK,this explains the camera issue then. I guess it's a system wide issue. Did you have this problem when you tested the build on XDA?
Sent from my Samsung SM-G800F using FastHub
@Spookcity I did not use this version for a long time, as there were constant reboots. But then I managed to install x-plore and from it a couple of applications., So x-plore saw the memory.
@Oleggluk OK,yeah the reboots were caused by a kernel issue that Tobias fixed. I'll try to look into the storage issue soon though.
Sent from my Samsung SM-G800F using FastHub
@Spookcity my camera also says to insert an sd card before being able to use it, although I have one. I also have trouble restoring my whatsapp chats backup, but I guess that doesn't have that much to do with the ROM though... other than that, everything else is working really smoothly and without any issues at all :)
That said, I do miss some personalization options such as locking the lock screen to only portrait, or to configure the button's behavior, but again I guess that's just not implemented in Lineage yet.
@Spookcity People are asking to make the kernel support TTL fixing. Some operators block the distribution of the Internet, but there are instructions on how to get around this. But the kernel must support the fixation of ttl. Quote: "On the operators of the Big Three, as well as Tele2, in contrast to the Iota TTL must be fixed, not changed. And it's on 64, and it's on the distributing. Others do not work. In addition, this device should be supported at the kernel level: if there is no TTL line in the file / proc / net / ip_tables_targets, then you need to change / compile the kernel.
@Oleggluk Yeah, I don't know much about this,but thanks fro providing the info. I will certainly look into it. It sounds rather easy from what you wrote.
@vonico Yeah.I am going to try to look into this storage issue later. LOS 15 is still in the early days,so it is missing a lot of features. I built AICP 13 as well,but it is simply LOS 15 at this point. In time more things will come.
@Spookcity Is AICP 13 also a memory issue?
@Oleggluk Honestly I'm not sure. I didn't test it. I would assume so though as it must be a device issue. Hopefully I'll have a little time later today to see about this.
Sent from my Samsung SM-G800F using FastHub
@Spookcity I have a lot of time today, I can check if you give me a link
@Oleggluk I don't have the AICP build any longer. I still have the sources though,but I was talking with Tobias and his build (the one on XDA) does not have the problem with memory/storage. That may make it easier. Either I just did something wrong...A new patch that has been added since his build or perhaps the sources have caused this issue. I think its more likely one of the first 2. I am going to try to build again shortly and see if I am able to sort it out. I will keep you posted.
@Oleggluk Any particular apps that don't detect storage? Aside from the camera. I would like to test. I tested the browser and it was not a problem.
@Spookcity for example, the x-plore file manager does not show partitions of internal and external memory at all.
@Oleggluk OK thanks,I just installed MiXplorer and indeed same thing.
Edit: Well kinda. It doesn't show the internal or external storage,but if I click to show images or audio for example,it displays everything correctly.
@Spookcity I tried downloading a pdf and it also told me that no sd card was detected. Also in whatsapp, I get an error when downloading pictures, besides from not being able to restore the backup I made...
@Spookcity It's strange, the system sees well the memory and the memory card, extracts the memory card without problems, all the volume readings and the names are correct., But somewhere something prevents the applications from seeing the memory and writing to it. I hope it will not be difficult to fix it
@vonico OK,thanks for the info. Interesting. I downloaded something via the browser app and had no issues.
@Oleggluk You are exactly right. This is exactly whats happening. I will mess with it a little more and see if I'm able to sort it out.
@Spookcity good luck! When you come up with a new build I'll be ready to try it out! :)
Alright,well I was unable to solve this yet. Its a strange issue. I have downloaded many things via the browser without issue. There's certainly something strange about it,but the logs didn't really show anything. I'm off for now,but if anyone can get any useful logs of the problem,particularly WhatsApp or similar that'd be great and I'll gladly have a look and try some other things tomorrow.
Sent from my Samsung SM-G800F using FastHub
@Spookcity But the program for logs can not save it as it will not see the memory)). Do I have to do this via adb on my computer? What commands need to be entered in adb for the correct log and how to save it in txt?
I got a logcat when downloading a picture in Whatsapp and another log when downloading the file in chrome logcat_whatsapp.txt logcat_chrome.txt
EDIT: idk if this is related, but I also see these lines quite often in the log just with the phone plugged in:
10-07 18:01:46.492 13846 14107 E android.hardware.memtrack@1.0-impl: hw_get_module memtrack failed: -2
10-07 18:01:46.494 13846 14107 E memtrack: Couldn't load memtrack module
10-07 18:01:46.494 13846 14107 W android.os.Debug: failed to get memory consumption info: -1
@vonico Many thanks! The lines you posted are not relevant to this issue I don't think. I'll have a look at your logs when I'm home later. Thanks again!
Sent from my Samsung SM-G800F using FastHub
@Spookcity I think this one is more detailed:
10-07 18:46:09.388 2052 3773 I AudioHardwareTinyALSA: AudioStreamOutALSA::write setDevice
10-07 18:46:09.388 2052 3773 E AudioHardwareTinyALSA: int android::AudioHardwareTinyALSA::open_hdmi_driver() cannot open video16 (-1)
10-07 18:46:09.388 2052 3773 D AudioHardwareTinyALSA: OutALSA::setDevice: mode = 0, newDevice=0x2, currentDevice=0x2 ,force= 0
10-07 18:46:09.388 2052 3773 D AudioHardwareTinyALSA: OutALSA::setDevice: mDevice 0x2, newDevice = 0x2
10-07 18:46:09.388 2052 3773 D AudioHardwareTinyALSA: setOutputVolume
10-07 18:46:09.388 2052 3773 D TinyUCM : setModifier Normal, en=1
10-07 18:46:09.388 2052 3773 E TinyUCM : modifier doesn't exists any more
10-07 18:46:09.388 2052 3773 I AudioHardwareTinyALSA: OutALSA::setDevice: mHandle NULL mode[0], Device[00000002]
10-07 18:46:09.389 2052 3773 I AudioHardwareTinyALSA: Open: mDefaults->direction=0 device=3
10-07 18:46:09.389 2052 3773 D AudioHardwareTinyALSA: Channel: 2, Samplerate: 48000, Format: 0, Peroid Size: 960, Period Count: 4
10-07 18:46:09.389 2052 3773 D AudioHardwareTinyALSA: ALSAStreamOps::open: after pcm_open: Card: 0, Device: 3
10-07 18:46:09.389 2052 3773 I AudioHardwareTinyALSA: before pcm_prepare
10-07 18:46:09.389 2052 3773 D AudioHardwareTinyALSA: [NXP] set PcmInterface is called
10-07 18:46:09.390 2052 3773 D AudioHardwareTinyALSA: setPcmInterface: Stream=0x1, iSamplerate=8000++
10-07 18:46:09.390 2052 3773 D AudioHardwareTinyALSA: setPcmInterface--
10-07 18:46:09.401 2052 2187 D AudioFlinger: mixer(0xaf983d40) throttle end: throttle time(32)
10-07 18:46:09.520 19384 24389 I System.out: Error inflating SSL session: error:100000a0:SSL routines:OPENSSL_internal:INVALID_SSL_SESSION
10-07 18:46:09.699 2045 2045 I display : [DYNAMIC_RECOMP] GLES_2_HWC by high FPS(60)
10-07 18:46:10.254 19384 19452 D WhatsApp: LL_D W [8926:WriterThread] SEND <iq id='00' xmlns='w:stats' type='set' to='s.whatsapp.net'><add t='1507394770'>WAM%03%88!%01%07SM-G800%20i0%0b%02%80%0d%0fsamsung-SM-G800%80%0f%058.0.0H%8f%02%c0%00%88%ef%01%08kminilteP/%a5%03%d9Y%80%11%082.17.368H%b1%02%dc%07%20%15%20%178y%06%038{%06%02%88%1f%01%07samsung)%16%02%12%01B%02%15%02V%03%b5%c0%0f%00)%cc%01"%01"%02F%03%14%02)%de%01"%01%12%03%12%04"%052%06%026%07%02)%c2%01"%012%02%02%12%04"%05F%06f%05P/%a6%03%d9Y)%cc%04%82%01%03mmgB%03u%02B%04%94%00%16%05P/%a7%03%d9Y%19%c8%012%01%022%02%0a%12%04%12%11%12%08%82%09%03mmg%12%0b%12%0c2%10%04B%05%18%02R%06%dd%a8%01%00B%0d%f1%012%0e%06B%0f%ff%01%12%132%14%02%16%15)P%03"%012%02%02B%03%ca%02V%04[%df%00%00P/%a8%03%d9Y%19%c8%012%01%022%02%0a%12%04%12%11%12%08%82%09%03mmg%12%0b%12%0c2%10%04B%05?%01R%06%8b%a1%01%00B%0d*%01"%0eB%0f<%01%12%132%14%02%16%15P/%aa%03%d9Y%19%c8%012%01%022%02%0a%12%04%12%11%12%08%82%09%03mmg%12%0b%12%0c2%10%04B%05v%03R%06"/%02%00B%0de%03"%0eB%0fs%03%12%132%14%02%16%15P/%ab%03%d9Y%19%c8%012%01%022%02%0a%12%04%12%11%12%08%82%09%03mmg%12%0b%12%0c2%10%04B%05%1f%01B%06q=B%0d%0d%01"%0eB%0f%1c%01%12%132%14%02%16%15P/%ad%03%d9Y%19%c8%012%01%022%02%0a%12%04%12%11%12%08%82%09%03mmg%12%0b%12%0c2%10%04B%05%1d%01R%06%13%99%03%00B%0d%0b%01"%0eB%0f%1b%01%12%132%14%02%16%15P/%d8%03%d9Y)V%03"%02"%03%12%07"%08F%0b9%03P/%e0%03%d9Y)%de%01"%01%12%03%12%04%12%052%06%02&%07)%c2%01"%01"%02%12%04%12%05F%06%a4%02P/%d2%04%d9Y%19%c8%012%01%022%02%0a%12%04%12%11%12%08%82%09%03mmg%12%0b%12%0c2%10%04B%058%03R%06%dd%a8%01%00B%0d%03%03%12%0eB%0f%16%03%12%13"%14%16%15</add></iq>
10-07 18:46:10.352 2045 2045 D SurfaceFlinger: duplicate layer name: changing com.whatsapp/com.whatsapp.Conversation to com.whatsapp/com.whatsapp.Conversation#1
10-07 18:46:10.372 2045 3775 W GrallocMapperPassthrough: buffer descriptor with invalid usage bits 0x400
10-07 18:46:10.382 19384 19395 I zygote : Background concurrent copying GC freed 32479(2MB) AllocSpace objects, 10(408KB) LOS objects, 49% free, 4MB/8MB, paused 5.202ms total 127.725ms
10-07 18:46:10.410 2045 2647 W GrallocMapperPassthrough: buffer descriptor with invalid usage bits 0x400
10-07 18:46:10.445 2045 2109 W GrallocMapperPassthrough: buffer descriptor with invalid usage bits 0x400
10-07 18:46:10.511 19384 24293 D WhatsApp: LL_D W [8954:ReaderThread] RECV <iq from='s.whatsapp.net' type='result' id='00'/>
10-07 18:46:11.218 19384 24305 W OkHttpClient: A connection to https://mmg.whatsapp.net/ was leaked. Did you forget to close a response body?
10-07 18:46:11.219 19384 24305 I chatty : uid=10102(u0_a102) OkHttp Connecti identical 4 lines
10-07 18:46:11.219 19384 24305 W OkHttpClient: A connection to https://mmg.whatsapp.net/ was leaked. Did you forget to close a response body?
10-07 18:46:11.944 2045 2045 I display : [DYNAMIC_RECOMP] HWC_2_GLES by low FPS(2)
10-07 18:46:12.198 2045 2045 I display : [DYNAMIC_RECOMP] GLES_2_HWC by high FPS(59)
10-07 18:46:12.434 2052 2187 D AudioHardwareTinyALSA: Entering AudioStreamOutALSA standby mode
10-07 18:46:12.434 2052 2187 V AudioHardwareTinyALSA: closePcmInterface++
10-07 18:46:12.435 2052 2187 V AudioHardwareTinyALSA: closePcmInterface--
10-07 18:46:12.435 2052 2187 I AudioHardwareTinyALSA: Close mHandle:b1740420
10-07 18:46:15.144 2259 2294 E memtrack: Couldn't load memtrack module
10-07 18:46:15.144 2259 2294 W android.os.Debug: failed to get memory consumption info: -1
10-07 18:46:15.293 2259 2294 E memtrack: Couldn't load memtrack module
10-07 18:46:15.293 2259 2294 W android.os.Debug: failed to get memory consumption info: -1
10-07 18:46:15.371 2259 2294 E memtrack: Couldn't load memtrack module
10-07 18:46:15.372 2259 2294 W android.os.Debug: failed to get memory consumption info: -1
10-07 18:46:16.324 2045 2045 I display : [DYNAMIC_RECOMP] HWC_2_GLES by low FPS(3)
@vonico Thank you! I am not really sure what to think though. Your chrome log didn't show anything. The only thing that stands out to me in the Whatsapp logs are the OkHttpClient warnings. I'm unsure if this is the problem though. I was able to download things fine with the stock browser. I will try chrome and see what happens. I will also try to search about the memtrack errors. This seems to be some problem although I'm pretty sure not related to this.
Edit: This seems to be this issue.From my Chrome log: W/MediaScanner( 487): Error opening directory '/mnt/sdcard/.android_secure/', skipping: Permission denied
Hmm strange.. Maybe changing the permissions in recovery explorer fixes it?
I don't think that would fix it. I tried a few things via adb shell,but that didn't work either. I'll try to look more into it tomorrow if I have time. Its weird that it's not all apps though. Like the default browser works fine,but obviously Chrome,WhatsApp and the camera do not.
Sent from my Samsung SM-G800 using FastHub
all are silent, and I also did not note a problem (( in Spookcity_Kernel-N_v5.1-1500mhz the problem with tension is solved, BUT new frequency 4294967 appeared again (( help please!!! I thank
@hard-sat I guess I messed something up with the steps or something. I am rather busy,but will see if I can fix it soon.
So this storage issue with LOS 15 appears to be an sdcardfs problem. I have successfully download stuff with Chrome and my storage now shows up in MiXplorer as well. This was achieved by disabling sdcardfs. This is not a proper fix though.
@Spookcity Want Want )
A continuation of #10, #18, #19, #20 and #21