I am on Note 4 Alpha S6 Revolution rom, with NK1 baseband and 3.4.0-Motion V2 kernel by aapav.
For Private Mode, I tried a few things like reinstalling by copying PersonalPageService.apk in system apps, using XSecureStorage in Xposed, after that tried with uninstalling Xposed.
But none of them could get it worked.
Each time after turning it on, it says "Failed to enable Private Mode. Try again".
I've googled and searched a lot of forums also but there's no solution, maybe some of you can help me.
Because the other rom which operates on almost same features and firmware kitkat has the private mode running smoothly(i.e. S6 Styled S5 Port Rom),
I'm unable to understand the difference, if some of you can help or give some tips, it would be nice.
Must reply.
Thanks.
Hi,
in my spare free time I compiled a new unofficial LineageOS 14.1 ROM on my beloved Phenom II system with ECC RAM and made it available to you for 90 days from
https://www.filefactory.com/file/5fqmz223n9gx/lineage-14.1-20170403-UNOFFICIAL-SonyLOS-kugo.zip
https://www.filefactory.com/file/121p40o8v8gb/lineage-14.1-20170403-UNOFFICIAL-SonyLOS-kugo.zip.md5sum
The ROM can be installed through a recovery like TWRP. I also applied some modifications, in particular:
- the SonyLOS kernel has been replaced with the Sony AOSP version which seemed to be more up to date
- using some 7.1 binaries of Sony AOSP instead of the 7.0 binaries used earlier enabling some more features (?)
- replaced the LineageOS camera with the Simple Camera app
- integrated Total Commander, Apollo music player v2, SELinux permission changer and Viper4Android apps since I need them
Consequently,
- patchlevel now is March 5th, 2017
- the fingerprint sensor now seems to be usable to unlock your device
- the FM radio works (however, you have to manually scan through the stations once because automatically finding the stations initially still does not seem to work completely)
- the selfie camera image no longer will be upside down (seemed to be an issue with the LineageOS camera app, also will work correctly with i.e. Focal if you prefer a sophisticated app instead of Simple Camera)
- I can now use Apollo again as I did on the Z1 compact with CM 12
- the bass boost and equalizer are back with Viper, you just need to invoke the SELinux changer on the rooted device and install the drivers initially through Viper itself
Thanks fly out to Sony AOSP, SonyLOS and the app providers. Feedback is also very welcome.
Regards,
jtk_de
@admin: Could we please move this thread and my previous one to the ROM section ? I'm still not allowed to post something there
Great to see you're still updating your ROM. Don't understand why you upload at filefactory (sloooow download) instead of androidfilehost for example. Will flash your ROM tomorrow.
- should I flash a stock ROM first or does it not matter which version I'm coming from
- what do I need the .md5sum file for?
- gapps are not included, right?
I tried to use androidfilehost but my uploads got interrupted so I had to stick with filefactory for now. You don't need to flash the stock ROM first, just wipe the system, cache etc. partitions in your recovery and flash the .zip.
The md5sum checksum file is there to ensure the ROM integrity and is not needed for the flash, however, TWRP optionally can read it and veryify that the ROM has been correctly downloaded and copied to your phone's storage. Gapps is not included since I use alternative apps, hence it must be installed separately.
Root access is integrated already and can be controlled via the developer settings. The only issue I experienced so far is that the volume cannot be altered yet during phone calls
I don't get viper4android to work. I install the drivers, reboot my device and then viper4android prompts me to install the drivers again. Am I doing something wrong?
Micka84 said:
I don't get viper4android to work. I install the drivers, reboot my device and then viper4android prompts me to install the drivers again. Am I doing something wrong?
Click to expand...
Click to collapse
You need to enable root first and start the SELinuxModeChanger installed with the ROM and set SELinux to "Permissive". Then the Viper drivers can be installed which can take quite long (a minute or so). If an Android dialog pops up because of this confirm that you would like to wait longer. Then reboot as indicated and enjoy the bass
That worked for me thank you
Hey,
many thanks for that ROM. Unfortunately i end up in a never ending boot animation. If i get in recovery (TWRP) and tell him to reboot, it tells me that no OS is installed. Any hints how this can be solved?
Thanks for any advice!
dreadavi said:
Hey,
many thanks for that ROM. Unfortunately i end up in a never ending boot animation. If i get in recovery (TWRP) and tell him to reboot, it tells me that no OS is installed. Any hints how this can be solved?
Thanks for any advice!
Click to expand...
Click to collapse
Hi!
I think there aren't any os on your device, thats wha twrp sad that... because, your systems encrypted. You could remove it. Try to flash again twrp from fastboot, than clear cache ( fastboot format cache ) and userdata ( fastboot format userdata ) from flashtools too. After that boot to twrp, than you could mount system, than flash the whole cm rom again. After that, i think it will boot correctly.
lba810701 said:
Hi!
I think there aren't any os on your device, thats wha twrp sad that... because, your systems encrypted. You could remove it. Try to flash again twrp from fastboot, than clear cache ( fastboot format cache ) and userdata ( fastboot format userdata ) from flashtools too. After that boot to twrp, than you could mount system, than flash the whole cm rom again. After that, i think it will boot correctly.
Click to expand...
Click to collapse
Thanks for the hint. Did what you said, but i cant mount system in recovery. It cant be selected in the list. Any other suggestions? Ok solved it. had to flash stock rom and boot.img before the steps you asked me to try. Thank you!
Thank you for putting this ROM together! There are the following problems on the OmniROM:
1. Incall speaker volume is not controllable
2. Slight incall echo on receiving side
3. Double tap to wake doesn't work
Is this still the case for your Lineage ROM?
avion540 said:
Thank you for putting this ROM together! There are the following problems on the OmniROM:
1. Incall speaker volume is not controllable
2. Slight incall echo on receiving side
3. Double tap to wake doesn't work
Is this still the case for your Lineage ROM?
Click to expand...
Click to collapse
1. Yes, the volume can't be changed during phonecalls
2. Didn't notice any echos so far
3. True
Could you try uploading to mega.nz? FileFactory is so slow
minimum Brightness
Hey!
i was just wondering if its possible to lower the minimal brightness a bit more. because minimal brightness is quite bright still. Im using this ROM for a few days now. Everything works pretty fine, but the battery life is a bit short for what i was expecting. If i dont use extreme battery saving mode its always around 24 hours. i barely do phone calls and i use it not very intensively... Highest Consumer is standby with 5%, which i think is wierd, isn´t it?
:good: Kudos. Everything seems to work well aside from the Bluetooth Audio cutting out after a few minutes. Overall I am really happy with it - happy enough that it's my daily driver.
Hi!
ROM will be better and better. Thanks.
Battery charging speed a bit slow, and if I'm using a mobil net, it's draining a little fast, plus in the evening, with wifi on, it goes down nearly 5%>. Camera is good. But, im using open cam software from google play. Fingerprint sensor working good, just a little hard to configure it. I'm using substratum theme engine, and i can theme most of the base and google apps. ( Except fingerprint sensor, with themed settings, the fingerprint setup screen cracked... but inthinknits theme problem ) And about bluethooth.. yes, it's dropping the connection after a few secs. But, if you left it, then reconnect automatically and just after that, it goes good. Until you turn it off. I used a sony sbh70 wireless headset with power amp.
And echo sound in calling. I can't hear echo, but other peoples in line, they sad it. They hear onselfs twice.. :/
If you would like it, maybe i can upload a logfile ( with matlog ) about the bluethooth problem.
Anyway, thanks foe thiese rom for our x compact.
It's good to see some other people are using the ROM and testing things that I can't test
According to my own experience battery lifetime is around 2-3 days when surfing via wi-fi, listening to music and calling from time to time. Battery charging with the Sony AC adapter coming with the phone is quite quick compared to the Z1C although the battery capacity is higher.
If I make another build I'll upload it to some faster provider though.
hello all,
give it some news there? Last entry April 2017.....
Hi all, are there some updates? I love Lineage OS
I'm wondering why there isn't an official build for the Xperia X Compact yet ? If I google "kugo lineageos" I get a hit for a stats page:
https://stats.lineageos.org/model/kugo
Which just says the page isn't rendered yet, but obviously someone has been devoting his/her time to the kugo. What could be the hold up? Same goes for the lack of other roms btw. It seems Sony is quite open towards the community but somehow this hasn't resulted in the overwhelming amount of roms I was hoping for ... It's quite underwhelming in fact. Could it be not enough (knowledgable) people own an Xperia X Compact ?
harryharryharry said:
It seems Sony is quite open towards the community but somehow this hasn't resulted in the overwhelming amount of roms I was hoping for ... It's quite underwhelming in fact. Could it be not enough (knowledgable) people own an Xperia X Compact ?
Click to expand...
Click to collapse
Sony gives us a sliver of what is needed for AOSP to run, camera, bluetooth, wifi, and radio band stuff all has to be manually made to work. The z3 line was the ONLY xperia line to ever get mainstream AOSP support from devs. If you bought your xperia thinking Sony's AOSP program was good you were sadly mistaken.
Hi everyone!
We've got three Redmi Pro in our family (two 3/64 GB and one 4/128 GB) - and unfortunately, two of them have the very same MAC-Adress. And this causes constant WiFi-Problems!
I tried almost every App and the Engeneer Mode to change the WLAN-MAC-Adress on my Redmi Pro Exclusive 4/128 GB (MIUI 8.3 from xiaomi.eu, TWRP 3.1.1, SuperSu 2.82, Xposed Framework, BusyBox, SELinux Toggler,....) - but nothing worked.
In another thread somebody with a Redmi Note 4 (MTK X20) succeded with changing SELinux to permissive and then using ChameleMAC and/or Engeneer Mode. This made me optimistic, because the CPU is quite similar to our MTK X25....
But ChameleMAC says "Device not supported" and in Engeneer Mode, I can't change the adress either (also I "write" a new MAC-Adress several times...)
Any ideas or solutions? Every help is greatly appreciated!
UPDATE!
I could install the SELinux Toggler by flashing the ZIP with TWRP... and could finally change the WLAN-MAC-Adress (after a few attempts) with SELinux set to permissive and writing a new MAC-Adress within the Engeneer Mode...
The only strange thing is, that after the first reboot the MAC-Adress changed again to a completely new one. But since then, it stays the same so far...
If you haven't already, try a MAC spoofer - it won't change your mac permanently, but will temporarily change it to something else. Here's a tutorial.
Finally succeded in changing my WLAN-MAC-Adress....but
theOriginalSuperl2 said:
If you haven't already, try a MAC spoofer - it won't change your mac permanently, but will temporarily change it to something else. Here's a tutorial.
Click to expand...
Click to collapse
Thanks for the tipp - but none of the MAC spoofers worked either...
But somehow I managed to change my WLAN-MAC-Adress with SELinux changed to permissive and writing a new MAC-Adress within the Engeneer Mode...
The only thing that is strange is, that after a reboot, I have a different (complete new) MAC-Adress...!?
Solutionman said:
Hi everyone!
We've got three Redmi Pro in our family (two 3/64 GB and one 4/128 GB) - and unfortunately, two of them have the very same MAC-Adress. And this causes constant WiFi-Problems!
I tried almost every App and the Engeneer Mode to change the WLAN-MAC-Adress on my Redmi Pro Exclusive 4/128 GB (MIUI 8.3 from xiaomi.eu, TWRP 3.1.1, SuperSu 2.82, Xposed Framework, BusyBox, SELinux Toggler,....) - but nothing worked.
In another thread somebody with a Redmi Note 4 (MTK X20) succeded with changing SELinux to permissive and then using ChameleMAC and/or Engeneer Mode. This made me optimistic, because the CPU is quite similar to our MTK X25....
But ChameleMAC says "Device not supported" and in Engeneer Mode, I can't change the adress either (also I "write" a new MAC-Adress several times...)
Any ideas or solutions? Every help is greatly appreciated!
UPDATE!
I could install the SELinux Toggler by flashing the ZIP with TWRP... and could finally change the WLAN-MAC-Adress (after a few attempts) with SELinux set to permissive and writing a new MAC-Adress within the Engeneer Mode...
The only strange thing is, that after the first reboot the MAC-Adress changed again to a completely new one. But since then, it stays the same so far...
Click to expand...
Click to collapse
for the snapdragon series (mido) is not permanent using change mac or the type of application in the play store ..., when restarting android he will return as before. you have to use QPTS to be permanent .. i have reset several times and its result is permanent. i think problem mac macress error can be resolved.
Code:
A couple of days ago I saw someone who claims to have a fix for random reboots in custom 5.0+ ROMs and after testing for 3 days till now not even a single auto reboot occurred
Please try it and tell me if it works
The fix is basically changing selinux mode from permissive to enforcing and there's an app for it called "selinux mode changer"
You'll find a link for it below
Note: I'm using Resurrection remix N 5.3.8 with built in selinux mode changer
I'm not a developer and don't know what it does so it's not my fault for anything damaged or any files missing
I accidentally cleared my browser's history and i tried to find the orginal forum to give credit to right people with no luck of finding it
if you know it please put the link in comments
Flashable zip link: [URL="https://drive.google.com/file/d/0B9MaJmh__z8uaUxoMGZISXlFNGs/view?usp=drivesdk"][url]https://drive.google.com/file/d/0B9MaJmh__z8uaUxoMGZISXlFNGs/view?usp=drivesdk[/url][/URL]
https://forum.xda-developers.com/galaxy-tab-2/general/fix-random-reboots-android-lollipop-t3310134
Here's the original post
Hey guys i currently have the atoto a6 pro model without gesture, and the problem im having is it is currently rooted and every time i open viper4android itll ask me to install drivers then it will reboot and when i open it again it basically asks for me to do it again. I can not for the life of me figure out how to fix this, I tried to change mode to permissive but i try to do it with terminal emulator where i put in setenforce 0 and it comes with selinux disabled or something like that. I even tried the selinux mode changer and it didnt work either. I really want to use viper4android if i cant ill have to send this unit back because there is hardly any eq options stock.
Can anyone help me with this? would really like get this problem fixed.
You have busy box installed??
Enviado do meu iPhone usando o Tapatalk
Yes busy box is installed.
Can anyone recommend the new joying unit? It seems to have a really nice eq, and fastboot. But hows the rca voltage? The atoto a6 has 4v preouts.
Did op ever work this out?