[DISCUSSION] RIL Problem in E980/F240 - LG Optimus G Pro

Hi, this is United Oxygen.
We're delaying our kernel/ROM release date because of very unstable RIL.
Too lazy catching signal, often RIL goes off to heaven etc...
When we fix RIL almost, then battery leak happens...
So we're in slump.
We want to ask you, is there any RIL problem in Official CyanogenMod 12.1 in e980.

There is RIL problem in every ROM, even in AOSP based (I'm maintaining unofficial slim build). RIL sometimes picks network up right away, sometimes seems too lazy to pick-up the network for 20-30s and after that is OK.
Our device libs need some serious updating, that's the main reason why this is happening...
In the meantime, I can give you the commits which will fix that for CM based ROMs - you'll need to patch frameworks_opt_telephony and android_device_gproj-common, that will make RIL work for after initial 20-30s of insanity..

If that's the case, that explains why the last pac rom 5.0 seems to never pick up the signal. I thought @emannuel's zip patch does a good job of fixing the problem. Blisspop seems to do a good job of picking up the signal, have any of you consulted @nerdyblond about the RIL issue?

No matter how you patch it (Emmanuel's patch, or Jan's patch I'm using) you'll have to maintain telephony_opt repo because it changes constantly, I had more work updating my fork of telephony repo than porting Slim.
Sent via carrier pigeon.

ShadySquirrel said:
No matter how you patch it (Emmanuel's patch, or Jan's patch I'm using) you'll have to maintain telephony_opt repo because it changes constantly, I had more work updating my fork of telephony repo than porting Slim.
Sent via carrier pigeon.
Click to expand...
Click to collapse
We think 20-30 secs delay may be come from rild problem.
And, we've also found that when rild crash is happening, Force Stopping com.android.phone process restores the signal according to log.
So, we're really looking foward to e980 developers to make this scripts : when rild crash happens, force stop com.android.phone process, then signal will be restored.

Genie's said:
We think 20-30 secs delay may be come from rild problem.
And, we've also found that when rild crash is happening, Force Stopping com.android.phone process restores the signal according to log.
So, we're really looking foward to e980 developers to make this scripts : when rild crash happens, force stop com.android.phone process, then signal will be restored.
Click to expand...
Click to collapse
For me, RILD crashes after telephony tries to set subID, and quickly recovers, and it all quckly happens while phone is still booting. After boot, phone has network connection on primary (and only slot), but after that it just keeps searching for additional slots/IDs - possibly connected to dual-sim support introduced earlier this year.
Only way to fix this without workarounds is to fix device's ril and libs, other stuff is just simple workarounds to make it somehow work...

ShadySquirrel said:
For me, RILD crashes after telephony tries to set subID, and quickly recovers, and it all quckly happens while phone is still booting. After boot, phone has network connection on primary (and only slot), but after that it just keeps searching for additional slots/IDs - possibly connected to dual-sim support introduced earlier this year.
Only way to fix this without workarounds is to fix device's ril and libs, other stuff is just simple workarounds to make it somehow work...
Click to expand...
Click to collapse
It is hard for us to fix ril and libs, so we've thought about workarounds, and found that closing com.android.phone process forcely makes RIL recovered.
If you test this method on your E980?

Genie's said:
It is hard for us to fix ril and libs, so we've thought about workarounds, and found that closing com.android.phone process forcely makes RIL recovered.
If you test this method on your E980?
Click to expand...
Click to collapse
I'm using this one: http://review.cyanogenmod.org/#/c/108153/ on CM-based ROMs, Slim doesn't need any kind of those fixes - it simply works, takes some extra time but it simply works, logs don't even show any crashes/segfaults (at least not for me). I can't even enter my PIN fast enough after boot, I'm already connected to the network so killing com.android.phone will just make some mess for me. E988 variant, flashed from stock Jellybean.
I'm trying different approach: I've extracted my old KitKat backup and I'm hunting down libs needed for RIL to work. If I manage do make it work faster that way, I'll post the (flashable) zip and push changes to my git.
Update on that: pushed all needed libs, rild seems to be starting but it continuously restarts with "memory violation" from audit. Gah. Maybe something more is missing?

Related

[ROM] [24/12/15] [Unofficial] CM 10 for HTC Desire 300 [Public Beta]

Unofficial CM 10 for HTC Desire 300 (g3u)
device_htc_g3u v0.8b (24/12/15)
Traded stagefright bug for a new kernel
(no more stagefright and a freshly compiled kernel)
device_htc_g3u v0.77b3 (04/10/14)
Battery comsumption (hot)fix
(rls should no longer drain your device)
device_htc_g3u v0.77b2 (01/10/14)
Wifi is working
(wifi0 is forced into compliance)
device_htc_g3u v0.77b (25/9/14)
jellybean
(nom nom nom)
Full Disclosure
This is my first android project, so go easy on me.
Project Status
It's usable as a phone
So any willing beta testers are welcome to join the 'fun' and report further bugs.
Project !Status
mobiledata works but will drain your battery
(if you need to use it, reboot after switching it off)
libaudio is not fully functional
(stock has no mic unless in a call and custom has no speaker)
USB only works in mtp mode
(mass_storage mode appears to be incompatible with rmt_storage)
FM Radio not available
(required apps are currently not compiling)
Camera (front) appears unstable
(didn't bother to check what might be the cause)
TODO
[high priority]
fix libaudio (recording in stock or speaker in custom)
[medium priority]
fix libril -> mobile data drains the battery
[low priority]
enable apps2sd -> 2GB internal should suffice for the time being
check if cm supports proximity & light sensors -> they do work fine
fix mass_storage -> mtp is working
fix video recording -> it's a phone not a camcorder
fix video playback -> at least they are running
fix camera -> it's a phone dammit
find a better fix for wifi -> it works for now
fix graphical glitches
Disclaimer
Use at you own risk. This is a public beta and not meant for daily use. Please keep that in mind.
I can not be held accountable for any damage you might cause to your device if you decide to flash this file.
Requirements
HTC Desire 300 with unlocked Bootloader and custom recovery
(S-ON or S-OFF does not matter)
Download
Click me if you want the initial wifi free version (9d0a8fcca957d09dbaf306a1986d14dd)
Click me if you want to drain your battery (688c2779b4864ed9b568260477708049)
Click me if you like the stock kernel (1ba8a225bc7772f34f1e56bff51bfe27)
Click me if you dare (78bbcf5bf0eb26520efff6d49adac106)
Warning!!! If you are not a certified beta tester the zip file might explode upon extraction!!! You have been warned!
Installation
Enter recovery and begin by backing up your current system.
Next choose Wipe Data / Factory Reset from the main menu and Wipe Dalvic from the advanced submenu.
Last but not least use the mount submenu to format system.
Now use sideload or zip install to start beta testing this tasty jellybean.
Special Thanks
go out to anyone who has ever contributed something to a msm8225, ath6kl or htc related android project
device_htc_g3u
kernel_htc_g3u
Branch: Android 4.1.2
Version: 3.4.0-g12f638f
Config: g3u_defconfig
Toolchain: arm-eabi-4.6
Click to expand...
Click to collapse
compiled by 4m8
(My mind is a swirling miasma of scintillating thoughts and turgid ideas.)​
What are the requirements ? I guess I should use the only recovery available for the device ? and also, since we don't have s-off working for this device I think we have to flash the boot.img right ?
I'd recommend using the recovery from this build for the job. It won't crash unlike the philz version.
And no, you don't need to flash boot seperately. The only requirement is an unlocked bootloader.
S-ON only protects hboot and radio from flashing so you can safely install this release from the recovery.
Don't forget to backup your current system.
I'm downloading the files now, will test and report ASAP
Can i promote this in 2 german Forums? ist German translation available?
when do you think you will fix wifi?
HUGE THANKS IN FORWARD FOR COMPILING CM!
After the experiment:
the Rom stable and fast, but Wi-Fi does not work and do not contain FM radio
Front camera not working
I wish you success in your work and I hope you update the version of Android to be higher than 4.1.2
Thank you very much ..
4m8 said:
I'd recommend using the recovery from this build for the job. It won't crash unlike the philz version.
And no, you don't need to flash boot seperately. The only requirement is an unlocked bootloader.
S-ON only protects hboot and radio from flashing so you can safely install this release from the recovery.
Don't forget to backup your current system.
Click to expand...
Click to collapse
In which way will PhilZ CWM crash? will it still install the rom or not? will it brick my phone?
bassam_tayyan said:
After the experiment:
the Rom stable and fast, but Wi-Fi does not work and do not contain FM radio
Front camera not working
I wish you success in your work and I hope you update the version of Android to be higher than 4.1.2
Thank you very much ..
Click to expand...
Click to collapse
Ah yes FM. It's included in the custom libaudio that can't connect to the speaker.
Which I currently simply replace with the stock lib to make it work as a phone so it can be used to test battery consuption etc.
Sadly the cm apps used for fm won't compile for me. So even if I get libaudio working FM would still be untestable without non cm apps.
I'll add it to the todo once the libaudio trouble is resolved.
The wifi is an annoying issue. I manged to get it to load the drivers so the p2p0 socket gets created.
But it tries to restart it as STA which if my google fu is correct it shouldn't do, since this firmware does not need restarting.
The front camera is a curious bug. It works absoluetly fine for me until I point it towards my face.
So it's either a problem with the proximity sensor or the nasty htc camera tries some facial recognition crap and dies.
If I ever decide to logcat the camera I can tell you more.
Now for a higher version, don't get your hopes up. At least not from my side.
First I'll try my best to fix this up. Then I'll wait for htc to release the kernel so I can get a closer look at the configuration
for this device and maybe adjust it to make this rom even better. Then again the last kernel I compiled was 10 years ago for a gentoo install.
LukeHorizon said:
In which way will PhilZ CWM crash? will it still install the rom or not? will it brick my phone?
Click to expand...
Click to collapse
If you are quick it will install fine. So if you prefer to live dangereously, don't let me stop you
I don't know if it is only an error that is presented on my device. Or maybe it was updated since then.
But for me philz recovery by SPSPawn does boot into a dead state. If you reboot it will crash until a panic reset is triggered.
Actually it is allready crashed while you are in recovery. Therefore you are on a timer until the device resets or you decide to
take out the battery.
I had the same problem on my build and it was caused by cwm always ignoring the ueventd.rc I had prepared because I didn't know
I had to copy it to root and not to recovery.
I've never bothered to figure out which missing element of this script was responsible because I had to substitute it in any case.
But honestly, tell me. Why do you prefer philz? I'm allready (so far unsuccessfully) trying to port twrp. If you have a few good arguments
I might be willing to try compiling a fixed version of philz aswell.
Well i didnt want to use a pc right now ... A TWRP port would be amazing
Is mobile data working?
Can you make your recovery flashable via cwm?
LukeHorizon said:
Well i didnt want to use a pc right now ... A TWRP port would be amazing
Is mobile data working?
Can you make your recovery flashable via cwm?
Click to expand...
Click to collapse
It always tried to download the google language pack for my region until I aborted it. So, yes mobile data should be available.
You mean put the recovery into an update zip thingy, right. Well I could, but you will have used a pc before I'll find the time to upload it.
I'll keep it in consideration for the next update.
Well, atleast internet
When do you think you'll fix wifi?
Regarding to wifi, it will be fixed once it's fixed. Or if you prefer the usual response: When it's done.
This will happen either after or before libaudio is fixed. And that's about as specific as I can get.
Well, it was worth a try still thanks for your effort!
Okay, here goes.
First I tried installing the ROM with the PhilZ recovery because I already had it on my phone, didn't work. Gave me some kind of error (not sure about the error code anymore). Flashed your recovery, worked flawlessly. Now for the ROM.
It's pretty stable, I've had only one strange crash and that was in the first 2 minutes of using it so I don't even know if it counts. The additional CM settings panel works fine, quick toggles are ok, I haven't tried overclocking yet - I'll leave that to someone else. But I have found some bugs:
-proximity sensor not working (screen doesn't go black when you place it up to your ear)
-ambient light sensor not working (auto brightness doesn't work)
-video recording doesn't work
-the camera app glitched up the first time I tried to zoom (was fine afterwards)
-sometimes when going from portrait to landscape I got 1 second of weird graphical glitches
-signal indicator seems to be stuck at 2 out of 4 bars and doesn't move
Overall very nice, keep up the good work!
luxb said:
Okay, here goes.
First I tried installing the ROM with the PhilZ recovery because I already had it on my phone, didn't work. Gave me some kind of error (not sure about the error code anymore). Flashed your recovery, worked flawlessly. Now for the ROM.
It's pretty stable, I've had only one strange crash and that was in the first 2 minutes of using it so I don't even know if it counts. The additional CM settings panel works fine, quick toggles are ok, I haven't tried overclocking yet - I'll leave that to someone else. But I have found some bugs:
-proximity sensor not working (screen doesn't go black when you place it up to your ear)
-ambient light sensor not working (auto brightness doesn't work)
-video recording doesn't work
-the camera app glitched up the first time I tried to zoom (was fine afterwards)
-sometimes when going from portrait to landscape I got 1 second of weird graphical glitches
Overall very nice, keep up the good work!
Click to expand...
Click to collapse
I guess wifi isnt working for you right?
It's not working, but I didn't put it on the list since he already knows it's bugged.
Well, i'll try today
Lets see what happens
Anyway, forgot to unpack the file ... GApps come with it?
SOOO, booting went fine, working like a charm... quicksettings page not available, quicksettings bar is working properly
Mobile Data works flawless, and i guess the rest is just fine
German language worked instantly
it feels way faster then Sense, a HUGE Thanks for you, makes me actually like that phone again ...
I'd like to promote it in German forums if i WiFi is fixed in near future
regards!
LukeHorizon said:
[...]
GApps come with it?
[...]
German language worked instantly
it feels way faster then Sense, a HUGE Thanks for you, makes me actually like that phone again ...
[...]
Click to expand...
Click to collapse
No, you have to get gapps on your own. Since there are multiple options you can choose for yourself. But if you did not format system,
as I've mentioned in the install instructions, chances are high that google apps did get picked up by the install script.
I am not sure if it can take them from the stock rom but it can and will take them from a cm rom and keep them on reinstall.
(I am really not very pleased by this behavior!)
I also should have mentioned that the primary language is decided by the simcard. (Which is annoying since I prefer english in any case)
Randnotiz:
Es freut mich das ich Dir den Spass am Gerät zurückgeben konnte.
Natürlich darfst Du es in deutschen Foren weiterverbreiten sobald die gröbsten Fehler behoben sind.
Einzige Vorraussetzung ist, daß Du es nicht als Deine Arbeit ausgibst.
luxb said:
[...]
-proximity sensor not working (screen doesn't go black when you place it up to your ear)
-ambient light sensor not working (auto brightness doesn't work)
-video recording doesn't work
-the camera app glitched up the first time I tried to zoom (was fine afterwards)
-sometimes when going from portrait to landscape I got 1 second of weird graphical glitches
-signal indicator seems to be stuck at 2 out of 4 bars and doesn't move
[...]
Click to expand...
Click to collapse
Wow. That's much more broken than I expected it to be. Kudos.
Regarding the sensors. I currently am using the stock lib. And logcat let's me assume that they are working as they should.
(i.e they don't crash or drift into madness afaik)
Maybe the stock lib doesn't play well with cm, or you are expecting features from cm that are not implemented.
I will definetly try to compile a working sensor lib in the future, so I guess we'll see....
Camera is also just the stock lib for now. So it's no surprise that somethings might be acting up.
I need a lot of research into that subject before I can specify the requirements for the camera in my boardconfig.
The graphical glitches are rather minor and can be ignored for now. I am aware they exist.
But for now I'd rather focus on the more prominent broken features.
Like wireless for those of us that can't or won't use mobile data. (I belong to the 2nd group)
I noticed the signal indicator aswell. but that should be a problem of the radio compatibility.
We can't flash radio and I'm using the stock libril as the radio interface which should give maximum compatibility in theory.
Of course it doesn't irl... typical -_- (I hate you, Murphy!)
Sidenote:
Why did you remove your avatar? I really wanted to make some "stop trying to kill spoderman" remark...
@all:
Does anyone have any clue how to use the mock locations for gps? They are enabled, but so far I couldn't find any way to set them to a specific location.

Weird CM 11 and CM 11 based ROMS issue with calling

Hi fellow forum members!
I recently found great ROMS at Kevin's web storage. I tried them all and they work amazingly well except for one thing. When I make a call for a first time after a clean boot everything is fine. But when I make another call I can not hear anything nor the person I'm calling. After a reboot I have one shot again. Each time I want to call I need to reboot my phone. It only happens on CM 11 based GPROJ ROMS. Anyone encoutered this issue before? Any suggesting? Solutions?
Thanks, Zunex
nuraH6 said:
Quote:
Originally Posted by ShorelineDroid
Can anyone confirm the new nightly still has the call issue?
Alright, so after chatting with a CM maintainer we've been able to narrow it down to an upstream CM issue along with the phone not going into deep sleep. So, point is, no matter how many of our commits I revert it still won't fix the problem until CM fixes it on their end. I'm told it shouldn't take too long and will keep an eye on CM gerrit to see when an update is pushed into their code to fix these issues. So its not just PAC it's an LGOG gproj that sync'd to CM after 10/4.
Until the issue is resolved you can use the nightly 10/4 as it doesn't have the dialer or deep sleep issues and I will update when I hear more.
Click to expand...
Click to collapse
Same problem here on PAC-man ROM
I am facing the same issue with 10/13 nightly build. Its so frustrating to miss out so many important calls due to this call issue. They pulled back their 10/16 and 10/17 nightly build citing some major issue with the builds. Expecting a build asap with fixed call issue.
I had same problem. I was going back to CM snapshot-M11. This doesn't have call problem.
Is it fixed yet? Any news on this?
Updated today to cm-11-20141025-NIGHTLY-e975 but the calls bug is still there...
So, what should we do to solve this?
Fotonic said:
Updated today to cm-11-20141025-NIGHTLY-e975 but the calls bug is still there...
So, what should we do to solve this?
Click to expand...
Click to collapse
Thanks for the heads up. I don't know. I really don't wanna go back to stock because of dsp manager but this bug forces me to. Hope it gets fixed soon.
Reading This I found the solution to audio-caf problem. The solution is replace in system/lib/hw the library audio.primary.msm8960.so for a working one, I used the library from official M11 and now everything is OK. Attached is the library I used.
I installed the stock rom after this issus. I think the stock rom has a good battery life.
cabe2001 said:
Reading This I found the solution to audio-caf problem. The solution is replace in system/lib/hw the library audio.primary.msm8960.so for a working one, I used the library from official M11 and now everything is OK. Attached is the library I used.
Click to expand...
Click to collapse
Confirmed working!
Thanks cabe2001.
Does anyone have the skills to create a flashable zip that overwrites audio.primary.msm8960.so with a working version?
Is it as simple as deleting everything from a standard CM zip?

[ROM][LineageOS 15.0][Unoficial][dev preview]

Disclaimer:
* You flash this ROM at your own risk and responsibility.
* This ROM is provided without ANY WARRANTY WHATSOEVER, not even the warranty that it works.
* None of the developers of this ROM will be held accountable for any damages, complaints or anything.
This rom is pre pre pre pre alpha, almost nothing is working! Just for everybody who want see Oreo look. I'm out of free time but I will update each time when I get some free time. Whats working, whats not working...etc? You tell me! You fix something, you tell me! You found something, you tell me! Adb somehow is not working, you need to change ro.build.type from userdebug to eng and adb will start working. If you have idea about whats going on with adb, you tell me! Somehow managed to boot this rom, a lot of work and time I spent to get Oreo boot, got also credentials working but somehow camera is fail to work, probably we must use Snap camera instead of the Camera2? You can try snap camera and tell me. You can try other cameras too and tell me!
Enjoy!
Source code && how to build:
https://forum.xda-developers.com/showpost.php?p=74724831&postcount=1008
Download:
https://mega.nz/#!ZB4ilbrL!nI_YV54IMBmKpA1BE4L9VYcwm3nsuLXAGKOu35NJdyQ
Can you post some screenshoots? Whats working? Whats not working? Etc? I'm so lazy
risk
while it is very risky to put this firmware.
munjeni said:
Can you post some screenshoots I'm so lazy Whats working? Whats not working? Etc?
Click to expand...
Click to collapse
Not a risky, just some more things is not working! Bugs need to be identified and fixed one by one.
Mobile data and camera are not working.
Viktor245 said:
Mobile data and camera are not working.
Click to expand...
Click to collapse
Wifi ok?
munjeni said:
Wifi ok?
Click to expand...
Click to collapse
Do not have the opportunity to check it out.
munjeni said:
Wifi ok?
Click to expand...
Click to collapse
Wifi can't be opened
Waoo, I changed my phone, now I can use my z1c to test all lol
In the afternoon I'm going to install it!
i will wait for working mobile data and wifi build
omkarmahananda said:
i will wait for working mobile data and wifi build
Click to expand...
Click to collapse
Me too I'm opened source code ppublic, everybody if free to use it and try fix something.
munjeni said:
Me too I'm opened source code ppublic, everybody if free to use it and try fix something.
Click to expand...
Click to collapse
actually i have no idea how this thing work.
but can you help learning ?!
any thread or any website or anything?
thank you
Did you have think include magisk for this version?
Sorry for being late:
Audio doesn't work
Wifi doesn't work
I'm not able to test cell data
Camera doesn't work, neither footej
ADB doesn't work, no usb at all, the device isn't listed neither with adb devices and devices control panel in windows
Bluetooth yes
Vibrating yes
@hackintosh5 here
Heyho. I just tested building from @munjeni 's sources. Unfortunately TWRP throwed an error 6. I checked the updater script and found some strange lines. With them removed I was able to install and boot
I'm really up for doing some fixes, but for me it's learning by doing which can be a time intensive process.
BTW: USB transfer works by disabling ADB in developer options... I just copied the screenshots off the device.
115ek said:
Heyho. I just tested building from @munjeni 's sources. Unfortunately TWRP throwed an error 6. I checked the updater script and found some strange lines. With them removed I was able to install and boot
I'm really up for doing some fixes, but for me it's learning by doing which can be a time intensive process.
BTW: USB transfer works by disabling ADB in developer options... I just copied the screenshots off the device.
Click to expand...
Click to collapse
But ADB works to you? Can you see the phone if you do adb devices?
@munjeni can I try to replace the libs just like as porting a custom rom from the N builds? Or it is wasted time?
-totonio- said:
But ADB works to you? Can you see the phone if you do adb devices?
Click to expand...
Click to collapse
Yes, adb works. But only if you revert this commit https://github.com/munjeni/android_device_sony_amami/commit/e0cde4386d51ad2b45d7700f495a85fdb75dc8d2.
Adb from the 8.0 tree seems to be broken, but maybe it's a problem with our devicetree.
Nevertheles, as Munjeni already did, replacing the adbd with a prebuilt one (I used one from an Android 7 tree i had lying around) works quite fine.
 @munjeni : Is adb built from 8.0 source working for you? Or is it a permission problem?
Hey. I've got some news. Wifi was working for me. I just installed a new build and was able to connect
I can't test data connection - the sim reader is broken in my test device.
I think we should move ahead to lineage 15.1 (android 8.1) because support for lineage 15.0 was already dropped.
Unfortunately there are several build issues - let's see what the time brings.
*Edit: adb is fixed now
Booted 15.1 some minutes ago.
Working
adb
MTP
brightness slider
not working
wifi
automatic brightness
audio
camera
LEDs
everything else...

[ROM][OFFICIAL] LineageOS 16.0 for S3NEO

Hi there,
If you haven't heard it already, we have official support now and Q is coming too.
links:
https://wiki.lineageos.org/devices/s3ve3gjv
https://wiki.lineageos.org/devices/s3ve3gxx
credits:
francescodario
me
LineageOS
Klte dev team (you guys rock)
Sources: www.github.com/LineageOS/android_device_samsung_s3ve3gxx
Deleted
Tested, works really well! Good job! Even the battery usage is great. It's smoother compared to 7.1.
As it's pointed out, Gapps breaks RIL. Everything else works except radio and offline charging. Installed Aurora Store and I'm pretty happy with it.
Things I tested:
☑ RIL
☑ Camera Front/Back
☑ Video Recording
☑ Bluetooth
☑ WiFi
☑ Sound
☑ GPS
☑ Calls
☒ Offline Charging, it loops.
☒ Radio, phone freezes.
@notfood
I can confirm your tests, but can you please test Videorecording with 1080p. For me the Video Quality (only with 1080p!) is low, becouse there are randomly White lines from the left to the right in the Video. (Like in all builds after 08/2018)
Humaxxx said:
@notfood
I can confirm your tests, but can you please test Videorecording with 1080p. For me the Video Quality (only with 1080p!) is low, becouse there are randomly White lines from the left to the right in the Video. (Like in all builds after 08/2018)
Click to expand...
Click to collapse
I see the white lines, they're sporadic but they're there only with 1080p.
HI
My findings so far: All things mentioned above are working for me as well, but with some exceptions:
GPS finds plenty of satelites, but doesn't snap in ( no position..).
Battery- charging freezes once, I had to reboot to go on.
In Whatsapp recorded video-sequences aren't playable ( frozen screen or artefacts..)
I couldn't find any menue to choose the touchscreen - triangles for moving the cursor in a text document.
I'm looking forward the next Version....:fingers-crossed:
Just tested this rom on my GT-I9301I for an hour or so and i have to say that auto-rotation doesn't work sometimes, also i don't know what exactly RIL is but i installed the gapps aroma (customized) and didn't realize any issue related to gapps until now, and also i got a new phone recently so the old phone doesn't have a sim card anymore, and i don't plan to put one on my GT-I9301I, so my old phone is somewhat like a test device now, i have tried some custom roms before but i didn't like them too much, this one doesn't look bad, except i wish you could do something about offline charging.
Error: this package is for device
Thank you for your contribution! I tried to flash it to my GT-I9301I with the help of TWRP 2.8.5.0 (I know its old, is there a better approach?). Before flashing i wiped everything, now when I try to install it from the sdcard it fails with the Error "E3004: This package is for device: s3ve3g, s3ve3gds, s3veg3gjv; this device is ." What am I doing wrong? Why is the installer not recognizing my device?
Koksnuss said:
Thank you for your contribution! I tried to flash it to my GT-I9301I with the help of TWRP 2.8.5.0 (I know its old, is there a better approach?). Before flashing i wiped everything, now when I try to install it from the sdcard it fails with the Error "E3004: This package is for device: s3ve3g, s3ve3gds, s3veg3gjv; this device is ." What am I doing wrong? Why is the installer not recognizing my device?
Click to expand...
Click to collapse
You have to use a newer Version of TWRP:
https://dl.twrp.me/s3ve3g/
I know this is only for the single sim variant, but would this work on a duos without ril at least? I don't really need ril that much right now.
JaadiBooti said:
I know this is only for the single sim variant, but would this work on a duos without ril at least? I don't really need ril that much right now.
Click to expand...
Click to collapse
Deleted
another useless ROM, we arrived at 10, or 15?
mariocaraf said:
another useless ROM, we arrived at 10, or 15?
Click to expand...
Click to collapse
Deleted
He didn't work he remained stuck
Please Help
Waiting for an edititon for Sony sensor! On Sony sensor not works camera and flashlight, but rom is usable as daily driver.
Auto-rotate is working in YT Vanced and other apps only sometimes.
This is very cool ROM, better than Nougat!
ayochan said:
He didn't work he remained stuck
Please Help
Click to expand...
Click to collapse
If it gets stuck, you are probably running an outdated firmware. Get the latest from Sammobile or check the Telegram group. You will need Odin or Heimdall to install it. Be careful which firmware you are burning, it can brick your device if it's the wrong one.
For more than an hour it is stuck in the installation screen
Humaxxx said:
You have to use a newer Version of TWRP
Click to expand...
Click to collapse
thanks, that worked perfect! I also like that encryption works
Just bought my a new Evo 860 ssd so I have enough storage for building multiple devices . So yes more build coming this week for Sony and dual SIM.
My 300gb ssd before didn't quite had enough.
Hi Thargorsson,
First of all. Excellent work on the new ROM!
I have just got a hold of 5x S3 NEO and wished they had a newer version than 4.4.2.
After some searches on Google I found this forum. I'm going to wait until you have an updated version of this ROM.
Please keep us all posted on any progress
Cheers,
Steve

[clark] Unofficial 18.1

It's that time of the year....
Recovery: download (6th Mar '21)
Gapps: download (16th Feb '21)
Lineage 18.1: download (8th Mar '21)
Please report stuff that doesn't work in this thread.
Update: 8th March
Recently fixed:
Bluetooth
Setting a lock screen
AUX / Line Out
Encryption
Gallery speed
Limitations of the current Lineage version:
VoLTE is disabled (will unfortunately not be able to fix that easily)
Dual SIM is not working (for devices that have Dual SIM)
Speakers do not sound as good as on stock
Camera is not as good as stock
Battery life when the screen is on is better on stock than on Lineage
------------
For developers:
device: https://review.lineageos.org/c/LineageOS/android_device_motorola_clark/+/304226/2
kernel: https://review.lineageos.org/c/LineageOS/android_kernel_motorola_msm8992/+/304218/1
vendor: https://github.com/chrmhoffmann/proprietary_vendor_motorola/tree/lineage-18.1
Note: Credits go to the usual lineage team from whom the device benefits enormously. Also the previous device maintainers have done a great job and we're still benefiting from that. E.g. the camera reverse engineering.
chrmhoffmann said:
It's that time of the year....
Recovery: download (16th Feb '21)
Gapps: download (16th Feb '21)
Lineage 18.1: download (16th Feb '21)
Please report stuff that doesn't work in this thread.
------------
For developers:
device: https://review.lineageos.org/c/LineageOS/android_device_motorola_clark/+/304226/2
kernel: https://review.lineageos.org/c/LineageOS/android_kernel_motorola_msm8992/+/304218/1
vendor: https://github.com/chrmhoffmann/proprietary_vendor_motorola/tree/lineage-18.1
Click to expand...
Click to collapse
Hello Chris, first of all, thanks for continuing on 18.1. I installed the rom and it booted fine. The set-up was buggy and laggy an kept crashing on setting up screen pattern. So I can't set screen pattern/pincode/password. Also I installed some apps from play store like whatsapp,gmail, telegram and they are doing fine. The phone gets hot and battery drains fast. Ambient display is a bit buggy, it's not working everytime. Anyways for the first build it's quite good. Thanks again
Maybe anybody else can also test?
Yes, setting up lock screen is broken. Will fix it in next build.
Chris
!
[QUOTE = "chrmhoffmann, post: 84511557, member: 361777"]
Да, не работает настройка экрана блокировки. Исправлю в следующей сборке.
Крис
[/ ЦИТИРОВАТЬ]
Dear Chris, everything is superb, but the function of broadcasting the screen in the quick settings menu does not work when connected (miracast) the phone is overloaded
I think bluetooth headsets are broken.
Chris
chrmhoffmann said:
I think bluetooth headsets are broken.
Chris
Click to expand...
Click to collapse
I can confirm that, it connects with my Haylou GT1 Pro but no sound.
Fixed. Uploading new build that fixes bluetooth and screen lock.
Note: If you have previously tried to setup lock screen, you will have to reset device (factory reset/wipe). Otherwise the device will crash right after bootanim stops. Sorry for that!!!
chrmhoffmann said:
Fixed. Uploading new build that fixes bluetooth and screen lock.
Note: If you have previously tried to setup lock screen, you will have to reset device (factory reset/wipe). Otherwise the device will crash right after bootanim stops. Sorry for that!!!
Click to expand...
Click to collapse
Thank you Chris, bluetooth and screen lock are fixed!
chrmhoffmann said:
Fixed. Uploading new build that fixes bluetooth and screen lock.
Note: If you have previously tried to setup lock screen, you will have to reset device (factory reset/wipe). Otherwise the device will crash right after bootanim stops. Sorry for that!!!
Click to expand...
Click to collapse
Can it be dirty flashed or should we do a clean install? It's cumbersome working with LOS recovery so the less I have to deal with it the better. Other than recovery it's a nice smooth rom. Thanks again
Wheels564 said:
Can it be dirty flashed or should we do a clean install? It's cumbersome working with LOS recovery so the less I have to deal with it the better. Other than recovery it's a nice smooth rom. Thanks again
Click to expand...
Click to collapse
I did a clean install, you can try dirty flash.
moviefirst said:
I did a clean install, you can try dirty flash.
Click to expand...
Click to collapse
I did a clean install. Since I have two of these phones I'm using this one for testing purposes for now and have 14.1 on the other one for daily use. At some point I'll change over to the 18.1 phone. I really like that dark theme is enabled on this rom that 14.1 never had It helps save battery.
which version of magisk will work?
Could someone test Netflix?
chrmhoffmann said:
Could someone test Netflix?
Click to expand...
Click to collapse
Seems to work fine in the U.S. on wifi. I'll let it run for a while to make sure it's stable. It appears to be running 1080p.
chrmhoffmann said:
Could someone test Netflix?
Click to expand...
Click to collapse
Netflix working here in the Netherlands, but the phone is lagging and takes time to open apps. Also I think battery was better in 17.1
In the camera I've noticed there's no icon to save to sdcard. also unless they've change snap camera I can't get the back or home button to come up to exit camera. I have to long press the power button to get access to home icon.
[email protected] said:
which version of magisk will work?
Click to expand...
Click to collapse
Latest version 21.4 works.
Wheels564 said:
In the camera I've noticed there's no icon to save to sdcard. also unless they've change snap camera I can't get the back or home button to come up to exit camera. I have to long press the power button to get access to home icon.
Click to expand...
Click to collapse
.
Swipe down from top to see home button. Save to sd card did not work on 17.1 so he removed the icon. Thanks for helping me find new forum!
Link to gapps is not working here.
Sorry for partial reposting this from 17.1 forum. Seems very functional on WiFi. Phone does not read VZW SIM on boot and can't pick up APN. I had to choose VZWINTERNET APN. Then LTE works for 30 seconds. Data drops for maybe a minute, then falls back to 3G which works. If LTE worked I think we would be golden.
Also get "DM config update keeps stopping" error. Not sure if this is related to SIM. I used NikGapps but don't think it is related.
Photos can not access SD card but Files has no problem. Edit. My bad. Photos works fine.
kb8no said:
Latest version 21.4 works.
.
Swipe down from top to see home button. Save to sd card did not work on 17.1 so he removed the icon. Thanks for helping me find new forum!
Link to gapps is not working here.
Sorry for partial reposting this from 17.1 forum. Seems very functional on WiFi. Phone does not read VZW SIM on boot and can't pick up APN. I had to choose VZWINTERNET VPN. Then LTE works for 30 seconds. Data drops for maybe a minute, then falls back to 3G which works. If LTE worked I think we would be golden.
Also get "DM config update keeps stopping" error. Not sure if this is related to SIM. I used NikGapps but don't think it is related.
Photos can not access SD card but Files has no problem.
Click to expand...
Click to collapse
Get a logcat when your trying to use LTE for Chris. I don't have a sim in my 18.1 phone or I would.
Link to MindTheGapps from OP is obsolete and updated link found on LOS link. I used NikGapps before and started over with clean flash using MindTheGapps but found it made no difference. Phone still does not read VZW SIM on boot and can't pick up APN. I had to again manually choose VZWINTERNET APN. Then LTE works for 30 seconds. Data drops for maybe a minute, then falls back to 3G which works and I get about 2 Mbps. Continue to get error "DM config update keeps stopping". I now believe this is related.
Has anybody yet tried TWRP from 17.1 thread?
Advanced restart is missing from developer options.
Addendum: I put in my ATT SIM. It found the APN and imported it correctly. It started LTE and similarly died. Data never came back at a lower rate.

Categories

Resources