Proximity sensor fix for CM based ROM
/* Info */
This thread is made to avoid speaking about this subject under devs threads. To save their time.
In this thread your going to find a step by steps way to fix Proximity sensor on our devices.
I'm working over a flashable .zip to automate process.
/* Disclaimer */
I am not responsible for bricked devices, dead SD cards,
thermonuclear war, or you getting fired because the alarm app failed.
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. Hard. A lot.
/* Supported device */
Galaxy S4 LTE + International (GT-I9506, ks01lte) : working.
HLTE : working.
Basically I think all the ROMs based over Cyanogenmod for Samsungs devices.
/* What you need to know */
This is only tested on
- KS01LTE on CM12 from Arter97 and CM11 of Solk2.
- HLTE based on CM12 version of temasek.
Other variants, other OS may not be fully compatible
/* Thanks to */
All devs who are working for our device. @arter97 @solk2 @temasek @DeHAWK @jonte28 @budda1996 @Genie's
The Cyanogenmod team.
@hilefin who gave me the way to fix proximity sensor and helped me in first step.
/* Downloads */
Coming in the close future.
Created 2015-01-09
Last Updated 2015-01-09
XDA:DevDB Information
Proximity sensor fix for CM based ROM, Tool/Utility for the Samsung Galaxy S 4
Contributors
likesatan
Version Information
Status: Testing
Created 2015-01-13
Last Updated 2015-01-14
Step by steps method
/*Requirement*/
TWRP or CWM recovery.
Terminal app (Go google play) with super user rights.
/*Backup*/
Reboot into recovery mod and save your EFS partition and nothing else.
It will save you time in case of troubles.
/*Step by steps way*/
1.
Go to "Google Play" download "Terminal".
Grant super user rights to Terminal app.
Open new terminal session.
2.
Type "/system/xbin/su -l"
3.
Type cd /sys/devices/virtual/sensors/proximity_sensor/
4.
With the proximity sensor uncovered.
Type "cat state" and write down the value (74 in my case).
5.
Type "cat prox_cal"
Write down the first value between parenthesis (this is the offset).
Eg. (0,31,75) take 0.
6.
Sum both values.
In my case it was (74+0) = 74.
7.
Convert the value to hex. Link.
In my case, 74(dec)=4A(hex).
8.
Instead of 4A, put your value.
Type "echo -en $'\x4A' > /efs/prox_cal"
9.
Type "chown system:system /efs/prox_cal"
10.
Type "chmod 644 /efs/prox_cal"
11.
Type "sync"
12.
Type "reboot"
13.
Done.
Last Updated 2015-01-09
Flashable ZIP
/*Under development*/
I'm porting this step by step process to a flashable ZIP.
Coming in the future.
/*Requirement*/
TWRP or CWM recovery.
/*Backup*/
Reboot into recovery mod and save your EFS partition and nothing else.
It will save you time in case of troubles.
/*BATCH CODE*/
If you want to help here is the batch code.
I think it's working. Have to test it.
Code:
#! /bin/bash
/system/xbin/su -l
SOMEVAR='n'
SOMEVAR='HEX'
n=0
HEX=0
cd /sys/devices/virtual/sensors/proximity_sensor/
Cat state
Cat prox_cal
Echo -n "Please type the sum of the first number and the second the first in parentesis. Eg first number 45. Second (23,00,17). Sum is 68."
Read n
HEX=`echo "obase=16;ibase=10; $n" | bc`
echo -en $'\$HEX' > /efs/prox_cal
chown system:system /efs/prox_cal
chmod 644 /efs/prox_cal
sync
echo "Done ! Touch the screen to reboot"
timeout /t -1
reboot
Then I'm going to use this tool to convert it.
Last update 2015-01-09
/*Known issues*/
Cat state is giving you 255 value.
255 is highest value. Meaning your sensor is thinking is covered with blanket.
Their is dust on sensor.
[Fix]
Clean with "canned air" duster.
Thanks to @ode_
/*Problems*/
In case of trouble you can flash your EFS backup you first made in TWRP/CWM recovery.
Other issue ?
This thread is made for that.
Any questions ?
Juste ask.
Last Updated 2015-01-09
FAQ
FAQ under construction.
Thank you for compiling this information. Can you clarify the statement, "Type "/system/xbin/su -l"". Is that last character a lower case letter L, or is it the vertical line character |?
---------- Post added at 08:50 PM ---------- Previous post was at 08:34 PM ----------
I got it. It took several attempts, so the recommendation to backup the efs partition was well received. Thanks! It works great!
---------- Post added at 08:52 PM ---------- Previous post was at 08:50 PM ----------
I cleaned my Note 3 thoroughly with a dry rag, and still my values were 214 and 76. Seems very high.
TU Homer said:
Thank you for compiling this information. Can you clarify the statement, "Type "/system/xbin/su -l"". Is that last character a lower case letter L, or is it the vertical line character |?
Click to expand...
Click to collapse
It's a lower case letter L !
I got it. It took several attempts, so the recommendation to backup the efs partition was well received. Thanks! It works great!
Click to expand...
Click to collapse
You're welcome so your proximity sensor is fixed now !
I cleaned my Note 3 thoroughly with a dry rag, and still my values were 214 and 76. Seems very high.
Click to expand...
Click to collapse
No it's going to work fine ! Had a huge value and It worked.
Regards,
Likesatan
"This is only tested on
- KS01LTE on CM12 from Arter97"
Why this ?
I dont have any proximity problems, if ppl mean that display should dim while holding phone near ear etc.
iBuu said:
"This is only tested on
- KS01LTE on CM12 from Arter97"
Why this ?
I dont have any proximity problems, if ppl mean that display should dim while holding phone near ear etc.
Click to expand...
Click to collapse
Because I only test this on my phone and ROM : i9506 - CM12.
Some people have tried it on HLTE it's working too !
As I haven't a lot people testing it on multiples device I dont know if it's working on all devices.
It should work on all CM based roms for samsungs devices.
Regards,
Likesatan
Reminder from personal experience; after battery was out and rebooted phone with grease on front glass over proximity sensor and my phone did recalibration, and my proximity sensor start act weird, kinda broken way.
All what I did after that was battery out(20sec)/in again, cleaning front glass and rebooted and proximity sensor started to work normally.
is it apply to CM 12 latest nightlies ?
sanioclement said:
is it apply to CM 12 latest nightlies ?
Click to expand...
Click to collapse
Yes it is ! I tried it over them
likesatan said:
Yes it is ! I tried it over them
Click to expand...
Click to collapse
Screenshots would be great in step by step description
Regards.
Easy Fix
1.Make sure u have root access
2.Download and install sensor kinetics pro from
3.Open it and scroll down to proximity sensor and turn it off
Awesome. This worked like charm. Even on my note2. Thank you somuch for shaing
Another Placeholder thread, there is definitely seperate rules...
Android-Desire said:
Another Placeholder thread, there is definitely seperate rules...
Click to expand...
Click to collapse
And why placeholder? He post step by step what you must make. Is a guide. And helped a lot of ppl.
Sent from my GT-I9506 using XDA Free mobile app
sevenlife said:
And why placeholder? He post step by step what you must make. Is a guide. And helped a lot of ppl.
Sent from my GT-I9506 using XDA Free mobile app
Click to expand...
Click to collapse
No zip to flash -> Placeholder, again different rules for different people.
Proximity sensor
Sorry for the ignorance...but what is exactly the proximity sensor?
i9500
Is it working on installed a CM 12.1 i9500? Need root?
Thanx
Related
DO NOT post in this thread until you have read the first three posts and last two pages of this thread in their entirety!
"Me Too" posts for known issues with no useful debugging information WILL BE REPORTED.
What is Omni?
Omni Gerrit Review
OmniLog - changelog
Disclaimer
Code:
#include <std_disclaimer.h>
/*
* 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. Hard. A lot.
*/
ROM:
Omni for Samsung Galaxy S 4
Gapps:
http://forum.xda-developers.com/showthread.php?t=2397942
(recommend the MODULAR FULL package, however, keep in mind that the STOCK package is intended for Nexus devices)
UPDATE FROM VARIANT OMNI BUILD TO UNIFIED BUILD
Backup your apps and other pertinent data and DO A FULL WIPE.
Don't complain about it. Just do it. If you try to post bug reports or complaints and you have not conducted a wipe of:
/system
/data
/cache
/dalvik
I will completely and utterly ignore you, as well as report your post for not reading the clearly posted rules at the top of this post.
UPDATE FROM OMNI VIA OPEN DELTA UPDATER
Settings -> System Updates -> Check for update
You will NOT need to wipe anything with the delta updates unless it is explicitly stated or you start having strange issues.
Omni only supports TWRP recovery, use any alternate recovery at your own risk.
Kernel Source: https://github.com/omnirom/android_kernel_samsung_jf
XDA:DevDB Information
Omni for Galaxy S4, ROM for the Samsung Galaxy S 4
Contributors
jakew02, xplodwild
Source Code: http://www.github.com/omnirom/
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
Version Information
Status: Nightly
Created 2014-05-28
Last Updated 2015-04-20
Important Information
This is NOT the place to ask questions like:
When will <feature> be included?
Is <feature> included yet?
Can you bring <feature> to Omni?
ETAs of any nature
Follow the rules. This is a new thread and it WILL remain clean and ON TOPIC. I will immediately report any off-topic posts, trolling, flaming, etc. of any sort. This is a DEVELOPMENT thread, and as such, has been posted in the DEVELOPMENT section.
INCLUDE LOGS when reported a bug. Even if you think that you might be the only one with the bug, POST LOGS, that will help narrow down the issue about 100 million times!
Explore the ROM a bit before posting here things like " WHERE IS <feature> CAN YOU ADD FEATURE etc. etc.
You have to understand, that gets extremely annoying after 50 posts like that. Most features can be seen on the blog or in the MERGED section of gerrit.
Root IS NOT included with Omni by default, so you will need to flash SuperSU in recovery SuperSU
How to build Omni from sources:
OmniROM - Setting Up A Compile Environment
Bug Reports and Feature Requests
jira.omnirom.org
Important Information Part 2
Omni XDA Discussion ( NOT DEVICE RELATED DISCUSSION ONLY)
http://forum.xda-developers.com/omni
IRC
Web Client
irc.freenode.net
#omni
First
Using 052814 unified build with 052414 full modular gapps...ROM boots but gets stuck at the "setup wizard". After you select your language and press the white triangle it reads " Welcome...please wait a few minutes" for a minute or so...the the screen goes black except for the status bar and the backlights on the hardware keys stay on.
I clean flashed twice then downloaded the ROM and gapps for a 2nd time then clean flashed those twice...all with the same results as described above.
Hope this helps.
Sent from my SPH-L720 using Tapatalk
Hello,
I know one can flash the 9505 rom on the i337m becuse the bootloader is not locked, but what about the AT&T version (i337), can i flash this (jflte) version on my i337 ?
rabiny said:
Hello,
I know one can flash the 9505 rom on the i337m becuse the bootloader is not locked, but what about the AT&T version (i337), can i flash this (jflte) version on my i337 ?
Click to expand...
Click to collapse
Yes. If you notice, I closed the individual variant threads and put a direct link to this thread. Basically, you can see a list of supported variants by checking this:
https://github.com/omnirom/android_device_samsung_jflte/blob/android-4.4/BoardConfig.mk#L129
That is the list of device asserts that the updater-script will accept.
buzzwyzr said:
Using 052814 unified build with 052414 full modular gapps...ROM boots but gets stuck at the "setup wizard". After you select your language and press the white triangle it reads " Welcome...please wait a few minutes" for a minute or so...the the screen goes black except for the status bar and the backlights on the hardware keys stay on.
I clean flashed twice then downloaded the ROM and gapps for a 2nd time then clean flashed those twice...all with the same results as described above.
Hope this helps.
Sent from my SPH-L720 using Tapatalk
Click to expand...
Click to collapse
I just flashed the 05/28 nightly (on my jfltespr) with the 4-16 Minimal PA Gapps with absolutely no errors. This most definitely sounds like a Gapps problem to me, since the SetupWizard is not packaged or built with the ROM, but instead flashed with Gapps. This is why if you were to NOT flash a Gapps package, you don't have to run through it.
jakew02 said:
Yes. If you notice, I closed the individual variant threads and put a direct link to this thread. Basically, you can see a list of supported variants by checking this:
https://github.com/omnirom/android_device_samsung_jflte/blob/android-4.4/BoardConfig.mk#L129
That is the list of device asserts that the updater-script will accept.
Click to expand...
Click to collapse
Thank you for the quick reply,
What about the locked bootloader, Are there any points I should pay attention to ?
Or i can just download the recent file (from http://dl.omnirom.org/jflte/) and flash it over my current version (jflteatt)
rabiny said:
Thank you for the quick reply,
What about the locked bootloader, Are there any points I should pay attention to ?
Or i can just download the recent file (from http://dl.omnirom.org/jflte/) and flash it over my current version (jflteatt)
Click to expand...
Click to collapse
If you are already running Omni then you're fine. Just follow the instructions from the OP.
These instructions are written under the assumption that you know how to root and install a custom recovery.
Sent from my X9006 using Tapatalk
Is custom hot word launcher built in yet?
ahoslc said:
Is custom hot word launcher built in yet?
Click to expand...
Click to collapse
Yes. I've been using it and it works perfectly fine.
You can see that from gerrit as well as the XDA News Portal...
I'm squashing questions like this now. Please re-read Post 2 as I have updated it.
flashed the 30th nightly, thought of asking about two things,
1. why does the initial setup page needs a working data connection?
2. i lost root after a clean install, am i missing something?
bala_gamer said:
flashed the 30th nightly, thought of asking about two things,
1. why does the initial setup page needs a working data connection?
2. i lost root after a clean install, am i missing something?
Click to expand...
Click to collapse
the root apk has to be flashed via recovery as stated on the first page post.
---------- Post added at 08:40 PM ---------- Previous post was at 08:27 PM ----------
Hello Jakew02
I moved over to your latest rom yesterday the 5/29 nightly and i came across a couple issues.
i have been using cm mod since the days of android cupcake and decided to try this out.
1st issue is when im trying to lower the phone ringer volume, it always goes to lower the sounds/music volume. it is pretty annoying because i have to make all the sliders come out and manually slide the phone ringer volume. even after switching between apps and what not it insists on lowering the music volume.
2nd issue is i cannot get the multi window to work or how to enable it. i have downloaded and installed these apps :halo)),multiwindowsidebar, toggle multiwindow, xhalo floating, xmultiwindow, and xposed installer. also the fixvisibilityofmultiplenonulls. Any help on getting it to work will be appreciated. i am very new to this feature since ive never had it in CM since i thought u couldnt get it, only on Stock Samsung roms.
lastly, is there any way to add shortcuts to the unlock slider like in cm?
thanks
djbootleg said:
the root apk has to be flashed via recovery as stated on the first page post.
---------- Post added at 08:40 PM ---------- Previous post was at 08:27 PM ----------
Hello Jakew02
I moved over to your latest rom yesterday the 5/29 nightly and i came across a couple issues.
i have been using cm mod since the days of android cupcake and decided to try this out.
1st issue is when im trying to lower the phone ringer volume, it always goes to lower the sounds/music volume. it is pretty annoying because i have to make all the sliders come out and manually slide the phone ringer volume. even after switching between apps and what not it insists on lowering the music volume.
2nd issue is i cannot get the multi window to work or how to enable it. i have downloaded and installed these apps :halo)),multiwindowsidebar, toggle multiwindow, xhalo floating, xmultiwindow, and xposed installer. also the fixvisibilityofmultiplenonulls. Any help on getting it to work will be appreciated. i am very new to this feature since ive never had it in CM since i thought u couldnt get it, only on Stock Samsung roms.
lastly, is there any way to add shortcuts to the unlock slider like in cm?
thanks
Click to expand...
Click to collapse
These aren't issues or bugs at all; you just haven't looked around the settings.
all of your questions can be answered by just looking through the settings.
OP updated, please re-read it.
Download page says 193 Mb, the download is 183 mb. I downloaded twice, both 183. Anyone else? The newest nightly.
Sent from a Shaftamle Galaxy S4
"Thanks Button" is always appreciated!
http://mycolorscreen.com/Shaftamle/
Shaftamle said:
Download page says 193 Mb, the download is 183 mb. I downloaded twice, both 183. Anyone else? The newest nightly.
Sent from a Shaftamle Galaxy S4
"Thanks Button" is always appreciated!
http://mycolorscreen.com/Shaftamle/
Click to expand...
Click to collapse
It's 183mb, I've just flashed. Working fine.
ZordanKV said:
It's 183mb, I've just flashed. Working fine.
Click to expand...
Click to collapse
Have you tried flashing a custom kernel with the latest nightlys?
bobbarker2 said:
Have you tried flashing a custom kernel with the latest nightlys?
Click to expand...
Click to collapse
Nope, already switched to the other ROM. Omni is good, but doesn't suit my needs
bobbarker2 said:
Have you tried flashing a custom kernel with the latest nightlys?
Click to expand...
Click to collapse
gpu drivers fixed
jakew02 said:
i have stated multiple times that kernel developers will need to begin released "omni-based" kernels.
I WILL NOT alter this ROM to accommodate custom kernels. the kernels need to change to be compatible with the ROM.
Custom kernels will not just magically start working. Kernel developers need to remove the flo adreno drivers and related commits from their kernels. If they don't know which commits those are, they can simply cherry-pick this commit: https://github.com/omnirom/android_kernel_samsung_jf/commit/068449af3996f1072c80dcc4a09a88af43abd7f7
contained in that commit is all of the reverts needed to make a cyanogenmod-based kernel work with Omni.
I have spoken with @Entropy512 about this a few times and we both agreed that we will NOT be altering the ROM in order to this one device to be able to use flo adreno stuff. That's just stupid and causes more work and problems for everyone else.
So the bottom line on this is, if you want a custom kernel, ask your kernel devs to cherry-pick the above commit and release Omni kernels separately from CM-based one.
If anyone has a problem with this, well, gerrit is free to use and open to all.
As before I will use this comparison to better justify my decision:
You wouldn't buy a Playstation controller(an accessory) to use with your Xbox(a primary), once you get home and realize it doesn't work because it's designed for something other than what you have, you call Microsoft and demand that they make the Xbox(primary) work with Playstation controllers(accessory)?
Absolutely Not. If ANYTHING, you would call Sony and demand that they make their controllers(accessory) work with the xbox system.
Hope this clarifies that issue a little better for everyone.
Also on another note:
I have narrowed down the camera preview freeze down to one repository
Click to expand...
Click to collapse
Jake the only reason I asked was because I did a bit of testing for you where the testbuild had support for custom kernels and you said that it should be fixed and you would push the change when you could. I even followed up with you at a later time and you said you hadn't had time/inclination to do it yet. I'm not demanding anything of you and I didn't want to bug you with the issue so I asked someone else who was in similar territory. Had I known about your changed stance on the issue, I wouldn't have brought it up.
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 5.0 (Lollipop), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include
/*
* 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.
*/
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Downloads:
CM server
Installation:
Unlock the bootloader
Flash a recovery
Reboot into recovery
Flash rom.
Reporting bugs:
You are allowed to report bugs only in this thread. Before reporting a bug, please make sure you are running as stock as possible. This means no custom kernel, no custom framework modification, etc. If you are using any of the above modifications, please flash the rom again to get rid of the modifications before reporting.
Report bugs on Jira at jira.cyanogenmod.org
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /proc/last_kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. The following is a useful format to follow. Note: If you can provide the latest night/build that the bug didn't exist, it would greatly help in tracking down what caused it.
Code:
What is your:
Phone model:
CM Download url:
Gapps version:
Radio (baseband):
CM version:
Did you:
Install xposed framework?
Restore apps in titanium backup?
Flash another kernel?
Are you using a supported recovery?
start Art Runtime?
search the thread for similar issues before posting?
I don't reply to tech support by pm or emails/hangouts messages.
If you have xposed installed, please bother to post.
The CyanogenMod team would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!
XDA:DevDB Information
Offiical cm for peregrine, ROM for the Moto G
Contributors
Somcom3X, @BlueFlame4
Source Code: http://www.github.com/CyanogenMod
ROM OS Version: 5.0.x Lollipop
ROM Kernel: Linux 3.4.x
ROM Firmware Required: Unlocked Bootloader with recovery
Version Information
Status: Beta
Created 2014-11-24
Last Updated 2015-04-20
Reserved
I present to you CyanogenMod 12 for the peregrine. After delaying my initial release to an almost fully working state, it is here now.
Video review:
Big thanks to @Cm9aphla
Bugs:
Wifi tether (Experimenting)
Bluetooth stack issues with multitasking. Somewhat buggy
GPS issues as well.
Reserved
Big thank you to all of the donators:
Please confirm your username by posting the remainder of the transaction ID. To donate, please send to [email protected] via paypal
Donators
Code:
S. Fabbro 4HR94540AN4xxxxxx
D. Noonburg 604068013C4xxxxxx
G. Girotto 9SH91349CF4xxxxxx
Gracias!
New recovery is in the works, stay tuned.
If anyone needs some assistance, join #cyanogenmod or #carbonrom on irc.
I'll be in #carbonrom-dev most of the time.
If no one responds instantly, simply wait. Don't be this guy (You know who you are):
Code:
[22:57:18] --> carbon_guest ([email protected]/web/freenode/ip.97.xx.3.xx) has joined #teamcarbon
[22:58:19] <carbon_guest> I'm having an issue, this is my first time trying the carbon ROM the installation
was succesful but every time i try to install the GAPPS it gives me an error and says (Satus 6), any aid please?
[23:01:02] <carbon_guest> anybody here?
[23:10:06] <carbon_guest> hellooooooooooooooooooooooooooooooooooooooooo
[23:26:12] <-- carbon_guest ([email protected]/web/freenode/ip.97.xx.3.xx) has quit (Quit: Page closed)
Great work! I'll stay here until official 5.0 ota arrives. [emoji16]
Which superuser flashable zip should I use? The ones I used in KK don't work.
---------- Post added at 10:33 PM ---------- Previous post was at 10:33 PM ----------
And the ROM is rock solid, congrats!
Awesomeness, grabbing it now and will run it through the paces.
@Somcom3X
great work man =D
Bugs that I saw:
Wifi Tether (mentioned on op)
CPU Clock on 1190 almost all the time when the screen is on
@Somcom3X Excellent release! Though I've encountered a few issues apart from the mentioned ones.
AOSP keyboard gesture swiping does not work
Power Off does not work
Notification sound does not work. Tried changing it a few times but none of which works. It vibrates though.
Notification LED doesn't work? I don't think it's working or how it's intended to work in 5.0 Lollipop, but Pulse Notification light is turned on (This seems to work for alarms though)
Random Settings force closes
Maps is not working -- I know it's totally unrelated but it could be GPS related as it just kept showing "Waiting for location..."
Some apps are left even after clearing all apps. ie: SuperSU requests, Contacts, app installs.
Volume rocker for Media Volume gets stuck at a certain point, though it's only a visual bug.
Crossed out stuff just suddenly worked. lol
Is it possible to get Busybox working on CM12 too? Can't find one that would install.
Using this as a daily driver until I find something that wouldn't let me.
zackwire said:
Which superuser flashable zip should I use? The ones I used in KK don't work.
---------- Post added at 10:33 PM ---------- Previous post was at 10:33 PM ----------
And the ROM is rock solid, congrats!
Click to expand...
Click to collapse
I used this and it seems to be working fine. http://download.chainfire.eu/589/SuperSU/
I'm testing since you release the zip in the other thread (I was even about to suggest a new thread ).
I did a dirty flash from cm11, so, maybe some of my reports here are specific about doing dirty flash (just in case, remember to redo your lockscreen security, because the dirty flash made your lockscreen accept anything as password. Remaking the lockscreen security fix it).
* Stock camera doesn't work (shows image, but doesn't take photos, even after cleanup the application). Downloading the google camera or whatever other camera works (and it seems the camera bug from cm11 is gone).
* f2fs doesn't work, ext4 works but useless (you can't do anything, but the cm12 reads that there's a partition and with size, etc), exfat doesn't work either. The worse is: using any of the filesystems I said made you unable to even reformat de sdcard. Only fat works for me. Btw, I'm unable to copy from pc to sdcard.
Thanks
Downloading now. Thanks for posting, been waiting for a lollipop rom.
Edit:
Gps is working fine for me, camera works when it wants to, replaced the stock camera with a port from the apps section of this forum.. Google camera seems a bit more stable. Installed no frills cpu control and disabled safety valve and other apps being able to set frequency and I noticed while it still says min is 1.1 if you look at stats it will go to 300 like normal.
Guest Mode is enabled ?
settings crash sometimes, but it's working well
thanks for your great work
Hi. I'm so excited to install this, but I want to know if I'll be able to go back to KK if there is any problem
Thanks for all your hard work!
Great work man
Just out of curiosity, the thread name is "[ROM] unOfficial Cyanogenmod 12 4.4.4 for the Moto G 4G (Peregrine)".
CM12 is made after 5.0, not 4.4.4 - right?
Or am I misunderstanding what the 4.4.4 means?
Thanks!
athlantar said:
Just out of curiosity, the thread name is "[ROM] unOfficial Cyanogenmod 12 4.4.4 for the Moto G 4G (Peregrine)".
CM12 is made after 5.0, not 4.4.4 - right?
Or am I misunderstanding what the 4.4.4 means?
Thanks!
Click to expand...
Click to collapse
This is CM12 5.0
Probably just a typo by SomCom3X.
Can confirm lack of GPS signal lock. Could be the same bug with CM11.2 where you need to get it just right with a previous signal lock on stock and then flash. Otherwise, running extremely smoothly. Latest SuperSU Beta 2.27 gives root without any big problems, restoring TiBu as we speak. Also can confirm lack of swipe in stock keyboard. SD Card access is working. Great work!
Getting a GPS lock before you flash cm12 worked for me. That should be step one from now on before flashing any ROM. Just in case ya know. So far everything's running great.
Level99 said:
Can confirm lack of GPS signal lock. Could be the same bug with CM11.2 where you need to get it just right with a previous signal lock on stock and then flash. Otherwise, running extremely smoothly. Latest SuperSU Beta 2.27 gives root without any big problems, restoring TiBu as we speak. Also can confirm lack of swipe in stock keyboard. SD Card access is working. Great work!
Click to expand...
Click to collapse
I've read it's an issue with quite a bit of Motorola devices. The stock GPS trick is the best thing possible to do at the moment.
zackwire said:
Which superuser flashable zip should I use? The ones I used in KK don't work.
Click to expand...
Click to collapse
here you go mate
edit:
whoops someone posted it already ^^
mhh, better more links than no links
gr3ud said:
here you go mate
edit:
whoops someone posted it already ^^
mhh, better more links than no links
Click to expand...
Click to collapse
Okay, when already posting links, there is latest beta v 2.27
Hey everyone ! This is an unofficial version of Carbon ROM LP-5.1.1 for Asus Zenfone 5.
I've designed it using some fragile source codes. This includes the source codes from quanganh2627 & tank0412.
Before you begin:
Code:
You know the story:
I'm not responsible if you device is wrecked....
....
....
Your warranty will be void(duh)!
....
....
And so on...
And the ROM has most common problems as expected from an AOSP/CM based ROM :silly:
Bug list:
1. Vibration doesn't work
2. Initial boot time is late
3. Battery backup is kinda low on extreme usage only
4. SystemUI crashes randomly
5. Setting would crash if you open info about Carbon ROM from Carbon Fibre option in settings
6. Occasional lags here and there
7. FM radio is not tested yet
8. Any other device apart from a500cg is also not tested. If interested you may.
9. GPS is not yet tested due to lack of time
10. Crashes of AOSP keyboard after theme change (occurs only at first)
11. HW key customization.
What is working: : :fingers-crossed:
1. Dual Sim
2. Brightness
3. Sounds
4. Customization
5. Multi-user mode
6. Memory card support
7. Pretty much everything else works quite fine.
Download:
System.img
Boot.img
Gapps
How to flash it:
( Actually the installation guide is provided with the .rar file downloaded. )
1. Download the system, boot & gapps from the links above.
2. Please make sure you have ADB & Fastboot available. If not please Google it or it's available in many thread too.
3. Now extract the "CarbonROM IMG Compressed.rar" to the ADB/Fastboot directory.
4. Copy the "boot.img" & "open_gapps-x86-5.1-pico-20160410.zip" to the same directory.
5. Reboot to recovery and clear user data.
6. Now from the recovery reboot to bootloader.
7. In the bootloader/droidboot/fastboot mode tpe in the following commands:
Code:
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash update open_gapps-x86-5.1-pico-20160410.zip
8. And you're done.
9. Please note that the first boot might take some time.
Thanks for giving it a shot...
XDA:DevDB Information
Carbon ROM for Zenfone 5, ROM for the Asus Zenfone 5
Contributors
PaletroxZ, tank0412, quanganh2627
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.10.x
ROM Firmware Required: Any 5.x.x based ROM
Based On: Carbon ROM
Version Information
Status: No Longer Updated
Created 2016-04-10
Last Updated 2016-11-04
--Error--
--Reserved--
--Error Again--
--Reserved Again--
Thanks @PaletroxZ i was actually waiting for this rom
shobint7 said:
Thanks @PaletroxZ i was actually waiting for this rom
Click to expand...
Click to collapse
You're welcome mate.
Sent from my ASUS_T00F using XDA-Developers mobile app
Good work! Welcome back! xD
Can you share your device tree? I want to look at it because i want to see all my mistakes. (I tried to build Carbon rom and i failed)
---------- Post added at 06:26 PM ---------- Previous post was at 06:20 PM ----------
And try this patch to fix vibrator:
https://github.com/quanganh2627/android_device_asus_a500cg-1/blob/aicp-r29/vibrator.patch
---------- Post added at 06:34 PM ---------- Previous post was at 06:26 PM ----------
And use zip archives instead of rar.
tank0412 said:
Good work! Welcome back! xD
Can you share your device tree? I want to look at it because i want to see all my mistakes. (I tried to build Carbon rom and i failed)
And try this patch to fix vibrator:
https://github.com/quanganh2627/android_device_asus_a500cg-1/blob/aicp-r29/vibrator.patch
And use zip archives instead of rar.
Click to expand...
Click to collapse
For vibrator is better to use this patch because quanganh's patch disables Low-Priority vibration.
Also, @PaletroxZ try this
- For late initial boot time
Code:
WITH_DEXPREOPT := true
Also I agree with tank, better use ZIP or 7-Zip to compress.
Hope it helps, great work!
Any ScreenShot?
Maybe i'll try sometime
Good job sir
Sent from my ASUS_T00F using Tapatalk
tank0412 said:
Good work! Welcome back! xD
Can you share your device tree? I want to look at it because i want to see all my mistakes. (I tried to build Carbon rom and i failed)
---------- Post added at 06:26 PM ---------- Previous post was at 06:20 PM ----------
And try this patch to fix vibrator:
https://github.com/quanganh2627/android_device_asus_a500cg-1/blob/aicp-r29/vibrator.patch
---------- Post added at 06:34 PM ---------- Previous post was at 06:26 PM ----------
And use zip archives instead of rar.
Click to expand...
Click to collapse
Okay mate I will. But there are also some mix up I did apart from the device tree. I'll PM you the download link . Thanks for helping us all out with the guides and ROMs mate...
dgadelha said:
For vibrator is better to use this patch because quanganh's patch disables Low-Priority vibration.
Also, @PaletroxZ try this
- For late initial boot time
Code:
WITH_DEXPREOPT := true
Also I agree with tank, better use ZIP or 7-Zip to compress.
Hope it helps, great work!
Click to expand...
Click to collapse
Thanks @dgadelha I'll give this a shot and let you know of the outcome ...
ShuviterDjogja said:
Any ScreenShot?
Maybe i'll try sometime
Good job sir
Sent from my ASUS_T00F using Tapatalk
Click to expand...
Click to collapse
I've attached the screenshots in the screenshots section mate.
Very good! New dev for zenfone 5. ?
clloud77 said:
Very good! New dev for zenfone 5.
Click to expand...
Click to collapse
lol he's not new. He's been making SleekStock Rom for us
ChristopherXI said:
lol he's not new. He's been making SleekStock Rom for us
Click to expand...
Click to collapse
Thanks My friend
Best part of this ROM
@PaletroxZ........bro.....the best part of this ROM is.......touch screen gets disabled when im in a call. I found other roms keep it enabled and caused me to turn on loud speaker/dialer/call hold/airplane mode etc. keep up your good work. :good: so far only 1 prob i have. like other custom roms, im facing the same camera black out issue.
a8962383 said:
@PaletroxZ........bro.....the best part of this ROM is.......touch screen gets disabled when im in a call. I found other roms keeps it enabled and caused me to turn on loud speaker/dialer/call hold/airplane mode etc. keep up your good work. :good: so far only 1 prob i have. like other custom roms, im facing the same camera black out issue.
Click to expand...
Click to collapse
Thanks mate . And could you elaborate the camera black out issue?
PaletroxZ said:
Thanks mate . And could you elaborate the camera black out issue?
Click to expand...
Click to collapse
My primary/back camera is always blank/dark/black when ever i open any camera app. It captures photos only when the flash is ON. Otherwise it takes black images. First, I thought it was related to hardware but i gave a try with stock(locked bootloader and only UL-ASUS_T00F-WW-2.21.40.30-user.zip, other zips couldn't fix it) and it worked fine. So the issue lies with unlocked bootloader/camera driver i guess, not with hardware. Moreover, when i turn on my front camera, it says "Camera failed to launch. Please reboot your device." pls check the attached log.
a8962383 said:
My primary/back camera is always blank/dark/black when ever i open any camera app. It captures photos only when the flash is ON. Otherwise it takes black images. First, I thought it was related to hardware but i gave a try with stock(locked bootloader and only UL-ASUS_T00F-WW-2.21.40.30-user.zip, other zips couldn't fix it) and it worked fine. So the issue lies with unlocked bootloader/camera driver i guess, not with hardware. Moreover, when i turn on my front camera, it says "Camera failed to launch. Please reboot your device." pls check the attached log.
Click to expand...
Click to collapse
I just looked at it.
connectLegacy: camera HAL module version 1 doesn't support connecting to legacy HAL devices
Other errors called by E/Camera_Conf and this:
[ 04-11 20:30:03.381 231: 5000 E/Camera_AtomAIQ ]
Error retrieving sensor params
[ 04-11 20:30:03.382 231: 5000 E/Camera_ControlThread ]
Error initializing 3A controls
[ 04-11 20:30:03.382 231: 5000 E/Camera_ISP ]
Xe Flash is supported only for primary camera!
[ 04-11 20:30:03.497 231: 5000 E/Camera_ScalerService ]
Atom_MessageQueue error: ScalerService queue should be empty. Find the bug.
[ 04-11 20:30:03.497 231: 5000 E/Camera_HAL ]
Error initializing ControlThread
So strange. Thats all.
a8962383 said:
My primary/back camera is always blank/dark/black when ever i open any camera app. It captures photos only when the flash is ON. Otherwise it takes black images. First, I thought it was related to hardware but i gave a try with stock(locked bootloader and only UL-ASUS_T00F-WW-2.21.40.30-user.zip, other zips couldn't fix it) and it worked fine. So the issue lies with unlocked bootloader/camera driver i guess, not with hardware. Moreover, when i turn on my front camera, it says "Camera failed to launch. Please reboot your device." pls check the attached log.
Click to expand...
Click to collapse
Hmm... Looks quite complicated. By the way did you check with other Camera Apps or try re-locking the bootloader? And I never got such issue. So which model are you precisely using, like a500cg or a502cg etc, which one??
PaletroxZ said:
Hmm... Looks quite complicated. By the way did you check with other Camera Apps or try re-locking the bootloader? And I never got such issue. So which model are you precisely using, like a500cg or a502cg etc, which one??
Click to expand...
Click to collapse
I have tried PixelMaster camera, CM default cam, CM cam2, Google Cam.........but the same issue persisted. My device is a500cg.
Mir Shahjahan said:
The ROM looks great. Thanks for this amazing work. I hope you'll fix all the bugs especially GPS
Click to expand...
Click to collapse
Other errors could be fixed but not the GPS. It's allmost impossible
a8962383 said:
I have tried PixelMaster camera, CM default cam, CM cam2, Google Cam.........but the same issue persisted. My device is a500cg.
Click to expand...
Click to collapse
Okay mate I'll look into it.
Mir Shahjahan said:
The ROM looks great. Thanks for this amazing work. I hope you'll fix all the bugs especially GPS
Click to expand...
Click to collapse
ChristopherXI said:
Other errors could be fixed but not the GPS. It's allmost impossible
Click to expand...
Click to collapse
I hope so too. Will need to check that out.
Code:
#include
/*
* I am not responsible for bricked devices, dead SD cards, thermonuclear
* war, or the current economic crisis caused by you following these
* directions. YOU are choosing to make these modificiations, and
* if you point your finger at me for messing up your device, I will
* laugh at you.
*/
This ROM is a personal project what i've working it... Different of official or non-modified sources, i've maked some forks and i'm building a ROM what have a lot of optimizations on device tree, kernel source, this will take a while but first new features are here:
21/12/2017 - First compillation:
-> Compilled with more audio processing support;
-> Compilled with mine Santoni Mods Pack modificantions (some of them);
-> Compilled with Kernel Source what will have future updates and improvements.
This rom is compilled based on these sources:
Device: github.com/LuizPauloDamaceno/android_device_xiaomi_santoni
Kernel: github.com/LuizPauloDamaceno/android_kernel_xiaomi_msm8937-1
What originally is based on these ones:
Kernel: github.com/Nikesh001/android_kernel_xiaomi_msm8937
Device: github.com/Nikesh001/android_device_xiaomi_santoni
For who don't know santoni mods pack: en.miui.com/thread-772720-1-1.html
ROM Download: www.androidfilehost.com/?w=files&flid=236707
I'm doing this on my free time, so please, be patient and say-me any trouble what you are experiencing.
Thanks.
Woow very nice. You next year next project Oreo rom?
Great job , next project oreo rom ?
bodnar1026 said:
Woow very nice. You next year next project Oreo rom?
Click to expand...
Click to collapse
I think yes, but first i will make this some updates, after, oreo.
Awsome work man . . hope to see oreo soon ?
Move ur thread on rom section bro
Will try this 4 sure. By the way many user want nethunter support on the kernel can u try to add it thank you
Please ask to moderator to move your thread to ROM & Kernel section. Thanks
LuizPauloDamaceno said:
Code:
#include
/*
* I am not responsible for bricked devices, dead SD cards, thermonuclear
* war, or the current economic crisis caused by you following these
* directions. YOU are choosing to make these modificiations, and
* if you point your finger at me for messing up your device, I will
* laugh at you.
*/
This ROM is a personal project what i've working it... Different of official or non-modified sources, i've maked some forks and i'm building a ROM what have a lot of optimizations on device tree, kernel source, this will take a while but first new features are here:
21/12/2017 - First compillation:
-> Compilled with more audio processing support;
-> Compilled with mine Santoni Mods Pack modificantions (some of them);
-> Compilled with Kernel Source what will have future updates and improvements.
This rom is compilled based on these sources:
Device: github.com/LuizPauloDamaceno/android_device_xiaomi_santoni
Kernel: github.com/LuizPauloDamaceno/android_kernel_xiaomi_msm8937-1
What originally is based on these ones:
Kernel: github.com/Nikesh001/android_kernel_xiaomi_msm8937
Device: github.com/Nikesh001/android_device_xiaomi_santoni
For who don't know santoni mods pack: en.miui.com/thread-772720-1-1.html
ROM Download: www.androidfilehost.com/?w=files&flid=236707
I'm doing this on my free time, so please, be patient and say-me any trouble what you are experiencing.
Thanks.
Click to expand...
Click to collapse
Hey... Great job dude.. but I think there must be two improvements
1. it doesn't reboots to recovery
2. "power menu" option required in hardware keys customization
I am on twrp 3.2.x
Great work.. but when I updated & installed Jan 3 release, recent key is not working.
Please don't ignore this post and send a solution immediately.
Apart from that, everything is buttery smooth. Especially, I am greatly impressed with this new kernel for fast charging.
And one more request. Please provide change-logs with the various releases.
Thanks for your assistance in advance.
gauravyadav712 said:
Please don't ignore this post and send a solution immediately.
Click to expand...
Click to collapse
Who are you to REQUEST an immediate response?
I had the same problem though: Button mapping seems to be a bit out of order. I was able to get the RECENT key to work changing the values in system/usr/keylayouts/Generic.kl - Button 139 needs to be declared as APP_SWITCH. Reboot and it works.
Sometimes the touch response feels a little dizzy, while the phone is charged. If I try to open an app on the homescreen, the app next to it launches. Its pretty easy to reproduce: Charge the phone, open the app drawer, try to long press on an icon: Most of the time, a totally different app launches. I did not have that problem while charging before. Happens while on an USB outlet of the laptop, so there is a pretty weak current ( like 500 milliamps max ).
Other than this, I did not encounter any problems so far :good:
Awesome work dev. It would be nice if you update the first post with the changelog when releasing a new image. I even didn't recognize that there are newer builds available.
Flashed version from 3. Jan today. No issues so far...
Regards,
Oliver
joha386 said:
Who are you to REQUEST an immediate response?
I had the same problem though: Button mapping seems to be a bit out of order. I was able to get the RECENT key to work changing the values in system/usr/keylayouts/Generic.kl - Button 139 needs to be declared as APP_SWITCH. Reboot and it works.
Sometimes the touch response feels a little dizzy, while the phone is charged. If I try to open an app on the homescreen, the app next to it launches. Its pretty easy to reproduce: Charge the phone, open the app drawer, try to long press on an icon: Most of the time, a totally different app launches. I did not have that problem while charging before. Happens while on an USB outlet of the laptop, so there is a pretty weak current ( like 500 milliamps max ).
Other than this, I did not encounter any problems so far :good:
Click to expand...
Click to collapse
Bro you dont have to do such hardwork . Just flash this file . This will fix the problem .
Still one issue.
Double tap to wake is not working. I am using January 3 release.
Hello!
I use lineage-14.1-20180117-UNOFFICIAL-santoni.zip, fm radio without RDS and not work irda.
Thanks for all the effort, it works nearly flawless on my device.
However, the github link for the current kernel does not work,
Could you please provide the kernel sources for your LOS port?
I'd be very much indebted to you,
if you could post the exact same ones used in the build you posted here.
Thanks in advance,
pinoaffe
I suspect that he is not allowed to post links. But the strings work. Copy the text to the browser...
Irblaster isn't working in 20180117 build for me, too.
Regards,
Oliver
olistudent said:
I suspect that he is not allowed to post links. But the strings work. Copy the text to the browser...
Irblaster isn't working in 20180117 build for me, too.
Regards,
Oliver
Click to expand...
Click to collapse
The url he posted for the current kernel sources does not work, it gives a 404.
I think it's this repo: https://github.com/LuizPauloDamaceno/msm-3.18
Regards,
Oliver
H!
Another bug, the statistics of the battery disappeared. And for the previous night, the charge decreased by 15%. Other assemblies were stricken overnight 1-2%. Applications are the same. I'll still watch, of course. But while here so. Version - lineage-14.1-20180117-UNOFFICIAL-santoni.zip
Developer : @vl_w
..soon official
Make sure to join>>>>Telegram Group : t.me/a300lineage_en
Github : https://github.com/vlw/android_device_samsung_a3lte
Supported Models:
* SM-A300F*
* SM-A300H*
* SM-A300M*
* SM-A300FU*
* SM-A300G*
* SM-A300Y*
* SM-A300YX*
Code:
* Your warranty is now void.
* The ROM is under developement and have some bugs.
* We are 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 us for messing up your device, we will laugh at you. By flashing this ROM, you accept this disclaimer.
Working : Everything .
BUGS : Let dev know .
Code:
* Steps for a Clean Install:
1) Put the .zip file in Internal or External Storage.
2) Reboot in Recovery Mode (Using TWR Recovery)
3) Wipe Data, Cache, Dalvik Cache and format /System
4) Install the ROM.
5) Flash the Google Apps you like.
6) Reboot and Enjoy!
ROM Download link : https://drive.google.com/file/d/1ki6A2YDplnW-bh8vWUti29CPOO1H1nqi/view?usp=sharing
latest update : https://androidfilehost.com/?fid=15664248565197181446
Recovery download link : https://androidfilehost.com/?fid=8889791610682896177
New build — 20210407 (Lineage 17.1)
Download:
https://drive.google.com/file/d/1OHDyqsyHCgc_fySisZQ-DEZWnF4It297/view?usp=sharing
Please consider donate to dev :
ETH: 0x8aee65788e039a9ac79f22d7bda6bdaa270ad4a2
Bitcoin: 1KCMryHTHSUKiEHkvvkCFCiS5Yxy7Nzh6Q
Latest version : 2021/04/07
@Ud4ba Please check your PM inbox. Thank you.
There will be soon an update for this ROM with a lot of fixes .
New update released today . Come join in telegram .
link:https://drive.google.com/file/d/1flQ6Yy1tnS5GXKxQE6P9TTmRpo95oR8l/view?usp=sharing
The update(17.1-20210323) brings :
* RAM optimization
* GPU render driver fix
* Faster screen on (changed touch-drivers behavior)
* Use SamsungDoze (should save battery)
* Fix NFC and battery leak on A300H
* Early bootanimation
Bug report :
VPN implementation is still broken
Reproduction step:
Install NetGuard and enable it..
Result:
No internet.
Thank you !
drnightshadow said:
Bug report :
VPN implementation is still broken
Reproduction step:
Install NetGuard and enable it..
Result:
No internet.
Thank you !
Click to expand...
Click to collapse
if im not wrong i found your post on reddit , too . I dont think there is a bug on VPN . My VPN works perfectly fine . And i tried with more than 2 VPNs .
Ud4ba said:
if im not wrong i found your post on reddit , too . I dont think there is a bug on VPN . My VPN works perfectly fine . And i tried with more than 2 VPNs .
Click to expand...
Click to collapse
Well it's still a bug and try orbot too. Its fails...
please tell your 2 vpn names .. I'll try it...
Every VPN app I tried including adaway VPN(non root method), all fails.
Thank you!
drnightshadow said:
Well it's still a bug and try orbot too. Its fails...
please tell your 2 vpn names .. I'll try it...
Every VPN app I tried including adaway VPN(non root method), all fails.
Thank you!
Click to expand...
Click to collapse
I have tried with ProtonVPN and MullvadVPN .
Edit : If you want to block ads on Android 9+ , use your Private DNS and set it to "dns.adguard.com" .
You will block all ads , and you will use 0GB of RAM or CPU .
drnightshadow said:
Bug report :
VPN implementation is still broken
Reproduction step:
Install NetGuard and enable it..
Result:
No internet.
Thank you !
Click to expand...
Click to collapse
FYI:
don't forget to join us on telegram with the dev!
See the link at the top of this page
carlos974 said:
FYI:
don't forget to join us on telegram with the dev!
See the link at the top of this page
Click to expand...
Click to collapse
I don't use TG, I respect my privacy.
If you're on TG, than you can report this bug, please. I really like to use fully working NetGuad. I'm rooted, so I'm using adaway root method and I'm happy with it. I can control host sources. So ads isn't my problems. And I'm also using XPrivacyLua for extra privacy protection. So all I miss is NetGuard.
Soo PLEASE again report this bug on TG and I hope dev will fix it.
Ah, yes say thank you to him in my name for developing LOS ROM for this old device. He's the beesssttt!
Thank you all!
drnightshadow said:
Bug report :
VPN implementation is still broken
Reproduction step:
Install NetGuard and enable it..
Result:
No internet.
Thank you !
Click to expand...
Click to collapse
Logcat for the dev!
I found this thread and became so thrilled that I could revive my old a3,
but there is always but,
no matter what I do I can't get 'unlock bootloader' (entry in settings) to appear.
Is there any way around it or some forced way to unlock bootloader, I assume it is necessary to have it unlocked, right?
kjsu0 said:
I found this thread and became so thrilled that I could revive my old a3,
but there is always but,
no matter what I do I can't get 'unlock bootloader' (entry in settings) to appear.
Is there any way around it or some forced way to unlock bootloader, I assume it is necessary to have it unlocked, right?
Click to expand...
Click to collapse
I would recommend you to join our telegram .
kjsu0 said:
I found this thread and became so thrilled that I could revive my old a3,
but there is always but,
no matter what I do I can't get 'unlock bootloader' (entry in settings) to appear.
Is there any way around it or some forced way to unlock bootloader, I assume it is necessary to have it unlocked, right?
Click to expand...
Click to collapse
A3 from 2015 doesn't have locked bootloader lol, all you need is flashing twrp from odin and viola you can flash any rom or root.
Search on xda forum for more info, but you can start with this link
[How to] Root, TWRP, Flash A300FU / A300Y Noob friendly guide
Bevor you do something with your Device do a Backup of all your Data (Contacts, Pic´s ect.) outside of your Device (in a Cloud or on your PC) I'm not responsible for bricked devices, dead SD Cards, broken phone chargers etc.You do all at your own...
forum.xda-developers.com
Good luck!
That's something lol. I'm so accustomed to always go through some 'unlocking' procedures that I didn't even realize that this also is true.
I have few more questions:
1) asaik Knox warranty void change from 0x0 to 0x1 is normal but on bootup also appeared new message:
Set Warranty Bit : kernel
I assume that it is ok as well ?
2) is this rom set to permissive or enforcing ?
permissive
3) checking help dev box on rom installation is enough for devs or you need some more logs to figure things out?
kjsu0 said:
That's something lol. I'm so accustomed to always go through some 'unlocking' procedures that I didn't even realize that this also is true.
I have few more questions:
1) asaik Knox warranty void change from 0x0 to 0x1 is normal but on bootup also appeared new message:
Set Warranty Bit : kernel
I assume that it is ok as well ?
2) is this rom set to permissive or enforcing ?
permissive
3) checking help dev box on rom installation is enough for devs or you need some more logs to figure things out?
Click to expand...
Click to collapse
1. Yes, yes
2. Right
3. Yes, but you can read how to log cat from my previous link.
Sorry that's it, we're going too much off topic. Read and search xda furum like "A300FU".
Good luck and stay safe!
Excited about the idea to have 10 on a Samsung A3 (2015)!
Little questions:
* is everything working as of today (sound, GPS, etc.) or are there still bugs?
* out of curiosity, why isn't it listed here: https://download.lineageos.org/
?
ErnestErnest25 said:
Excited about the idea to have 10 on a Samsung A3 (2015)!
Little questions:
* is everything working as of today (sound, GPS, etc.) or are there still bugs?
* out of curiosity, why isn't it listed here: https://download.lineageos.org/
?
Click to expand...
Click to collapse
Read the the title..
pro tip : unofficial
> is everything working as of today
Click to expand...
Click to collapse
Everything works great but it might vary depending on model in use
> out of curiosity, why isn't it listed here:
Click to expand...
Click to collapse
It's unofficial but I read somewhere that it might become official for now it looks like releases are somewhat irregular eg. latest come with security patches from December 2020.
kjsu0 said:
Everything works great but it might vary depending on model in use
It's unofficial but I read somewhere that it might become official for now it looks like releases are somewhat irregular eg. latest come with security patches from December 2020.
Click to expand...
Click to collapse
source???? You read.. where? Fake news? There is no news about that on any official sites. Who are maintenances?