Related
[Q&A] [ROM][4.4.4/KTU84P][OMNIROM][LINARO/OPTIMIZED] FML: Fork My Life (10/08/2014)
Q&A for [ROM][4.4.4/KTU84P][OMNIROM][LINARO/OPTIMIZED] FML: Fork My Life (10/08/2014)
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
kbfirebreather said:
Anyone having problems with torch on the beta build? Not turning on LED for me, and keeps force closing.
Click to expand...
Click to collapse
I'm having issues with it as well. Sometimes it sits there thinking it works, other times it waits a few seconds and then crashes. It worked for a day...not sure what I did past that to break it.
Is there anyway to overclock the latest update? I know I can't install a new kernel with this ROM.
Also, any option for Volume Rocker unlock? I'm new to this ROM, coming from CM. I kinda rely on that option, since my power button is kinda on the fritz.
Fml 4.4.4 beta
I love this rom but my after clean flashing it the gallery and the camera will not show
Pictures. Is there anything I can do to fix it so I can get camera and gallery to work?
vicious01 said:
I love this rom but my after clean flashing it the gallery and the camera will not show
Pictures. Is there anything I can do to fix it so I can get camera and gallery to work?
Click to expand...
Click to collapse
Which gapps package are you using? I'm using the modular mini. Try another clean flash (sorry) and use a different package than you are now.
aaa
nothing
I've tried a lot of KitKat ROMs, but each one with a lot of issues. So I came back to the 4.3, it surprised me for his stability (1 year with bugged ROM make you feel that your phone sucks more than it actually does [no, it doesn't, I love it!]) and I decided to don't try your FML. Now I can't wait for Lollipop, and even if I haven't tried your ROM, I trust in it and I think it will be the best choice. Good work and thanks!
Could some1 possibly upload a video of this good work ? Got a maguro and I'm very curious
thx in advance!
Samsung Galaxy Nexus FML Lollipop
Hello. I hope this is the right place to post this. I have less than 10 posts so I have to post here...
I've tried to install your FML rom (the lollipop beta) on my Samsung Galaxy Nexus, but I seem to be having the same issue that coleburns is having. Namely, I flashed the rom from recovery, but when I reboot the phone, it shows the Google splash screen and then keep rebooting over and over again.
I understand that the first boot is supposed to take some time, but I've left it for over an hour and it still won't boot into the OS. Is there a step I'm missing?
I'm using the custom version of TWRP that you linked to in the first post. I also formatted all the partitions to ext4. Before flashing the rom, I performed the factory reset from recovery and also cleared the /system folder.
I've managed to load on the KitKat version of your ROM just fine...I can't work out what I'm doing wrong!
Anyway, if you need some logs or something to help debug the issue, let me know. Or, if I'm doing something wrong, could you please let me know? I'm very keen to try Lollipop!
Thanks.
Could some1 possibly upload a video of this good work ? Got a maguro and I'm very curious
thx in advance!
lollipop build 2
Haven't seen anybody ask... In your changelog for lollipop you said the rom takes a VERY LENGTHY FLASH TIME. Are we looking at 5 minutes or more?
edit: VERY LONG... over 5 minutes for me
This is the best rom ever!
When you said, "These builds are very early! They aren't daily-driver-stable, but they are progressing extremely fast." I was expecting junk, then I tried it. I was a big fan of your kit kat rom as well but once I tried this android l rom I fell in love. I have used this all day and it is extremly stable. The only bug I have to report that isnt even a need is the app drawer is the app drawer animation is very laggy. I tried enableing 2d gpu acceleration just in case that had something to do with it but it still didnt help. Any suggestions would be great. Oh and yes I have tried closing other apps, multitasking is no issue with this rom, the memory management is great. I thank you so much for such a great rom, keep up the amazing work.
Installing TWRP Problem
So I am currently on CWM and am trying to switch over to TWRP. I'm have a slight problem. When I install TWRP (via twrp manager app), I am also using the recommended custom twrp from the first post. It installs successfully, then I go into reboot options and reboot into recovery...and it's still CWM. I've tried it multiple times. I am rooted, I do have busybox installed, I can't figure out what the problem is. IM STUCK WITH CWM, HALP!
Mondos said:
So I am currently on CWM and am trying to switch over to TWRP. I'm have a slight problem. When I install TWRP (via twrp manager app), I am also using the recommended custom twrp from the first post. It installs successfully, then I go into reboot options and reboot into recovery...and it's still CWM. I've tried it multiple times. I am rooted, I do have busybox installed, I can't figure out what the problem is. IM STUCK WITH CWM, HALP!
Click to expand...
Click to collapse
Download the file in the OP for FML (twrp 2.7.1). Flash with Flashify. Reboot to recovery.
Don't worry too much about it not working. It's fully working for me but it's pretty slow when you actually need to use it. If you get it going it will pick up the pace, but it's far from usable, being in an app for longer than a minute and touching the home screen button will freeze it up for 10 seconds before it takes you to an empty screen that takes another few seconds to load all the apps and widgets back in. I'd wait for a newer release.
Feedback
Hello i have tried the older version and it was great but i really need my camera so i went back to 4.4 but i appreciate you so much thanks !
Please fix the camera asap and i will definitely install this rom ! and i tried to install the new version but it said Error Binary something in TWRP recovery what can i do thanks!
Q
Is the camera fixed yet?
Notification Light
Is there a way to disable the notification light while the phone is plugged in via USB? It's a little annoying to be on while I'm sleeping. It's not a huge issue though.
TheIbanez97 said:
Is there a way to disable the notification light while the phone is plugged in via USB? It's a little annoying to be on while I'm sleeping. It's not a huge issue though.
Click to expand...
Click to collapse
I don't think so.
I found that the miscellaneous section of the battery stats was taking up most of the battery usage. I don't have any apps installed other than the stock standard.
Hello! Pretty new in XDA forum and I have a couple of questions and concerns. I was browsing through some threads and I was wondering if I could get some opinion/help from other members.
I have a second phone that I want to mod and I need some help.
Device: Samsung Galaxy S4 (ROOTED)
Model#: SGH-M919
Android Version: 4.4.4
Baseband: M919UVUFNK2
It's an old phone and lately, it's been running really slow and if possible, I'd like to make it run as if it was brand new or at least somewhat close. So the question is, are there any recommended stable roms/mods I could use and if there are/is, will I be able to use it with my rooted phone or do I have to completely factory reset it before I apply the mods/roms?
Thank you!
Hi @Mr.LinK,
Just yesterday I finally got sick of my M919 slow/battery drain/old stuff and decided it was time for a reset. I was running SlimKat from over a year ago and while it was a great ROM, I had accumulated so much crap that it was getting really bogged down. This just happens over time no matter what OS, no fault to Slim. But I was also looking to move to Lollipop. Here's what I did:
1. Backed up using several methodologies (full backup with TWRP just in case, then from Android I backed stuff up with Helium, and used Backup My Mobile for SMS/MMS etc., an EFS backup just in case, etc..)
2. From within Android, did a factory reset. This sent the phone into recovery, and it formatted the data partition.
3. Rebooted to recovery again, and used TWRP to manually format the media section, just in case something was left there. Then wiped everything except the external SD.
4. Used ODIN to flash the OH3 firmware onto my MDL M919, without letting reboot after (unchecked the reboot checkbox). Pulled battery, rebooted back into download mode again, and flashed OH3 a second time... this gets around some instance people have reported about incomplete upgrades of firmware and all sorts of issues... better safe than sorry.
5. Let phone boot into now 100 % stock OH3 Android 4.4.4. YEEEUKKK. Some part of me thought I would just root the thing and get rid of Samsung crapware, but just the sheer annoyance of the T-Mobile boot animation was enough to remind me why I left stock long ago. Anyway, I let it boot, and set it up minimally with just 1 Google account, not restoring from backup. To my surprise it found the ATT network (I'm an ATT user, not T-Mobile... I just prefer T-Mo phones because they have unlocked bootloaders) and APN no problem no effort from me. Usually I have to enter an APN.
6. I tested the phone out to make sure all systems were working. GPS, WIFI, Bluetooth, etc.. To my surprise, first time I ran the camera app, it applied a firmware patch. Sweet. I'm glad I went through this step. Coming from ancient MDL, I figured there might be some kinks like this. I let it sit on stock for a few hours while I did stuff with my kids.
7. Back home, I did a factory reset from within Android. Then I flashed the latest TWRP tar file (2.8.7.0) using ODIN, and in TWRP did a full wipe of everything again.
8. At this point I flashed Danvdh's GPE edition of Lollipop from here.
http://forum.xda-developers.com/showthread.php?t=2539361
Installation went smoothly. It's a very basic set of apps that it comes with (Google play is there, but you have to download email/messaging apps from the store such as Gmail and Messaging, Maps, etc). I like this approach!
I've been gradually setting things back up, and am very happy with things so far. Haven't run into any problems yet. The nice pure GPE android experience is refreshing.
@Frankenscript Thanks for the information. I was reading the linked thread and it looks really good so I'll give it a try
Mr.LinK said:
@Frankenscript Thanks for the information. I was reading the linked thread and it looks really good so I'll give it a try
Click to expand...
Click to collapse
Good luck and let us know how it goes!
Frankenscript said:
Good luck and let us know how it goes!
Click to expand...
Click to collapse
I just completely flashed my phone with the ROM and I'm pretty happy with the outcome. No bloatware feels so nice. I've been tinkering with it for a while now and I haven't encountered any problems so far but I did notice that model number changed to GT-I9505G. I'm assuming that's normal since the rom is based off of another variant which makes sense, correct me if I'm wrong. Will this complicate future updates or other rom installation? If so, are there any ways of reverting back to the original model number?
Mr.LinK said:
I just completely flashed my phone with the ROM and I'm pretty happy with the outcome. No bloatware feels so nice. I've been tinkering with it for a while now and I haven't encountered any problems so far but I did notice that model number changed to GT-I9505G. I'm assuming that's normal since the rom is based off of another variant which makes sense, correct me if I'm wrong. Will this complicate future updates or other rom installation? If so, are there any ways of reverting back to the original model number?
Click to expand...
Click to collapse
I'm pretty sure we can change the reported model number by modifying the build.prop file. I just haven't poked around with it yet... I did ask the question in the thread and am waiting for a reply. I haven't had to do this kind of thing for over a year, and I forget the build.prop key that does it. But I had some concern that it might bork something else down the road so I decided to wait a bit. IT's just a cosmetic thing and I'm SOOO enjoying the experience right now.
Two little things I'm still fishing around for answers to:
-In the drop down quick access menu, I wish there was a sound/vibrate/mute toggle. I can make one with PowerToggles but maybe there's a way to adjust what's in the native one.
-Really silly, but the power off button when pressed just seems to ... power off the phone!? No option for restart / recovery. Maybe there's an option to set this somewhere; haven't checked.
Still, these are all minor things to sort out. Really, I think I'm very sold on GPE editions now thanks to Danvdh's work.
Marc
Just an update, my phone just rebooted twice in the last 5 mins or so. Was watching on my netflix and it randomly rebooted. Any idea what's causing it and how to prevent it from happening?
Mr.LinK said:
Just an update, my phone just rebooted twice in the last 5 mins or so. Was watching on my netflix and it randomly rebooted. Any idea what's causing it and how to prevent it from happening?
Click to expand...
Click to collapse
Haven't seen random reboots. I think I got maybe one reboot since installing the ROM. Then again, I haven't put NF on the phone. I do know that Netflix app had some issues on my Shield tablet, and the manufacturer (Nvidia) came out with a patch... maybe it's something general in Lollipop?
Frankenscript said:
Two little things I'm still fishing around for answers to:
-In the drop down quick access menu, I wish there was a sound/vibrate/mute toggle. I can make one with PowerToggles but maybe there's a way to adjust what's in the native one.
-Really silly, but the power off button when pressed just seems to ... power off the phone!? No option for restart / recovery. Maybe there's an option to set this somewhere; haven't checked.
Click to expand...
Click to collapse
Both if those can be fixed with Xposed modules.
Sent from my SGH-M919 using XDA Free mobile app
Will look into doing this in a week or so. Thanks
Sent back in time via Android 9.0 TimeText feature.
Hi, im using CM13, moved from stock rom kitkat 4.4 few months ago. After that time of using cm13 im kinda tired of how unstable it is, on the same time i dont want to go back to stock rom, which seemed to be fat and had a lot of issues as well (bugged front camera for example, sd card issues).
Actually everything worked 'fine' untill last snapshot, that ****ed everything up. Battery is super low (not lasting whole day, at night it drops for ~20%, used to 5% - i callibrated it), phone is randomly restarting and when that happens i cant turn it on, cuz it often stucks on lockscreen (in other word, i cant unlock phone after restart) and need to restart again and again and again (it takes sometimes 30min to make it work). And even before that update it didn't support NFC.
So, here i am, saying 'enough' and looking for best rom for Samsung S4 Mini. Hoping that it will be Android 6 that won't make any conflict with Xposed framework.
Aztek92 said:
Hi, im using CM13, moved from stock rom kitkat 4.4 few months ago. After that time of using cm13 im kinda tired of how unstable it is, on the same time i dont want to go back to stock rom, which seemed to be fat and had a lot of issues as well (bugged front camera for example, sd card issues).
Actually everything worked 'fine' untill last snapshot, that ****ed everything up. Battery is super low (not lasting whole day, at night it drops for ~20%, used to 5% - i callibrated it), phone is randomly restarting and when that happens i cant turn it on, cuz it often stucks on lockscreen (in other word, i cant unlock phone after restart) and need to restart again and again and again (it takes sometimes 30min to make it work). And even before that update it didn't support NFC.
So, here i am, saying 'enough' and looking for best rom for Samsung S4 Mini. Hoping that it will be Android 6 that won't make any conflict with Xposed framework.
Click to expand...
Click to collapse
You must have had a bad install as I've not heard of anyone else with those sorts of issues. Though it could be an incompatible app or bad/old data etc Z you might want to ry fixing first eg wiping all app data or factory reset or fresh install (backup your files first )
Sent from my Galaxy S4 Mini using XDA Labs
@IronRoo
Ok, i will try.
1. What about NFC? Can it be something about bad install? Does it work for you?
2. That thing about battery - im not sure. I saw someone with same issue on reddit.
3. I flashed TWRP via Heimdall Suite, not Odin. Could it be an issue? Do i have to flash it again to maybe fix something? Or having TWRP there, working is enough? Do i have to update recovery to one that came with snapshot? https://download.cyanogenmod.org/?device=serrano3gxx
Aztek92 said:
@IronRoo
Ok, i will try.
1. What about NFC? Can it be something about bad install? Does it work for you?
2. That thing about battery - im not sure. I saw someone with same issue on reddit.
3. I flashed TWRP via Heimdall Suite, not Odin. Could it be an issue? Do i have to flash it again to maybe fix something? Or having TWRP there, working is enough? Do i have to update recovery to one that came with snapshot? https://download.cyanogenmod.org/?device=serrano3gxx
Click to expand...
Click to collapse
1. I see from your link you have the 3g version of the mini, I didn't think that one supports NFC, only the LTE (I9195) has it I think. As NFC needs the right hardware you won't be able to get it. But I don't have the 3g version so I'm not 100% certain if it has support or not.
2. Ii don't think the battery is related to CM13 directly otherwise there would be lots of people with the issue. What is the exact date of the snapshot? There was one that had battery issue but they updated it a few days later is it definitely 20160820 and not the one from a few days before you are running?
Else: If there any app showing high battery usage that doesn't normally? Or is there a problem white a wakelock? You can install an app like Trepn that will show you apps with high cpu usage (even when they are showing in about the usual place in battery stats, my browser recently locked into some sort of loop and was using a high % of cpu occasionally)
3. Always possible but unlikely it's due to Heimdal flash. TWRP should do fine. More likely the wrong Gapps causing instability, you should be on Open Gapps 6 for CM13
Sent from my Galaxy S4 Mini using XDA Labs
@IronRoo
1. Yes, it was supported on stock rom, it's gone now. By the way, im not sure if i really have GT-I9190, since there are parts in my device with name of I9195, also it's called I9195 when booting (but i guess that's just recovery). Cyanogenmod doesn't allow mi to install I9195 (ltexx) roms, saying it's 3gxx device. Then again, when it comes to firmware, there is nothing for my country. Seems like I9190 is only for ~south america or something. No problem finding ROM for poland in I9195 tho.
2. I have 20160820 snapshot, updated from previous one - 20160816. That's where things went wrong. On 20160418 everything (besides NFC) was working fine. Since then battery turned into garbage. At the beggining i thought that it was about Pokemon Go, that has big need for battery. Nonetheless, when i stopped playing it turned out that battery is pretty low on that snapshot. I recallibrated it, but that doesn't help. I had an issue, when battery was droping about 40% in a minute or two. https://www.dropbox.com/s/6oc4yyd1f44pfe7/2016-09-01 14.03.36.png?dl=0
3. Should i check 'update recovery along with cm'? I don't know how it will work.
4. And i forgot - everytime i turn on the phone there is notification that system stopped working. Clicking OK or Wait solves the problem (ofc when its not stuck on lockscreen). That probably is leading me to format and install clean system from new snapshot i guess.
5. Btw. Do i need to format something beside Cache, Data and System for a clean install? Im asking, cuz at some point i tried to install stock rom, but it was stuck on booting, so i restore the backup of CM. This time i will probably wipe internal storage, since i installed a lot of apps, there is probably a lot of junk left.
Thx for helping btw c:
edit. I just installed SlimKat for GT-I9195, worked like a charm, NFC was working as well. Now i reinstalled CM13, clean install of 20160820 (3gxx)- we will see how it will work. Still NFC is not working and notifictation 'process system stopped working' is still there.
Aztek92 said:
@IronRoo
1. Yes, it was supported on stock rom, it's gone now. By the way, im not sure if i really have GT-I9190, since there are parts in my device with name of I9195, also it's called I9195 when booting (but i guess that's just recovery). Cyanogenmod doesn't allow mi to install I9195 (ltexx) roms, saying it's 3gxx device. Then again, when it comes to firmware, there is nothing for my country. Seems like I9190 is only for ~south america or something. No problem finding ROM for poland in I9195 tho.
2. I have 20160820 snapshot, updated from previous one - 20160816. That's where things went wrong. On 20160418 everything (besides NFC) was working fine. Since then battery turned into garbage. At the beggining i thought that it was about Pokemon Go, that has big need for battery. Nonetheless, when i stopped playing it turned out that battery is pretty low on that snapshot. I recallibrated it, but that doesn't help. I had an issue, when battery was droping about 40% in a minute or two. https://www.dropbox.com/s/6oc4yyd1f44pfe7/2016-09-01 14.03.36.png?dl=0
3. Should i check 'update recovery along with cm'? I don't know how it will work.
4. And i forgot - everytime i turn on the phone there is notification that system stopped working. Clicking OK or Wait solves the problem (ofc when its not stuck on lockscreen). That probably is leading me to format and install clean system from new snapshot i guess.
5. Btw. Do i need to format something beside Cache, Data and System for a clean install? Im asking, cuz at some point i tried to install stock rom, but it was stuck on booting, so i restore the backup of CM. This time i will probably wipe internal storage, since i installed a lot of apps, there is probably a lot of junk left.
Thx for helping btw c:
edit. I just installed SlimKat for GT-I9195, worked like a charm, NFC was working as well. Now i reinstalled CM13, clean install of 20160820 (3gxx)- we will see how it will work. Still NFC is not working and notifictation 'process system stopped working' is still there.
Click to expand...
Click to collapse
edit: see arco's reply below,
The 3g CM ROM will not have the NFC code I guess
No do not check "update recovery" as you might lose your current recovery
gotta go get my son now!
Sent from my Galaxy S4 Mini using XDA Labs
Aztek92 said:
@IronRoo
1. Yes, it was supported on stock rom, it's gone now. By the way, im not sure if i really have GT-I9190, since there are parts in my device with name of I9195, also it's called I9195 when booting (but i guess that's just recovery). Cyanogenmod doesn't allow mi to install I9195 (ltexx) roms, saying it's 3gxx device. Then again, when it comes to firmware, there is nothing for my country. Seems like I9190 is only for ~south america or something. No problem finding ROM for poland in I9195 tho.
Click to expand...
Click to collapse
Turn off your phone. Remove the back cover and then the battery. On the white sticker the model number is printed. If it says GT-I9195, then you have the wrong recovery installed, since you say it says it's a 3gxx device when installing ltexx roms.
arco68 said:
Turn off your phone. Remove the back cover and then the battery. On the white sticker the model number is printed. If it says GT-I9195, then you have the wrong recovery installed, since you say it says it's a 3gxx device when installing ltexx roms.
Click to expand...
Click to collapse
Thanks Arco!
(I was trying to say toggle the "signature verification" option but that could lead to more problems if he has the wrong recovery!)
Sent from my Galaxy S4 Mini using XDA Labs
Yup, its GT-I9195, maybe that's from all the problems comes, wrong rom, wrong recovery. I feel kinda dumb, that i didn't check under battery before, sorry for that.
I have work to do today i guess.
@IronRoo @arco68
Ok, few days into right and stable CM13. It's working ultra nice
Battery is still an issue here (again dropped ~30% in a minute), but i guess at this point its hardware problem. Maybe i screwed it with my powerbank.
Btw. Im kinda supprised that system let me install wrong recovery... and the wrong recovery didn't let me install right rom
Aztek92 said:
@IronRoo @arco68
Ok, few days into right and stable CM13. It's working ultra nice
Battery is still an issue here (again dropped ~30% in a minute), but i guess at this point its hardware problem. Maybe i screwed it with my powerbank.
Btw. Im kinda supprised that system let me install wrong recovery... and the wrong recovery didn't let me install right rom
Click to expand...
Click to collapse
Hi, sorry for bringing up this somehow old thread, but I have the exact same battery issue on my wife's serranoltexx.
I just installed CM13 on her phone, and after a reboot battery dropped from 40% to 5%. This happened twice, so no coincidence here.
Have you found where the problem came for ? Was your battery dead or have you found a fix ?
Also, I have seen your post about sview cover, very interesting. Will try it out tonight !
Hi, no worries
No, I didn't find an issue sadly - just like i said before, changing recovery and rom to correct version didn't help. I tried everything at this point, i recalibrated battery like 10 times to be sure, but it still likes to drop madly. For now im just trying to stay above 50%, but (don't take it wrong) im glad im not only one with issue Maybe someone who knows a thing or two about it will be interested in it.
Thanks about S-view. It's really more like noob-geeky-style solution, but it did work for me If you will have any problem, we will try to fix it
Aztek92 said:
Hi, no worries
No, I didn't find an issue sadly - just like i said before, changing recovery and rom to correct version didn't help. I tried everything at this point, i recalibrated battery like 10 times to be sure, but it still likes to drop madly. For now im just trying to stay above 50%, but (don't take it wrong) im glad im not only one with issue Maybe someone who knows a thing or two about it will be interested in it.
Thanks about S-view. It's really more like noob-geeky-style solution, but it did work for me If you will have any problem, we will try to fix it
Click to expand...
Click to collapse
Thanks for your answer !
If changing ROM and calibrating did not help, then I guess it's a hardware problem. That was my first thought when I saw this drop yesterday and I already told my wife that we'll have to buy a new one. Cheers to Samsung for building phones with replaceable batteries !
Even a geeky workaround for the sview cover might suit her needs. I think she just wants to check the time and her notifications with the cover on, I don't think she even needs to answer calls (she said it never worked for her, a touchscreen sensitivity issue I believe).
If she doesn't like it, I still have the possibility to downgrade her to CM11. It seems that sview worked fine on this release. And I'm sure she won't mind kitkat as she's not as geeky as I can be
I've been using CM13 nightly (latest) for 4 days or so.
Pros:
Battery last much longer, you have many battery profiles which is nice.
External SD can be integrated as Internal (nice that some apps are automatically installed onto SD)
Cons:
Can't find tar file which is backup I made using CWM recovery rom. Looked everywhere!
Icons dissappear from home after every bootup
Can't move sys apps or preinstalled apps to ext sd card. Can't use Link2SD once you configure External SD as internal. Not so flexible.
Overall, big improvement I feel is the battery life which is good, the bad thing is that Internal storage space gets filled up easily, especially because I know the CWM backed up ROM is stored there yet I can't find it. Which sucks big time.
kennyk09 said:
Overall, big improvement I feel is the battery life which is good, the bad thing is that Internal storage space gets filled up easily, especially because I know the CWM backed up ROM is stored there yet I can't find it. Which sucks big time.
Click to expand...
Click to collapse
Look in /data/media it should be there somewhere. Need root access though.
I recommend using TWRP instead of CWM.
arco68 said:
I recommend using TWRP instead of CWM.
Click to expand...
Click to collapse
Yes, but TWRP can't flash CM11 if I'm not mistaken. Old ROM, I know, but it's the latest one with S-View Cover support.
Also yesterday, I tried to restore my stock ROM backup with TWRP but could not get it to work. Stuck on "starting apps" during boot. Wiping Dalvik and cache did not help.
@thewild
If changing ROM and calibrating did not help, then I guess it's a hardware problem.
Click to expand...
Click to collapse
Not nessessary. Please notice, that i moved from CM13 (i9590) to... CM13 (i9595). I had an issue with wrong recovery. I also didn't have any problem on stock rom. If you're still gonna change battery, tell me how it worked for you.
Btw. there is something called hall monitor https://github.com/durka/HallMonitor But still i have no idea how and if it (still) works.
Yes I tried halmonitor on CM13. It worked... kind of.
Basically, it allowed the power button to turn the screen on when the cover is closed. The problem is that CM13 lockscreen is not suitable for the view cover.
Then I saw your solution, which should also work with halmonitor as long as dashclock and the xposed module are supported on CM13.
As for the battery, well I'm not 100% sure.
Battery was bad before CM. I'm quite confident that I flashed the correct recovery (i9195), and the correct ROMs. But it's not my phone, so I'm not familiar with it. I'd say that my problem is hardware, and new batteries (official ones) can be found for 10€, so I'll give them a try and let you know.
thewild said:
Yes I tried halmonitor on CM13. It worked... kind of.
Basically, it allowed the power button to turn the screen on when the cover is closed. The problem is that CM13 lockscreen is not suitable for the view cover.
Then I saw your solution, which should also work with halmonitor as long as dashclock and the xposed module are supported on CM13.
As for the battery, well I'm not 100% sure.
Battery was bad before CM. I'm quite confident that I flashed the correct recovery (i9195), and the correct ROMs. But it's not my phone, so I'm not familiar with it. I'd say that my problem is hardware, and new batteries (official ones) can be found for 10â?¬, so I'll give them a try and let you know.
Click to expand...
Click to collapse
€10, they would have to be fake! (or used)
What is the screen on time (battery>screen) you are getting? I bet it's low & that is the reason for your sudden drops, with my old battery (original Samsung) I was lucky to get 3hrs and that had sudden drops, new battery gives me 6hrs SOT.
Can't tell you the sot because it's not my phone, but it sure is very low. And the battery drops from ~50% to 0% in seconds.
10€ seems to be the right price. They are 20€ on samsung's store, but 10€ is on Amazon, sold by Amazon. I never got fake / used items from them.
Anyway, it's worth a try. I can send it back for free if it's not OK.
Long time lurker first time poster.
I've searched both Google and the various Android forums (XDA, Android Central, Android Authority) on how to increase the volume beyond the defaulted max and have come up empty handed. I've seen the whole method of enabling dual speakers but can't find anything on simply increasing the level of the main bottom blasting speaker. There are various apps on the Play store but the reviews seems to make them out to not truly boost the volume.
I've found methods of editing files for other phones (http://forum.xda-developers.com/nexus-6/general/guide-to-boost-audio-t2961352) but I haven't seen the same values in the files it says to change and TBH I don't want to mess it up due to my inexperience with Android (switched from jailbroken iPhone scene for the Pixel XL).
TL;DR: Anyone know of a method to increase the speaker volume on the Pixel XL?
Thanks in advance!
Nate
not unless you root there isnt any other way
wase4711 said:
not unless you root there isnt any other way
Click to expand...
Click to collapse
I am rooted ready and willing. Sorry for not clarifying.
since you are inexperienced with Android, you might want to wait until we have a custom recovery before you go messing with the /system files or directories...if you mess those up, you wont be able to boot back to the rom, and you will have to used ADB types of commands to flash back to the stock rom, if modifying those files messes up your phone..
I've been using Viper and Arise sound mods on my nexus 6 for a long time, and it makes a tremendous difference in the sound, both on calls and for listening to music, but since those files are best flashed in recovery, I haven't even bothered with them for the Pixel at this point, just waiting for a custom recovery to come out, then I will root and flash them.
You might want to read up on Viper and Arise sound mods here on XDA to learn about them before you think about flashing them..
wase4711 said:
since you are inexperienced with Android, you might want to wait until we have a custom recovery before you go messing with the /system files or directories...if you mess those up, you wont be able to boot back to the rom, and you will have to used ADB types of commands to flash back to the stock rom, if modifying those files messes up your phone..
I've been using Viper and Arise sound mods on my nexus 6 for a long time, and it makes a tremendous difference in the sound, both on calls and for listening to music, but since those files are best flashed in recovery, I haven't even bothered with them for the Pixel at this point, just waiting for a custom recovery to come out, then I will root and flash them.
You might want to read up on Viper and Arise sound mods here on XDA to learn about them before you think about flashing them..
Click to expand...
Click to collapse
That certainly answers my question thank you kindly for the quick response. Cheers!
ndhusmc said:
That certainly answers my question thank you kindly for the quick response. Cheers!
Click to expand...
Click to collapse
no problem; it shouldnt be that much longer before a custom recovery pops up, and it will make your life alot easier when there is one!
I would also like to increase the speaker volume. Now that TWRP and Magisk are working on the Pixel/Pixel XL(though Magisk is experimental), it should be possible to flash Viper. I actually tried to install the Viper Magisk module but got an error. I'll try it again after a reboot later, but has anyone else tried it?
hello. i bought an old wildfire; s-off, h-boot 1.0.xxxx and i installed new stock rom (method flashing zip via bootloader) and the boot is veeery long; i think i waited 10 minutes, and after that the stock lockscreen remained blocked...i cant turn off the display, actioning the volume or making any gesture...is freezed, dead... and still same if i remove battery and turn on again...what can be done?
straciatella said:
hello. i bought an old wildfire; s-off, h-boot 1.0.xxxx and i installed new stock rom (method flashing zip via bootloader) and the boot is veeery long; i think i waited 10 minutes, and after that the stock lockscreen remained blocked...i cant turn off the display, actioning the volume or making any gesture...is freezed, dead... and still same if i remove battery and turn on again...what can be done?
Click to expand...
Click to collapse
Hi there, I saw your comment on the other thread but decided to reply here. If you have reflashed the stock rom and its crashing at the lock screen you only have two choices really. 1: Try a custom rom like cyanogenmod 7 to see if the lighter rom runs on your old hardware. 2: Give up on the phone.
I accept that 2 may not be what you want to hear but this device is very old now (in phone years) and a lot of the services that used to support it well, like the android market (Google play) do not really support this device. If you only really want to use the phone for phone calls a cheap "dumb" phone will perform much better than this device in that regard.
If you do want to try though, cm7 is your best bet as it gave the best "performance"on this device back in its hayday.
Best of luck.
heavy_metal_man said:
Hi there, I saw your comment on the other thread but decided to reply here. If you have reflashed the stock rom and its crashing at the lock screen you only have two choices really. 1: Try a custom rom like cyanogenmod 7 to see if the lighter rom runs on your old hardware. 2: Give up on the phone.
I accept that 2 may not be what you want to hear but this device is very old now (in phone years) and a lot of the services that used to support it well, like the android market (Google play) do not really support this device. If you only really want to use the phone for phone calls a cheap "dumb" phone will perform much better than this device in that regard.
If you do want to try though, cm7 is your best bet as it gave the best "performance"on this device back in its hayday.
Best of luck.
Click to expand...
Click to collapse
mya...i tryed before to install cm7,9,10 etc, but still same... i was hoping that ill repair it not for daily use ,services.with apps ,etc, but only for calling and messaging. anyway, thanks for your answer