The info about the issues provided as on 2017 September 13.
The text was last edited on 2019 August 24.
Hello.
Sorry for mistakes in my poor English.
I had used every day LOS14.1 and RR5.8.3-5.8.4 custom ROMs for Samsung Galaxy S2 (model: GT-I9100) for more than 2 months in the middle of 2017 and this is my serious test report:
1) When you will get an incoming phone call, receive a message via cellular network or a file via bluetooth then Galaxy S2 with the custom ROM will rings and vibrates but the screen can be fully dark for several seconds without any notification about it.
This bug almost does not exist in RR 5.8.4.
2) Multiple issues are with the smartphone storages (internal and external).
a) Some apps can do not work with the smartphone storages. They can start to work with storages after the smartphone reboot or after few reboots only.
The same bug is in the Resurrection Remix ROM 5.8.4. The screenshots attached to this message proof the existense of this bug in RR 5.8.4.
b) Only during my attempt to use the custom ROMs LOS 14.1 and RR 5.8.3-5.8.4 on Samsung Galaxy S2, I lost the 1 file (it was the important file to me) on an external microSD card and yet file explorer apps start to show the 2 suspicious unerasable zero size files in file listings there, which I can not delete nor rename nor even copy - file explorers to continue to show they in file listings still today after years on my microSD card. It is interesting that these zero size undeletable files was discovered not in an upper directory but instead deep in the old different long directories on my microSD card. Thus, may they was implemented hiddenly as masking labels there for a reason remained unknown.
c) Impossible to appoint an user installed file explorer app as a default file explorer for pick-up files from another programs. For instance, when the smartphone user want to send a file via Skype then there is always only the file explorer opens with the poor and uncomfortable interface, which implemented in the custom ROM as default forever. And only then from its ugly interface the user can choose one of other installed file explorers for using they once for find and pick-up a file.
The famous FX File Explorer app does not work with the default internal folder 'Documents'. The app also can not delete a group of selected files on an external SD card.
The RR 5.8.4 ROM haves even 2 implemented file manager apps which work smooth but they both have poor UIs with limited functions.
Factually, do not providing Android APIs correctly the custom ROM developers refuse to use user installed apps fullfledgely but instead they compel the users of their ROMs to use only an ersatz bloatware soft implemented by the ROM developers in the custom ROMs.
3) The big battery drain after every reboot and a significant battery drain in general.
As more media files (videous, images include offline map tiles, sounds) are in the internal or external storage (an microSD card) of smartphone then more extensive battery drain Galaxy S2 will suffer after every reboot and after some operations with access to storages. This bug appears in both ROMs: in Lineage OS 14.1 and in Resurrection Remix 5.8.3 - 5.8.4.
For instance, if 128GB microSD card almost full of various videous and photos is in the smartphone then it becomes very hot for more than 1 hour after every reboot!
Some my futher research reveals that the high temperature with the battery drain caused by the dubious activity of Media Storage app implemented in the Lineage OS based ROMs hiddenly. This app finds and analises all media files (and may more) by unoptimized and uneffective way creating and saving big hidden databases, wasting CPU, a battery and an internal storage.
Unfortunately, disabling of this dubious hidden app leads to the smartphone loses functionality partly.
Please, pay in opinion that this bug produces the same traces as usually produced by some hidden virus activity: excessive scanning of user files, an unexpected load on the hardware, eventual draining of the battery...
4) Multiple lags (short freezes) are at various programs interfaces using. A main Android 7 menu is more or less smooth only.
For instance, Skype app version 8 has lags to several seconds in its menu.
Also the smartphone touchscreen is more sensible with the latest original Samsung's firmware (Android 4.1.2) rather than with LOS 14.1 or RR 5.8.4.
On another hand, Galaxy S2 with LOS 14.1 or with RR 5.8.4 scores more points in AnTuTu test but it is only mostly due to becoming of supporting F2FS and yet getting additional points for an newer additional rendering engine.
5) Sometimes over-the-air updates becomes impossible due to already after downloading an update file the smartphone then displays an error message 'Unable to reboot into recovery'. For instance, this bug appears after 2nd August 2017 and 23th August 2017 updates.
6) Camera1 and Camera2 APIs do not provided correctly. Some serious camera apps report about it clearly by a message and then close. Another camera apps are buggy.
I just will give few examples...
All videous recorded with a mono sound only but can be saved as allegedly with a stereo sound.
The famous A Better Camera app by Almalence loses all its settings unexpectedly time to time and becomes as its first launch again. This bug does not exist in RR 5.8.4 but instead there is another bug with A Better Camera app: it can not record videous with scene mode setting. And it is very sad due to the app can significantly improve the camera in our old device specially for photo and videorecordings in low light conditions (it can be reached by choosing manually ISO800 and then the Fireworks scene mode).
The implemented in the ROM the Snap camera app is very weak with the ugly uncomfortable interface.
7) There is a trouble to enter the year manually in the data settings in a portrait mode due to number of years limitation. The same bug was in RR 5.8.3 but it was fixed in RR 5.8.4.
This bug does not exist in a landscape mode.
8) It can send and receive only the very limited kinds of files via bluetooth, which filename extensions are listed among a poor list of files recognised by the custom ROM itself (not by user installed apps). Factually, it is like an unwanted blocking filter at the bluetooth.
For instance, you can create an effective compressed .zipx archive file by the WinZip app for Android OS on Galaxy S2 but you will be unable to send such archive file via bluetooth. And you will be unable to receive such files too.
Many file extensions do not recognized by the custom smartphone ROM: among they are modern Opus music format, RAR archives and etc, etc. You will be unable to send or receive they via bluetooth.
The same bug is in RR 5.8.4.
Please, pay in opinion this issue does not seem as a mistake of the ROM developers but just opposit: it seems more as an unwanted blocking filter specially implemented on the bluetooth. And their reason for it remains unclear and suspicious.
9) There is an implemented feature to record a phone call but there is not an option to record all phone calls automatically. Instead only after hand up there inside the tree of dialer settings appears a hidden option which allow manually start to record the current call. So, if you want to record the call then only already during the call you need to go into the dialer menu tree and activate this hidden option, which is uncomfortable.
Moreover, external apps for phone call recordings does not work properly with this ROM (they do not record sounds from another side).
The same bug is and in RR 5.8.4.
10) The famous SuperSU root tool by ChainFire does not compatible with Lineage OS 14.1 for Galaxy S2. And apps which require only the SuperSU root can do not work properly.
The same bug is in the Resurrection Remix 5.8.4.
11) The small window with the text 'MTP host error' appears in the screen foreground like a ghost.
The same bug is in RR 5.8.4.
12) The settings menu haves a white background everywhere and it causes wasting of short lifetime span of pixels of OLED display triggering yet the additional unwanted battery drain and provoking an eye strain.
Unfortunately, a wallpaper does not change it.
There is not a simple option in the settings menu for just to change its white background to black.
It is not a bug but it is a significant disadvantage of the Lineage based ROMs - specially the Resurrection Remix ROM, which haves miltiple various settings and options but except needful simple this one.
13) The official Lineage OS bug tracker does not accept bug reports by easy way. Instead it requests a registration in advance via a full user name and other personal data, which can be sensitive and used by unappropriate way. It does not allow the registration via the World famous and trusted Google+ or Facebook social networks. Moreover, sometimes the bug tracker does not work and have an announcement about sheduled technical maintenance on a web-hosting side.
14) The ROM developers do not fix even well known simple bugs like described here at the points 8 or 9.
Talking very softly: some XDA forum users (include moderators) also do not welcome for public bug reports in proper topics of the XDA forum. It seems like they conceal the existence of many bugs and only lure new people to become victims of the buggy ROMs. And I did started this topic for stop it.
I do not know what their purpose is exactly.
But after some time observation it is possible to determine that someone actually regularly 'dilute' proper topics on the XDA forum by short luring messages in parrot style like 'I had installed it and it is great!' Unfortunately, such kind of simple messages are just alluring fakes high probably.
The another short trap parrot messages are like that 'It runs fast and smooth!'. The deception there is that it attracts only by the Android 7.1.2 menu appearance on the old device for purposes like a brag but really conceal that the whole device with this ROM becomes unreliable for serious fullfledge using.
I was attracted by topics on the XDA forum about Android 7.1.2 for Samsung Galaxy S2 (model: GT-I9100) and I had lost more than 2 months period installing latest Lineage OS 14.1 updates and Resurrection Remix ROMs 5.8.3 - 5.8.4 and I had decided that the last official Samsung's firmware with Android 4.1.2 is not ideal but much reliable on Galaxy S2 rather than LOS 14.1 or RR 5.8.4.
15) The custom ROMs does not provided as a single useful full package unlike it was with a Samsung's official firmwares. Actually, things, which called Lineage OS 14.1 or RR 5.8.4 for Galaxy S2, are main parts of unresonant firmwares only. It means that in a case of installing such firmwares the user discovers many disadvantages of they and after asking questions on the XDA forum he gets endless tips like: to find in the internet and install other necessly parts and yet to make very specific technical adjustments manually or even experiment with they. All it can be interesting and feasible for the smartphone entusiasts but not for an ordinary user.
For instance, some messages on the XDA forum suggest to download and install the special version of Kernel Adiutor app then run it and experiment with its settings for make the smartphone runs smooth because the ROM developers did not preselect best settings and did not adjusted they before as default values. Moreover, you will need to find in the internet and install separately yet a modem firmware for a better signal, the Substratum app and a proper theme just for make the screen background black everywhere and etc, etc.
Factually, Lineage OS 14.1 and Resurrection Remix 5.8.3 or 5.8.4 ROMs for the Samsung Galaxy S2 smartphone are not 'Plug&Play' kind of firmwares. They are unfeasible for an average user.
Please, pay serious attention: an user of these buggy custom ROMs can get a negative impact to his behavior (even to his mental health) and to his business.
JaLoou said:
[...]last official Samsung's firmware with Android 4.1.2 is not ideal but much reliable on Galaxy S2[...]
Click to expand...
Click to collapse
Obvious obviousness.
Custom ROMs are not meant to replace commercial firmware, but so that the community can learn and be happy to discover new things.
The screenshots, published with this message, proof the big battery drain after reboot and yet just after charging without even using the Galaxy S2.
I had experiment specially:
after the middle of a night I had swithed off my smartphone, I charged it to 100%, unplugged then I switched it on and leaved immidiately for several hours while I sleeping to late morning.
Then I got the varios battery stats and saved it on the 3 screenshots.
So, everyone can see that the battery lost 39% from full charge without the smartphone being used by the user for several hours.
Moreover, there is a big battery drain just after every charging without the smartphone using and 4th screenshot proofs it too.
And later in response to some nit-pick criticism about this battery consumption test then I had attached yet here a 5th screenshot of the same stand-by battery test on my device swithing on after a full charge but with Samsung's latest official firmware with Android 4.1.2. So, 5 screenshots here give a full picture for compare easy the custom ROMs and Samsung's latest official firmware with Android 4.1.2 in the terms of power consumption.
You can see it clearly that Samsung's latest official healty ROM with Android 4.1.2 consumes not only much less power in stand-by mode but also it consumes power for another purposes at all mostly for cellular network only while the suspicious custom ROMs like LOS 14.1 or RR 5.8.3-5.8.4 consume the enormous big amount of power like crocodiles at stand-by mode for the unwanted excessive file scanning on the user's smartphone!
The next screenshot proofs the bug of inability to install over-the-air updates (after a firmware update file already downloaded the smartphone shows the error message 'Unable to reboot into recovery').
Please keep in mind that none of the developers gets paid for his work. Complaining about bugs not being fixed like this appears disrespectful to me.
Thanks anyway for the thread, might help some people to decide whether to give this ROM a shot or not.
A big thanks to the XDA-Devs for this ROM which I have on my phone since 2 months.
In this time, I haven't been able to "seriously" use my phone. Everything is working except the bugs mentionned above, but the phone has become soooo slow... and some issues with battery life also. Sometimes the device just gets hot in my pocket for no reason, drains half the battery in a few minutes (though I have done the "calibration").
Every action becomes a hassle, but works in the end. It's like using Windows 95 on a 486.
So: nice if you want to try out stuff, but no to recommended for every day use IMHO.
BenjyTec said:
Please keep in mind that none of the developers gets paid for his work. Complaining about bugs not being fixed like this appears disrespectful to me.
Thanks anyway for the thread, might help some people to decide whether to give this ROM a shot or not.
Click to expand...
Click to collapse
Concealing many bugs the ROM developers did lured me (and many others) as free unpaid beta-testers for their unreliable ROM.
Moreover, the bug tracking functions in Lineage OS and Resurrection Remix are not clear and suspicious. Persons who manage it can get easy a various sensitive information about the smartphone users and can use this data by unappropriate way.
If sort the all known bugs then it is possible to reveal easy that the most part of they haves access to user files on the smartphone. These bugs are:
- the unwanted blocking filter at bluetooth,
- excessive user files scanning,
- wrongly provided Android APIs accompanied with attempts to constraint the users to use only the bloatware ersatz file managers implemented in the custom ROMs and an ugly bloatware ersatz camera app.
The bugs mentioned above are well known but did not fixed for a long period of time. And it triggers really an assumption that they can be specially implemented in the custom ROMs for get a full control over the user files without the user knowledge about it. By another words they are not the unfixed bugs but they are the traces of hidden viruses implemented in the custom ROMs.
These viruses can be ordered and paid masking via chains of proxies by an interested party. Ordered viruses and vulnerabilities can be easy implemented villaintly inside some of many allegedly useful patches on every stage in a long way from an initial open publication of Google's Android source code to a last compilation for get a firmware binary file for a target gadget model.
The device Samsung Galaxy S2 was sold over 40 millions (according to Wikipedia). High probably several millions (may even decades of millions) are remain in use today. And they are an attractive target for an interested party.
Moreover, viruses implemented in a firmware almost impossible to determine by an antivirus software.
The party interested in productions of infected custom ROMs can be also discovered easy by researching and proper sorting the several users of the XDA forum, which was indicated in the hostil activity: they was against the public exposures of serious issues in the custom ROMs, they did tried masked to blackwash me and they lure really new people to become unwill victims of the unreliable custom ROMs. The convinced persons are all have same specific feature...
Unfortunately, one of the XDA moderators forbid to explain about it futher.
But what I allowed to tell here is that any custom ROM development can be supported by a party interested in a mass distribution of viruses hidden in firmwares.
Complaining about bugs not being fixed like this appears disrespectful to me.
Click to expand...
Click to collapse
Fully disagreed, as long it's constructive critism it helps other to see what is currently working and what not to easier decide to switch to the ROM or not. The main reason is (I asume) to show the list of bugs, which make sense cause the specific LOS thread not shows the current issue, or you need to go trough each comment separately.
I'm glad we still getting updates and **** but some bugs are years old and just migrated because no one seriously took a closer look at it, so I'm happy that this thread exist to share the experience and to list the known issue.
Here you are, not the developers, not doing the right thing.
You want everything at once, and what you did for it.
https://forum.xda-developers.com/showpost.php?p=73346796&postcount=1814
CHEF-KOCH said:
Fully disagreed, as long it's constructive critism it helps other to see what is currently working and what not to easier decide to switch to the ROM or not. The main reason is (I asume) to show the list of bugs, which make sense cause the specific LOS thread not shows the current issue, or you need to go trough each comment separately.
Click to expand...
Click to collapse
Exactly what I wrote in the second half of my post
I understood the purpose of this thread. What I said just refers to two or three sentences the OP posted. Thank you and goodbye.
JaLoou said:
In this message I only want to publish screenshots, which proof just one of many stupid bugs in Lineage OS 14.1 (Android 7.1.2) for Samsung Galaxy S2 (GT-I9100) smartphone.
As you can see sometimes an user is able to press link 'connect' after entering even 5 symbols of password for WiFi!
But an user is denied of possibility to connect to a WiFi hotspot if he did entered a password of 8 symbol length!
Or 9 symbols and etc, etc!
I did received and installed new updates for Lineage 14.1 every week but NO one known bug was fixed include this one.
Click to expand...
Click to collapse
First of all, Please don't use !!!!!! It looks like you offend people!! Even people who tries to help you!
Secondly, the issue isn't an issue of i9100. It is an issue of the ROM, meaning on all devices. A device maintainer maintains his devices when something changes in the ROM (changes in LineageOS and Android google sources) to keep it up to date.
Thirdly, have you ever connected with your dummy passwords to the Wifi Access Point? Or are you just trying to find "stupid" bugs?
There is a validation mechanism depending on the used security type of the Access Point which is auto detected
WPA2 PSK => minimal password length is 8 WEP
WEP40/104/128 => valid lengths 5, 13, 16 or HEX-values valid lengths 10, 26, 32 and ofcourse 0-9 A-F as allowed characters
If you want to help, try to configure your WIFI access points and verify LineageOS's behavior when configuring with WPA2 PSK/WEP.
Also look in JIRA if the issue is already reported. I saw this issue last week about wifi-password for example:
https://jira.lineageos.org/browse/REGRESSION-912?jql=text ~ "wifi password"
---------- Post added at 06:46 PM ---------- Previous post was at 05:55 PM ----------
Here are my comments on your reported bugs.
1) When you will get an incoming phone call or receive a message then your Galaxy S2 will ring and vibrate but the screen can be fully dark without any notification about the call.
I'm aware of this symptom. The problem is memory and running background processes. Having to much apps installed (Facebook, instagram, snapchat, etc) causes the OS to memory swap when the phone-app must be active. ART uses more memory than Dalvik.
2) Some programs can not work with an external SD card. They can start to work with it after reboot or after few reboots only.
Which programs? The solution is probably using emulated storage.
3) Galaxy S2 with Lineage OS 14.1 becomes hot with a big battery drain for some significant period of time after every reboot. So, rebooting trying to make installed apps work properly you can just quickly fully empty your battery and finish on it.
This is a known issue and can't be resolved. Android 7.1.2 takes more boottime than 4.1.2. The CPU is constantly at 1200Mhz during boot and several minutes after boot because of apps starting up. Our 1600mah battery can't cover this 'boot'-drainage multiple times. It needs 'resting' time to stablelize (like a car battery). Try the app Battery Log to see how the CPU at max speed is pulling the voltage down.
4) The famous FX File Explorer app does not work with the default internal folder 'Documents'.
When you will delete a file on an external SD card this app may not delete it but just rename the file to hidden only (a name started with a dot).
There is another file manager app implemented in the ROM but its interface seems very poor and uncomfortable.
I don't know what the issue with this App. A possible issue could be that we don't use emulated storage
5) Sometimes there is impossible to connect to a password protected WiFi hot-spot due to the link 'CONNECT' in the WiFi menu remains inactive (gray coloured) after password typing 8 symbols or more. This bug appears constantly at a connection with some password protected WiFi hotspots only. And it can become a serious unexpected trouble if you are on the go and in a need to connect to a new hot-spot.
This is by design. Validation depends on used security WEP/WPA2 PSK
6) Camera1 and Camera2 api do not provided correctly. So, camera apps are buggy.
For instance, the famous A Better Camera app by Almalence loses all its settings unexpectedly time to time and becomes as its first launch again. Yet there are another troubles with A Better Camera app.
The implemented in the ROM the Snap camera app is very weak with the ugly uncomfortable interface.
A great of effort has been made to make the legacy Camera api's work in the framework for legacy devices like our i9100 since google dropped its support. It is not perfect and probably never will be. Expect same issues later on in Android O.
7) There is a trouble to enter the year manually in the data settings in a portrait mode due to number of years limitation. This bug does not exist in a landscape mode.
Use small display view. We have a very low-res phone for 2017
8) There is an implemented feature to record a phone call but there is not an option to record all phone calls automatically. Instead only after hand up there inside the dialer settings appears a hidden option which allow manually start to record the current call. So, if you want to record the call then only already during the call you need to go into the dialer menu and activate this hidden option, which is uncomfortable.
Moreover, external apps for phone call recordings does not work properly with this ROM.
Was there ever a automatic recording option in the ROM? We need to investigate some apps why it fails recording.
9) The famous SuperSU root tool does not compatible with Lineage OS 14.1 for Galaxy S2. And apps which require only the SuperSU root can do not work properly.
It is still an issue I think. Please see http://www.lineageosrom.com/2017/01/download-supersuzp-and-su-removalzip.html
10) The small window with the text 'MTP host error' appears in the screen foreground like a ghost.
Our old kernel needs some patches, but it is unclear which patches.
11) The official Lineage OS bug tracker does not accept bug reports by easy way. Instead it requests a registration in advance via a full user name and other personal data, which can be sensitive and used by unappropriate way. It does not allow the registration via the World famous and trusted Google+ or Facebook social networks. Moreover, sometimes the bug tracker does not work and have an announcement about sheduled technical maintenance on a web-hosting side.
12) The ROM developers do not fix even well known simple bugs like described here at the points 5 or 7.
Seems they also do not welcome for public bug reports in proper topics on the XDA forum. It seems like they conceal the existence of many bugs and only lure new people to become victims of their buggy ROM. And I did started this topic for stop it.
I do not know what their purpose is exactly.
But after some time observation it is possible to determine that someone actually regularly 'dilute' proper topics on the XDA forum by short luring messages like 'I had installed it and it is great!' Unfortunately, such kind of simple messages are just alluring fakes high probably.
The another short trap messages are like that 'It runs fast and smooth!'. The deception there is that it attracts only by the Android 7.1.2 menu appearance on the old device for purposes like a brag but really conceal that the whole device with this ROM becomes unreliable for serious using.
I was attracted by topics on the XDA forum about Android 7.1.2 for Samsung Galaxy S2 (model: GT-I9100) and I had lost 1 month period installing latest Lineage OS 14.1 updates and Resurrection Remix 5.8.3 and I decide that the last official Samsung's firmware with Android 4.1.2 is not ideal but much reliable on Galaxy S2 rather than LOS 14.1 or RR 5.8.3.[/QUOTE]
I'm using 2 S2's as daily drive. One for work and one private. I don't have many big apps installed and use my s2 also as car navigation using waze or Google maps. Yes sometimes you have to be patient for a 6 year old device.
Hello.
It is good that the ROM developer had come here in this topic at least.
First of all I do not offend all people. I help Galaxy S2 users to do not fall in the trap, in which I had falled already after being lured by false messages on the XDA forum about allegedly the existence of good ROM Lineage OS with Android 7.1.2 for i9100...
But the ROM is very buggy actually.
For second, all bugs which I described in this topic do not exist in the Samsung's official firmware for Galaxy S2 but only in Lineage and Lineage related ROMs like Resurrection Remix 5.8.3.
JaLoou said:
Hello.
It is good that the ROM developer had come here in this topic at least.
First of all I do not offend all people. I help Galaxy S2 users to do not fall in the trap, in which I had falled already after being lured by false messages on the XDA forum about allegedly the existence of good ROM Lineage OS with Android 7.1.2 for i9100...
But the ROM is very buggy actually.
For second, all bugs which I described in this topic do not exist in the Samsung's official firmware for Galaxy S2 but only in Lineage and Lineage related ROMs like Resurrection Remix 5.8.3.
For instance, with Samsung's official firmware I was able to connect to the exact 2 WiFi hot-spots (as in the screenshots published before) and to many more. But with Lineage 14.1 (and RR 5.8.3) I'm unable to connect to the same 2 WiFi hot-spots. This is enough.
It does not matter which security use this 2 WiFi hot-spots. I was able to connect to them before with the Samsung's official firmware and now I'm unable to connect to them with Lineage.
Before I was able to enter the proper passwords to them. Now I'm unable to do it.
Click to expand...
Click to collapse
In my opinion, you are making a cardinal mistake comparing Stock Android with version 4.1.2 with custom ROM version 7.1.2.
Each of these versions represents a far different operating model in the hardware layer.
But test yourself, if you have enough free time.
ze7zez said:
In my opinion, you are making a cardinal mistake comparing Stock Android with version 4.1.2 with custom ROM version 7.1.2.
Each of these versions represents a far different operating model in the hardware layer.
But test yourself, if you have enough free time.
Click to expand...
Click to collapse
I'm explaining about bugs exactly. They are simple stupid bugs in the Lineage ROM for Galaxy S2, which people face with.
It is also clear that the ROM developers conceal bugs only instead of fixing they.
I had attached the screenshot to this message, which proofs the bug with a manual inability to enter the current year correctly in a date settings at a portrait mode due to an unwanted limitation of number of years available for choose from.
JaLoou said:
Hello.
It is good that the ROM developer had come here in this topic at least.
First of all I do not offend all people. I help Galaxy S2 users to do not fall in the trap, in which I had falled already after being lured by false messages on the XDA forum about allegedly the existence of good ROM Lineage OS with Android 7.1.2 for i9100...
But the ROM is very buggy actually.
For second, all bugs which I described in this topic do not exist in the Samsung's official firmware for Galaxy S2 but only in Lineage and Lineage related ROMs like Resurrection Remix 5.8.3.
For instance, with Samsung's official firmware I was able to connect to the exact 2 WiFi hot-spots (as in the screenshots published before) and to many more. But with Lineage 14.1 (and RR 5.8.3) I'm unable to connect to the same 2 WiFi hot-spots. This is enough.
It does not matter which security use this 2 WiFi hot-spots. I was able to connect to them before with the Samsung's official firmware Android 4.1.2 and now I'm unable to connect to them with Lineage Android 7.1.2.
Before I was able to enter the proper passwords to them. Now I'm unable to do it.
The WiFi hot-spot 'Net 48' haves the password of 10 symbols length. So, it is not WEP secured exactly. But with Lineage Android 7.1.2 I unable to connect to this hot-spot now but before I was able to connect to this hot-spot with the Samsung's official firmware Android 4.1.2 quickly and without any delays.
Click to expand...
Click to collapse
That's important information you describe about the wifi. Please determine which security and password you are using so we can reproduce the issue. The Name of your sid doesn't matter.
rINanDO said:
That's important information you describe about the wifi. Please determine which security and password you are using so we can reproduce the issue. The Name of your sid doesn't matter.
Click to expand...
Click to collapse
Found the bug! It was introduced in linageos since April 27th. https://github.com/LineageOS/androi...mmit/9663c3179fad5e7de7bf4bf31e40649749f33861
The newly introduced faulty input validation is incorrect for WEP. It should not distinguish hex values or plain characters on input. I will create a fix for this.
Some serious camera apps report clearly about the wrong implementation of Camera2 API in Lineage 14.1 for Galaxy S2. I had attached screenshots to this message for proof it.
Hello.
The bug with entering password for connect to some WiFi hot spots, which about I did reported here few times, this bug was fixed or such reporting was my mistake and I really sorry for that. Now I'm able to connect to the 2 WiFi hot-spots, to which I was unable to connect before. Probably, both WiFi hot-spots are WEP secured with passwords of 10 (decimal) symbols length.
Please, excuse me for disturbance about this bug. Probably, I was mistaken due to I did not know about password lenghts limits to 5 and 10 (decimal) symbols in the WEP.
Very sorry.
But another bugs in the ROM continue to exist and they need to be fixed.
JaLoou said:
Hello.
The bug with entering password for connect to some WiFi hot spots, which about I did reported here few times, this bug was fixed or such reporting was my mistake and I really sorry for that. Now I'm able to connect to the 2 WiFi hot-spots, to which I was unable to connect before. Probably, both WiFi hot-spots are WEP secured with passwords of 10 (decimal) symbols length.
Please, excuse me for disturbance about this bug. Probably, I was mistaken due to I did not know about password lenghts limits to 5 and 10 (decimal) symbols in the WEP.
Very sorry.
But another bugs in the ROM continue to exist and they need to be fixed.
Click to expand...
Click to collapse
It is ok. No bad feelings. The very confusing password length has been removed in the official. It was not in Google's android source anyway and the LOS team has merged my commit.
Other good news, I found a workaround to get the camera scene-mode working! It is possibly a bug in the camera firmware which resets the scenemode when the camera starts streaming. It will be in the next official build. As far as I can reproduce, the actual 'night vision'-mode is fireworks.
rINanDO said:
It is ok. No bad feelings. The very confusing password length has been removed in the official. It was not in Google's android source anyway and the LOS team has merged my commit.
Other good news, I found a workaround to get the camera scene-mode working! It is possibly a bug in the camera firmware which resets the scenemode when the camera starts streaming. It will be in the next official build. As far as I can reproduce, the actual 'night vision'-mode is fireworks.
Click to expand...
Click to collapse
Hello.
The semi night vision trick for videorecording by A Better Camera app is to choose manually ISO800 and then choose the scene mode 'Fireworks'.
For more brightness enhancement you can yet choose the 'Cloudly' white balance preset.
I have an old small app, which updates the camera firmware on i9100. I had attached this app to the message. May it will help to someone.
I'm a noob but I think the problem with A Better Camera app is not in the camera hardware but somewhere close to a memory (RAM or flash). And I will try to explain it:
if I launch A Better Camera app for a first time then it shows a simple introductive help on its screen.
If I close the app and run it again then it does not shows the intro help at next launches. It is ok.
But if I press the home button for long time then I get a list of recent apps on the screen and if I scroll it up and clear all the recents list
then only A Better Camera app loses all its settings and becomes like at its first launch (there an introductive help appears again after the app launch).
This bug was not with the Samsung's official firmware Android 4.1.2.
A Better Camera app can improve the camera of our smartphone significantly for video recordings at low light conditions. Moreover, A Better Camera app provides the best DRO-mode among other camera apps, IMHO. It is like a second life for the old camera of our smartphone. So, please pay attention to fix the bug with A Better Camera app.
Related
This is a thread for the Nexus One SuperOSR ROM. This ROM is descended from the SuperAOSP ROM. It does not appear SuperAOSP will be further developed, the last version was v8.6. That xdaforums thread is here:
http://forum.xda-developers.com/showthread.php?t=966635
I value the "Super" line of ROMs because they have been rock stable, have built in Apps2SD, many CM additions, and good battery life.
The primary forum for this ROM is a Spanish one, called movilzona.es. Anything posted here from that forum has been run through google translate, with mixed results. If a native speaker would like to help correct some of these translations, great!
I do not have any say or input into the development of this ROM. I obtained permission of the ROM cook (nelo360), who makes the Nexus One version, to post information about it here. He has explicitly stated he cannot provide any support other than on the original Spanish forum. Of course, the forum community will try to help each other out. I will try to update new releases here.
All credit of course goes to nelo360 and the rest of the development team, [email protected]
The original thread on movilzona.es is here:
http://www.movilzona.es/foro/superosr-nexusone-base-superte-gingerbread-t5882.html
The following is directly from their forum, translated poorly:
Message Super @ Take it and accepted by the group SuperTed @ m.
Disclaimer:
NOT going to give any support to this ROM from any forum other than this one (movilzona.es), this is it is very common for people to hang it in another forum and then have to be looking where it hung in addition to the main forum and I can not respond to external requests of this kind, because I can not be everywhere.
It's funny to talk over the ROM from elsewhere, since the main from which it hung, plus you have to think that this would not be possible if there were forums like this, from which terminals to lend me all enjoy ROMS varied. For questions, NO is posted in HTCMANIA because this forum was banned for posting ROMS here.
For any questions of why this resolution, since many people keep asking me from twitter, because I hang on HTCMANIA ROMS can see the explanation here:
http://www.movilzona.es/foro/superatmel-f73.html
Click to expand...
Click to collapse
Install Notes
SuperOSR for Nexus One AntiWipe
- Clarification and instructions
Once you start, leave the phone 3 to 5 minutes at rest so it can configure itself on first boot. The LED will shine blue through this period. Once it turns off, you can start using the phone.
IMPORTANT App2SD will not turn on without restarting the phone at least once.
Can be activated from: SupSetup/Options/App2SD and LinuxSwap/Activate App2SD
If you want to install extra apps from SupSetup is important to do before you set google account, this way, when we install any application market will be downloaded automatically apps we select the SupSetup.
If you have problems after installing, before blaming the ROM, try to install it with full wipe.
DOWNLOAD from here:
v2.4.0
http://goo.gl/htXpe
v2.2.0
http://goo.gl/iJpoi
v2.1.0
http://goo.gl/KfT2U
Update to flash from the recovery that we restore the original source in the lock screen:
http://goo.gl/vX4Eo
Click to expand...
Click to collapse
<I don't know what that last sentence is supposed to mean>
I recommend you skip google account login the very first time you install. Configure the ROM first, turn on apps2sd if you wish (it will auto-reboot), then do your google login. Otherwise, it will start auto-downloading all your apps from market, and generally make a huge mess.
Screenshots:
Changelog
Changelog v1 SuperOSR AW *
- Based on Android 2.3.5
- All improvements CyanogenMod
- New kernel 2.6.38.8 redstar
- Added ADWLauncher as default launcher
- New visuals
- many internal improvements and bug repaired
v2.0.0
- New boot animation
- New Wallpaper
- New graphical look
- Updated some apps
- Fixed the bug of random color of the trackball
- Restructuring wireless menu
- Modified apn Pepephone (I think this is a mobile service provider in Spain)
- Internal improvements and optimizations
v2.0.2
- Blue LED activity during installation. (Expect to be off to start playing)
- Removed some apps (you can install from the market)
- ADW is changed by the original launcher modified
- Increased the cache to 1024 kb sd to increase the writing speed via USB
- Compiled 2.6.38.8 kernel redstar, with the latest updates
- Improved power consumption
- Modified the graphics in different rom sites
- (CM) has rewritten part of the code led the trackball notifications
- Base CodeAurora
v2.1.0
- Based on android 2.3.7
- Added support for multiple languages
- New lockscreen options
- Fixed some pngs
- Several small bugs fixed
v2.2.0
- Sources synchronized (17.11.2011) Google and CM
- New battery (MIUI style) by default
- Option to take screenshots by pressing the power button for a while
- Fix that greatly improves the speed of writing on the sd (overhtc thanks for the tip)
- Reorganization and edit some menus
- New version lockscreen ring (center ring only)
- Removed some apps to make the lightest rom (can be installed from the market)
· Google Docs
· Google Plus
· Adobe Flash Player
V2.4.0
- Sources synchronized (02/12/2012)
- New animations of ICS
- New visual options lockscreen ring
- More Parts and other translations on menus
- Option to share the screenshots after transmission
- Internal optimizations
Some things I've noticed with v1, coming from a complete wipe.
Market is the older 2.3.6 version
Gmail is an older version which FCs on me. Updating to the new version works fine.
Maps is an older version.
Apparently there is a problem with notifications, from user nodnarb:
Notifications are given as normal, but when you pull down the notifications bar to select any of the notifications it doesn't acknowledge the tap.
Click to expand...
Click to collapse
Great. Any screenshoots?
Already customized my ROM after installing, so graphically it's not particularly impressive.
Basically the ROM runs ADWLauncher, so not so much to show more than that.
I'll post some shots from the settings pages.
Also, some screenshots available here from the older version. Graphically, not much has changed.
http://www.movilzona.es/foro/superaosp-para-nexus-one-por-superatmel-tolemac-t4675.html
Go to post #3. Except it will be in English =)
Been running the new version since last night. So far it's not bad. I did like the old launcher better then ADW but what do ya do....Battery life seems great so far. So far my notifications seem to work ok. Not any significant changes but maybe the subtle ones will show up with use. Too bad the only support is on a Spanish only site. I suppose we can all support it here as well to an extent....
I have been running this rom since yesterday and so far no issues at all! No notification issues or Gmail FC's here. am glad that you have created a thread there. I too am a big fan of Super line of roms. Thanks for your effort.
hackermail said:
I have been running this rom since yesterday and so far no issues at all! No notification issues or Gmail FC's here. am glad that you have created a thread there. I too am a big fan of Super line of roms. Thanks for your effort.
Click to expand...
Click to collapse
I'm glad for the thread too.
Are here any special requirements that I missed - for example, A2SD (mentioned on movilzone thread) usually entails an ext4.. could this be why my installation never worked out? It's just a hunch (I don't have an ext4).
I did have fc of gmail too - do i simply go ahead and update it from market then? I never got to test gtalk. Market is not the newer version which I suppose one can live with.
I flashed it for my wife's phone but as it never gave me any joy, i reverted to SuperAosp 8.6 which works 100%.
Galloway said:
... Too bad the only support is on a Spanish only site. I suppose we can all support it here as well to an extent....
Click to expand...
Click to collapse
If you use Google Chrome as your browser, it does a fantastic job of instant auto translating the site. I speak Spanish and can attest to its acceptable accuracy. Chrome also helped me with the Chinese on the original MIUI site.
tanclo said:
I'm glad for the thread too.
Are here any special requirements that I missed - for example, A2SD (mentioned on movilzone thread) usually entails an ext4.. could this be why my installation never worked out? It's just a hunch (I don't have an ext4).
I did have fc of gmail too - do i simply go ahead and update it from market then? I never got to test gtalk. Market is not the newer version which I suppose one can live with.
I flashed it for my wife's phone but as it never gave me any joy, i reverted to SuperAosp 8.6 which works 100%.
Click to expand...
Click to collapse
For a2sd, you can have an ext3 or ext4 partition. Mine is ext3. Any other specific problems?
Right now, I'm not seeing a big difference between 8.6 AOSP and 1.0 OSR, except for some graphical changes (the pop-up boxes look different, the thumbscroll graphic is dark instead of gray).
Actually one thing I have noticed is that my bluetooth autoconnect is not working the way it should. Before it worked okay just by changing one line in the audio.conf file in etc/bluetooth/ (set autoconnect=on). Currently experimenting.
Don't seem much difference in this ROM compared to Superaosp
i have been having some issues tho, wifi no longer works, won't connect to any networks
battery life is half that of superaosp. will try a reflash and see what happens.
I too have had zero issues. All is well here.
No partitioning of my SD card since I don't used A2SD. Just one fat32 partition.
No problems with any notifications, gmail or market.
Battery life is also very good. I'm averaging 24hrs with moderate usage with SetCPU having one state to throttle speeds down to 128-384 when screen is off.
Anyone having any issues with bluetooth connections?
I restored some bluetooth pairings with TB. Maybe should have left it alone and started anew.
Been messing with the etc/bluetooth/audio.conf file with no improvements.
Good rom. It's working well
No issues so far and my battery life is quite a bit better! I did have to manually connect Bluetooth tonight to my car but I find that happens quite often the first time I flash a new ROM...I'll monitor and see if that continues.
Figured out my bluetooth issue.
Previous, I could swear just by changing (turning on) the autoconnect=on parameter in audio.conf, I could forgo repairing/relearning my bluetooth pairings.
So I changed it after the wipe/flash, and couldn't get it to automatically pair. In fact, couldn't get it to connect at all for any duration.
After putzing around with all the other parameters, I realized I should have just changed back the original thing I had altered ("#autoconnect=on"), and it works fine now.
So, the take home lesson is, don't mess with the etc/bluetooth/audio.conf file that comes preloaded! And just re-pair whatever BT items you had previously.
xdraw said:
Don't seem much difference in this ROM compared to Superaosp
i have been having some issues tho, wifi no longer works, won't connect to any networks
battery life is half that of superaosp. will try a reflash and see what happens.
Click to expand...
Click to collapse
I too have been less impressed. Battery life I feel is either about the same or worse. (yesterday I got down to 30% by the evening, which is unheard of for SuperASOP).
The other things that have sucked has been a random reboot into recovery (WTF?!), and GPS is slower to lock.
And then to top it all off, this morning the phone was off sitting in my desktop cradle (but 100% charged, LOL). I could live with that because my T-Bolt woke me up, but usually its the other way around in that my N1 is the Old Faithful that I can rely upon for alarm, tethering, etc.
Signal reception is also notably poorer compared to 8.4. Has anyone else noticed this?
I will give it one more day, but I may wipe everything and go back to 8.4, which had the best combo of battery life, signal, and stability for me.
Thanks for your commentary. Even as the OP here, I haven't seen major advances since 8.4 (wonk fix). And I never actually had the wonk! Did you try 8.6 and go back to 8.4? If so, why?
Though, I have not had any wifi issues, or random reboots, or slow GPS locking.
I did notice that sometime in between 8.2, maybe in 8.4, my wifi signal dropped a few bars in my living room, which isn't that far from the router. I had heard there was there some adoption of new wifi driver code?
I'm trusting you did a clean wipe flash? I think some have said that it flashes fine over 8.6, but probably not recommended.
no have Chinese , Unfortunately.
China has a lot of people , interest in the ROM.
But , they can not use this ROM .
Because they English is so so so bad ,Including me .
First, I'd like to thank Josegalre and all that have helped him in developing this ROM. It's a very good ROM that shows much promise. I hope that this will both help the developer(s) in resolving the issues I encountered, and in deciding if this ROM is suitable for your device.
The powers that be here won't allow me to post in the development threads, because I'm a "newbie". I may be here, but I'm a "Recognized Contributor" on Tytung's Nexus-HD2 forum with the handle of "Odysseus".
Since the board's software also won't allow me to post links yet, let me take a brief moment to introduce myself. I've been a computer hobbyist since before most here were born (got my first PC in 1984). I was an "official" beta-tester on the old Compuserve network for Microsoft's "Chicago" project that later became Windows 95, then continued in that capacity for Win 98, NT-4.0, Win ME, Win 2000, and finally Windows XP, before I jumped ship completely to Linux. I had been experimenting with Linux since 1997, but made it primary OS in 2001. I've been running Gentoo Linux (a source-based distribution) since 2003 and more specifically using the latest cutting edge "unstable" repositories or as we say in Gentoo "~arch" since 2005. I'm a contributor on the Gentoo and Sabyon Linux Forums as "Odysseus". I've also contributed to the Gentoo project itself, as I've submitted patches that have been accepted into the kernel tree, developed several workarounds and have written numerous detailed bug reports to both the Gentoo and upstream developers as I've discovered issues. Not bad for a 51 year old truck driver with no formal training.
Back to the topic: Since I can't post in the other thread and there is no Q/A&T thread yet for the new [ROM][10/NOV/13][UNOFFICIAL][4.3.1] PACman [Source Build] project I'd thought I'd start one here.
After using it for a day these are my observations, It's solid and stable, but does have a few issues that need to be resolved before it can become my daily driver and they are:
1) Data acquisition - This is a show stopper for me. Much like the recent Evervolve-3.3.0-p1, this ROM takes quite a bit of time to establish a stable data connection. In my case it can take anywhere from 3-10 mins for the signal to stabilize. Once connected, data transmission is as fast as it should be. This isn't a major problem if stationary, however, maintaining a usable connection while driving is problematic. WiFi on the other hand connects quickly and is very stable.
2) Battery life - Without tweaking this ROM under moderate use drains battery 25-35% faster than my current daily driver the "|Aug 6th| Energy™ -.¸¸.·´¯ ICS 4.0.3". I don't know what could be causing this issue. (Perhaps related to the data-connection issue?) My experience on both my HD2 and Amaze has been that Cyanogenmod based ROMs are generally more battery efficient than Sense based counterparts.
3) System-wide font size consistency - As mentioned, I'm no spring chicken. Even with my reading glasses on I need to increase font size to comfortably read on any ROM. Changing the system font-size in Jellybean based ROMs is usually a matter of changing the desired size in System Settings / Display, however, with this ROM there is no consistency. Some elements remain tiny (menu in browser), while others grow too large, furthermore, many apps don't appear to honor the system-wide settings. This is especially troublesome with the included browser.
4) The Browser - To me, the included browser is better suited for a larger screen. The fonts are extremely small even after increasing them system-wide. This applies to fonts in menus, title bar, address bar, tabs, and to the browser itself. Additional font size adjustment from within the browser to 115% for both bars and setting the minimum size to 14pts was still strained reading. My workaround was replacing it with one from Tytung's latest ROM.
5) Connecting to public WiFi hotspots - Generally WiFi works well, however there is a minor glitch when initially connecting. The default behavior should be to notify of potential connections as they become available. Once selected the browser launches if needed to complete the connection. I visited my local Starbucks yesterday shortly after installing, so the connection was already in the list. This morning I waited 10 mins before giving-up and manually initiating connecting, then manually launching my browser to complete connecting.
6) Camera and Video recorder - As mentioned in the development thread.auto-focus isn't working and the video recorder force closes immediately upon selection from within the app.
On a more positive note, most issues which have been plaguing Jellybean ROMS for the Amaze seem to have been resolved. There are no echoes anymore and adjusting in-call volume actually adjusts the volume, not the microphone. I haven't had a chance to check out tethering or bluetooth pairing yet, but will with the next release. Unfortunately, since I earn my living on the road, the data-connection issues require me to revert back to my old, but reliable EnergyRom.(thanks NRGZ28)
All in all, this is an outstanding effort that's very close to being a fully functional JellyBean ROM suitable for everyday use. It seems like things are progressing positively around here. With the upsurge in development recently we're sure to see one soon.Kudos to all involved!
If anyone else care to chime in, please feel free.to do so.
Ciao
After weeks of hard work we (Setmov and uncle Fab) proudly present you the first Una ROM for the galaxy Grand 2 I7102, based on 4.3 XXUANG4.
DISCLAIMER
As usual, your phone your responsability, we won't take any responsability if it flies out of the window or if your girlfriend/boyfriend runs away with it.
PLEASE, DO READ OP COMPLETELY AND CAREFULLY BEFORE ASKING ANY QUESTIONS, ANSWERS TO MOST PROBLEMS ARE THERE
WHAT IS UNA?
Una is a new concept that takes security to a new level.
Are you tired of seeing so much blatant, outrageous and shameless invasion of your privacy and data mining hidden behind nice sentences like "enhanced use experience" or "complete integration with the system"? We decided to develop secure ROMs where privacy means just that – Private!.
It’s free of charge, we are a non profit structure and we are not here to make big bucks
WHAT UNA ISN'T
UNA isn't a way to help you to stealthily buy massive destruction weapons to foment a coup d'etat in your favorite banana republic or to prepare the third world war.
UNA secures what leaves from your phone (ie your personnal data doesn't leak and no app can look over your shoulder to spy your activities), but it can't completely secure what comes into your phone.
Why is that?
Because it's just not possible to fully secure a phone from what comes into it, and anyone claiming to be able to do it is either a liar, or an ignorant, or both.
There are too many attacks, some not well documented, if documented at all, and some unknown to the public, and there are too many ways to hack a phone, especially if the user doesn't use his/her common sense.
If you are the type of person that installs apps from shaddy source and/or warez web sites (sites offering cracked paid apps) chances are that at some point you will unknowingly install a malware or a spyware. The same applies if you click on any link, specially on SMS' and emails, if you let any pop out window appear or if you don't protect your lockscreen with a password/pin/pattern and let anyone get physical access to your phone.
A bit of judgment and common sense can save you a lot of trouble, but there's unfortunately nothing UNA can do about it.
Then, if you use your phone to call through GSM your provider will know where you are. If he didn't you wouldn't be able to make any call, the signal has to find you and there's nothing UNA or anyone can do about it.
The only way to prevent that is to disable the phone functions (but then your phone will turn into a wifi only device) and reenable them when needed, head to the scripts section to learn how to do it.
Last but not least, bear in mind that the agencies have armies of tech savvy henchmen and 10 storeys computers, and tricks we can't even imagine, so think twice and use your brain before you attempt to outsmart them...
UNA IS FOR YOU IF:
. You are willing to learn how to use an unconventional ROM and generally speaking to understand how things work, even if it sometimes requires a little effort to fix this or that little problem (bear in mind that it took us a lot of work to develop Una to where it is now),
. You don't mind a few little occasional bugs here and there that come from all the restrictions the ROM contains,
. You want to take back ownership of your phone from google’s claws.
UNA IS NOT FOR YOU IF:
. All that you care about is the latest gimmick in the latest OS,
. You can't live without the google’s apps,
. You are the kind of person that never reads through the OP and only scroll down to the download section, and then complain that things don't work and/or ask stupid questions that have already been answered in OP.
An example? One guy makes a mod and writes clearly in OP that it's specifically for 4.2.2. Then some people complain: "it doesn't work on 4.4.2"...
ARE WE PARANOID TIN FOIL HATS? OR TERRORISTS? OR CARTEL BOSSES?
Nope, we only are people that don't see why we shouldn't be in control of our phones. Or why our phones can be wiped remotely, why apps or updates or who knows what can be downloaded and installed without asking for our consent, why SMS' can be sent without us to know, why we should pay for the bandwidth used for data mining and unwanted downloads, and why all those activities should deplete our battery and kill our RAM.
You think we are overreacting here?
You don't have to take our word for it, just download and install Network Log from here:
https://f-droid.org/repository/browse/?fdfilter=network+log&fdid=com.googlecode.networklog
Give it root permission, start logging and open some web pages. Come back to Network Log after a few minutes and see for yourself, you'll be surprised (or maybe horrified?) to find out that your android system, your settings, your kernel etc. connect to all sorts of funny IPs, including and foremost google’s.
Now you see what we mean?
It's time to go for Una
UNA'S FEATURES
. Rooted.
. Deodexed.
. Zipaligned.
. Busybox and sqlite installed.
. Init.d support and scripts.
. Auto start disabled for most apps.
. About 120 system apps, 40 framework jars, 30 permissions xmls and 25 libs removed, plus files here and there.
. Very low RAM and CPU consumption, more than 8 hours screen time with the WIFI on, 1% battery decrease every 10-12 hours while in stand by.
. Heavily and extensively modified system, in order to make it secure and prevent it from leaking your data.
. App Settings, Firewall and Xprivacy built-in, and already applied out of the box to make sure you are well protected.
. Xprivacy is a fantastic tool but it has one big limitation, it can't restrict the Android System from accessing your serial numbers and leaking it. For that reason these IDs have been edited as follows:
build.serial (androidboot.serialno), ro.boot.serialno and ro.serialno are both set to "1",
android id is set to "id",
net.hostname is set to "1".
. Wlan serial number set to "00000001" (this number identifies you everytime you connect to the internet, and Xprivacy can't do anything about it).
. USB ID (iSerial) set to 1.
. Unreadable cp access.
. Vulnerabilities patched thanks to Master Key Multi Fix.
. ADB disabled (can be re-enabled, see below).
. By default ADB, all google access (including youtube, blogspot and google search), the Live Wallpaper Picker and the Media Storage are disabled. You can re-enable some or all of them, instructions are in the "HOW TO USE THE ROM" section.
. Plenty of under the hood modifications to make the ROM fast and fluid.
. Multi-purpose navigation keys.
. Call button in contacts.
. Because secure doesn't mean ugly, the whole ROM has been themed with a beautiful green color (if there are enough requests other themes will follow), transparency, and Lollipop HD wallpapers.
. Multiwindows have been revamped, they are no longer only static in Samsung style but now they can float and be resized/minimized too, like on a computer.
. All apps can be opened in floating mode.
. KK style quad view multiwindows.
. Heaps of hand picked and carefully scrutinized open source apps.
There are 2 non open source apps (Greenify and Quick Pic) but they are safe, believe me, I have thoroughly examined them. Still, you can always uninstall them if you feel like it.
In time we will develop our own apps, but first we want to see how people respond to the Una concept...
Installed apps/tools
. 920 Editor, to create and edit scripts or text files.
. AF+ Firewall.
. Alarm clock.
. APG, to encrypt messages.
. App Settings, to restrict apps' permissions, change DPI on a per app basis and more.
. Arity, a calcultor.
. Conversations, a secure and encrypted chat, modded by uncle Fab for increased security.
. Fdroid, an alternative to the Play Store, and all the apps are open source!
. Floating stickies, to make small notes on the fly.
. FTP Server, to copy files to/from your phone wirelessly.
. Ghost Commander, a very powerful dual panel root file manager.
. Gravity Box, a theming engine.
. Greenify, to make apps behave by hibernating them when not in use.
. K9 Mail, an email client.
. Kernel Adiutor, if you feel like playing with kernel tweaks (but you have to know what you are doing).
. Lightning, a fast and light weight browser.
. Master Key Multi Fix, a patch to some vulnerabilities.
. Network Log, to check where your apps connect and chase unwanted connections.
. Open Camera.
. Tor (Orbot) for Android, modded by uncle Fab for increased security.
. OS Monitor, to monitor and kill your phone's processes, and more.
. Pale Moon, based on Firefox for Android, for a full desktop experience with Mozilla add-ons preinstalled for enhanced security.
. PDF Reader.
. Preferences Manager, to edit the otherwise difficult to read shared_prefs files in data/data.
. Quick Dic, a good selection of free dictionaries.
. Quick Pic, a Gallery app.
. Rmaps, a maps app where you can download maps from various sources for offline use.
. Search Light, a torch.
. Terminal Emulator, fire up your commands and show your phone who is the boss!
. Text Secure, a secure and encrypted SMS app, modded by uncle Fab for increased security.
. Tint Browser, another fast web browser.
. Urecord, to record sounds with different sample rates.
. USB Mass Storage Enabler, to connect your phone to any computer (note that it only mounts the external SD).
. Viper4Android FX, a powerful sound enhancer.
. Viper4Android XHiFi, some more sound enhancements.
. VLC, a video and music player favourite.
. WI-Fi Privacy Police, to secure your connections even better than they already are.
. Xposed Installer, a great framework that enables apps like App Settings or Xprivacy to work.
. Xprivacy, last but not least, the best privacy app.
WHY DO WE USE A 4.3 ROM AS BASE INSTEAD OF THE LATEST 4.4.2?
Because when it comes to privacy Kit Kat 4.4.x is a complete
disaster, the newer the android version the more buit-in spying there is (and the more difficult it is to remove it), despite google's sweet talk about "enhanced user's experience.
Lollipop seems to be even worse, but that's another story.
INSTALLATION
As usual, make a backup first!
Do backup your contacts and whatever is important because all your apps and data will be erased (your sd card contents won't be deleted though).
Do backup your /system/csc folder, in case you need it for later.
Do backup your efs folder (VERY IMPORTANT).
Open an android terminal from your phone and type:
su
enter, then type:
busybox dd if=/dev/block/mmcblk0p11 of=/sdcard/efs.img
enter, this will create an efs backup caled efs.img in your sd card.
To restore it, first make sure the efs.img is in your internal sd card, then type:
su
enter, then type:
busybox dd if=/sdcard/efs.img of=/dev/block/mmcblk0p11
enter, your efs will be restored in no time.
If that sounds like too much work you can use the scripts provided to backup/restore your efs, instructions are in the scripts section.
To install the ROM you need a Custom Recovery and Philz' comes highly recommended.
We chose Philz since AFAIK it's the only one that allows you to lock you recovery with a password (if your recovery is not password protected it wouldn't take more than 2 minutes for someone to disable your pattern or pin protected lockscreen and access all your personal data on the phone).
I'm not sure whether there's a Philz recovery or not for the Grand 2, if there isn't then CWM or TWRP will do.
Custom recovery installation instructions
You need to have Samsung drivers installed.
Boot your phone into download mode (press volume down and power at the same time).
Open Odin 3.07 and connect your phone.
Click on the PDA slot, navigate to where the Custom Recovery is located and select it.
DOUBLE CHECK AND MAKE SURE THAT "RE-PARTITION" IS UNTICKED (only "Auto Reboot" and "F.Reset Time" should be selected).
Click start and wait while Odin flashes the Recovery.
If everything went well your phone will now auto-reboot into the system. Go into recovery, you should see your brand new Custom Recovery.
If you are still on stock recovery then repeat the above steps, but this time untick “Auto Reboot” in Odin.
When in recovery, if before you reboot you see a text on the screen displaying “yes – disable flash recovery”, select it to avoid stock recovery overwriting the Custom Recovery.
Download Una for Grand 2 from here (click on the menu at the top right and go to the download section):
http://unaos.com
Unzip the ROM and copy it to the backup folder that is inside the clockworkmod folder in your sd card (if there's no backup folder create it by choosing "mkdir" in Ghost Commander).
Boot into recovery.
Go to restore from sdcard, choose 1970-01-01.10.06.02, and go for it!
IMPORTANT!!!
If you are on Kit Kat (4.4.2) you must downgrade first to stock 4.3 before you attempt to install Una ROM, otherwise you may end up with a bricked phone.
Here are 2 threads to assist you in the downgrading process:
http://forum.xda-developers.com/galaxy-grand-2/general/how-to-downgrade-galaxy-grand-2-sm-t2857767
http://forum.xda-developers.com/galaxy-grand-2/help/downgrade-to-4-3-t2857183
If it works please report here so that other people will know, thanks in advance!
Once it's done reboot, congratulations, you have installed Una ROM on your phone!
HOW TO USE THE ROM
. Swipe down to access the applications drawer.
. Swipe up to turn off the screen.
. Go to settings and set a stong password/pin/pattern protected lockscreen (recommended).
. Go in recovery and set a recovery password (recommended).
. Long pressing on the menu key toggles expanded desktop (full screen, no more navigation bar and no more status bar).
. Double pressing the menu key kills and hibernates the current application.
. Long pressing the recent key brings you back to the last application (convenient to switch from one app to another).
. Between the home and the back key there's a supplementary key that can display up to 12 apps (editable in gravity box).
Double pressing that key shows the sound panel, long pressing it shows the reboot menu (note that there's an option to take screenshots in the reboot menu).
. You can open an app in full screen mode by dragging it from the Flash Bar (the side bar), then you can drag and add more windows to the view (up to 4 on the same screen).
Or, you can open apps in resizable and movable floating mode by clicking on them (double tapping the top bar minimizes them into a bubble, double tapping the bubble restores them).
. Go to /system/etc/security/cacerts, check the certificates that are there (you'll find the certificate's name approximately by the middle of the file), and erase the ones you don't need/like.
When you want to transfer files to/from your phone open the USB Mass Storage Enabler app and enable mass storage, that's it. When you are done, don't forget to eject your phone from the computer and to reenable MTP from the app.
. When you install a new application, by default it will be fully restricted in both Xprivacy and the Firewall.
Before you open the newly installed app wait until the Xprivacy icon appears in the status bar, then and only then can you open it.
Most likely the app will crash.
Go to Xprivacy, open its settings and then usage data, you will see what restrictions caused the crash. Re enable some, provided that they are not too invasive.
Many apps require "load.Library" to be allowed in the shell section, that's ok.
Others may need to access the sd card, that's in the storage section and it's ok to allow it for apps that really need to access the storage, like players, cameras or file managers (for other apps try to keep it restricted).
Root apps obviously need "su" and/or 'sh", and sometimes "exec", in the shell section.
Always try to enable as few fields as possible, and bear in mind that data requested by an app is not necessarily needed for that app to work (especially true for identification, internet and mcc/mmc access).
Lastly, give the app internet access in the Firewall if, and only if, it needs it, and restrict some more permissions in App Settings.
If you can't tame the app consider uninstalling it and look for a similar one that has less built-in spyware.
SCRIPTS
. As said above, by default ADB, all google access (including youtube, blogspot and google search), the Live Wallpaper Picker and the Media Storage are disabled.
If you want to re-enable some or all of them, open the script folder located in system/etc.
Click on the desired script and choose edit.
Copy the whole text and paste it into the Android Terminal, voila, the script is automagically executed.
. You will see more scripts to disable/enable the Bluetooth, the FM Radio and the Phone.
If you disable the Phone and later want to re-enable it do as follows:
untick App Settings in Xposed's modules section, re-enable Phone, reboot, then enable App Settings again.
. Some scripts will enable you to backup/restore your efs partition and flash a recovery.img (to restore or flash an .img, make sure it's in your internal sd and execute the script).
. Other scripts can enable/disable am and pm, but don't play with it unless you know what you're doing.
. You can uninstall the Live Wallpaper Picker, the Wallpaper Chooser and the Media Storage if you want, or keep them disabled and resurrect them when needed.
. If you are very privacy concerned you should consider using the "uncle's phone lite" mod because it enables you to call with only the Phone and the Telephony Provider apps (CSC, Contacts, Contacts Storage, Logs Provider and STK are completely de-activated). That's the method I use to make calls, but you have to know that the dialler forces close after you complete the call (not a big deal in my opinion but still, I may look into it one of these days). You'll find the mod in the add-ons section.
ENCRYPTION
If encryption is your thing we have you covered with the following installed apps:
APG, Conversations, K9 Mail and Text Secure.
BUGS
. Quick Dic won't download any dictionary, actually it's not a bug but a Una restriction since Quick Dic downloads from a google owned web site.
If you need to download dictionaries, temporarly enable google by running the "enable_google" script (don't forget to disable it again when you're done). After you've run the script go to the firewall, open its settings, go to "Set custom script" and click "OK" (do the same if you decide to disable again google's stuff).
. For some reason the ADW Launcher doesn't allow transparency in the navigation bars while in portrait, I'm working on that.
. You can't download anything from Lightning and Tint Browser, that's because the Download Manager and the Download UI have been uninstalled. If you need to download something, copy the link and paste it in Pale Moon, it has its own download engine.
. I didn't have time to properly and restrictively set Text Secure (the SMS app), because I don't own this phone and the person I borrowed it from wanted it back ASAP. Sorry about that, you'll have to do it on your own (if you want to make it simple just restrict its internet access).
. All the installed apps work, but other apps you install may crash. I call that kind of apps "google’s henchmen", they only work if the play store services or the bla bla app are installed and of course they won't on Una since all that garbage has been removed.
If I install your app, why do you want to force me to install your boss' app too? Forget about those apps and search Fdroid, you'll find what you need...
. Depending the way you use your phone you may have to fine tune Xprivacy and reenable some permissions, I'm sorry for the inconvenience but it's impossible to set Xprivacy for all users since we all have different ways to use our phone.
ADD-ONS
. Sony Xperia Keyboard, flash it in recovery.
Credits KristianCarl for porting it, and unclefab for theming it in green.
It's not open source and that's why it's not included in the rom by default, but it's my every day keyboard because it works fine and because I themed it to make it look nice.
Don't give it internet access in the Firewall.
In Xprivacy, only allow "loadLibrary" in the shell section. You may have to enable a few fields in the contacts section depending your phone's configuration.
In App Settings, restrict "Read_Phone_State" and "Record_Audio".
I removed the Chinese Keyboard, tell me if you want it and I'll readd it.
. Universe Wallpapers
If there are enough users' requests then I'll upload the following:
. Uncle's phone lite (with clipboard and dialer) for hardcore users. It's safer than using the regular phone configuration, but the dialer forces close when you hang up the call. Flash it in recovery, wipe dalvik-cache, reboot.
. Completely disable internet access for the Android System. Lightning and Tint Browser won't connect anymore since they use the same web engine as the Android System, but Pale Moon still works thanks to its build-in web engine. Flash it in recovery, wipe dalvik-cache, reboot.
RECOMMENDED NON OPEN SOURCE APPS
. Pri-fy, from chainfire the root master:
http://forum.xda-developers.com/showthread.php?t=2631512
. Logging Test:
http://androidsecuritytest.com/
UPDATES?
I'm working on some improvements on kernel and system level to make Una even more secure, but I will release them for the Grand 2 if, and only if, there are enough users' feedback for the current version, because it's a lot of work to implement such stuff in a ROM.
No ETA though, you'll have to be patient because now we have to design and release Una for many other phones.
Still, any suggestions/comments/bug reports are welcome, help us to improve Una!
FEATURE REQUESTS
Yeah, sure, we'll see what we can do but we don't promise anything
SCREENSHOTS
I didn't have time to make screenshots since I ran short of time, so the ones you'll see here come from another phone.
They are very similar in shape, layout and color though, and you'll get the idea.
That's all for now, enjoy the ROM!!!
The Una team
CREDITS
Big thanks to:
F-Droid
M66B (Xprivacy)
Rovo89 (Xposed)
Tungstwenty (App Settings, Master Key Multi Fix)
Ukanth (AF+Firewall)
Jecelyin (920 Editor)
Kraigsandroid (Alarm Klock)
Thialfihar (APG)
Arity (Arity calculator)
Siacs (Conversations)
Ppareit (FTP)
Ghost Squared (Ghost Commander File manager)
Mohammad Adib (Floating Stickies)
C3C076(Gravity Box)
Oasisfeng (Greenify)
K-9 Dog Walkers (K9 Mail)
Grarak (Kernel Adiutor)
Anthonycr (Lightning)
Xperiacle (Multiwindows Manager)
Pragmatic Software (Network Log)
Mdwh2(Open Camera)
The Guardian Project (Orbot)
Eolwral (OS Monitor)
Moon Child and Cyansmoker (Pale Moon)
Droidapps (PDF Reader)
Simon Marquis (Preferences Manager)
Thad Hughes (Quick Dic)
Q-Supreme team (Quick Pic)
Robert.Developer (Rmaps)
Search Light (Search Light)
Jackpal (Terminal Emulator)
Anasthase (Tint Browser And Tint Browser Adblock Addon)
Thomasebell (Urecord)
Mohammad Abu-Garbeyyeh (USB Mass Storage Enabler)
Zhuhang (Viper4Android FX and Viper4Android XHiFi)
Videolan.org (VLC)
Brambonne (Wi-Fi Privacy Police)
i dont own a galaxy grand 2 , although i may have to get one , but thank you for sharing your work. i'm not a developer so i can only imagine ( which probably falls way short ) of what this took to build.:thumbsup:
"all i can really do , is stay out of my own way and let the will of heaven be done"
Please do a 4.4.4/4.4.2 version. What about the security? Like anyone can hack into your phone....
salimtn said:
4.3 ?! Not interrested
Sent from my SM-G7102 using Tapatalk
Click to expand...
Click to collapse
Laurisss said:
Please do a 4.4.4/4.4.2 version. What about the security? Like anyone can hack into your phone....
Click to expand...
Click to collapse
Thank you for your useful feedbacks.
PLEASE, DO READ OP COMPLETELY AND CAREFULLY BEFORE ASKING ANY QUESTIONS, ANSWERS TO MOST PROBLEMS ARE THERE
WHY DO WE USE A 4.3 ROM AS BASE INSTEAD OF THE LATEST 4.4.2?
Because when it comes to privacy Kit Kat 4.4.x is a complete disaster, the newer the android version the more buit-in spying there is (and the more difficult it is to remove it), despite google's sweet talk about "enhanced user's experience.
Lollipop seems to be even worse, but that's another story.
And NO, not anyone can hack into your phone, but many can and google already did it!
salimtn said:
4.3 ?! Not interrested
Click to expand...
Click to collapse
Thank you soooooo much to take time to reply and show how much consideration and respect you have for someone that worked about 100 hours to build a rom and share it for free with the community.
It feels sad to know that you won t run Una rom on your phone, and thanks again for informing us that we won t count such a great person like you amongst our users, but maybe next time you should read OP:
UNA IS NOT FOR YOU IF:
. All that you care about is the latest gimmick in the latest OS,
. You can't live without the google’s apps,
. You are the kind of person that never reads through the OP and only scroll down to the download section, and then complain that things don't work and/or ask stupid questions that have already been answered in OP.
Click to expand...
Click to collapse
You see guys?
It s thanks to that kind of person that so many devs have left, leave, or will leave the forum...
Please do a 4.4.4/4.4.2 version
Click to expand...
Click to collapse
As written in OP there might be updates:
I'm working on some improvements on kernel and system level to make Una even more secure, but I will release them for the Grand 2 if, and only if, there are enough users' feedback for the current version, because it's a lot of work to implement such stuff in a ROM.
Click to expand...
Click to collapse
Well, time will tell, but so far if you were me what would you think/do?
Thanks for your valient efforts.
But most of the phones would have been upgraded
to k.k. and downgrading them to 4.3 is rather risky.
Even I wonder whether I can downgrade to 4.3 add you rightly mentioned
about 4.4 and 5 android versions.
Even then I will try to down grade to 4.3 and also
try this room. I am willing to take the risk for the developer.
salimtn said:
4.3 and a cute dev. ?! Still not interested ...
Click to expand...
Click to collapse
Still not interested?
Such a pity, people like you are every devs' dream and it would have been a real honour to count such a VIP like you amongst our users.
Thanks for letting us know, next time we ll try to do our best to satisfy demanding users like you...
wrishaba said:
Thanks for your valient efforts.
But most of the phones would have been upgraded
to k.k. and downgrading them to 4.3 is rather risky.
Even I wonder whether I can downgrade to 4.3 add you rightly mentioned
about 4.4 and 5 android versions.
Even then I will try to down grade to 4.3 and also
try this room. I am willing to take the risk for the developer.
Click to expand...
Click to collapse
Thank you for your support. With this attitude you are definitely repaying every effort made.
wrishaba said:
But most of the phones would have been upgraded
to k.k. and downgrading them to 4.3 is rather risky.
Even I wonder whether I can downgrade to 4.3 add you rightly mentioned
about 4.4 and 5 android versions.
Even then I will try to down grade to 4.3 and also
try this room. I am willing to take the risk for the developer.
Click to expand...
Click to collapse
I really dislike 4.4 because it s full of spying, but on the other hand I definitely could build a 4.4 rom for the Grand 2 cuz I can understand that not many people want to take the risk to downgrade.
The only problem is that I don t own the phone, and that the person I borrowed it from doesn t want me to install 4.4 on it, because of knox and because 4.3 runs well.
One thing you have to bear in mind is that latest android version doesn t mean best version, and since 4.1 it s actually been quite the opposite.
Google install 2-3 gimmicks to "enhance users' experience" bla bla, and at the same time strengthens its grip on android.
It got particularly bad with 4.4, and I read reports that it went even worse with 5x...
unclefab said:
I really dislike 4.4 because it s full of spying, but on the other hand I definitely could build a 4.4 rom for the Grand 2 cuz I can understand that not many people want to take the risk to downgrade.
The only problem is that I don t own the phone, and that the person I borrowed it from doesn t want me to install 4.4 on it, because of knox and because 4.3 runs well.
One thing you have to bear in mind is that latest android version doesn t mean best version, and since 4.1 it s actually been quite the opposite.
Google install 2-3 gimmicks to "enhance users' experience" bla bla, and at the same time strengthens its grip on android.
It got particularly bad with 4.4, and I read reports that it went even worse with 5x...
Click to expand...
Click to collapse
spying? Meh. 80% of people are on kitkat and a few are on lollipop. No reports of something hack-ish.
Laurisss said:
spying? Meh. 80% of people are on kitkat and a few are on lollipop. No reports of something hack-ish.
Click to expand...
Click to collapse
Most people don t realise they are being spyied.
Do one test.
Download network log from here:
https://f-droid.org/repository/browse/?fdfilter=network+log&fdid=com.googlecode.networklog
Install it, open it, give it root access and start logging by clicking "logging on" on the top.
Then do some browsing, going to this or that site, but don t go to any google related web site (no search, no youtube etc.).
Come back to network log, you will see that your phone connected to many funny addresses, including of course google, and that quite a lot of data has been transfered both inbound and outbound.
That s just a small test, there s actually much more than that but you ll get the idea.
You could make another test with xprivacy, and if you do so you ll see that all apps request various private data like ids and cell towers location.
The thing is that the higher the android version the more difficult it is to prevent that data mining, data mining that is little more than spying by looking over your shoulder.
Una roms have been designed to prevent that, and more (see OP), but it s up to everybody to install it or not.
I really appreciate your Hard work , I can imagine how much hard work you would have done by working on a phone which you do not own , borrowing it again and again , testing the ROM on someone else's phone and the fear of bricking it . But as someone mentioned in the thread many users are on 4.4 . Many here fear bricking there devices while downgrading it. The mere fact that you have to downgrade your device to use the ROM is what cause of lack of users . personally I really liked what your ROM offers. Just to help you for further development H6 is the most stable and without Knox count firmware. Some 60-70 % users who flash custom ROM are on this firmware and even many custom Roms use it as a base . Hope to see this ROM on kk .
Best of luck.
unclefab said:
I really dislike 4.4 because it s full of spying, but on the other hand I definitely could build a 4.4 rom for the Grand 2 cuz I can understand that not many people want to take the risk to downgrade.
The only problem is that I don t own the phone, and that the person I borrowed it from doesn t want me to install 4.4 on it, because of knox and because 4.3 runs well.
One thing you have to bear in mind is that latest android version doesn t mean best version, and since 4.1 it s actually been quite the opposite.
Google install 2-3 gimmicks to "enhance users' experience" bla bla, and at the same time strengthens its grip on android.
It got particularly bad with 4.4, and I read reports that it went even worse with 5x...
Click to expand...
Click to collapse
Definitely I wanna going to try this rom. I never said 4.4. Or 5 is best versions of android.
But the fact is downgrading is some what risky. Eben then I am going to try.
No need to pay me for taking sweet.
wrishaba said:
Definitely I wanna going to try this rom. I never said 4.4. Or 5 is best versions of android.
But the fact is downgrading is some what risky. Eben then I am going to try.
No need to pay me for taking sweet.
Click to expand...
Click to collapse
I didn t read everything about the downgrade procedure, but of what I have read you have to odin flash a specific KK version first, and then a specific 4.3.
Anyway, if it s really that risky maybe you shouldn t try and wait until we manage to release a 4.4 Una rom.
The problem is that the person that owns that phone uses it for business purposes, so I have to be very careful not to loose all the whatsapp, bbm etc. contacts and settings, and if it was ok to backup her rom, work on making una during nights and then restoring her original rom in the early morning, it would be a different story to switch from 4.3 to 4.4 to again 4.3 every night...
Let s see if I can convince her to use 4.4 as her daily rom, but I can t lie and tell her that 4.4 is better than 4.3, and I don t think she will accept to sacrifice her phone.
I meet her again next month and I ll keep you informed in case she accepts.
For now what you can do if you want to make your phone more private and secure is to follow what I explain in my security thread (check my signature "how to secure your phone").
unclefab said:
I didn t read everything about the downgrade procedure, but of what I have read you have to odin flash a specific KK version first, and then a specific 4.3.
Anyway, if it s really that risky maybe you shouldn t try and wait until we manage to release a 4.4 Una rom.
The problem is that the person that owns that phone uses it for business purposes, so I have to be very careful not to loose all the whatsapp, bbm etc. contacts and settings, and if it was ok to backup her rom, work on making una during nights and then restoring her original rom in the early morning, it would be a different story to switch from 4.3 to 4.4 to again 4.3 every night...
Let s see if I can convince her to use 4.4 as her daily rom, but I can t lie and tell her that 4.4 is better than 4.3, and I don t think she will accept to sacrifice her phone.
I meet her again next month and I ll keep you informed in case she accepts.
For now what you can do if you want to make your phone more private and secure is to follow what I explain in my security thread (check my signature "how to secure your phone").
Click to expand...
Click to collapse
All builds prior to NK1 are without KNOX.
NH6 is good and speedy.
I'm a dev too, and I don't recommend the over-VIP experience you're using to grab customers. I ain't sure, but it looks humiliating to you to give picky users a VIP experience.
Just tell them to get the hell off the thread if they hate the idea (I really like it and would've upgraded if I was a TW user. I use AOSP CM).
Also, the screenshots are from a Grand 1, and our device is SM-G7102, not I7102. You mixed up with the Grand 1 i9082.
Oah you know, customers is maybe not the right word, unless they pay which is not the case!
Then I don t know if that can be called a vip experience, but I understand your point, maybe sometimes I m too nice, what to do...
For the screenshots, I didn t mix 'em, I explained in OP that I didn't have time to make any since I ran short of time, and that the ones I put here come from another phone.
A galaxy grand i9082, yep, well done, you have a sharp eye!
They are very similar in shape, layout and color (apart from the cascade icon to minimize windows that Samsung has removed after 4.2.2, a big mistake to my opinion), so people can get the idea.
WaseemAlkurdi said:
I'm a dev too, and I don't recommend the over-VIP experience you're using to grab customers. I ain't sure, but it looks humiliating to you to give picky users a VIP experience.
Just tell them to get the hell off the thread if they hate the idea (I really like it and would've upgraded if I was a TW user. I use AOSP CM).
Click to expand...
Click to collapse
In some ways you are right, but we think that being professional is not a bad thing, despite the fact that the forum is full of picky users, ready to make bad comments even without trying the product. Of course, we can and we will also give a VIP experience, but it is reserved for the ones that will earn it.
In any case we appreciate your support. Thank you
WaseemAlkurdi said:
All builds prior to NK1 are without KNOX.
NH6 is good and speedy.
I'm a dev too, and I don't recommend the over-VIP experience you're using to grab customers. I ain't sure, but it looks humiliating to you to give picky users a VIP experience.
Just tell them to get the hell off the thread if they hate the idea (I really like it and would've upgraded if I was a TW user. I use AOSP CM).
Also, the screenshots are from a Grand 1, and our device is SM-G7102, not I7102. You mixed up with the Grand 1 i9082.
Click to expand...
Click to collapse
When downgrade strucked at boot logo "samsung".
Thai version. 4.3. What to do wasim? Any idea.
Odin flash failed. Again flashed NH6. Again boot loop.
Pllllzzzzz download link
Sent from my SM-G7102 using XDA Free mobile app
wrishaba said:
When downgrade strucked at boot logo "samsung".
Thai version. 4.3. What to do wasim? Any idea.
Odin flash failed. Again flashed NH6. Again boot loop.
Click to expand...
Click to collapse
As I recall, wiping (data/cache/Dalvik cache) from recovery worked.
You're lucky you ain't in a hard brick
Note that you need ClockWorkMod Recovery to wipe Dalvik.
EDIT: Please direct any development questions, queries, etc. to the new thread in the Development Forum, concerning all development-y things.
http://forum.xda-developers.com/grand-prime/development/unofficial-cyanogenmod-12-1-g530w-t3424761
============================================================
I've recently started working on a custom ROM for the Samsung Grand Prime G530W [gprimeltevl/gprimeltecan], and so far I have built a somewhat working ROM (without any radio/wireless capability or audio for now).
If there is interest in this project (which I think there is; the lack of any kind of love shown for the G530W is annoying), I'll continue hacking away at it until I (hopefully) have a working ROM.
I'm new to Android ROM building in general, and there have been several bumps along the way, so any help would be appreciated.
Thanks.
I will be uploading images daily to my Drive storage, in folders named by date (if the date today is not there, then the image had not been built or uploaded yet), and will be compressing the system.tar images with either gzip or xz to reduce the image size.
I will also be updating this area with issues and fixes as necessary.
What I have managed to get working so far (23/07/2016)
Limited mobile connectivity [ sending/receiving texts ].
- Calls can be received or made but there is no audio (speaker or microphone).
- Mobile data is not working.
- Currently the system does not show the mobile connection as active, but texts can still be sent and received.
Bluetooth is working
Audio is working (microphone, speaker)
Multimedia playback working
GPS is working
Wifi is working
Screen brightness controls working
Sensors are working (magnetic, rotation/gyro,proximity)
App installation is now working
Camera is kinda working - only back camera works, and the image is distorted.
Issues
Radio [ modem ] is not working properly
NFC is not working
MTP is not working
Cameras are not working
Here is a link to the system.tar, boot.tar and recovery.tar flashable by ODIN or fastboot (when unpacked).
https://drive.google.com/open?id=0B-bYwctD_MoDaWJGcUQ4eWtzRTQ
Project GitHub Repositories:
https://github.com/vince2678/android_device_samsung_gprimeltecan
https://github.com/vince2678/android_vendor_samsung_gprimeltecan
If there are any other issues I missed, let me know.
Great effort
vince2678 said:
I managed to compile and get an image working for the G530W.
What I have managed to get working so far
Bluetooth is working
Audio is working (microphone, speaker)
Multimedia playback working
GPS is working
Sensors are working (magnetic, rotation/gyro,proximity)
Issues
Device fails to unlock and heats up [only once, so far]
Wifi is not working
Radio [ modem ] is not working
User interface crashes periodically
Screen brightness controls not working
MTP is not working
Cameras are not working
Here is a link to the system.tar, boot.tar and recovery.tar flashable by ODIN or fastboot (when unpacked).
https://drive.google.com/folderview?id=0B-bYwctD_MoDVzd0eS1aaDV6RW8&usp=sharing
I'll be working at it to get at least the Wifi working, if there are any other issues I missed, let me know.
Click to expand...
Click to collapse
Good work so far!
I recently purchased a g530w and I would love to boot the stock ROM.
However, I am still busy researching and reading up on this device before I attempt to flash anything. Actually, I did create an update zip file to remove Skype and tried applying it while not rooted but it failed because it was not properly signed.
Anyway, I will watch your progress with keen interest!
Zippy Dufus said:
Good work so far!
I recently purchased a g530w and I would love to boot the stock ROM.
However, I am still busy researching and reading up on this device before I attempt to flash anything. Actually, I did create an update zip file to remove Skype and tried applying it while not rooted but it failed because it was not properly signed.
Anyway, I will watch your progress with keen interest!
Click to expand...
Click to collapse
Sounds interesting. Did you try rooting your phone and using Link2SSD to remove the app(s)? It works pretty well, and you don't have to go through the whole effort of packing and unpacking the ROM.
vince2678 said:
Sounds interesting. Did you try rooting your phone and using Link2SSD to remove the app(s)? It works pretty well, and you don't have to go through the whole effort of packing and unpacking the ROM.
Click to expand...
Click to collapse
Here's my plan for my new phone:
Reading and research (in progress)
Setting up Odin on a virtual machine (I am a Linux user) and testing a restore of the stock ROM. Do you have a good link to such a ROM? I briefly looked at http://www.sammobile.com/firmwares/ and this site looks a little sketchy to me.
Root the device. I believe the method described in this G530T thread has worked for our G530W.
Debloat the crapware. Surprisingly, there is not all that much on the device - mostly some Micro$oft crap, Skype, and an old, old version of Chrome which I cannot uninstall. As root, I'll just go in and delete the unwanted stuff from /system/app using a terminal emulator.
Once it get this far, I can probably live with stock Lollipop. Question, if you are learning how to port a ROM, have you considered starting with Marshmallow? I'm keen to move up.
Build the ROM myself and then attempt to build it with my Linaro toolchain which I built from scratch myself.
Questions, with what you know so far, will the G530H ROM in this thread work on our phone? Is this what you started from? What differences between the 2 devices what preclude it from working on ours - different hardware? software - i.e. different bootloader?, etc?
Zippy Dufus said:
Here's my plan for my new phone:
Reading and research (in progress)
Setting up Odin on a virtual machine (I am a Linux user) and testing a restore of the stock ROM. Do you have a good link to such a ROM? I briefly looked at http://www.sammobile.com/firmwares/ and this site looks a little sketchy to me.
Root the device. I believe the method described in this G530T thread has worked for our G530W.
Debloat the crapware. Surprisingly, there is not all that much on the device - mostly some Micro$oft crap, Skype, and an old, old version of Chrome which I cannot uninstall. As root, I'll just go in and delete the unwanted stuff from /system/app using a terminal emulator.
Once it get this far, I can probably live with stock Lollipop. Question, if you are learning how to port a ROM, have you considered starting with Marshmallow? I'm keen to move up.
Build the ROM myself and then attempt to build it with my Linaro toolchain which I built from scratch myself.
Questions, with what you know so far, will the G530H ROM in this thread work on our phone? Is this what you started from? What differences between the 2 devices what preclude it from working on ours - different hardware? software - i.e. different bootloader?, etc?
Click to expand...
Click to collapse
Hey Zippy,
That sounds like a good idea.
That website does seem kinda sketchy, and their downloads take millenia, but it's the only option available and their images actually work (just make sure to get the correct one).
Setting up a virtual machine is a good idea, because heimdall doesn't work with this device and I'm not keen on bricking my device trying to force it.
Rebooting between builds to test firmwares because of a lack of a good recovery was becoming a pain. (CyanogenMod Recovery is still missing critical features but it's better than stock).
You can use CF-Auto-Root to root the device (so simple) at:
https://download.chainfire.eu/774/C...uto-Root-gprimeltecan-gprimeltevl-smg530w.zip
Yup, debloating is good, i wanted to do so at first but I wanted to be done away with KNOX and have an su binary which worked flawlessly for good so I decided to start from scratch.
I've considered starting from M, but that will be a task for later. It is troublesome to start from a fimware above what your device is at when you're porting, because the vendor libraries and binaries you copy might not work in the newer version of Android because of linking errors.
You can copy the binaries fine but obscure errors due to missing references will pop up in the logs which will stop the modules from loading or binaries from running.
I'm having these issues with a build ID that is just a few apart from the one used on the stock ROM - LMY49J on the cm build versus LMY47X on the stock).
My Git repos are above - you can get yourself a cm12.1 source tree, pull my device_ and vendor_ trees, pull proprietary files using the scripts in the vendor tree, build from source and then flash the resultant images to your device.
The G530H ROM might, in theory flash without issue and actually boot, but whether it will be usable is another thing.
The thing that differs between the devices, as far as I'm aware, is mostly the baseband, some other device hardware (e.g the G530W has 1.5GB RAM instead of 1GB as most G530 devices), and the device bootloader. As such, the kernels and modules used might differ slightly in terms of modules compiled in, even though they're built from the same kernel source.
And yes, indeed, I started from a G530 device and vendor tree, though whether it was that one, or perhaps one for the G530FZ, I don't remember (though I think it's the G530FZ, it's the device closest to the G530W).
Finally something for this variant, I've been waiting for ages. Huge thumbs up dude, from a thankful Canadian. I don't use this phone as my daily driver so I'll be flashing this without delay. Mind if I trouble you for the order of operations? I've never used Odin to flash a custom ROM before.
Some more questions ...
Hi again @vince2678, I have more questions:
Do you have a local_manifest.xml that drives your build? ... I have a single-purpose Fedora24 virtual machine which I use to build android ROMs.
Does your build actually produce a CM12.1 zip installation package? ... And do you simply harvest the system.img, etc afterwards to put into a flashable this tar file?
What is the command line that do you use to create the flashable tar files? ... I'm just curious.
What version of the firmware does your device have? ... Mine has G530WVLU1AOFB. Apparently, this is the Tanzanian version! WTF? I purchased my phone from a Costco in Oakville, Ontario, Canada. It was purported to be unlocked for all Canadian carriers. My carrier is Virgin Mobile (owned by Bell) and it works fine. But, my understanding is that device actually locks to your SIM card upon first use so you can't use it for other SIM cards, but I haven't proven this yet. BTW, I got over half of the stock ROM DL'ed from SamMobile before it stopped due to a "network error". Yeah right! I'll try again later.
Have you (or are you) cherry-picking patches from the G530H CM12.1 ROM? ... android_device_samsung_fortuna3g I suggest DL'ing their key files and comparing them to yours. They appear to be in the final exhilarating phase of perfecting their ROM.
So you have totally removed the KNOX software without in deleterious consequences? ... I thought that I read in an XDA thread where somebody did this and then had issues such as connecting to WIFI, etc. It appeared that there may be a dependency in the BIOS.
Did you trip the KNOX e-fuse hence void the warranty? ... Not that I care about the warranty, I only worry about bricking the device.
Unlike @Pbotelho, this is my daily driver so I will be proceeding slowly and cautiously and look forward to his experience flashing it.
Pbotelho said:
Finally something for this variant, I've been waiting for ages. Huge thumbs up dude, from a thankful Canadian. I don't use this phone as my daily driver so I'll be flashing this without delay. Mind if I trouble you for the order of operations? I've never used Odin to flash a custom ROM before.
Click to expand...
Click to collapse
Hi Pbotelho, thanks man. You will have to enable Developer Mode on your phone and unlock the bootloader from the settings. I don't remember what exactly in the settings that option is, but it should be in the Debugging area for sure.
Once done, reboot into Download Mode [Press Power+Volume Down+Home].
Once you've done that, grab the boot.tar, system.tar.xz and recovery.tar from the links above. Extract the system.tar.xz with 7zip or `xz -d system.tar.xz` if under Linux to get a system.tar file, and flash the recovery, boot, and system, one after the other, in whatever order, by booting into download mode as soon as it is done flashing a file.
You will need to wipe your cache and data partitions, which can be done by rebooting into recovery [Power+Volume Up+Home].
The button options are built into the hardware so they can be used at any point after the phone is on.
When all that is done, you can report any problems here [or on the github page] and post logcats and I'll look at them if there's any issue I've missed.
Zippy Dufus said:
Hi again @vince2678, I have more questions:
Do you have a local_manifest.xml that drives your build? ... I have a single-purpose Fedora24 virtual machine which I use to build android ROMs.
Does your build actually produce a CM12.1 zip installation package? ... And do you simply harvest the system.img, etc afterwards to put into a flashable this tar file?
What is the command line that do you use to create the flashable tar files? ... I'm just curious.
What version of the firmware does your device have? ... Mine has G530WVLU1AOFB. Apparently, this is the Tanzanian version! WTF? I purchased my phone from a Costco in Oakville, Ontario, Canada. It was purported to be unlocked for all Canadian carriers. My carrier is Virgin Mobile (owned by Bell) and it works fine. But, my understanding is that device actually locks to your SIM card upon first use so you can't use it for other SIM cards, but I haven't proven this yet. BTW, I got over half of the stock ROM DL'ed from SamMobile before it stopped due to a "network error". Yeah right! I'll try again later.
Have you (or are you) cherry-picking patches from the G530H CM12.1 ROM? ... android_device_samsung_fortuna3g I suggest DL'ing their key files and comparing them to yours. They appear to be in the final exhilarating phase of perfecting their ROM.
So you have totally removed the KNOX software without in deleterious consequences? ... I thought that I read in an XDA thread where somebody did this and then had issues such as connecting to WIFI, etc. It appeared that there may be a dependency in the BIOS.
Did you trip the KNOX e-fuse hence void the warranty? ... Not that I care about the warranty, I only worry about bricking the device.
Unlike @Pbotelho, this is my daily driver so I will be proceeding slowly and cautiously and look forward to his experience flashing it.
Click to expand...
Click to collapse
Hi Zippy,
I do not have a local_manifest, if you want you can just manually pull the device and vendor trees into your build area, or you can make one yourself if you wish.
I will probably make one though, because the build has dependencies on some qcom sources.
I just use 'make -j8' to build everything, though you can use 'make otapackage' to build a flashable zip [You'll need the CMR recovery from here though, the images can't be flashed by stock recovery]
For creating flashable tar files, you can just use `tar`. You don't need to make .md5 verifiable archives, those are just to ensure a download wasn't corrupted [I provide md5sums for checking].
The system.img in the output directory will have to be renamed to 'system.img.ext4' and then archived, as so:
Code:
cd out/target/product/gprimeltecan
ln system.img system.img.ext4
tar cf system.tar system.img.ext4
tar cf boot.tar boot.img
tar cf recovery.tar recovery.img
Then you can move the files wherever and flash them with Odin.
Yes the gprimeltevl/gprimeltecan baseband is indeed G530WVLU1AOFB, though this should work with all G530WXXXXXXXs (not sure how many different ones are out there].
I'm not sure about the SIM locking thing, I cannot confirm this, someone might have to try to check.
I did consider sourcing from that repository, though ultimately i ended up using another one [I don't remember the name]. I might take a look at their source to see what I can do about mine though.
I did trip KNOX, though that was back when I was still trying to root my phone with CF-Root, so I'm not sure if flashing this will trip KNOX. And yes, KNOX is completely gone from this device, with no problems from the phone.
vince2678 said:
Hi Pbotelho, thanks man. You will have to enable Developer Mode on your phone and unlock the bootloader from the settings. I don't remember what exactly in the settings that option is, but it should be in the Debugging area for sure.
Once done, reboot into Download Mode [Press Power+Volume Down+Home].
Once you've done that, grab the boot.tar, system.tar.xz and recovery.tar from the links above. Extract the system.tar.xz with 7zip or `xz -d system.tar.xz` if under Linux to get a system.tar file, and flash the recovery, boot, and system, one after the other, in whatever order, by booting into download mode as soon as it is done flashing a file.
You will need to wipe your cache and data partitions, which can be done by rebooting into recovery [Power+Volume Up+Home].
The button options are built into the hardware so they can be used at any point after the phone is on.
When all that is done, you can report any problems here [or on the github page] and post logcats and I'll look at them if there's any issue I've missed.
Click to expand...
Click to collapse
I got impatient with it so I took a gamble and inferred with some background knowledge. Got it up and running several hours ago. Performance wise, it seems dead on perfect. There's no lag, no force closing of apps. Everything runs as snappy as it should. Its fast as f***. Now I even installed xposed framework and added in a few modules, one of those being the Android N-ify project, and it works really well with it, so kudos on this area. I'll be sure to uninstall xposed when it comes to error reporting and logcats.
The only issues I'm seeing besides the ones you've already outlined are graphical in nature. I'm not home at the moment but I'll upload some logcats when I get the chance.
1) What I'm seeing is a blackout out lock screen. I have a theme installed and used it to apply a custom lock wallpaper to test this out. The wallpaper only shows once you've accessed the Pattern input by swiping up. Haven't tried it with a pin. If you're only using swipe, it'll stay black until unlocked.
2) When unlocked and swiping down to access the notifications panel and quick settings, the same blackout effect is present. This is present only while you're looking at your notifications or tiles, and returns to normal when swiped back up.
3) The first half of this part is only noticed when using the material glass theme. When swiping down to access the notification panel without notifications, the "no notifications" text will be present as it should be, however, when swiped down again to access the quicksettings tiles, the "no notifications" text isn't cleared away. It sits behind the brightness slider. This isn't noticeable on the stock theme because its opaque, while material glass features transparency as their main selling card. If using the battery saver, the text from this persistent notification will appear instead.
Edit: Upon further analysis, it seems that the notification content is linked to the bottom of the header instead of the bottom of the quicksettings tiles, and that's why it works this way. When expanding or shrinking the header, the notification also moves directly with it.
Second half: whether on the stock theme or not, the "no notifications" text will continue to stick and be viewable on the lockscreen, retaining its position that is viewed in the notification panel. It sits directly above the clock. The persistent battery saver notification works the same way. I'm no expert, but I believe that since the notification panel and lockscreen both go to black, that this might be linked in some way.
4) Sometimes when using the stock theme and toggling options in the quick settings tiles, it'll glitch out and turn into what I can only describe as a zombie menu. The pixels of the status bar are replaced by that proportionate area of the quick settings menu, and when swiping down to use the menu, access is disabled (it can't be touched) and it closes itself when attempted. Only way I've been able to fix it was to toggle the theme to material glass and all was restored, still subject to the above three points.
Edit: 5) when using kernel adiutor to try to adjust the CPU frequencies, the only option that comes up for both minimum and maximum is 0MHz. The button seems to work as well, bringing the clock max speed down to 0 for a split second before it reverts to a a maximum of 200MHz. Adjusting the governor after the fact won't restore the maximum, seems only a reboot will get it done. I'm slightly amazed to be honest as before on Touchwiz, it was impossible to get it to hold onto a lower maximum. It would jump all over the place as it pleased.
Edit: 6) The recents hardware button is disabled. Touching it, holding it, nor double tapping brings up a function. It also isn't present in settings when trying to map the button functions. Its the only one that's missing. Power, home, back, and volume are all there.
That's all I got for the moment, I tried to be as descriptive as possible as I won't be able to get the logcats up for awhile. Let me know if you have any questions about what I've said here.
And also, are you taking feature requests?
Pbotelho said:
I got impatient with it so I took a gamble and inferred with some background knowledge. Got it up and running several hours ago. Performance wise, it seems dead on perfect. There's no lag, no force closing of apps. Everything runs as snappy as it should. Its fast as f***. Now I even installed xposed framework and added in a few modules, one of those being the Android N-ify project, and it works really well with it, so kudos on this area. I'll be sure to uninstall xposed when it comes to error reporting and logcats.
The only issues I'm seeing besides the ones you've already outlined are graphical in nature. I'm not home at the moment but I'll upload some logcats when I get the chance.
1) What I'm seeing is a blackout out lock screen. I have a theme installed and used it to apply a custom lock wallpaper to test this out. The wallpaper only shows once you've accessed the Pattern input by swiping up. Haven't tried it with a pin. If you're only using swipe, it'll stay black until unlocked.
2) When unlocked and swiping down to access the notifications panel and quick settings, the same blackout effect is present. This is present only while you're looking at your notifications or tiles, and returns to normal when swiped back up.
3) The first half of this part is only noticed when using the material glass theme. When swiping down to access the notification panel without notifications, the "no notifications" text will be present as it should be, however, when swiped down again to access the quicksettings tiles, the "no notifications" text isn't cleared away. It sits behind the brightness slider. This isn't noticeable on the stock theme because its opaque, while material glass features transparency as their main selling card. If using the battery saver, the text from this persistent notification will appear instead.
Click to expand...
Click to collapse
Hi Pbotelho,
I'll try to answer everything as completely as I can.
The blackout lock screen thing seems to be an issue with Trebuchet. I found that using a different lock screen app solves this issue.
As for the blackout on the notification area, I'm not sure what exactly is causing this, though I think this may be a problem with the cm-12.1 source and not necessarily the device port itself.
Second half: whether on the stock theme or not, the "no notifications" text will continue to stick and be viewable on the lockscreen, retaining its position that is viewed in the notification panel. It sits directly above the clock. The persistent battery saver notification works the same way. I'm no expert, but I believe that since the notification panel and lockscreen both go to black, that this might be linked in some way.
Click to expand...
Click to collapse
This seems to be an issue with Trebuchet again, and using a different lock application fixes this.
Sometimes when using the stock theme and toggling options in the quick settings tiles, it'll glitch out and turn into what I can only describe as a zombie menu. The pixels of the status bar are replaced by that proportionate area of the quick settings menu, and when swiping down to use the menu, access is disabled (it can't be touched) and it closes itself when attempted. Only way I've been able to fix it was to toggle the theme to material glass and all was restored, still subject to the above three points.
Click to expand...
Click to collapse
I'm aware of this one, for now you can fix this by disabling Brightness Control in the settings ( Settings->Status Bar->Brightness Control).
This again might be an issue with the cm-12.1 source, though it'll need some checking to confirm.
Edit: when using kernel adiutor to try to adjust the CPU frequencies, the only option that comes up for both minimum and maximum is 0MHz. The button seems to work as well, bringing the clock max speed down to 0 for a split second before it reverts to a a maximum of 200MHz. Adjusting the governor after the fact won't restore the maximum, seems only a reboot will get it done. I'm slightly amazed to be honest as before on Touchwiz, it was impossible to get it to hold onto a lower maximum. It would jump all over the place as it pleased.
Click to expand...
Click to collapse
I'm using Kernel Adiutor and frequency setting is fine. Did you try using a tunable governor like interactive? That may be the issue.
Edit: 6) The recents hardware button is disabled. Touching it, holding it, nor double tapping brings up a function. It also isn't present in settings when trying to map the button functions. Its the only one that's missing. Power, home, back, and volume are all there.
Click to expand...
Click to collapse
I'm aware of this, you can blame this on my bad arithmetic skills . I had set the wrong bit field mask for the button settings in the device frameworks.
I'll be pushing a fix addressing this shortly.
And also, are you taking feature requests?
Click to expand...
Click to collapse
That depends on what the features are, if they're reasonable and within my capabilities, then yeah .
PS: I would appreciate any help I can get, and if you have any coding skills and time to compile builds, you can help me polish up the device port.
Thanks!
vince2678 said:
Hi Pbotelho,
I'll try to answer everything as completely as I can.
The blackout lock screen thing seems to be an issue with Trebuchet. I found that using a different lock screen app solves this issue.
As for the blackout on the notification area, I'm not sure what exactly is causing this, though I think this may be a problem with the cm-12.1 source and not necessarily the device port itself.
This seems to be an issue with Trebuchet again, and using a different lock application fixes this.
I'm aware of this one, for now you can fix this by disabling Brightness Control in the settings ( Settings->Status Bar->Brightness Control).
This again might be an issue with the cm-12.1 source, though it'll need some checking to confirm.
I'm using Kernel Adiutor and frequency setting is fine. Did you try using a tunable governor like interactive? That may be the issue.
I'm aware of this, you can blame this on my bad arithmetic skills . I had set the wrong bit field mask for the button settings in the device frameworks.
I'll be pushing a fix addressing this shortly.
That depends on what the features are, if they're reasonable and within my capabilities, then yeah .
PS: I would appreciate any help I can get, and if you have any coding skills and time to compile builds, you can help me polish up the device port.
Thanks!
Click to expand...
Click to collapse
1) Aww man I love using Trebuchet, I like to keep my install as small as possible so I'm not one for installing additional apps. I'm a resource junkie though, so its just a matter of personal preference.
2) Again, I'm not an expert, but I suspect it might be the device port. Previously, I've had an unofficial version of CM12.1 installed on a Galaxy Tab 3 as well as a CM12.1 based Pac-rom installed on a Galaxy S4. I'm not sure if this is something those developers corrected on their own or not when building their ROMs, so it could be the source. That's the best of my knowledge on the topic.
3) Will do for the brightness slider, but again, it isn't something I experienced on the other devices with CM12.1 and the sister project.
4) Yeah I played around with the governors and tried all of them. They all list 0MHz as the only option. Maybe its a CPU hotplug issue? I didn't try playing around with those so I'll have to get back to you on that one.
5) Look forward to the update I have a question regarding it though. I'm really familiar with updating custom ROMs through recovery using the zip file format, but this is the first time I'm using Odin to do the job. Will flashing an update with Odin this way cause a factory reset? Or will it update as expected?
6) A couple more graphical hiccups I remembered. The blackout also happens when going to About Phone>Status. In About Phone, the device field says unknown (doesn't bother me, I just don't know if its significant or not), the illumination for the hardware buttons isn't working (I usually keep them off to save battery anyways, but someone out there probably uses it). And finally, when switching recents by holding the home button, only the title bars of the individual apps are viewable. The content of the windows themselves is completely transparent so it looks like a series of floating title bars.
(Apologies if some of these features are already included, I didn't get the opportunity to check, I just think they're awesome)
Feature requests:
1) When phone is off and charging, percentage is displayed inside battery symbol.
2) CPU and GPU undervolting built into the kernel. These custom ROMs are much better than the stock ROM in terms of functionality, but the battery life on the stock Samsung experience is no joke.
3) If possible, more steps for CPU frequency adjustments, every 100MHz or so. I remember the stock ROM had limited options. My S4 is the example I'm going to use here, it has a step for every 108MHz.
4) USB fast charging, aka setting USB to "charge only".
5) Wakelock Blocker. Its built into the latest Resurrection Remix for the S4, not sure if that could be of viable use to you. It'll certainly help out with battery improvements.
6) Boot Manager. Decide which apps get to start at boot. Its built into Marshmallow and an xposed module also exists for this purpose, so really low priority on this one, for me at least.
7) This one is a doozy. Absolutely the one I care most about, but most likely asking for too much. USB tethering. Already exists, I know, but not the way I hope it to. I have an old WRT54G router with DD-WRT installed. My goal is basically this: Phone's network connection>USB Tether>Micro-USB-LAN adapter>WAN port of router. In this sense, the phone would be acting as the modem in a regular home network. I know its possible to do this if the router has a USB port, but mine doesn't, and I also know its possible if you have an intermediate device that bridges the connections for you. Like a laptop, PC, or raspberry pi. Cost efficiency as a student is what I'm working towards though, so this one is a wishlist request.
Ps. The only coding skills I have are from high school's Visual Basic and HTML, truly beginner stuff, and that was about 10 years ago. I'm running Ubuntu on a core i5-2500k with 16GB of RAM and about a terabyte of space though, so compiling is definitely a possibility with some instructions.
Pbotelho said:
5) Look forward to the update I have a question regarding it though. I'm really familiar with updating custom ROMs through recovery using the zip file format, but this is the first time I'm using Odin to do the job. Will flashing an update with Odin this way cause a factory reset? Or will it update as expected?
Click to expand...
Click to collapse
Nope, this should be pretty much the same as flashing a zip from recovery. If you modified the system partition though (like by flashing GApps for example) your changes will be lost.
Pbotelho said:
6) A couple more graphical hiccups I remembered. The blackout also happens when going to About Phone>Status. In About Phone, the device field says unknown (doesn't bother me, I just don't know if its significant or not), the illumination for the hardware buttons isn't working (I usually keep them off to save battery anyways, but someone out there probably uses it). And finally, when switching recents by holding the home button, only the title bars of the individual apps are viewable. The content of the windows themselves is completely transparent so it looks like a series of floating title bars.
Click to expand...
Click to collapse
I fixed this in the device tree, once I've built a new image this should be corrected.
Pbotelho said:
(Apologies if some of these features are already included, I didn't get the opportunity to check, I just think they're awesome)
Feature requests:
1) When phone is off and charging, percentage is displayed inside battery symbol.
Click to expand...
Click to collapse
I'll be looking into this one.
Pbotelho said:
2) CPU and GPU undervolting built into the kernel. These custom ROMs are much better than the stock ROM in terms of functionality, but the battery life on the stock Samsung experience is no joke.
Click to expand...
Click to collapse
I'm still using the stock kernel in my builds, once the builds are stable I'll start compiling the kernel from source and I'll see if I can do something about this.
Pbotelho said:
3) If possible, more steps for CPU frequency adjustments, every 100MHz or so. I remember the stock ROM had limited options. My S4 is the example I'm going to use here, it has a step for every 108MHz.
Click to expand...
Click to collapse
According to the configurations, this is already how it is.
PS: I changed the governor under Kernel Adiutor to performance from interactive and switched back, and became unable to change the frequencies (like you were experiencing). I'll need to play around more with this to see why.
Pbotelho said:
4) USB fast charging, aka setting USB to "charge only".
Click to expand...
Click to collapse
This is already available under the Settings->Storage->USB Computer Connection menu
Pbotelho said:
5) Wakelock Blocker. Its built into the latest Resurrection Remix for the S4, not sure if that could be of viable use to you. It'll certainly help out with battery improvements.
6) Boot Manager. Decide which apps get to start at boot. Its built into Marshmallow and an xposed module also exists for this purpose, so really low priority on this one, for me at least.
Click to expand...
Click to collapse
Not sure I could do this, I'll check.
Pbotelho said:
7) This one is a doozy. Absolutely the one I care most about, but most likely asking for too much. USB tethering. Already exists, I know, but not the way I hope it to. I have an old WRT54G router with DD-WRT installed. My goal is basically this: Phone's network connection>USB Tether>Micro-USB-LAN adapter>WAN port of router. In this sense, the phone would be acting as the modem in a regular home network. I know its possible to do this if the router has a USB port, but mine doesn't, and I also know its possible if you have an intermediate device that bridges the connections for you. Like a laptop, PC, or raspberry pi. Cost efficiency as a student is what I'm working towards though, so this one is a wishlist request.
Click to expand...
Click to collapse
I don't quite understand what you mean by this, how does it differ from the normal USB tethering?
Pbotelho said:
Ps. The only coding skills I have are from high school's Visual Basic and HTML, truly beginner stuff, and that was about 10 years ago. I'm running Ubuntu on a core i5-2500k with 16GB of RAM and about a terabyte of space though, so compiling is definitely a possibility with some instructions.
Click to expand...
Click to collapse
If you can't code, that's fine, you could set up a build environment on your computer for creating images from the source.
vince2678 said:
Nope, this should be pretty much the same as flashing a zip from recovery. If you modified the system partition though (like by flashing GApps for example) your changes will be lost.
I fixed this in the device tree, once I've built a new image this should be corrected.
I'll be looking into this one.
I'm still using the stock kernel in my builds, once the builds are stable I'll start compiling the kernel from source and I'll see if I can do something about this.
According to the configurations, this is already how it is.
PS: I changed the governor under Kernel Adiutor to performance from interactive and switched back, and became unable to change the frequencies (like you were experiencing). I'll need to play around more with this to see why.
This is already available under the Settings->Storage->USB Computer Connection menu
Not sure I could do this, I'll check.
I don't quite understand what you mean by this, how does it differ from the normal USB tethering?
If you can't code, that's fine, you could set up a build environment on your computer for creating images from the source.
Click to expand...
Click to collapse
Sounds awesome, I'll flash it as soon as possible and continue testing it for you.
I uploaded a logcat to the other thread in development. The performance governor is set up as the default for me so I'm set up with that situation from the get go.
It technically isn't different from regular USB tethering, but it seems that no one has done it successfully before. There are adapters that you can use to provide a wired Ethernet connection to an android device over micro USB, but no one has been able to do it the other way around. Google results don't turn up any answers.
And I'm willing to learn how to code, but I fear that I may slow you down with this project as I get past the learning curve. That being said, I can definitely set up a build environment and compile it from source for you. That'll be a learning experience on its own. Just point me towards a noob guide and I'll get it done.
Pbotelho said:
Sounds awesome, I'll flash it as soon as possible and continue testing it for you.
I uploaded a logcat to the other thread in development. The performance governor is set up as the default for me so I'm set up with that situation from the get go.
It technically isn't different from regular USB tethering, but it seems that no one has done it successfully before. There are adapters that you can use to provide a wired Ethernet connection to an android device over micro USB, but no one has been able to do it the other way around. Google results don't turn up any answers.
And I'm willing to learn how to code, but I fear that I may slow you down with this project as I get past the learning curve. That being said, I can definitely set up a build environment and compile it from source for you. That'll be a learning experience on its own. Just point me towards a noob guide and I'll get it done.
Click to expand...
Click to collapse
The USB tethering thing sounds interesting, though I would need to have one of the adapters to test that, and time at hand as well.
As for the build environment, the best source of information is the CM wiki. You can look at these links below on how to get started:
https://wiki.cyanogenmod.org/w/Development#Learning_To_Build_CM
https://wiki.cyanogenmod.org/w/Doc:_Building_Basics
https://docs.omnirom.org/Setting_Up_A_Compile_Environment
https://wiki.cyanogenmod.org/w/Build_for_captivatemtd
http://jira.omnirom.org/browse/OMNI-1263
http://forum.xda-developers.com/showthread.php?t=2329228
The guides above are just outlines to detail the general build process - you will need to do things slightly differently from the steps above to get the proper source and device trees.
The attached local_manifest can be used with repo when obtaining the cm-12.1 source.
Remember you'll be getting the cm-12.1 source - not anything else.
vince2678 said:
The attached local_manifest can be used with repo when obtaining the cm-12.1 source.
Remember you'll be getting the cm-12.1 source - not anything else.
Click to expand...
Click to collapse
So if I add in your device tree and provide a toolchain, I should be good to go? (I think so.)
Thanks!!
EDIT: Not so fast! I'll have to find a kernel as well.
Pbotelho said:
Edit: 5) when using kernel adiutor to try to adjust the CPU frequencies, the only option that comes up for both minimum and maximum is 0MHz. The button seems to work as well, bringing the clock max speed down to 0 for a split second before it reverts to a a maximum of 200MHz. Adjusting the governor after the fact won't restore the maximum, seems only a reboot will get it done. I'm slightly amazed to be honest as before on Touchwiz, it was impossible to get it to hold onto a lower maximum. It would jump all over the place as it pleased.
Click to expand...
Click to collapse
I've test Kernel Adiutor and I too got the O MHz only window for both as the only option. Though Now I wonder if it is because I used the latest beta Kernel Adiutor, I'll further check with the normal stable version. Pretty sure it'll fix it if it worked normally for Vinc. --- Update; As strange as it might look while re opening kernel adi to take a screenshot, the list of normal MHz values is there and working properly.. Strange.. Magic? Huh technology, you're so unpredictable.
Zippy Dufus said:
So if I add in your device tree and provide a toolchain, I should be good to go? (I think so.)
Thanks!!
EDIT: Not so fast! I'll have to find a kernel as well.
Click to expand...
Click to collapse
Hi Zippy,
The kernel source was included there as well (it's just a dummy source so that the build can get the necessary source files for libraries which need them). The build still uses the default prebuilt kernel though.
vince2678 said:
Hi Zippy,
The kernel source was included there as well (it's just a dummy source so that the build can get the necessary source files for libraries which need them). The build still uses the default prebuilt kernel though.
Click to expand...
Click to collapse
As an experiment, why don't you try downloading the G530H ROM, unzip, take the boot.img, and flash it over top of your stock kernel? See if it boots and how it performs.
Meanwhile, I plan to hack at putting together complete manifest, possibly with the G530H kernel and my Linaro 4.9 toolchain and see if I can build a complete ROM.
Have you extracted the firmware?
However, I don't want to flash anything until I see your ROM's modem working because it is my daily driver. But I'm keen though!!
I've managed to download the stock ROM from SamMobile but I'm now thinking of going straight to your ROM once it is a bit more complete and stable.
SM-G991U - Since Android 12 upgrade, often when unlocking I set a random pop-up that says, "item already copied to clipboard". I can't find anything to tun it off and it screaming doesn't affect to issue either. Anyone else have this and fix it? It makes no sense.
I'm also experiencing this but unfortunately I've no idea what's causing it. I'll keep an eye out for more reports of it.
I found some complaints on the Samsung forum too. Nothing suggested seems to fix it. I keep f'ing with settings that not only don't fix this but other things then get FU. Supper annoying.
What I think is happening is that unlocking the screen triggers the copying to clipboard pop-up but it's just the message. I can't see that anything is copied to clipboard except text I choose.
Not sure my AT&T POS can be rooted easily but when I get tired of this clipboard nonsense I'll look into it. I imagine a custom de-bloated ROM will fix it is Samsung won't.
Do you have KDE Connect installed? If so, could you try disabling Clipboard Sync in the plugin settings and see whether that stops the pop-ups?
Thanks. That suggestion has promise. I assume that worked for you. I've disabled it and will let you know after a day or two. Maybe the reason it isn't a huge problem is that that Android/Linux users aren't a big user base?
Since I've disabled that option in KDE Connect I've not seen the pop-up once (been a couple of days).
It makes sense because I think KDE Connect is regularly copying stuff to the clipboard from the connected computer. A lot of the time it will be the same data and whereas Android 11 never reported it, Android 12 obviously does.
So it's not an Android issue as such (although why _would_ it report that a needless copy to clipboard operation has been performed? It would just be an annoyance anyway!), I think KDE Connect needs to change to a check before copying to the clipboard.
Raised a bug: https://bugs.kde.org/show_bug.cgi?id=446567
Excellent. You totally nailed KDE Connect as causing it. I haven't gotten the pop-up for 2 days now.
KDE Connect could "fix it" by simply making the "feature" off by default. I'm still inclined to think Android should fix it. Earlier Android releases didn't have this problem. I've had KDE Connect for years.
Thanks for the work around!
I am having this issue( item already copied to clipboard) with a new Samsung A52 (recently updated to android 12 One UI 4.0 but was doing the same prior to update), i do not have KDE connect installed that i can find.
Well, since removing KDE Connect I haven't had any issue with it. I suggest you start a new thread for the A52. This thread solves is for the S21.
UbinTook said:
I am having this issue( item already copied to clipboard) with a new Samsung A52 (recently updated to android 12 One UI 4.0 but was doing the same prior to update), i do not have KDE connect installed that i can find.
Click to expand...
Click to collapse
Same, i have the same issue on Galaxy Fold 3 and no KDE installed
Crazy idea but knowing that removing KDE Connect from the S21 fixed the issue, install KDE Connect and then uninstall KDE Connect. Maybe it leaves some residual that corrects the problem. Can't hurt.
I also recommend starting a thread for the A52 asking this question.
jerryp7 said:
Crazier things have happened ! i will look into that and see if it works .
i have indeed started a thread in the A52 forum ( about 3 weeks ago)with no responses as of yet .
(https://forum.xda-developers.com/t/...ied-to-clipboard-copied-to-clipboard.4392851/)
Click to expand...
Click to collapse
Best I can do is keep my fingers crossed for you. Sorry
It is not an issue. It's a feature in Android 12 that warns user that the app is copying the content of the clipboard. It's a privacy feature and you can turn it off at settings - privacy.
Didn't work for me while KDE Connect was installed. Maybe this is the problem "Alert when clipboard accessed" being turned on under privacy for the A52 users.