Related
Device Reset
powered by fiinix's DllImport Project
description
--- restart or shutdown device
recognition
--- XDA Portal
pre-installed
--- Rataplan ROM
release log
--- Device Reset v3.0.0.0
------ see Post #31 or click here
--- Device Reset v2.0.1.0
------ see Post #25 or click here
--- Device Reset v2.0.0.0
------ see Post #16 or click here
--- Device Reset v1.2.0.0
------ see Post #15 or click here
--- Device Reset v1.1.0.0
------ see Post #14 or click here
does soft reset wipe the device?
soft reset restarts back your phone.
power will shutdown your phone thoroughly(no need to press the power switch button)
Nice app, THX (+)
Thanks sh4d0w86!!
congratulations for first wp7 development!!
will keep my power button intact much longer! that was needed
I'm sure hard-reset is a good idea, but if a bad manip occurs it can be upsetting...or with a flashy red background color for warning purpose...
would it be possible to have all restart options? i mean one which start with the tricolors screen, another for usb update (the one used to load goldcarded .nbh)...?
NebZoNe said:
I'm sure hard-reset is a good idea, but if a bad manip occurs it can be upsetting...or with a flashy red background color for warning purpose...
Click to expand...
Click to collapse
+1 !!!
Just a small notification to confirm Hard-Reset please ...
Thankx for developpement
will it be possible to have a sleep button as a tile?
if possible pinnable tiles on the homescreen...
Magpir said:
does soft reset wipe the device?
Click to expand...
Click to collapse
soft reset = restart, reboot
hard reset = [factory] restore
Ttblondey said:
soft reset restarts back your phone.
power will shutdown your phone thoroughly(no need to press the power switch button)
Click to expand...
Click to collapse
exactly.
NebZoNe said:
Thanks sh4d0w86!!
congratulations for first wp7 development!!
will keep my power button intact much longer! that was needed
I'm sure hard-reset is a good idea, but if a bad manip occurs it can be upsetting...or with a flashy red background color for warning purpose...
would it be possible to have all restart options? i mean one which start with the tricolors screen, another for usb update (the one used to load goldcarded .nbh)...?
Click to expand...
Click to collapse
thanks, NebZoNe.
those were my thoughts exactly when wanting to build this app.
i will, of course, have notification pop up to execute a hard reset.
actually, that is the main reason it isn't implemented in first release...
unsure how to exactly do that, yet.
that is an awesome idea. will look into it.
poloche said:
+1 !!!
Just a small notification to confirm Hard-Reset please ...
Thankx for developpement
Click to expand...
Click to collapse
already on my to-do list.
glad you like the app.
Magpir said:
will it be possible to have a sleep button as a tile?
if possible pinnable tiles on the homescreen...
Click to expand...
Click to collapse
already on my to-do list.
unsure how to do, though, yet, which is why it wasn't already included.
sh4d0w86 said:
already on my to-do list.
unsure how to do, though, yet, which is why it wasn't already included.
Click to expand...
Click to collapse
put this in your MainPage.xaml.cs
could work
Code:
private string tag;
//If the app navigates to the MainPage.Xaml this function tries to read a a tag-property from the Uri.
//You use the Uri to navigate between pages by calling the NavigationServices.Navigate(new Uri("/MainPage.xaml",UriKind.Relative)).
//To push a parameter to the site you can add them to the uri as following:
//"/MainPage.xaml?tag=tagnvalue&otherproperty=othervalue"
//If you launch the app these settings are empty
//If you launch it with the pinned tile you can set this Uri to submit the parameters
protected override void OnNavigatedTo(System.Windows.Navigation.NavigationEventArgs e)
{
//get the value.
NavigationContext.QueryString.TryGetValue("tag", out tag);
//restart, shutdown... depending on the tagvalue. if tag is empty nothing happens (you can add a case default: "your code" break; to perform a default action)
switch(tag)
{
case "soft":
softreset(); //your void to perform the softreset
break;
case "hard":
hardreset();
break;
case "shotdown"
shotdown();
break;
}
}
//the functions performing the different restart modes
private void softreset()
{
}
private void hardreset()
{
}
private void shutdown()
{
}
//this action creates a softreset tile by calling PinToStart("soft");
private void PinToStart(string tag)
{
string title = "";
//set the title of the tile
switch (tag)
{
case "soft":
title = "soft reset";
break;
case "hard":
title = "hard reset";
break;
case "shotdown"
title = "shutdown";
break;
}
//search the tile with the title given by the tag in the step before
ShellTile TileToFind = ShellTile.ActiveTiles.FirstOrDefault(x => x.NavigationUri.ToString().Contains("DefaultTitle=" + tag));
//if it's not existing this creates a new one
if (TileToFind == null)
{
//the data for the tile
StandardTileData NewTileData = new StandardTileData
{
//you can create different images for the tiles called "softTile.jpg", "hardTile.jpg", etc. in you "Images" folder
BackgroundImage = new Uri("Images/" + tag + "Tile.jpg", UriKind.Relative),
Title = title,
//Count = 12,
//BackTitle = "",
//BackContent = "",
//BackBackgroundImage = new Uri("Blue.jpg", UriKind.Relative)
};
//create a new tile with the tiledata
ShellTile.Create(new Uri("/MainPage.xaml?tag=" + tag, UriKind.Relative), NewTileData);
}
Does anyone notice/try change background to white while accent color to blueberry and when you open the Device Reset you can't see anything. Is it a bug?
ne0cr0n said:
put this in your MainPage.xaml.cs
could work
Click to expand...
Click to collapse
thanks for that bit of code. unfortunately... i have no idea what it does exactly. :/
Ttblondey said:
Does anyone notice/try change background to white while accent color to blueberry and when you open the Device Reset you can't see anything. Is it a bug?
Click to expand...
Click to collapse
not a bug, an overlook on my part. everything still there and works, it is just white font on white background. fixed for next release. good catch. next release, app will match Theme & Accent choice.
sh4d0w86 said:
thanks for that bit of code. unfortunately... i have no idea what it does exactly. :/
Click to expand...
Click to collapse
I added some comments to the code
sh4d0w86 said:
thanks for that bit of code. unfortunately... i have no idea what it does exactly. :/
not a bug, an overlook on my part. everything still there and works, it is just white font on white background. fixed for next release. good catch. next release, app will match Theme & Accent choice.
Click to expand...
Click to collapse
Just an 'accidentally' catch. Well, will wait for the next release.
Device Reset v1.1.0.0 released
--- Added/Updated
------ Accent & Theme support
------ Message Boxes
--------- Hard Reset
--------- Shutdown
--- Fixed
------ White Theme bug
--- Issue(s)
------ Hard Reset
--------- still not working
Device Reset v1.2.0.0 released
--- Added/Updated
------ removed DLLImport hyperlink(s)
------ revised Application Icons
--- Removed
------ Hard Reset
Device Reset v2.0.0.0 released
--- Added/Updated
------ Double Tap to execute actions
------ Pinnable Soft Reset/Shutdown Tile(s)
--------- Hold button
--------- pinned actions execute from Tile
auto on/off airplane mode
Hi,
Can you add a feature in your app to auto on/off airplane mode at scheduled time??? It could be a great battery saver...
updated Post #1. also, added additional pictures; Tiles, Tile Actions
kushal3110 said:
Hi,
Can you add a feature in your app to auto on/off airplane mode at scheduled time??? It could be a great battery saver...
Click to expand...
Click to collapse
sorry, but that would be a total random feature...
Thanks for this apps
Nikolo33 said:
Thanks for this apps
Click to expand...
Click to collapse
welcome and thank you for using and supporting it.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I am going to fill this op with Questions and answers from all devices supported by Team Horizon. Please keep the respect and KEEP ALL NON DEVELOPMENT DISCUSSION HERE OR OUR
GOOGLE PLUS PAGE
Click to expand...
Click to collapse
.
Click to expand...
Click to collapse
Q. I came from 4.1.2 and I flashed your 4.2.1 and I can't access my files now?
A. Well this is because after the 4.2.1 update Google implemented a feature with in its ROM to allow for the use to apply user specific accounts. I suggest reflashing a 4.1.2 ROM, Then mount the phone once booted, Take all of the information you choose to keep and place it on your desktop, Once complete then reboot the phone into recovery and wipe the rm and reflash 4.2.1 once you have flashed rom and gapps, Before you leave recovery wipe the sd card. Once phone reboots then simply replace the information you placed on your desktop to its corresponding folder.
Click to expand...
Click to collapse
Q. my wifi is always on when in standby?
A.Disable wifi optimization, And avoid poor connections in wifi advanced options.. If you have Franco kernel, wifi fast pm helps too
Click to expand...
Click to collapse
Q. HELP I don't have a rom on my SD card and I am stuck in a boot loop what do I do?
A. You need to make sure you have a working adb setup along with all proper fastboot and device drivers installed. Place the rom you wish to flash in the root of the adb folder.
Make sure phone is in recovery mode and that it is plugged into the computer.
Open a command prompt and cd to the directory of the adb folder. ( or simply hold the shift key and right click your adb folder and choose to open command windows here)
now type: adb push (rom.zip) /sdcard/ (replace the (rom.zip) with the entire name of the rom.zip.)
Click to expand...
Click to collapse
Q. How come fast charge is not working or its enabled but not working?
A. Answer is simple, The roms stock kernel doesn't allow for fast charge. you may simply flash Franco kernel and or any other 4.2.1 kernel that supports to to gain functionality.
Click to expand...
Click to collapse
Q. Can I dirty flash (flash ROM without wipe)?
A Yes you may flash the ROM without wiping. YOU WILL HAVE TO REFLASH GAPPS. We don't recommend doing this but if you are pressed for time or its just too difficult then have at it. We will not support complaints from those that choose to go this route.
Click to expand...
Click to collapse
Warez Removed
Q. I have downloaded the ROM but it wont boot?
A. Please make sure you are downloading the correct ROM and completely wiping before flashing!
Crespo- http://d-h.st/users/iceandfire/?fld_id=9532#files
Grouper- http://d-h.st/users/iceandfire/?fld_id=8701#files
Maguro- http://d-h.st/users/iceandfire/?fld_id=8699#files
Mako- http://d-h.st/users/iceandfire/?fld_id=9438#files
Toro- http://d-h.st/users/iceandfire/?fld_id=8700#files
Toro Plus- http://d-h.st/users/iceandfire/?fld_id=9002#files
Click to expand...
Click to collapse
Q. Somebody know, how to disable waking up phone by pressing volume button?I dont like this feature.
A. Menu>settings>display>enable then disable the volume key MOD
Click to expand...
Click to collapse
Q. Where are my Chrono settings for weather and clock?
A. Menu>System Settings>Display>Clock widget
Click to expand...
Click to collapse
Q. Are the round widgets shown in the OP contained in the ROM? If not, are they available anywhere? Also, I cannot for the life of me figure out how to put a lockscreen widget. When I go into the Chronus settings, there are settings for the clock, weather and calendar widgets, but I can only add the clock widget to my device.
A. OK the widget is not included but called one more clock widget. To apply the clock. Lock the screen then place your finger on the clock and slide down till you reach the lock icon or the white outline is the write screen amd let go. Then long press the clock ad delete it. Then click the add widget . After you enabled everything in display then go to chrono in the options onthe lockscreen (the + sign from earlier) and add it. To add muliple widgets then slide down on clock to fill screen then swipe left or right.
Click to expand...
Click to collapse
Q. What is fast charge? what does it do for me? How do I get it to work?
A.
Fast charge is a option baked into the kernel that doesn't allow the phone to be mounted to the pc.
Keeps computer from mounting your sd card everytime its plugged in.
You need to install a kernel that supports it. Stock XennonHD doesn't allow for this. I suggest using Franco Kernel. found here: http://forum.xda-developers.com/showthread.php?t=1367341
Click to expand...
Click to collapse
Q. What gapps do i install on this rom? I installed the gapps from ice not all my apps are there?
A.
Download these gapps: http://goo.im/gapps/gapps-jb-20121212-signed.zip
Because all of the apps missing can be manually installed from the market. He did this to lighten the download.
Click to expand...
Click to collapse
Q. How to create a log cat
A. the code for logcat to output to a file is
adb logcat > name of problem.txt
you can also do
Click to expand...
Click to collapse
adb logcat -f name of problem.txt
how I prefer to do it is this way
Click to expand...
Click to collapse
:
adb logcat -v long > name of problem.txt
with the -v flag & the long argument, it changes output to long style, which means every line of logcat will be on its own line (makes it a little neater, imo)
Note: When outputting to a file, you will see a newline, but nothing printed, this is normal. To stop logcat from writting to a file, you need to press ctrl+c.
Click to expand...
Click to collapse
Here's where using logcat (via adb makes life really easy)
Lets say you find a problem you're having after looking at a logcat.
For example:
When I was trying to use a different ramdisk, wifi wouldn't work so I got a logcat that's almost 1300 lines long (a lot of stuff happens in the background)
So if you are searching for an error in the logcat file (it's always e/ for error, f/ for fatal. Those are the two main things that will break a system.)
D/dalvikvm( 871): GC_CONCURRENT freed 472K, 6% free 10224K/10823K, paused 1ms+6ms
V/AmazonAppstore.DiskInspectorServiceImpl( 871): Available blocks: 21981, Block size: 4096, Free: 90034176, Threshold: 5242880, withinThreshold? true
D/AmazonAppstore.UpdateService( 871): Received action: null from intent: Intent { cmp=com.amazon.venezia/com.amazon.mas.client.framework.UpdateService }
W/AmazonAppstore.UpdateService( 871): Confused about why I'm running with this intent action: null from intent: Intent { cmp=com.amazon.venezia/com.amazon.mas.client.framework.UpdateService }
D/dalvikvm( 890): GC_CONCURRENT freed 175K, 4% free 9375K/9671K, paused 2ms+3ms
V/AmazonAppstore.ReferenceCounter( 871): Reference (MASLoggerDB) count has gone to 0. Closing referenced object.
E/WifiStateMachine( 203): Failed to reload STA firmware java.lang.IllegalStateException: Error communicating to native daemon
V/AmazonAppstore.UpdateService( 871): runUpdateCommand doInBackground started.
V/AmazonAppstore.UpdateService( 871): Running UpdateCommand: digitalLocker
V/AmazonAppstore.UpdateCommand( 871): Not updating key: digitalLocker from: 1334228488057
V/AmazonAppstore.UpdateService( 871): Finished UpdateCommand: digitalLocker
V/AmazonAppstore.UpdateService( 871): Running UpdateCommand: serviceConfig
V/AmazonAppstore.MASLoggerDB( 871): performLogMetric: Metric logged: ResponseTimeMetric [fullName=com.amazon.venezia.VeneziaApplication_onCreate, build=release-2.3, date=Wed Apr 11 13:10:55 CDT 2012, count=1, value=1601.0]
V/AmazonAppstore.MASLoggerDB( 871): onBackgroundTaskSucceeded: Metric logged: ResponseTimeMetric [fullName=com.amazon.venezia.VeneziaApplication_onCreate, build=release-2.3, date=Wed Apr 11 13:10:55 CDT 2012, count=1, value=1601.0]
W/CommandListener( 118): Failed to retrieve HW addr for eth0 (No such device)
D/CommandListener( 118): Setting iface cfg
D/NetworkManagementService( 203): rsp
D/NetworkManagementService( 203): flags
E/WifiStateMachine( 203): Unable to change interface settings: java.lang.IllegalStateException: Unable to communicate with native daemon to interface setcfg - com.android.server.NativeDaemonConnectorException: Cmd {interface setcfg eth0 0.0.0.0 0 [down]} failed with code 400 : {Failed to set address (No such device)}
W/PackageParser( 203): Unknown element under : supports-screen at /mnt/asec/com.android.aldiko-1/pkg.apk Binary XML file line #16
D/wpa_supplicant( 930): wpa_supplicant v0.8.x
D/wpa_supplicant( 930): random: Trying to read entropy from /dev/random
D/wpa_supplicant( 930): Initializing interface 'eth0' conf '/data/misc/wifi/wpa_supplicant.conf' driver 'wext' ctrl_interface 'N/A' bridge 'N/A'
D/wpa_supplicant( 930): Configuration file '/data/misc/wifi/wpa_supplicant.conf' -> '/data/misc/wifi/wpa_supplicant.conf'
D/wpa_supplicant( 930): Reading configuration file '/data/misc/wifi/wpa_supplicant.conf'
D/wpa_supplicant( 930): ctrl_interface='eth0'
D/wpa_supplicant( 930): update_config=1
D/wpa_supplicant( 930): Line: 4 - start of a new network block
D/wpa_supplicant( 930): key_mgmt: 0x4
(mind you, that's 29 lines out of 1300ish, just for example)
Click to expand...
Click to collapse
I then could do the following with logcat:
adb logcat WifiStateMachine:E *:S -v long > name of problem.txt
and this will only print out any errors associated with WifiStateMachine, and anything which is fatal, which makes it about a million times easier to figure out what's going on!
Click to expand...
Click to collapse
In WifiStateMachine:E, the :E = to look for Errors, the full list of options is as follows:
V — Verbose (lowest priority)
D — Debug
I — Info (default priority)
W — Warning
E — Error
F — Fatal
S — Silent (highest priority, on which nothing is ever printed)
You can replace the :E with any other letter from above to get more info.
In order to filter out anything other than what you are looking for (in this case, WifiStateMachine) you must put a *:S after your last command (i.e. WifiStateMachine:E ThemeChoose:V ... ... AndroidRuntime:E *:S)
Click to expand...
Click to collapse
Q. I am in the download section but what rom is for my device?
A.
Crespo- nexus S
Grouper- Nexus 7
Maguro- gsm galaxy nexus t-mobile
Mako- galaxy nexus 4
Toro- Galaxy nexus Verizon Wireless
Toro Plus- sprint galaxy nexus
Click to expand...
Click to collapse
Click to expand...
Click to collapse
==================================================
Important please read
I. Appreciation
There are many ways to show your support to us. You can:
Press the "Thanks" button.
Hit the donation button and help support the team
Wear our specially prepared banner
Share your opinion about my work and write some feedback in our threads.
Advertise our work to your friends, family, anyone who owns this device.
Rate our threads with 5 stars.
We appreciate all the support you give us, but we don't expect anything
Click to expand...
Click to collapse
II. Sharing
XDA-Developers.com is all about sharing. If you would like to use any part of our work, please feel free to do so but remember to do the following beforehand:
Inform - Please send us a PM or email telling us
Permission - Please, if you do not have permission from us, don't use it. Most of the time, we will allow you to, but if you don't get our permission first, we will report.
Credits - No one wants their work stolen. Please remember to give proper credits when using our work.
Click to expand...
Click to collapse
:
III. Support
If you have any issues or questions, please feel free to post them in the our threads. However, because all of us have social lives outside of XDA, your questions may not always be answered right away. Members who are more experienced in our work, please help out the ones who don't.
If you want to get the fastest and the best answer - ask the question in our threads instead of PM'ing us. Chances are, other users will be able to help you when Team Members don't have the time to.
Click to expand...
Click to collapse
IV. Updates
We are a busy team! Every Team Member has lives outside of XDA. You cannot expect us to sit in front of the computer all day and develop Android. Please do not ask for ETA's. The update will come when we release it. Sometimes, there is a good reason for why we have not released an update in a while. Please be patient with us, we will do as we promise. Updates will come.
Click to expand...
Click to collapse
V. Responsibilities
We are not responsible for your device! We do not guarantee that everything will work the way it's supposed to. Not every device is created equal, what might work on our devices may not work on yours or vice versa. Please be a responsible person when it comes to flashing. This is a mature site, don't act immaturely when your device becomes problematic. If you cry and blame us for "destroying" your device, we will laugh at you. Your device is your responsibility, act like it.
Thanks for choosing Team Horizon, we hope you enjoy our works as much as we enjoy working with them.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
MOD Section
This is going to be a section where I post add ons for this ROM. Enjoy!
Click to expand...
Click to collapse
<---------http://dl.dropbox.com/u/44672998/supporter.png
My Dev-Host Account With All The Add On Downloads!
http://goo.gl/4rscI
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Invered Gapps! 4.2.1
CLICK ME
Click to expand...
Click to collapse
:highfive:
HELP!
Please Help Contribute To This Project. Either Post Question With Answer and I Will Add To OP or PM Me The Stoofz
:highfive:
Great idea Tory, You have been a real asset to the team, thanks for all you do.
Sent from my SCH-I535 using Tapatalk 2
I'm transferring this topic from the main page. I'm running 1.5 for Toro and had issues with WiFi tether. I dirty flashed from the prior version. I was running Franco 356. I wiped and restored 12-22 then dirty flashed again to 1.5. This time I'm still running the included kernel. I tested WiFi tether and it seems to work. Thusly, I think the issues may be related to Franco 356. Anybody got WiFi tether working with Franco?
Sent from my Galaxy Nexus using Tapatalk 2
crispy1 said:
I'm transferring this topic from the main page. I'm running 1.5 for Toro and had issues with WiFi tether. I dirty flashed from the prior version. I was running Franco 356. I wiped and restored 12-22 then dirty flashed again to 1.5. This time I'm still running the included kernel. I tested WiFi tether and it seems to work. Thusly, I think the issues may be related to Franco 356. Anybody got WiFi tether working with Franco?
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I am on latest franco and fixing to test wifi tether. hold (on gsm tho)
crispy1 said:
I'm transferring this topic from the main page. I'm running 1.5 for Toro and had issues with WiFi tether. I dirty flashed from the prior version. I was running Franco 356. I wiped and restored 12-22 then dirty flashed again to 1.5. This time I'm still running the included kernel. I tested WiFi tether and it seems to work. Thusly, I think the issues may be related to Franco 356. Anybody got WiFi tether working with Franco?
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I was able to connect wifi tether and usb tether with the latest franco. Keep in mind that I ALWAYS WIPE before flashing any updates to iron out those pesky little bugs.
pr0xy mAn1Ac said:
I was able to connect wifi tether and usb tether with the latest franco. Keep in mind that I ALWAYS WIPE before flashing any updates to iron out those pesky little bugs.
Click to expand...
Click to collapse
OK, good to know. I'll flash Franco and if it is still broken, I'll clean flash 1.5 followed by an update to Franco.
Sent from my Galaxy Nexus using Tapatalk 2
crispy1 said:
OK, good to know. I'll flash Franco and if it is still broken, I'll clean flash 1.5 followed by an update to Franco.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Please keep us posted on your progress. let me know if I can help.
Quick Unlock
Is quick unlock working? It has not worked for me for a while, but I saw one person say it works. I have done a full wipe with each version. Thanks!
pr0xy mAn1Ac said:
Please keep us posted on your progress. let me know if I can help.
Click to expand...
Click to collapse
I reflashed clean and am still unable to connect. Still on default kernel. I can see the network but I cannot connect even without security. Tried both an iPad and an Android tablet. Blue tooth tether works but that us too slow. I'm out of options. This is a show stopper for me.
Sent from my Galaxy Nexus using Tapatalk 2
crispy1 said:
I reflashed clean and am still unable to connect. Still on default kernel. I can see the network but I cannot connect even without security. Tried both an iPad and an Android tablet. Blue tooth tether works but that us too slow. I'm out of options. This is a show stopper for me.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I have to have tethering. Flashed back to CNA 3.8 and I got it back. May need to hang on to 4.1.2 a bit longer.
Sent from my iPad using Tapatalk HD
crispy1 said:
I have to have tethering. Flashed back to CNA 3.8 and I got it back. May need to hang on to 4.1.2 a bit longer.
Sent from my iPad using Tapatalk HD
Click to expand...
Click to collapse
edited
10char
Navigation bar opacity
I love the whole ROM, been using it for a while. I was very excited to see a translucent menu bar option in the 12/30/12 release. However im not sure of its functioning properly. On the home screen the nav bar is translucent however in any app its a solid black background again. When I zoom using accessibility feature (triple tap) the nave bar goes back to being all but invisible. Is this transparent effect only supposed to do what it does on my case? Thanks man, keep up the good work
Just a quick question pr0xy ... Do I have to wipe data in order to install inverted gapps or can i dirty flash over the 20121212 package? Thx in advance!
Just flash the gapps brother no wiping needed. Enjoy.
Sent from my Galaxy Nexus using Xparent ICS Tapatalk 2
Ok, another stupid question inc! :/ Proxy - do you know of any place where I could get "Black Facebook" to match the inverted gapps ? Since I kinda prefer it over the stock white FB app ... I could find only some lower versions which are slow and buggy, so ... Thx in advance
Doomhamma said:
Ok, another stupid question inc! :/ Proxy - do you know of any place where I could get "Black Facebook" to match the inverted gapps ? Since I kinda prefer it over the stock white FB app ... I could find only some lower versions which are slow and buggy, so ... Thx in advance
Click to expand...
Click to collapse
It is included with the inverted gapps. Enjoy.
Sent from my Galaxy Nexus using Xparent ICS Tapatalk 2
pr0xy mAn1Ac said:
It is included with the inverted gapps. Enjoy.
Sent from my Galaxy Nexus using Xparent ICS Tapatalk 2
Click to expand...
Click to collapse
No it's not ... That's why I asked
*DUMB NEWBIE QUESTION*
how to flash this rom ?
just tried to flash the rom using TWRP, but it stucks at bootlogo.
now restored the rom and N4 is working normal.
any solution ?
thx in advance.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Opening this thread in order for the users to post their issues here instead of the development section or CM10 bug report thread.
This thread refers to discussions/bug reports for CM10.1 (Android 4.2.2) released by arco68 here.
As usual, it would be best to keep an organized fashion of your bug reports for the developers to easily spot them and maybe fix them.
On behalf of the SGW users, big thanks to arco68 and the CyanogenMod Team!
Great job, guys!
Note: bugs concerning custom kernels are to be reported into the corresponding threads! Please, don't post them here.
In order to avoid posting bugs that are not actually bugs, please, make sure you follow this little tutorial before upgrading/installing CM10.1:
For installation, first, make sure you got CM10.1 ROM and the correct Gapps on your External SD Card. Both can be found in the Mirrors section below.
After that, enter CWM and:
select "wipe data / factory reset"
go to "mounts & storage" and format /system. This is extremely important!
under the same menu, format /sdcard (be careful NOT to format /external_sd by mistake)*
install CM10.1 (from the external sd)
install Gapps for JB+ (from the external sd)
reboot your phone
* On newer CWM Recovery versions, you might find the internal memory mounted as /sdcard0 and the external one as /sdcard1. For this case, make sure you don't format /sdcard1 by mistake.
Please, note that every step of this tutorial is mandatory!
For apps backup & restore using Go Backup Pro, please, follow the tutorial below, step by step:
For Backup
1. Make sure you have an external SD card inserted
2. Download Go Backup Pro (of course)
3. Enter the app and go to Settings (from the 3 vertical dots on the right side of the screen)
4. Make sure that for the Backup Path, you have selected External storage (if I'm not mistaken, this is the default setting anyway, but it's good to confirm, just in case)
5. Go back and go to New/Restore Backup section
6. Click Batch Backup (bottom left of the screen)
7. Select what you want to backup*
*Tip: to select/unselect all User Data, all System Settings etc, you have a checkbox on the same row with the actual User Data or System Settings texts.
8. Click Start Backup
9. Wait for it to finish and click Finish
For Restore
1. Assuming that by now you already have a backup to restore, go to New/Restore Backup section again
2. Click Batch Restore
3. Now, pay attention to the User Applications section of that screen. Right underneath the User Application text, you have an option that says "Restore Content".
4. Click on "APK + Data" from Restore Content and select "Restore app only". Now the Restore Content section will show only APK.
5. Uncheck the apps for which you need app data. Those apps won't be restored, for now. Please, go on with the tutorial.
5. Click Start Restore
6. Wait for it to finish and click Finish
7. Now that we chose what apps we want to be restored without app data, let's go back and enter New/Restore Backup section (yeah, again ).
8. Click Batch Restore
9. Uncheck everything*.
*Tip: to select/unselect all User Data, all System Settings etc, you have a checkbox on the same row with the actual User Data or System Settings texts
10. Now, pay attention to the User Applications section of that screen. Right underneath the User Application text, you have an option that says "Restore Content".
11. Click on "APK" from Restore Content and select "Restore app and data". Now the Restore Content section will show APK+ Data.
10. Check only the apps for which you DO need app data to be restored (the ones that were left unrestored from last time ).
11. Click Start Restore
12. Wait for it to finish and click Finish.
How to post a bug report:
Copy-paste the lines below in your post, filling up the required information:
HTML:
[B]Version:[/B] CM10.1 - Beta 4
[B]App/Game/Subject:[/B] WRITE HERE SUBJECT
[B]Bug title:[/B] WRITE HERE BUG TITLE
[B]Probability of occurrence:[/B] WRITE HERE "LOW/MEDIUM/HIGH" (depending on how often the bug occurs)
[B]Description:[/B] WRITE HERE DESCRIPTION
Mirrors:
CM10.1 Beta 4 20140509 (MEGA): here
md5sum: c7e9114d760c0e924919b1be95425048
Gapps 20140507 JB+ (MEGA): here
md5sum: b0d6e6b62cb9149aea5de2531026f33a
Changelog Gapps:
Changelog Gapps 20140507:
* Google Search v3.4.16.1149292.arm
* Google Maps v8.0.0
* Hangouts v2.1.100(1151589-30)
* Google Play Services v4.3.25(1117461-034)
* Google Play Store v4.6.17
* Google Text-to-Speech Engine v3.0.11.1070024
Changelog Gapps 20140209:
* Google Maps v7.6.0
* Hangouts v2.0.303 (1004807-30)
* Google Play Services v4.1.32 (978161-34)
* Google Search v3.2.17.1009776.arm
Changelog Gapps 20131214:
* Google Maps v7.5.0
* Gmail v4.7.1 (946962)
* Google Play Services v4.0.34 (924341-34)
* Google Play Store v4.5.10
* Google Search v3.1.24.941712.arm
* Hangouts v2.0.217 (944332-30)
* Talkback Service v3.5.1
* Google Text-to-speech v2.4.3.864779
Changelog Gapps 20131001:
* Gmail v4.6 (836823)
* Google Search v2.8.8.849369.arm
* Google Hangouts v1.2.018 (849105-30)
Changelog Gapps 20130917:
* Google Maps v7.2.0
Changelog Gapps 20130825:
* Google Search v2.7.9.789824.arm
* Google Hangouts v1.1.2.778356
Changelog Gapps 20130817:
- Google+ (can be redownloaded from Google Play Store, if needed)
* Google Play Store v4.3.11
* Google Maps v7.1.0
Changelog Gapps 20130814:
+ Google Hangouts v1.1.1.753199**
+ Google Maps v7.0.2**
* Hangouts libs
* Google Play Services v3.2.25 (761454-34)
* Google Play Store v4.3.10
+ Google+ v4.0.2.48854689
**Re-added to the new base package from goo.im
Changelog Gapps 20130726:
* Google Hangouts v1.1.1.753199
Changelog Gapps 20130718:
* Google Play Services v3.1.59 (736673-34)
* Google Maps v7.0.2
Changelog Gapps 20130715:
* Google Talkback Service v3.4.0
Changelog Gapps 20130712:
* Google Maps v7.0.1
Changelog Gapps 20130630:
* fixed Hangouts video calling FC
Changelog Gapps 20130628:
* Google Search v2.6.7.721924.arm
* Gmail v4.5.2-714156
Changelog Gapps 20130624:
+ Google Street View (Google Maps addon) v1.8.1.2
+ minor changes
Changelog Gapps 20130612:
+ Gmail v4.5-694836 (the new, beautiful Gmail app)
+ Google Maps v6.14.4
* Google Play Services v3.1.36 (669520-34)
* Google Play Store v4.1.6 (the new Google Play Store)
* Google Search v2.5.8.675703 (the new Google Search with Google Now)
* Google Hangouts (ex Google Talk) v1.0.2.695251
* Google Talkback Service v3.3.2
+ means that the app was newly added
* means that the app was upgraded by replacing it with the newer version
- means that the app was removed
To enable Developer Options: go to Settings -> About Phone and tap the Build Number 7 times to enable Developer Options.
To enable Advanced Reboot options: go to Settings -> Developer Options and check the Advanced Reboot box.
Please, see the screens below for more information.
To swap memories (internal with external SD Cards) in Alpha 3 and above without modifying the vold.fstab file, go to /System/build.prop using any File Explorer with root privileges (recommended X-Plore) and change from 0 to 1 in the code below*:
Before
Code:
# Change to 1 for swapping SD cards
persist.sys.vold.switchexternal=[COLOR="Blue"]0[/COLOR]
After
Code:
# Change to 1 for swapping SD cards
persist.sys.vold.switchexternal=[COLOR="Red"]1[/COLOR]
*Thanks to Madridii for this.
Videos
Bugs reported/still occurring so far (Beta 3):
1. Camera/Gallery (To be confirmed in Beta 4)
Camera/Gallery app becomes unresponsive when locking&unlocking the screen multiple times (about 4 times in my tests). After that, if the user chooses to force close the Gallery app, when entering the Camera app again, he will be prompted with the following error message: "Can't connect to the camera".
Please, see the attached screenshot and the log below for more info.
Code:
[ 08-05 15:13:30.010 441: 456 W/ActivityManager ]
Activity idle timeout for ActivityRecord{41225ca0 u0 com.android.gallery3d/com.android.camera.CameraLauncher}
[ 08-05 15:13:31.521 441: 503 I/InputDispatcher ]
Application is not responding: AppWindowToken{414fc260 token=Token{41691380 ActivityRecord{41225ca0 u0 com.android.gallery3d/com.android.camera.CameraLauncher}}} - Window{4122f110 u0 com.android.gallery3d/com.android.camera.CameraLauncher}. It has been 5003.1ms since event, 5001.2ms since wait started. Reason: Waiting because the focused window has not finished processing the input events that were previously delivered to it.
[ 08-05 15:13:31.531 441: 503 I/WindowManager ]
Input event dispatching timed out sending to com.android.gallery3d/com.android.camera.CameraLauncher
[ 08-05 15:13:31.621 441: 503 I/Process ]
Sending signal. PID: 5350 SIG: 3
[ 08-05 15:13:31.621 5350: 5355 I/dalvikvm ]
threadid=3: reacting to signal 3
[ 08-05 15:13:31.701 5350: 5355 I/dalvikvm ]
Wrote stack traces to '/data/anr/traces.txt'
[ 08-05 15:13:31.701 441: 503 I/Process ]
Sending signal. PID: 441 SIG: 3
[ 08-05 15:13:31.701 441: 444 I/dalvikvm ]
threadid=3: reacting to signal 3
[ 08-05 15:13:31.882 143: 5647 E/CAM_FD ]
cam_conf: In config thread
[ 08-05 15:13:31.992 441: 503 I/Process ]
Sending signal. PID: 553 SIG: 3
[ 08-05 15:13:31.992 553: 560 I/dalvikvm ]
threadid=3: reacting to signal 3
[ 08-05 15:13:32.002 441: 444 I/dalvikvm ]
Wrote stack traces to '/data/anr/traces.txt'
[ 08-05 15:13:32.002 441: 503 I/Process ]
Sending signal. PID: 656 SIG: 3
[ 08-05 15:13:32.002 656: 670 I/dalvikvm ]
threadid=3: reacting to signal 3
[ 08-05 15:13:32.042 553: 560 I/dalvikvm ]
Wrote stack traces to '/data/anr/traces.txt'
[ 08-05 15:13:32.092 656: 670 I/dalvikvm ]
Wrote stack traces to '/data/anr/traces.txt'
[ 08-05 15:13:32.212 441: 443 D/dalvikvm ]
GC_CONCURRENT freed 1916K, 21% free 10090K/12716K, paused 4ms+7ms, total 97ms
[ 08-05 15:13:32.212 441: 503 D/dalvikvm ]
WAIT_FOR_CONCURRENT_GC blocked 65ms
[ 08-05 15:13:32.422 441: 503 D/dalvikvm ]
GC_EXPLICIT freed 777K, 21% free 10132K/12716K, paused 4ms+5ms, total 91ms
[ 08-05 15:13:32.632 441: 1243 E/Sensors ]
type : 0, deley : 66667000
[ 08-05 15:13:32.632 441: 1242 E/Sensors ]
type : 0, deley : 20000000
[ 08-05 15:13:33.003 441: 503 I/Process ]
Sending signal. PID: 1051 SIG: 3
[ 08-05 15:13:33.003 1051: 1056 I/dalvikvm ]
threadid=3: reacting to signal 3
[ 08-05 15:13:33.103 1051: 1056 I/dalvikvm ]
Wrote stack traces to '/data/anr/traces.txt'
[ 08-05 15:13:33.113 441: 503 E/ActivityManager ]
ANR in com.android.gallery3d (com.android.gallery3d/com.android.camera.CameraLauncher)
Reason: keyDispatchingTimedOut
After rendering the Panorama shots, when the camera returns to the Panorama Mode for the user to take another panoramic shot, the camera preview is flickering. This happens only if the Auto-Rotate function is ON and the screen in Portrait mode. With the Auto-Rotate OFF, this bug does not occur.
Please, see the attached screenshot for, hopefully, more info on this.
Camera/Gallery app becomes unresponsive when taking a picture, sliding left to see the picture and tapping on it to see it in "full screen" then locking the screen for about 10 seconds. After that, if the user chooses to force close the Gallery app, when entering the Camera app again, the user will be prompted with the following error message: "Can't connect to the camera". Please, see the attached screenshot for more info.
Setting the light exposure to 4 or -4, the icon on the bottom right doesn't show any number (as it does for any other value) and if slide to the left to enter the Gallery and come back to camera app, the icon appears distorted. This happens only for value "4" or "-4". Workaround: switch to any of the other values and then back to 4.
Please, see the attached screenshot for more info.
Zooming in/out doesn't work in video mode. Nothing happens when using two fingers to zoom in or out. No change in the actual image.
Please, see the log below for zooming issue.
Code:
E/QualcommCameraHardware(148): Failed to get maximum zoom value...setting max zoom to zero
2. Text cut off in photo editor (To be confirmed in Beta 4)
The text for the "straighten" option is missing the first 2-3 letters in the default photo editor (please, see the attached screenshot for more info). The options section from that screen cannot be slid more to the left to see the rest of the word.
This happens most likely because the spaces between the icons (options) from the top row of editing options don't adjust to the new screen orientation (Portrait). They look ok in Landscape mode, but it seems that the space between the icons from that row is kept the same no matter of the screen orientation, leading to some of the options not to be completely visible.
3. cLock widget not properly resizing in landscape mode (To be confirmed in Beta 4)
cLock widget does not properly resize when the launcher is set to Landscape mode (launcher auto-rotate option is ON). The widget is cut off (please, see the attached screenshot for more info). The widget looks good in Portrait mode. But when turning the screen to landscape mode, it's cut.
4. Phone encryption (To be confirmed in Beta 4)
Enabling encryption in the Security Settings will make the PIN code for the SIM card (assuming it's set to be requested) not to be requested anymore, thus making the "phone" part of the device unusable. No calls (voice or data), no SMS, no MMS can be sent or received. Workaround: make a nandroid backup before encrypting and restore it afterwards.
If the user turns off the SIM card PIN code request before performing the encryption, after it's finished, the APNs previously set will disappear and there won't be any way to re-add them manually, thus making the data connection unusable. He will be able to make voice calls and send SMS though.
After the encryption, if SIM PIN request is OFF, in the notification drawer and quicksettings panel, the user will be informed that he has no service (please, see the attached screenshots for more info) although, by going into Settings -> About Phone -> Status, he will see that the network is successfully recognized and there is definitely some service. (please, see the attached screenshot for more info on this too).
5. Random reboots after recently closing a phone call (To be confirmed in Beta 4)
From time to time, but apparently more often after recently (not immediately after) closing an incoming voice call, the phone reboots.
This does not happen with kernel 3.4.56 but it does happen with 3.4.57 so it might be because of that reverted commit.
6. Some third party camera apps don't work properly in CyanogenMod. (To be confirmed in Beta 4)
Some third party camera apps don't work with any CM version from CM9 to CM10.1. For example, Camera 360 Ultimate v4.5 works ok on stock Android 4.1.2 and 4.2.2 (tested on Nexus devices) but doesn't work properly with any CyanogenMod version. After taking a picture, the camera preview gets stuck. No change in preview when tilting the phone.
Please, see the log below from the moment when taking a picture with Camera 360. Maybe it helps solve this problem.
Code:
W/System.err( 2142): at vStudio.Android.Camera360.photo.EffectInfoFactory.getParentParam(EffectInfoFactory.java:1433)
W/System.err( 2142): at vStudio.Android.Camera360.photo.EffectInfoFactory.search(EffectInfoFactory.java:1303)
W/System.err( 2142): at vStudio.Android.Camera360.camera.logics.ModeAbstract.setEffect(ModeAbstract.java:106)
W/System.err( 2142): at vStudio.Android.Camera360.camera.logics.ModeNormal.onCameraStartPreview(ModeNormal.java:370)
W/System.err( 2142): at vStudio.Android.Camera360.camera.CameraBaseActivity.onCreate(CameraBaseActivity.java:749)
W/System.err( 2142): at vStudio.Android.Camera360.camera.CameraMain.onCreate(CameraMain.java:551)
V/QualcommCameraHardware( 143): As Auto Focus is not in progress, Cancel Auto Focus is ignored
V/QualcommCameraHardware( 143): cancelAutoFocusInternal X: 0
I/QualcommCameraHardware( 143): stopPreviewInternal X: 0
V/QualcommCameraHardware( 143): initRawSnapshot E
I/QualcommCameraHardware( 143): runframethread: waiting for preview thread to complete.
V/QualcommCameraHardware( 143): initRawSnapshot X
V/QualcommCameraHardware( 143): takePicture: X
I/ShotSingle( 143): ShotSingle::takePicture end
I/CameraHAL( 143): camera_take_picture--- rv 0
I/QualcommCameraHardware( 143): initPreview: old preview thread completed.
QualcommCameraHardware( 143): destroying MemPool record
camera_set_preview_window---: window is NULL
V/QualcommCameraHardware( 143): Overlay object NULL. returning
I/CameraClient( 143): Destroying camera 0
I/CameraHAL( 143): camera_device_close+++: device 0x1f68650
I/SecCameraHardwareInterface( 143): SecCameraHardwareInterface destroyed: pid=143
I/ShotSingle( 143): ShotSingle destroyed: pid=143
I/ShotCommon( 143): ShotCommon destroyed: pid=143
No JNI_OnLoad found in /data/app-lib/vStudio.Android.Camera360-1/libmp3lame.so
I/ActivityManager( 430): Process vStudio.Android.Camera360 (pid 2142) has died.
7. USB tethering does not work
8. USB OTG does not work. (To be confirmed in Beta 4)
XDA:DevDB Information
CyanogenMod 10.1 - Beta 4 - Discussion thread / Bug report, ROM for the Samsung Galaxy W I8150
Contributors
arsradu
ROM OS Version: 4.2.x Jelly Bean
Version Information
Status: Testing
Created 2013-09-29
Last Updated 2014-05-19
charge
Opening off the phone while charging for no reason
sorry my bad english:angel:
I got help from google translate:victory:
Re: CyanogenMod 10.1 - Discussion thread / Bug report
Why blackcat using old xistance kernel? And is he'd using latest bcmdhd wifi driver by arco or just old one? Thanks
-Sent from 4.2.2 powered i8150-
hotheabilly said:
Why blackcat using old xistance kernel? And is he'd using latest bcmdhd wifi driver by arco or just old one? Thanks
-Sent from 4.2.2 powered i8150-
Click to expand...
Click to collapse
arco new bcmdhd wifi driver dont working
The phone had been rebooting often.
Happened occasionally it rebooted even using camera and browsing the net.
I installed this rom. But sometimes, phone is locking and freezing. I am obliged to reboot.
(Sorry for my bad English)
Please rename this rom.
I'm writing this post because I read the whole thread in the Development section and it seems to me that calling this rom CM 10.1 is a bit misleading.
Sure blackcat67 may have done a bunch of work to get this out, but I don't think he has the rights to call it CM.
So I'm asking @blackcat67...PLEASE RENAME YOUR ROM.
Call it something like... [4.2.2][Blackcat]...as Xistance did for his... [4.2.1][Rootbox Alpha 1] ...but please don't call it CyanogenMod.
arsradu said:
Opening this thread in order for the people to post their issues here instead of the development section or CM10 bug report thread.
This thread refers to discussions/bug reports for CyanogenMod 10.1 posted today by blackcat67 here.
As usual it would be best to keep an organized fashion of your bug reports for the developers to easily spot them and maybe fix them.
For that, please, copy-paste this in your posts, editing it accordingly:
HTML:
[B]Version:[/B] CM10.1 - Alpha 1
[B]App/Game/Subject:[/B] WRITE HERE APPNAME
[B]Bug title:[/B] WRITE HERE BUG TITLE
[B]Description:[/B] WRITE HERE BUG DESCRIPTION
Click to expand...
Click to collapse
I Will wait for Arco's or Camcory's version:crying:
Re: CyanogenMod 10.1 - Discussion thread / Bug report
Bernedeboi said:
I Will wait for Arco's or Camcory's version:crying:
Click to expand...
Click to collapse
Do we need to close this thread?
Sent from my GT-I8150 using xda app-developers app
ipromeh said:
Do we need to close this thread?
Sent from my GT-I8150 using xda app-developers app
Click to expand...
Click to collapse
I don't know, man.
I would keep it open just in case someone will post another CM10.1.
There is no source thread to discuss for now, that's true. But maybe there will be soon. So, I don't know. I'll leave this decision to mods.
From my point of view, I just want a CM10.1/AOSP 4.2.2 soon, and it's not really important who posts it. So...I don't know. You decide.
Re: CyanogenMod 10.1 - Discussion thread / Bug report
arsradu said:
I don't know, man.
I would keep it open just in case someone will post another CM10.1.
There is no source thread to discuss for now, that's true. But maybe there will be soon. So, I don't know. I'll leave this decision to mods.
From my point of view, I just want a CM10.1/AOSP 4.2.2 soon, and it's not really important who posts it. So...I don't know. You decide.
Click to expand...
Click to collapse
Everybody want that, just patiently waiting. . .
-Sent from 4.2.2 powered i8150-
ipromeh said:
Do we need to close this thread?
Sent from my GT-I8150 using xda app-developers app
Click to expand...
Click to collapse
no, we don't have to closed this thread, The Real Devs will post their CM10.1 someday,
we just need to be patient
Re: CyanogenMod 10.1 - Discussion thread / Bug report
arsradu said:
Version: CM10.1 - Alpha 1
Click to expand...
Click to collapse
Hmmm.... How about deleting the CM10.1 version, other users would think that there IS a CM10.1 ROM for the W but its already deleted...
Ehndroix JB with S3 Style Pack :thumbup:
TiTAN-O-One said:
Hmmm.... How about deleting the CM10.1 version, other users would think that there IS a CM10.1 ROM for the W but its already deleted...
Ehndroix JB with S3 Style Pack :thumbup:
Click to expand...
Click to collapse
OK. I edited the OP so that it doesn't contain any link or info related to that post.
Re: CyanogenMod 10.1 - Discussion thread / Bug report
Its time reopen this thread.
Arco has just released CM10.1
Sent from my GT-I8150 using xda premium
Re: CyanogenMod 10.1 - Discussion thread / Bug report
Now we can continue to discuss about cm10.1 here
Sent from my GT-I8150 using xda premium
Re: CyanogenMod 10.1 - Discussion thread / Bug report
Welcome guys to CM10.1 *unbelievable happy face*
---------- Post added at 07:27 PM ---------- Previous post was at 07:26 PM ----------
I'll do a Pristine Flash tomorrow and report here.
Re: CyanogenMod 10.1 - Discussion thread / Bug report
Me too. Feel very happy and excited. I dont know how to express my happiness. Sir is really amazing. Thanks sir
Sent from my GT-I8150 using xda premium
I will flash it now :fingers-crossed:
downloaded
Edit: flashed , it is the smoothest rom ever ... It is the best from the best developer
fo the swap go here
http://forum.xda-developers.com/showpost.php?p=39749848&postcount=22
Hey guys I'm fairly new to rooting but I finally got lineage os on my phone at first I thought the ROM was great until I saw it would reboot automatically. I installed a custom kernel to see of it makes it worse or better, then I compared lineage kernel and it still reboots. So it either has to be the apps, or the ROM itself. What do you guys think
Thanks
Does anyone who have lineage os on their one plus 2 experience this too or is it just me
Also even with lineage os my battery said that lineage os and it's kernel took 20% and 10% of the whole battery and it was in the background... What gives
The other kernel I had was the boeffla in case someone is wondering. It is still in beta but my phone was crashing without so I don't think that's the main reason why it's rebooting
With the 20170313 nightly on my Mi4, I have the same problem, yesterday it was several times in the same day
Jsmoov5 said:
Does anyone who have lineage os on their one plus 2 experience this too or is it just me
Also even with lineage os my battery said that lineage os and it's kernel took 20% and 10% of the whole battery and it was in the background... What gives
The other kernel I had was the boeffla in case someone is wondering. It is still in beta but my phone was crashing without so I don't think that's the main reason why it's rebooting
Click to expand...
Click to collapse
I have the OnePlus 2 aswell, I have seen 7-8-9-14+++ random reboots today
With Franco kernel I'm down to 1-2 random reboots each day.
hey, i have the OP2 as well and my phone randomly reboots but 95 % of the time the reboots happen while my phone isn't awake. Also, the reboots tend to happen in sequences: i can get like up to 10 of them in 1 hour and none at another moment of the day... pls help if you know anyhing. ( im using the default kernel i guess. Should I try to install another one ?
---------- Post added at 08:18 PM ---------- Previous post was at 08:01 PM ----------
krugm0f0 said:
With Franco kernel I'm down to 1-2 random reboots each day.
Click to expand...
Click to collapse
Imma try it then, are there any particular settings wich make it better ?
Current version seems more stable : no reboot since the update
Need Help
Hey guys! I built Lineage 14.1 for NX510J by using the source code. But it didn't boot. So I used the boot.img from another LOS-14.1 for the NX510J which can work normally . Although my phone can boot, it rebooted every time when entried into setup wizard. Can someone help me fix it? Any suggestion will be appreciated！
Same here. My phone (Samsung S3) random reboots. Any suggestion?
It looks like there's an open issue submitted on LineageOS JIRA regarding random reboot.
https://jira.lineageos.org/plugins/servlet/mobile#issue/BUGBASH-667
***Please Note: As always, I welcome any member to help with further valuable information/clarification for any of my posts.
Sent via Communicator [d2vzw] from the Bridge of the U.S.S. Enterprise.
Me too: LG G3 D855
Hi All,
I'm also seeing reboots.
Sometimes I go for weeks with no reboot. Other times I get several in an hour. Lately I've even seen them immediately after a reboot, when I unlock the screen for the first time!
I've had this for as long as I can remember, but just got around to mentioning it.
In other respects - thanks guys for the great achievement of LineageOS!
BTW: the last time this happened (this morning) I was running last week's nightly:
lineage-14.1-20171030-nightly-d855-signed.zip
Martin
Random reboots have been a "feature" of cm/Los based roms for years. Which was never fixed. That is why dev teams stopped using them as a base.
zelendel said:
Random reboots have been a "feature" of cm/Los based roms for years. Which was never fixed. That is why dev teams stopped using them as a base.
Click to expand...
Click to collapse
So you are saying that lineageos is inherently unstable and always will be?
What do the development teams use as a base now?
robjg63 said:
So you are saying that lineageos is inherently unstable and always will be?
What do the development teams use as a base now?
Click to expand...
Click to collapse
Unless they go back and fix it (tons of work) then yes. Many started over with pure aosp back in 5.0 - 6.0 so many have their own bases. Some also use caf bases for snapdragon based devices.
So I have a Galaxy note 2 that I recently flashed lineageos on. It's actually been going quite well - but I have noticed random reboots from time to time. Sometimes its ok for a day or two - and other times it might do it a couple of times in a day.
If there are some other packages that have a different base (than Lineageos) is it ok for you to mention them so I can do a bit of research?
I think, the reboot issue is device specific. My moto e (condor) only reboots, when I use the power button for lock & wake. Now I let gravity screen app do that and there are no reboots.
robjg63 said:
So I have a Galaxy note 2 that I recently flashed lineageos on. It's actually been going quite well - but I have noticed random reboots from time to time. Sometimes its ok for a day or two - and other times it might do it a couple of times in a day.
If there are some other packages that have a different base (than Lineageos) is it ok for you to mention them so I can do a bit of research?
Click to expand...
Click to collapse
I am not sure about what is avaiable for that device. Samsung devices were not picked up by all the teams as they were difficult to get working without issues. I would try maybe SLim roms. They are AOSP based. But to be honest. If I had a samsung I would use a stock based rom (even if it is older) this way I dont lose any of samsungs features
kurtn said:
I think, the reboot issue is device specific. My moto e (condor) only reboots, when I use the power button for lock & wake. Now I let gravity screen app do that and there are no reboots.
Click to expand...
Click to collapse
Thats the thing, the causes are different for different devices. This is why it would be tons of work. They would have to start over from scratch. With a pure base and make their changes bit by bit. Testing as they go (which didnt happen alot when it was CM. Depending on who pushed the commit it would just be merged without testing)
zelendel said:
Unless they go back and fix it (tons of work) then yes. Many started over with pure aosp back in 5.0 - 6.0 so many have their own bases. Some also use caf bases for snapdragon based devices.
Click to expand...
Click to collapse
So, could you name a few ASOP ROMs that *don't* have random reboots? Please?
mcatkins said:
So, could you name a few ASOP ROMs that *don't* have random reboots? Please?
Click to expand...
Click to collapse
The only one I can name is Slim roms. Most of the other teams I use have left xda and dont allow their builds here. I personally use Dirty Unicorns but again they are not on XDA.
This also depends on your device. If you have an older device then you may only be stuck with CM/Los as most aosp teams only support devices that someone on the team owns. This way it can be tested in real time and not just "the code should work on every device" frame of mind.
Random reboots on i9505 with lineage os 14.1
My dmesg.log tail reads:
<6>[ 29.992553] synaptics_rmi4_i2c 3-0020: [0][R] 0x00 M[7] V[5c]
<6>[ 36.075195] [SSP]: debug_work_func(1) - Sensor state: 0x3fff, RC: 0, MS: 0
<6>[ 39.306854] sec-fuelgauge 11-0036: 0x02(0xb6), 0x03(0xf0), 0x04(0x3a), 0x05(0xdf), 0x06(0x00), 0x07(0x00), 0x08(0x00), 0x09(0x12), 0x0a(0x00), 0x0b(0x00), 0x0c(0x6c), 0x0d(0x1e),
<6>[ 39.310455] sec-fuelgauge 11-0036: 0x14(0x00), 0x15(0xff), 0x16(0xfe), 0x17(0x42), 0x18(0x7d), 0x19(0x00), 0x1a(0x01), 0x1b(0xff),
<6>[ 39.310455] sec-fuelgauge 11-0036: sec_fg_get_atomic_capacity: old : 29, current : 29
<6>[ 39.310974] max77693_get_input_current: CHG_CNFG_09(0x17)
<6>[ 39.322479] sec-battery sec-battery: sec_bat_get_battery_info:Vnow(3658mV),Inow(460mA),SOC(29%),Tbat(361)
<6>[ 39.322509] sec-battery sec-battery: sec_bat_monitor_work: Status(Discharging), mode(None), Health(Good), Cable(1), siop_level(100)
<6>[ 39.323516] max77693-muic max77693-muic: func:max77693_muic_monitor_status, ST1:0x3f, ST2:0x0 CABLE:0
<6>[ 47.075164] [SSP]: debug_work_func(1) - Sensor state: 0x3fff, RC: 0, MS: 0
<6>[ 48.058441] synaptics_rmi4_i2c 3-0020: [0][P] 0x01
<6>[ 48.128845] synaptics_rmi4_i2c 3-0020: [0][R] 0x00 M[5] V[5c]
<6>[ 49.404785] synaptics_rmi4_i2c 3-0020: [0][P] 0x01
<6>[ 49.506958] synaptics_rmi4_i2c 3-0020: [0][R] 0x00 M[8] V[5c]
<6>[ 52.727386] synaptics_rmi4_i2c 3-0020: [0][P] 0x01
<6>[ 52.786834] synaptics_rmi4_i2c 3-0020: [0][R] 0x00 M[4] V[5c]
<6>[ 56.678344] synaptics_rmi4_i2c 3-0020: [0][P] 0x01
<6>[ 56.748291] synaptics_rmi4_i2c 3-0020: [0][R] 0x00 M[5] V[5c]
<6>[ 57.720306] synaptics_rmi4_i2c 3-0020: [0][P] 0x01
<6>[ 57.790283] synaptics_rmi4_i2c 3-0020: [0][R] 0x00 M[5] V[5c]
<6>[ 58.075164] [SSP]: debug_work_func(1) - Sensor state: 0x3fff, RC: 0, MS: 0
<6>[ 59.085662] synaptics_rmi4_i2c 3-0020: [0][P] 0x01
<6>[ 59.457580] synaptics_rmi4_i2c 3-0020: [0][R] 0x00 M[33] V[5c]
Do they suggest any anomaly?
I kind of suspect my China made extended battery isn't up to snuff
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
brought to you by the
Code:
/*
* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...).
* Please do some research if you have any concerns about features included in the products you find here before flashing it!
* YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
* Your warranty will be void if you tamper with any part of your device / software.
* Same statement for XDA.
*/
****
These builds are for all G4 models: official unlocked and UsU'd devices
****
UsU? http://bit.do/unlockg4
About /e//e/ is a mobile ecosystem (ROM + onlines services) that:
is open source
is pro-privacy
is compatible with most existing Android applications
cares about usability
is as far as possible freed from shackles by Google and OEMs
already exists!
It’s the alternative to the Apple/Google duopoly on the smartphone.
... so again and just to be clear: /e/ is not just a ROM, it is more a complete privacy ecosystem and consists of:
an installable mobile operating system for smartphones, which is forked from Android and strongly “ungoogled”
a set of sorted and improved default open source applications
various online services that are linked to the mobile operating system, such as: a meta search engine for the web, drive (with synchronization), mail, calendar, notes, tasks.
Features
Based on LineageOS so a very stable base
microG fully pre-installed with Signature Spoofing in restricted mode!
All features described on the /e/ page: What is e
full OTA update support
... you know that thing which informs you that a new update is there and where you just click to download + install
Difference from pure /e/ or: why are the builds CUSTOM?
F-Droid has been added (The OpenSource alternative store. First search for any apps here!)
Dozens of F-Droid repositories are pre-installed but NOT activated by default (activate them with just a finger tip! That's needed to ensure you only get what you want)
added PhoneSky a patched Google playstore allowing in-app-purchase on microG
added Lawnchair (latest from their TG group)
The above changes are the reasons why my builds are of the type "CUSTOM" and not "UNOFFICIAL".
This is according to the rules /e/ defined.
Known issuesKeep in mind that this is brand new stuff so it may (still) contain unknown issues!
So back up regularly and frequently!
Check the current issues at the github tracker (feel free to help, provide logs etc!)
If you find a bug not listed, follow the instructions here and provide me with the logs: FAQ #1
Requirements
Your device need to be unlocked either officially (h815 international or h811) or by UsU
Your bootloader stack should be on lastest MM version for your model. That is e.g. 20p for the H815 models or 20x for H811.
So.. NO SUPPORT ON LOWER bootloader stacks then the latest MM version for your model
... and NO SUPPORT for the BETA v29A as well!!
-> for your convenience I have created TWRP flashable files for that !!!! (click)
Of course ensure you just use files for your model, your ARB and UsU'd or not. If unsure ask.
in particular that means this thread is for:
F500, H810, H811, H812, H815 (official unlocked or UsU'd), H819 , LS991, US991, VS986
Latest TWRP - PREVIEW build: click or SHRP build: click
Do a full Nandroid backup before doing anything!
Installation
This single very first step is for UsU'd devices only (SKIP when you have an official unlocked model):
If you have ever flashed the UsU baseband package: Clean flash the modem partition from your backup in TWRP.
If you do not know if you ever flashed it simply re-flash your modem partition again and you can be sure. This can't do any harm.
If you have no backup:
- TWRP flashable MM modems (N will not work)
Ensure your bootloader is current! You will have issues if you are not on the latest bootloader stack. Read the above Requirements topic to find a link to TWRP flashable files.
Full clean install as described here (FAQ "#2") is highly recommended. DO NOT REPORT ISSUES when you have skipped that step!
Flash /e/
Optional (if you want root): Flash Magisk
Flashing OpenGapps ????? NO No no! you don't want that on a google-free phone! /e/ contains everything you need to live without Google! So flashing OpenGapps on /e/ is like using a bit more secure LOS but that's not the point of /e/. Either try without or go with LOS (imho).
Boot it (will take a bit on first boot!!! be patient!)
Enjoy the most easy way to have a privacy focused and google-free phone!
Download
Not available (yet) -> OFFICIAL builds (new install or re-install):
https://doc.e.foundation/search?q=LG G4
CUSTOM builds (new install or re-install):
http://leech.binbash.rocks:8008/e-os/a11
If you have /e/ installed already and just want to update to a newer release:
Android settings -> Updater (yes my CUSTOM builds have OTA support like OFFICIAL has!)
Note:
CUSTOM builds: Builds are updated as soon as possible. There is no fix build cycle.
Information pertaining to your device is displayed accordingly.
The current build is the latest for your device.
Changelogs
CUSTOM: posted in my Telegram build channel
OFFICIAL: https://gitlab.e.foundation/e/os/releases/-/releases
SupportOf course in this thread but also by Telegram. I have created a generic group for all stuff around Android : here
and another one if you want to keep up2date whenever I build something (TWRP, SHRP, LOS, /e/, ...): here
Credits
LineageOS (the base of /e/)
The /e/ foundation and all related devs making this experience possible!
The LG G Four team (aoleary, steadfasterX, Paul Tully)
and more..
Sources
build manifest
e OS source
Frequently Asked Questions (FAQ)
Q #01: I want to report an issue. What is the proper way to do so?
I'm glad that you are asking: before doing so check the KNOWN ISSUES topic in the OP and ofc the other FAQ's listed here!
If you encountered a kernel panic follow FAQ #6 in this post instead.
If you have issues with "just" the boot process follow FAQ #7 for a very easy way to grab the boot logs.
if you have an audio issue follow FAQ #10 instead.
If your issue is not listed there click here to proceed:
If your issue is not listed there follow the directions here briefly and I may can fix it:
logcat GUIDE
Ensure you have done a full CLEAN install before doing so (refer to FAQ #2 for what that means).
Warning: LIMITED SUPPORT when:
- magisk is installed (known to cause issues sometimes - regardless of the ROM or version)
If you have magisk installed currently UNINSTALL or better do a FULL CLEAN install (see FAQ #2) before doing anything else. Try to re-produce the issue. If it is gone, its magisk related. otherwise follow the above to grab the log.
Magisk is a great piece of software and besides that it is Open Source which SuperSu never was.
I just saying I do not "support" issues with LOS when you have Magisk installed. Why? It is (like Xposed) extendable with modules (made by whoever) and those can cause billions of issues.
Other then that magisk was sometimes the reason for battery drain etc. Magisk modifies the boot "process" and is placed very deep in the system (which is needed to make it work ofc) but that has the potential to make a system/ROM unstable or result in strange behaviors.
so in order to support a specific issue I have to be sure the ROM is in a "clean" state, no magisk, no xposed.
Pro-Tip: set magisk to core functions only to see if an extension causes your issue or not.
Q #02: I want to install clean, how? What is a clean install? What is the recommended way to flash a new ROM version?
A clean install ensures that there are no leftovers from any previous install. One can say that there are 2 phases of a clean flash:
1) regular
2) full - when you (still) encounter issues
Usually the regular one is fully ok when flashing a new ROM version but if you encounter strange issues nobody else is reporting or if a release post is recommending it you should do a full clean install instead.
A regular clean install can be done like this:
WIPE -> Advanced -> select: System + Cache
Flash the ROM
reflash root addon/magisk if you want root
A full clean install needs 2 steps more then the regular:
follow the steps for regular clean
go back in WIPE -> touch Factory Reset and let it do its job
go back in WIPE -> touch the "FORMAT data" button and type "yes" to format the internal storage (you will LOOSE ALL YOUR DATA - obviously)
REBOOT -> Recovery
Flash the ROM
reflash root addon/magisk if you want root
It is absolutely recommended to create a backup before and COPYING IT to your PC(!) before doing the above.
Q #03: Are there any plans or a chance of official /e/ builds?
yes this might happen when the following has been solved / implemented (which is NOT the case currently (see known issues):
- selinux = enforcing
- device encryption working
Q #04: Will this ROM support / pass SafetyNet?
When you install Magisk you can hide and so yes you might be able to pass SafetyNet. Which can change every day though because even when that might work atm you should note the following:
Magisk has its own protections to ensure you pass safetynet but this is something which will change one day and there is no known method yet to workaround that.
Q #05: It looks like the CPU cores 5 and 6 are disabled - how can I fix that?
TLDR;
There is no fix required! it is fully ok when those are idle. they get hot plugged whenever needed.
Details:
we have 2 clusters of CPU cores resulting in a Hexa-core CPU set: (4x1.4 GHz Cortex-A53 & 2x1.8 GHz Cortex-A57)
the big one (2 CPU cores - higher performance = more battery drain, more heat which potentially causing the: bootloop issue) and the little (4 CPU cores - less battery drain but a bit slower) are handled dynamically based on the load of your device.
the big cluster will run ONLY when it is NEEDED - i.e. high load.
so when you look closer: those are not DISABLED they are IDLE which is a big difference.
Q #06: I get a kernel panic or green/purple/blue screen how to grab logs for this?
When you encounter a kernel panic and you are able to reboot without taking out the battery (taking out the battery will erase RAM and so erase the needed logs):
1) reboot (without taking out the battery!) to either TWRP/SHRP or (if you have root access) to your ROM
2) grab everything need from here: /sys/fs/pstore/ (e.g. adb pull /sys/fs/pstore/)
If you don't have a pc near you can do it directly from the device as well:
Enable the terminal app in developer options or download any
Open the terminal app.
su
cd /sdcard/Download
tar czf pstore.tgz /sys/fs/pstore
Attach pstore.tgz to your post.
It is crucial important that you do this only after the reboot happened . It's not important "when" though - as long as the device stays powered on.
Developers note:
convert PMSG log (requires a linux system):
Code:
tr -cd '\11\12\15\40-\176' < pmsg-ramoops-0 | sed 's/TENS\s/\n/g' > readable-pmsg.txt
Q #07a: I get a kernel panic on boot or having other boot issues but the pstore log are empty! What should I do?
Q #07b: How can I provide a clean boot log?
Since a while there is a very easy way to provide debug logs for the boot process. Before my convenient logging you had to follow FAQ #1 to grab them and it was a bit of PITA for some users.
So here you go for a much easier way:
boot Android
once booted : reboot to TWRP/SHRP
when you have a bootloop instead: take the battery out just before the bootloop occurs, or better press the key combo to get into TWRP all the time to eventually get there directly
once in TWRP ensure that "Cache" is mounted in the "Mount" menu (if not mount it by ticking the box)
open a terminal on your PC and type:
Code:
adb pull /cache/debug/boot_lc_crash.txt
adb pull /cache/debug/boot_lc_full.txt
adb pull /cache/debug/boot_lc_kernel.txt
paste one by one to a paste service like https://del.dog/ , https://paste.systemli.org/ or https://paste.omnirom.org/
Q #8: upgrade your bootloader stack only?! Read here how:
Check the OP of this thread which has TWRP flashable files linked.
Q #9: Is there an /e/ specific FAQ?
Sure:
FAQ: click
Forum: click
HOWTOs: click (a great resource for all your first questions)
Q #10: issues with audio (e.g. echo's, silence on one or the other site, ..)? Read here how to provide a specific log for that:
Do the following steps:
1) Ensure you have adb set up on your PC, and have adb debugging and adb root enabled in developer options on your phone
2) Then perform the following (all one command)
On Linux:
adb root ; adb shell "stop audioserver; logcat -c -b all; start audioserver" && sleep 10 && adb logcat -b all |egrep -vi "(dialer|telecom|ril|gsm|touch|brightn|dct|QC-time-services|SST|sensors|AlarmMan|Lights|perfp)"
Click to expand...
Click to collapse
On windows:
adb root ; adb shell "stop audioserver; logcat -c -b all; start audioserver && sleep 10 && logcat -b all |egrep -vi '(dialer|telecom|ril|gsm|touch|brightn|dct|QC-time-services|SST|sensors|AlarmMan|Lights|perfp)' "
Click to expand...
Click to collapse
3) Then re-produce your audo issue and cancel the logcat from step 2 before hanging up!
4) Share the logcat output from the console screen using paste.omnirom.org
Q #11: I'm scared about that microG , I don't want to expose my phone so is this /e/ version a security risk?
First of all you need a lot of trust installing ANY custom ROM. A developer can do nasty things right? Besides that yes microG allowing to let apps act like as they are another app, also known as signature spoofing. This CAN be a good and a bad thing. Read on why my builds are different:
In general the microG patch is an all or nothing. A ROM which supports microG (i.e. signature spoofing) have that feature enabled, always.
The difference in my /e/ builds is that I am using the "restricted" option of signature spoofing so as long as you trust me you are as safe as without microG.
Q #12: I have graphic glitches / issues, what can I do?
My builds using OpenGL instead of skiaGL since a while. skia is the new and faster renderer coming with pie by default but it can cause graphic glitches in some applications and/or situations.
Is there any fix for skiaGL coming? No, details here .
To check if your current ROM version is using skiaGL do this:
Code:
adb shell getprop debug.hwui.renderer
If you get an empty result or "skiagl" it means skiaGL is active.
If for any reason you wanna enforce skiaGL you can do so by
temporary (immediately activated):
Code:
adb root (must be enabled in dev options)
adb shell setprop debug.hwui.renderer skiagl
or make that change persistent:
Code:
boot TWRP
backup system
mount system
adb shell
echo "debug.hwui.renderer=skiagl" >> /system/build.prop
sync
reboot
.-
I uploaded it, good speed, I will continue to try. Thank you
Thanks for this new ROM
I recommend a full cleanup with format
The only issue I have so far is that I can't connect to my Murena.io account, it keeps on loading. Logs attached
Thanks for this Rom, installed 72 hours ago, feels a bit slower than the same Pie Rom,thats expected, but it is fine, very usable. You do an excellent job with this Rom, feels more fluid and energy efficient than linage pie plus gapps and gms working as it should out of the box, this is the first and only Rom of all, i have tried, in every phone i had since my first android, from 2011 doing that. Wont gonna write nothing about battery usage, or SoT, batteries are the oem LG put in these phones.
Until now the only incovenience is that with dark theme enabled, sometimes, 3 out of 10 times, when i wake the screen its lights wont use the brightness it supposed to use, it wake very dim, i´m still debuging this glitch, pushing the power button to turn it off and then pushing it again bring back to full brightness the screen.
cvmg333 said:
Thanks for this Rom, installed 72 hours ago, feels a bit slower than the same Pie Rom,thats expected, but it is fine, very usable. You do an excellent job with this Rom, feels more fluid and energy efficient than linage pie plus gapps and gms working as it should out of the box, this is the first and only Rom of all, i have tried, in every phone i had since my first android, from 2011 doing that. Wont gonna write nothing about battery usage, or SoT, batteries are the oem LG put in these phones.
Until now the only incovenience is that with dark theme enabled, sometimes, 3 out of 10 times, when i wake the screen its lights wont use the brightness it supposed to use, it wake very dim, i´m still debuging this glitch, pushing the power button to turn it off and then pushing it again bring back to full brightness the screen.
Click to expand...
Click to collapse
The blackout when phone display is off is a well known issue since years with any custom ROM for the g4. We tried to fix that for a long time without any real success.
Interesting note, i did not know about it, thanks for the tip, i will use light theme now onwards then, got another little problem with the microphone, the other person hear me to low, only when i use speakerphone in a whatsapp call, with out the speakerphone activated every thing is working well, have not tried in a normal telephone call yet, i have tried changing microphone volume setting in kernel with ex kernel manager, but no success in that, changing screen colors and saturation works in that app, thank you.
@steadfasterX this could be tried https://github.com/sthomsonpl/devic...mmit/07db7d8be41997765f9a0c60d7e7476b5440545e
I installed this ROM yesterday, and its running fine so far.
Thanks a lot for bringing this gem to ye ole G4.
You really did an excellent job!
Auto rotate not working. H815 UsU'd. Yes - flashed UsU zip.
Edit: Also, when turning on bluetooth, connecting bluetooth headphones then playing a video, bluetooth turns off.
I haven't tested bluetooth on the pie /e/OS or the various LineageOS builds, so it could very well be affecting those too.
Hello,
I have unlocked my G4 H815 EU version with USU and installed /e/-OS with Android 11 on it, but afterwards I noticed that I can't make phone calls. I also can't receive phone calls, but the phone sends a message that I have received a phone call. How could this error be fixed?
pizza_alarm said:
Hello,
I have unlocked my G4 H815 EU version with USU and installed /e/-OS with Android 11 on it, but afterwards I noticed that I can't make phone calls. I also can't receive phone calls, but the phone sends a message that I have received a phone call. How could this error be fixed?
Click to expand...
Click to collapse
flash 20p bootloader stack and modem
Thanks. Where can I find the correct bootloader and modem files?
pizza_alarm said:
Thanks. Where can I find the correct bootloader and modem files?
Click to expand...
Click to collapse
pls check the OP -> Requirements (bootloader stack), Installation (Modem)