Related
{
"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"
}
This is a port from the EVO 4G of a ROM by kendallc123, this thread can be found here:http://forum.xda-developers.com/showthread.php?t=1974067
-CM7 Stability
-a2sd
-GApps included
-JB font
-JB wallpapers
-Nexus 4 UI sounds, ringtones, and notification sounds
-ICS/JB Theme by Sonnysekhon (inside theme chooser)
-Sony Xloud Audio Engine and Beats Audio
-Bravia Engine
-3G, 4G, & Wifi Speed Hack
-Battery Saving Tweaks
-Zipaligned
v1:
-Added ICStorch
-Added Email
-Added Sense 4.0 clock
-Keyboard Lights
1. Download ROM
2. Place ROM on sd
3. Reboot into recovery
4. Make a nand backup (if you want, usually a good idea)
5. Superwipe at least 3 times
6. Wipe dalvik cache
7. Install ROM from sd
8. Reboot and enjoy
*kendallc123-for letting me use this ROM
*LOTK:
-jamieg71
-ropodope
-PapaSmurf151 (for his continued help)
-kendallc123
*megaghostgamer
*BigSplit
-Anyone who I forgot, shoot me a PM.
Disclaimer: You are responsible for your own actions.
Link:
http://d-h.st/YRK
MD5 Sum:*c30d051f1b63bed84e40cc0fbdcb8ae4
If you like or appreciate my work hit the THANKS button.
Screenshot 1
Screenshot 2
Screenshot 3-Camera
Reserved
Good job on all the ports and roms guys time to load up boot manager again
sent from a nuclear explosion
Looking Hellua nice
will not boot for me i did the fastboot commands and still
tello2323 said:
will not boot for me i did the fastboot commands and still
Click to expand...
Click to collapse
Do you have an SD partition? I think you have to have one for this ROM, didn't think to test without an SD partition. A2SD is baked in. It would be great if someone could confirm this, cuz I don't wanna delete my partition lol.
bilgerryan said:
Do you have an SD partition? I think you have to have one for this ROM, didn't think to test without an SD partition. A2SD is baked in. It would be great if someone could confirm this, cuz I don't wanna delete my partition lol.
Click to expand...
Click to collapse
Well in SS the a2sd version will still boot with no partition but it will reboot upon installing a app.
His md5 could be bad or maybe not a full wipe. Its hard to tell based on info provided
Sent from a freaked out Jellybean
If you guys have problems with a ROM: BE AS SPECIFIC AS POSSIBLE AND IT IS MORE LIKELY TO GET SOLVED. It's not just my ROMs we are talking about, we can't help you if you are vague. And logcats are the most helpful thing if you have a problem that is not in the OP. We are here to help but you have to help us to help you.
bilgerryan said:
If you guys have problems with a ROM: BE AS SPECIFIC AS POSSIBLE AND IT IS MORE LIKELY TO GET SOLVED. It's not just my ROMs we are talking about, we can't help you if you are vague. And logcats are the most helpful thing if you have a problem that is not in the OP. We are here to help but you have to help us to help you.
Click to expand...
Click to collapse
Well put, I used to hate someone saying this is broke and leaving it at that. Because 75% of the time its user specific or created so its hard for us to track down what happened. The standard for reporting bugs should be
The security type of phone eg s-on/s-off
Wipe process( most important part of flashing)
If the md5 was checked and matched. If anything else was restored in recovery or flashed with the ROM. But that's my opinion
Sent from a freaked out Jellybean
Yes definitely. The more relevant information provided, the easier to diagnose the issue. Then formulate a solution.
TEAM MiK
MikROMs Since 3/13/11
Thanks so much for this, much different than the stock GingerBread I just replaced.
I've only been using Android about 6 months and was running a rooted stock kernel and dodgekernel, but I have to say this build feels much quicker and looks much slicker and has a very nice kernel built in.
I don't know if I was just behind the times or what but is that really just a skin/look change on the Play Store? It's extremely different and very nice looking to what I was using before (and about 10x faster).
I did run in to a couple issues, that are probably just user issues.
I've reinstalled all the apps I was used to but noticed that starting up a navigation, or music file or inputting an address doesn't bring up the prompt I'm used to of "Which application should we open this with". In fact I cannot find where any default tasks can be assigned anywhere. Whenever I go to manage applications, "Launch by default" always says "No defaults set." for every single application.
Another oddity that I think is related to this, when I hit the 'action'/'smart' button my bluetooth it just goes 'dut-dut' and does nothing.
I'm pretty sure Voice Commands is installed, but it won't come up and now I've installed My MotoSpeak and that will not respond either, and I think this is because I cannot choose that button as a task and nothing is set up by default.
Thanks for the help and the nice build.
EDIT: I just noticed that the CM10 roms says that "BT call audio." could be a problem. I know that is a whole different animal, but could that be an issue here as well? Its odd, my BT will play media music fine, but will not play phone/call audio correctly, just hear a buzzing.
itjstagame said:
Thanks so much for this, much different than the stock GingerBread I just replaced.
I've only been using Android about 6 months and was running a rooted stock kernel and dodgekernel, but I have to say this build feels much quicker and looks much slicker and has a very nice kernel built in.
I don't know if I was just behind the times or what but is that really just a skin/look change on the Play Store? It's extremely different and very nice looking to what I was using before (and about 10x faster).
I did run in to a couple issues, that are probably just user issues.
I've reinstalled all the apps I was used to but noticed that starting up a navigation, or music file or inputting an address doesn't bring up the prompt I'm used to of "Which application should we open this with". In fact I cannot find where any default tasks can be assigned anywhere. Whenever I go to manage applications, "Launch by default" always says "No defaults set." for every single application.
Another oddity that I think is related to this, when I hit the 'action'/'smart' button my bluetooth it just goes 'dut-dut' and does nothing.
I'm pretty sure Voice Commands is installed, but it won't come up and now I've installed My MotoSpeak and that will not respond either, and I think this is because I cannot choose that button as a task and nothing is set up by default.
Thanks for the help and the nice build.
EDIT: I just noticed that the CM10 roms says that "BT call audio." could be a problem. I know that is a whole different animal, but could that be an issue here as well? Its odd, my BT will play media music fine, but will not play phone/call audio correctly, just hear a buzzing.
Click to expand...
Click to collapse
There are ICS/JB themes you can download, but some of the theming is within the ROM. As for BT calling, I am only able to test BT by sending files, I no longer own a headset (My Planatronics took a ride in the washer).... Speed is what I shoot for on all my ROMs
Also... Did you restore data when you restored your apps? If you did, reflash and restore apps without data, it might fix your problem.
bilgerryan said:
Also... Did you restore data when you restored your apps? If you did, reflash and restore apps without data, it might fix your problem.
Click to expand...
Click to collapse
Absolutely agree :good: . A Fresh CLean install when first flashing a Rom will avoid a lot of issues. It may take more effort, and time. But it usually gives the best results.
bilgerryan said:
Also... Did you restore data when you restored your apps? If you did, reflash and restore apps without data, it might fix your problem.
Click to expand...
Click to collapse
I used to HATE restoring data, but in most cases its safe since the recent updates to TiBU
Sent from a KangBanged JellyBean
bilgerryan said:
Also... Did you restore data when you restored your apps? If you did, reflash and restore apps without data, it might fix your problem.
Click to expand...
Click to collapse
I actually didn't know there was an option for that, how would you go about doing that for future reference?
Whenever I run a new rom I wipe data 3 times, cache and davlik and start fresh.
I don't use that many apps anyway, just some key ones every day for the drive, so only takes about a couple hours to get set back up and much of that time is just experiencing the new rom and finding what's different.
Yeah speed is incredible, I mean my old kernel was ok when run at 1.5Ghz, but that stock htc launcher or whatever 2.3.5 had would often 'spin' for 5-10 seconds when just trying to switch apps or multitask. There were other instances too, just felt like I/O speed was much different.
I'm sure it helped to not have any of the Sprint/HTC cruft to deal with, but especially navigating apps in the launcher, multitasking and browsing Play Store are beyond incredible, basically instant. My wife finally played with the new rom a bit and said she thought it was just 'too fast' compared to her 4s, she just "didn't like it". I have no idea what that means, but I for one love the speed. I don't need it to be slow to convince me it's working .
This is also my first time using link2sd, I didn't know about it with my old rom and was perpetually with ~40mb left (and a full SD). My trial of the rom and adding sd-ext was because I finally upped to a 32gb and decided to look around while I was upgrading.
As for exact issues: Pressing the 'smart' button on my Bluetooth headset does nothing, getting me 2 quick beeps.
Voice/phone audio through my BT will not work. It's odd because all media, music, text to speech, everything else works fine, and the microphone works fine for voice recognition, etc.
But when on the phone, it sounds a bit like when a phone is half off the hook, a steady, kinda staticy tone and every now and then a juggling/clunk sound (reminds me when someone on the other end played with hanging or half hanging up the receiver). I can switch to headset or speaker while in the call and both are fine, and bluetooth goes silent while in the other modes. It's crazy though because I will hear my gps speak to me overtop of the staticy 'lack of phone' while on BT.
The first issue I fixed: After much internet searching I found other users on ICS experiencing the same issue with the button and they suggested downloading Voice Control Test. It sounds odd, because I've downloaded all sorts of stuff and they work but I have to touch the screen to start them. But just as was reported on the website I found it on:
1) Install Voice Control (Test)
2) Start it up
3) Press the button on your BT
4) MAGIC, suddenly your phone brings back the old Gingerbread option asking which App you'd like to use to complete this action and you can choose to pick a default too, my choices were Voice Control Test or My Motospeak, for some reason stuff like iris and jeannie were missing, but regardless, I hit default, My MotoSpeak and now my 'Smart' button works fine.
5) Un-install Voice Control, button keeps working fine.
Also I haven't tested entering a GPS location yet, but I was playing with some other apps and again was prompted for that other action. This might have reenabled the old prompting for various commands somehow.
Also, I noticed that there was no option for 'Voice Command', which most forums seem to suggest is the old 'built in' app that ran when you pressed the BT button. I'm not sure, but that basic issue might just be that no default app was installed to begin with, but it is annoying that installing something like My Motospeak doesn't help and there's no way to manually set this to the BT button 'action'. Maybe having something lightweight like Voice Command in the rom by default would be a nice feature, the same way you have that light term emulator there by default.
Any thoughts at all about phone audio over BT? It seems so odd since media works and seems more difficult, like maybe an issue with how the dialer is handing off or passing the audio stream to the BT. Maybe there are other 'dialers' in play store, I'm not that familiar, but this seems like it'd be in a common piece in the rom that handles phone audio.
For now I'm going to try to get a voip/sip set up and see if that works, might be nicer anyway because then I can use data while on the 'phone' finally on Sprint.
Thanks again for the work on the rom.
itjstagame said:
I actually didn't know there was an option for that, how would you go about doing that for future reference?
Whenever I run a new rom I wipe data 3 times, cache and davlik and start fresh.
I don't use that many apps anyway, just some key ones every day for the drive, so only takes about a couple hours to get set back up and much of that time is just experiencing the new rom and finding what's different.
Yeah speed is incredible, I mean my old kernel was ok when run at 1.5Ghz, but that stock htc launcher or whatever 2.3.5 had would often 'spin' for 5-10 seconds when just trying to switch apps or multitask. There were other instances too, just felt like I/O speed was much different.
I'm sure it helped to not have any of the Sprint/HTC cruft to deal with, but especially navigating apps in the launcher, multitasking and browsing Play Store are beyond incredible, basically instant. My wife finally played with the new rom a bit and said she thought it was just 'too fast' compared to her 4s, she just "didn't like it". I have no idea what that means, but I for one love the speed. I don't need it to be slow to convince me it's working .
This is also my first time using link2sd, I didn't know about it with my old rom and was perpetually with ~40mb left (and a full SD). My trial of the rom and adding sd-ext was because I finally upped to a 32gb and decided to look around while I was upgrading.
As for exact issues: Pressing the 'smart' button on my Bluetooth headset does nothing, getting me 2 quick beeps.
Voice/phone audio through my BT will not work. It's odd because all media, music, text to speech, everything else works fine, and the microphone works fine for voice recognition, etc.
But when on the phone, it sounds a bit like when a phone is half off the hook, a steady, kinda staticy tone and every now and then a juggling/clunk sound (reminds me when someone on the other end played with hanging or half hanging up the receiver). I can switch to headset or speaker while in the call and both are fine, and bluetooth goes silent while in the other modes. It's crazy though because I will hear my gps speak to me overtop of the staticy 'lack of phone' while on BT.
The first issue I fixed: After much internet searching I found other users on ICS experiencing the same issue with the button and they suggested downloading Voice Control Test. It sounds odd, because I've downloaded all sorts of stuff and they work but I have to touch the screen to start them. But just as was reported on the website I found it on:
1) Install Voice Control (Test)
2) Start it up
3) Press the button on your BT
4) MAGIC, suddenly your phone brings back the old Gingerbread option asking which App you'd like to use to complete this action and you can choose to pick a default too, my choices were Voice Control Test or My Motospeak, for some reason stuff like iris and jeannie were missing, but regardless, I hit default, My MotoSpeak and now my 'Smart' button works fine.
5) Un-install Voice Control, button keeps working fine.
Also I haven't tested entering a GPS location yet, but I was playing with some other apps and again was prompted for that other action. This might have reenabled the old prompting for various commands somehow.
Also, I noticed that there was no option for 'Voice Command', which most forums seem to suggest is the old 'built in' app that ran when you pressed the BT button. I'm not sure, but that basic issue might just be that no default app was installed to begin with, but it is annoying that installing something like My Motospeak doesn't help and there's no way to manually set this to the BT button 'action'. Maybe having something lightweight like Voice Command in the rom by default would be a nice feature, the same way you have that light term emulator there by default.
Any thoughts at all about phone audio over BT? It seems so odd since media works and seems more difficult, like maybe an issue with how the dialer is handing off or passing the audio stream to the BT. Maybe there are other 'dialers' in play store, I'm not that familiar, but this seems like it'd be in a common piece in the rom that handles phone audio.
For now I'm going to try to get a voip/sip set up and see if that works, might be nicer anyway because then I can use data while on the 'phone' finally on Sprint.
Thanks again for the work on the rom.
Click to expand...
Click to collapse
If you are using Titanium Backup it restores app data by default, there are three options near the top of the screen when choosing apps to restore... Thanks for the input tho, it's something I don't really think about because I no longer have a BT headset. I'll have to look into it... Too fast? Lol there's no such thing.
{
"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"
}
This is a project I was working on about a month or two ago but put on the back burner because I got mad at it. It is a port from the EVO 4G found here. It was originally Designed and Developed by Provision Team. http://www.provisionmod.com/about
I used JellyBelly as my base for this and it includes Strapped365's Linaro o3 Optimized kernel.
Features:
Cool notifications panel with customizable quick settings
GApps baked in
a2sd (See instructions below)
SuperSU
Seeder.apk v2.0
Apollo
Choice of Apex or Trebuchet launchers. (I prefer Apex)
And much more...
What works:
Almost everything!
Issues:
No 4g
Bluetooth works for some and not for others
I can't figure out how to get the weather to work FIXED!!!
Navigation bar in Provision customizing doesn't work
Camcorder is broken
Sometimes the notification bar doesn't want to come down properly. So go into apex settings/Behavior settings. There you can use the swipe gesture of choice to show the notifications.
Disclaimer: Flash at your own risk!
*It is important to note that there may be additional issues I don't know about and as I am a truck driver, not a programmer I may or may not be able to fix things.
Everyone is encouraged to do whatever you like with anything I post.
Instructions:
Download ROM to the root of your sd card
Boot into recovery. (I use CWM)
Wipe dalvik cache, system and data/factory reset 3x each
Install ROM from sd card
Reboot system
Downloads:
Android File Host
A2SD: (DO NOT FLASH UNLESS YOU HAVE AN SD-EXT PARTITION)
http://d-h.st/kTT- Thanks CRIME INC. and jmztaylor
A2SD INSTRUCTIONS: Thanks drob311 and Halrulez!!!!
1. Get a properly formatted sd-ext partition. (Do not move on until you have done this.)
2. Reboot into recovery
3. Wipe dalvik cache and cache 3x
3. Go into Mounts & Storage
4. Mount cache, data, sd-ext, sdcard and system
5. Flash DarkTremor's a2sd zip (above)
6. Reboot
7. After reboot, go into terminal
8. Type-> su -> hit enter->hit "allow" when SuperSU prompts you
9. Type-> a2sd reinstall-> hit enter
10. Wait until it reboots. If this doesn't work, start over at step 1 and do it again.
11. To make sure it worked, go into Titanium Backup. If there is an a2sd partition at the bottom it worked.
Change log:
6/25/2013 Original release
6/27/2013 Changed the Framework.jar with the modded one by BigSplit to fix the weather. Changed the SystemUI.apk to the modded one by geloczigeri and updated some apps and added Greenify
Credits:
Thanks goes out to TroNit for bringing Provision to the EVO and for giving me permission to bring it to the Shift.
Thanks to bilgerryan for all of his work for the Shift especially for JellyBelly and letting me use it for my base.
Thanks to the Provision team for their original work.
Thanks to Strapped365 for the kernel and all the hours you've invested in us here at XDA.
Thanks to BigSplit and ivanrvf for the weather fix!
Thanks to geloczigeri for the modded SystemUI.apk!I'd also like to say a special thank you to the Evo Shift 4g community as a whole for all the help, time and energy invested in each other as well as our device.
Thanks!
Awesome chad! hope u guys enjoy it. Good work!
Sent from my Evo 4G LTE using Tapatalk 2
Some more screenshots. I included 2 sense themes.
this looks great, thanks. as for the weather, i noticed a while ago (several months ago actually) that weather stopped working on all of the cm ports for us. i thought it was just something i borked in my phone or me not using gps and wifi location in google settings. i havent gotten around to it but now that google has its own settings app try adjusting the location settings in that instead of the rom.
I've been thinking the problem has to do with the web address the weather information comes from. All the google settings does is link to the ROM's gps settings...
Looks great bro, my power button is starting to go, so I will try and flash this before it does.
Team Rejectz
Chad The Pathfinder said:
I've been thinking the problem has to do with the web address the weather information comes from. All the google settings does is link to the ROM's gps settings...
Click to expand...
Click to collapse
yeah i wasnt sure. i havent decompiled a rom in ages and the last rom i used that had working weather in it was aokp.
Cool, I just figured out how to get a2sd to work on this!
Really Neat! I've always loved you and Ryans work. Hopefully they can make a 4.2.2 version of this rom and then I can use it =)
Sent from my DROID4 using xda premium
Well there's only been 4 DLs so far. I guess there aren't many Shift users left.
Chad The Pathfinder said:
Well there's only been 4 DLs so far. I guess there aren't many Shift users left.
Click to expand...
Click to collapse
installed last night, excellent ROM. gonna fiddle with it throughout the day. i did notice last night though that when adding/removing toggles it fc's the systemui. tried rebooting it to see if itd help but it didnt. had to set it back to defaults and reboot to fix the systemui.
sorry, no logs since i removed all dev stuffs from my laptop a while back
I noticed the same thing earlier when I was first messing with it but at the time I thought the ROM was just resetting the systemUI.apk because it came right back on for me. This morning I changed a few toggles again but the systemUI didn't reset. Maybe after things have settled in that won't happen anymore.
Chad The Pathfinder said:
I noticed the same thing earlier when I was first messing with it but at the time I thought the ROM was just resetting the systemUI.apk because it came right back on for me. This morning I changed a few toggles again but the systemUI didn't reset. Maybe after things have settled in that won't happen anymore.
Click to expand...
Click to collapse
well i messed with the toggles some more this morning and it seemed to be ok as long as you dont fiddle with more than 2 at a time. do 2 and let it save then do more, etc..
odd bug but systemui isnt crashing anymore.
Thats the only bug I've noticed so far too. Bluetooth worked perfectly for me.
BigSplit said:
Thats the only bug I've noticed so far too. Bluetooth worked perfectly for me.
Click to expand...
Click to collapse
That's cool! The problem I have with bluetooth may be related more to my headset. I've had a lot of trouble with it not working on several ROMs.
Arggg.... If you are viewing the toggles when you dismiss the dropdown then it becomes a pain to open your notifications again. It acts like it loses focus as soon as the toggles become visible and it closes. If you make sure to tap back to the notifications view before you dismiss it though then there is no problem
BigSplit said:
Arggg.... If you are viewing the toggles when you dismiss the dropdown then it becomes a pain to open your notifications again. It acts like it loses focus as soon as the toggles become visible and it closes. If you make sure to tap back to the notifications view before you dismiss it though then there is no problem
Click to expand...
Click to collapse
yeah, noticed that too
Guys, I am unable to duplicate what you're talking about with the toggles. If I close the notification bar while the toggles are showing, when I reopen it they are still there but all I have to do is hit the button just to the left and it shows the notifications fine. In face I've tried this with just a few turned on and with all of the toggles on and its the same thing. I wonder why they work ok for me and not for others?
Edit: There is an option in apex settings/Behavior settings that you can set so when you use the swipe gesture of choice, it'll show the notifications. Maybe this can help...
Chad The Pathfinder said:
Guys, I am unable to duplicate what you're talking about with the toggles. If I close the notification bar while the toggles are showing, when I reopen it they are still there but all I have to do is hit the button just to the left and it shows the notifications fine. In face I've tried this with just a few turned on and with all of the toggles on and its the same thing. I wonder why they work ok for me and not for others?
Click to expand...
Click to collapse
i think you misunderstood. yes, the toggles are still there but the drop down is more of a pain in the a$$ when you close it on toggles instead of notifications.
After rooting I have noticed that after a while when I open the camera app, it no longer takes pics when tapping on the screen. I can pull up the menu and try to hit the camera button, that also does nothing, same with even the back button. This is a huge deal breaker, if I can't fix this the phone is going back.
Rooted apps running:
Titanium Backup (de-bloat)
Xposed
G3 Tweakbox
AutoHide Soft Keys
If someone could recreate this and help me out that would be awesome! until then back to the Note 3! Please note that it takes a few times of opening the camera app for this to occur, also after rebooting the phone it seems to work for one or two pics once in a while.
KrInEn said:
After rooting I have noticed that after a while when I open the camera app, it no longer takes pics when tapping on the screen. I can pull up the menu and try to hit the camera button, that also does nothing, same with even the back button. This is a huge deal breaker, if I can't fix this the phone is going back.
Rooted apps running:
Titanium Backup (de-bloat)
Xposed
G3 Tweakbox
AutoHide Soft Keys
If someone could recreate this and help me out that would be awesome! until then back to the Note 3! Please note that it takes a few times of opening the camera app for this to occur, also after rebooting the phone it seems to work for one or two pics once in a while.
Click to expand...
Click to collapse
Have you tried disabling all modules on Xposed and tried every tweak one at time? are you using an app for the Autohide Soft Keys or are you using the built in feature?
I don't have problems with the camera and have similar configuration.
fgarcia10 said:
Have you tried disabling all modules on Xposed and tried every tweak one at time? are you using an app for the Autohide Soft Keys or are you using the built in feature?
I don't have problems with the camera and have similar configuration.
Click to expand...
Click to collapse
I am using an app for the auto hide. For some reason the stock hide does not allow you to hide them in apps like Messages, or in the launcher. kinda dumb those are where I want it to hide the most.
First off, it is likely something that you have loaded (or removed) since rooting that has caused the issue.
What apps did you de-bloat? It is possible that you removed or froze something that is required for normal camera operations.
Do you have any of the "Camera Tweaks" selected in the G3 TweaksBox module (if so, I recommend that you deselect them and reboot).
If that doesn't work, I would suggest turning off and removing the "autohide softkeys" module. That isn't a common module for G3 users and it may be interfering with the normal operation of the phone.
Second off, you shouldn't return the phone because you messed it up. You were willing to root and modify your phone, so it is on you to fix it (especially when it is so easy to do). Worse case scenario, you should return it back to the original stock image and start over. For more information on how to do this, please read over this thread....... http://forum.xda-developers.com/showthread.php?t=2799647
If none of this works, you return the phone back to stock and it still doesn't work right, then it might be a hardware issue. If this is the case, then you should return the phone. But only after exhausting all other avenues and only after returning the phone back to stock and testing to see if the problem still exists. You have to return the phone back to stock in order to return it anyway.
Here is a question, when you are in the camera app do you have the menu up? Start with teh simplest things, rule them out and work your way up to find the problem.
If it looks like this, you have to hit the camera icon
{
"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"
}
If it looks like this, screen touch
Rooting does cause issues with the camera. I haven't done anything but root and the camera doesn't allow for the touch to take a picture and it also messes with the menu and edit options. As a matter of fact, if you remove or disable Google+ you have NO edit options. You can find a third party app to use in place of this, but it does mess up the camera edit functions.
droidiac13 said:
Rooting does cause issues with the camera. I haven't done anything but root and the camera doesn't allow for the touch to take a picture and it also messes with the menu and edit options. As a matter of fact, if you remove or disable Google+ you have NO edit options. You can find a third party app to use in place of this, but it does mess up the camera edit functions.
Click to expand...
Click to collapse
I'm rooted and the camera is working just as it did before.
KrInEn said:
After rooting I have noticed that after a while when I open the camera app, it no longer takes pics when tapping on the screen. I can pull up the menu and try to hit the camera button, that also does nothing, same with even the back button. This is a huge deal breaker, if I can't fix this the phone is going back.
Rooted apps running:
Titanium Backup (de-bloat)
Xposed
G3 Tweakbox
AutoHide Soft Keys
If someone could recreate this and help me out that would be awesome! until then back to the Note 3! Please note that it takes a few times of opening the camera app for this to occur, also after rebooting the phone it seems to work for one or two pics once in a while.
Click to expand...
Click to collapse
I have deleted Busybox and Odn pro. The problem was solved. For navbar hide i use g3 tweakbox.
droidiac13 said:
Rooting does cause issues with the camera. I haven't done anything but root and the camera doesn't allow for the touch to take a picture and it also messes with the menu and edit options. As a matter of fact, if you remove or disable Google+ you have NO edit options. You can find a third party app to use in place of this, but it does mess up the camera edit functions.
Click to expand...
Click to collapse
ScooterG said:
I'm rooted and the camera is working just as it did before.
Click to expand...
Click to collapse
Looks like its apps that hide nav bar that cause camera not to work.. at least in my limited experience (VZW G3)
Off to try G3 tweaks to hide nav bar
Same Problem
KrInEn said:
After rooting I have noticed that after a while when I open the camera app, it no longer takes pics when tapping on the screen. I can pull up the menu and try to hit the camera button, that also does nothing, same with even the back button. This is a huge deal breaker, if I can't fix this the phone is going back.
Rooted apps running:
Titanium Backup (de-bloat)
Xposed
G3 Tweakbox
AutoHide Soft Keys
If someone could recreate this and help me out that would be awesome! until then back to the Note 3! Please note that it takes a few times of opening the camera app for this to occur, also after rebooting the phone it seems to work for one or two pics once in a while.
Click to expand...
Click to collapse
I have the same problem as you, and I'm fairly sure it's because of the auto hide soft keys. Something goes wrong when it is enabled, but disabling it makes the camera app work just fine. I've reverted to using the google camera app, but it sometimes takes a few seconds to snap a photo...
Hello,
I tried to look for this problem over the internet but no success.
Has anyone faced this problem after upgrade?
My nexus 5 was good with no problem before the update, and even 1 day after.
The problem started on yesterday, when suddenly the speaker didn't work. Tried to switch on and off the volume, and sometimes it does come back! But most of the time it silent.
Do you know about anything i can do to fix it ? Or just try to wipe everything?
Thanks
Sent from my Nexus 5 using XDA Free mobile app
No one faced this yet ?
Sent from my Nexus 5 using XDA Free mobile app
No volume with lollipop
I had a similar problem. When I adjust the speaker volume with the volume buttons, there is no sound at all. I downloaded an app to test the internal speakers, and they work fine. So, there must be something wrong with the lollipop installation that is preventing the speakers from playing properly.
t-tomer said:
Hello,
I tried to look for this problem over the internet but no success.
Has anyone faced this problem after upgrade?
My nexus 5 was good with no problem before the update, and even 1 day after.
The problem started on yesterday, when suddenly the speaker didn't work. Tried to switch on and off the volume, and sometimes it does come back! But most of the time it silent.
Do you know about anything i can do to fix it ? Or just try to wipe everything?
Thanks
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
same issue here.
I have the same issue after upgrade to lollipop 2 days ago. Speaker sound is intermittent.
I went through following troubleshooting items except for reseting to factor settings.
It is still an issue.
================FROM Google support ================
Here are the troubleshooting steps that we discuss on the phone.
If you are having any audio, speaker, or microphone issues with your device, please follow the steps below.
Step 1: Update to the latest version of Android OS.
Go to "Settings" > scroll down to "System" > touch About phone (or tablet) > touch System updates.
If your device is modified or rooted, revert your device to original factory image since troubleshooting steps may not work on modified/rooted devices. You can use our Nexus factory images to re-image your device.
Step 2: Remove obstructions.
Remove any cling film, stickers, covers/cases/bumpers, or anything else that can be obstructing the device.
Step 3: Enable safe mode on your device.
Ensure your device's screen is on, then press & hold the Power button.
Touch and hold the Power off option in the dialog box.
Touch OK in the following dialog to start safe mode.
To exit safe mode, turn your device off and on again.
If you discover that the issue doesn't occur while your device is in safe mode, it's likely that a third-party app or Android OS modification is causing the issue. You can start to use and narrow down your installed apps to try to pinpoint the specific app. When the culprit is identified, you can uninstall the app or contact the developer of the app for further support as follows:
Navigate to play.google.com.
Find the app and click on it to view its main page.
Scroll down to the "Additional Information" section. Here, you'll see "Contact Developer" options.
Step 4: While in safe mode, turn off Bluetooth.
Go to "Settings" > under "Wireless & Networks", touch Bluetooth.
In Bluetooth settings, if Bluetooth is on, touch the slider to switch Bluetooth off.
Step 5: While in safe mode, make sure the volume is on.
Go to "Settings" > under "Device", touch Sound > touch Volumes.
In Volume settings, slide all three indicators all the way to the right to make sure all sound is on and at max volume.
Note: When each slider is adjusted, a sound will be heard.
Step 6: Check if the issue is resolved.
Play with the volume levels to hear sound.
Make a test phone call.
Use Google Now to test your microphone.
If your issue isn't resolved, continue to the next step.
Step 7: Reset your device to factory settings.
If you're still unable to resolve the issue, or if the issue is so severe that you can't boot your device into safe mode, resetting your device to factory settings may help. Resetting your device to factory settings will erase all local data on your device. Backup of your personal local data (pictures, music and video files) is recommended.
To backup personal data on your device
To reset your device to factory settings
If your issue has been resolved, great! Let us know.
Speaker not working in Nexus 5 after Lollipop update
I am facing the same problem in my Nexus 5 [32 GB]. Everything was working fine before updating to Lollipop. Now, the speaker is not working. Headphone is working but there is no external sound.
Have you found any way to solve the problem? I think the problem is with Nexus 5 32 GB version, your one is 32 GB or 16 GB?
t-tomer said:
Hello,
I tried to look for this problem over the internet but no success.
Has anyone faced this problem after upgrade?
My nexus 5 was good with no problem before the update, and even 1 day after.
The problem started on yesterday, when suddenly the speaker didn't work. Tried to switch on and off the volume, and sometimes it does come back! But most of the time it silent.
Do you know about anything i can do to fix it ? Or just try to wipe everything?
Thanks
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
hey guys!
So after a couple of days i manage to find the problem, and i am sorry to tell - it's hardware issue.
i realized that if i press in the middel of the back of the nexus its suddenly works.
taked the cover off and started to analyze the issue. I realized the problem is this part:
{
"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"
}
the upper conector is the one that does the problem.
i don't know why now, after a year just right after i installed lollipop...
anyway, i disassamble it, cleaned it and put it back.
for now it is working good. i think i will order a replacment just incase...
check this thing in your nexus (at your own risk).
hope it helps
I did a hardware reset and everything appears to be working fine now. I haven't had any further sound issues. I know it's a pain, but at least folder contents are now backed up so the restore is less laborious for organized people. You only have to worry about re-entering user/password information for selected apps to be back in business.
niluthpol said:
I am facing the same problem in my Nexus 5 [32 GB]. Everything was working fine before updating to Lollipop. Now, the speaker is not working. Headphone is working but there is no external sound.
Have you found any way to solve the problem? I think the problem is with Nexus 5 32 GB version, your one is 32 GB or 16 GB?
Click to expand...
Click to collapse
How to do the hardware reset?
Iceman1968 said:
I did a hardware reset and everything appears to be working fine now. I haven't had any further sound issues. I know it's a pain, but at least folder contents are now backed up so the restore is less laborious for organized people. You only have to worry about re-entering user/password information for selected apps to be back in business.
Click to expand...
Click to collapse
T-tomer. What part is that. Having the same issues and id like to swap out that part. Thanks
I've been fighting similar issues on my nexus 5 32.
Media volume totally silent, Google now voice detection stops working, phone only works in speaker mode. Usually safe mode didn't solve anything and I've ended up flashing a stock image.
Here's what seems to fix it for me (no computer access so fastboot is a no go).
For whatever reason, it's like the hardware thinks there's a headset installed. Plug in a headset, listen to some music on Google play (just what I did) reboot, listen again. Remove headset.
Some combination of this has been fixing it every time for me; I cringe thinking of how many times I've fresh flashed...
I disassembled my N5 enough to re-seat the board-to-board the connectors on that board. I also unplugged and re-plugged the battery. Put it back together and I have sound again! It's possible that it was just the connection to the speaker or battery and maybe I didn't have to re-seat all those other connectors but I have no way of testing that now.
Anyway thank you so much!:good:
t-tomer said:
hey guys!
So after a couple of days i manage to find the problem, and i am sorry to tell - it's hardware issue.
i realized that if i press in the middel of the back of the nexus its suddenly works.
taked the cover off and started to analyze the issue. I realized the problem is this part:
the upper conector is the one that does the problem.
i don't know why now, after a year just right after i installed lollipop...
anyway, i disassamble it, cleaned it and put it back.
for now it is working good. i think i will order a replacment just incase...
check this thing in your nexus (at your own risk).
hope it helps
Click to expand...
Click to collapse
On mine, mic and media volume stopped. (You could use the phone only in speakerphone mode). Easiest fix for me so far, plug in headset, listen to music, unplug headset, (music will automatically pause) hit play on music, sound and mic are back.
Of course, if you prefer disassembling your phone, or fast boot flash a new system, those have worked for me also. But the headphone trick works for me.
t-tomer,
Running into the same problem as you mentioned. I have had my phone for over a year, and after the Lollipop 5.0.1 update, my speaker just started cutting out. But after reading this post and as you mentioned, if I apply some pressure from my finger to the back of my phone in the region just below the camera lens in the upper middle, I will get full sound from my speakers.
My 2 questions for you:
1) When you mention the part that you cleaned of the "upper connector", is that in the lower left of your posted picture?
2) Did you end up replacing the part? Or was a cleaning good enough?
Thanks!
t-tomer said:
hey guys!
So after a couple of days i manage to find the problem, and i am sorry to tell - it's hardware issue.
i realized that if i press in the middel of the back of the nexus its suddenly works.
taked the cover off and started to analyze the issue. I realized the problem is this part:
the upper conector is the one that does the problem.
i don't know why now, after a year just right after i installed lollipop...
anyway, i disassamble it, cleaned it and put it back.
for now it is working good. i think i will order a replacment just incase...
check this thing in your nexus (at your own risk).
hope it helps
Click to expand...
Click to collapse
Did you eventually replace this part? I disassembled my nexus 5 and re-set all of the cable connections and am still having an issue with no sound unless I depress the middle-back of the case. I'm considering purchasing the part pictured and replacing it but, wanted to see it doing that would necessarily correct the problem. What's your experience? Thanks in advance.
H_Scrappy said:
Did you eventually replace this part? I disassembled my nexus 5 and re-set all of the cable connections and am still having an issue with no sound unless I depress the middle-back of the case. I'm considering purchasing the part pictured and replacing it but, wanted to see it doing that would necessarily correct the problem. What's your experience? Thanks in advance.
Click to expand...
Click to collapse
If you know what you'r doing, try to check the soldering of the socket it connects to.
If not, take it to a Lab or to somone with experience to check this and fix it.
This is probably the problem.
good lack!
Problem Solved suddenly.
The problem solved automatically in my case. Same problem. No sound from speaker, headphone was working. And in Safe Mode also no sound. I tried things like reset, but no luck.
Then Suddenly it started working. The charger was connected, as charge percentage was below 10%. For making a call, I removed charger and there was sound from phone[which notifies of charge below 15%]. After that, sound is working fine. It was like a magic.
I don't know how it solved. I think some application, which was not actually compatible with lollypop was causing problem. In the meantime, the app may have updated and 5.0.1 update came, so the problem solved. Or may be, like some guys have mentioned to restart a lot of times to solve the problem.
t-tomer said:
***excellent solution***
Click to expand...
Click to collapse
Had the same problem, no audio after Lollipop-upgrade (besides when headphones was attached and in calls).
Your solution with cleaning the connector worked like a charm, thanks!
Damienzzz said:
Had the same problem, no audio after Lollipop-upgrade (besides when headphones was attached and in calls).
Your solution with cleaning the connector worked like a charm, thanks!
Click to expand...
Click to collapse
How did you go about cleaning the connector?
Thanks.
Cabelly said:
How did you go about cleaning the connector?
Thanks.
Click to expand...
Click to collapse
I cleaned the parts/connectors with a rocket blower and a fine brush (my camera cleaning kit).
Had the same issue with my nexus 5. No sound, no google now, headphones worked. Randomly found out the issue whilst trying to use my headphones on another device and I couldn't hear anything. Noticed that the top of the headphone jack was missing and *ding* the lightbuld went off in my head. Looked in the headphone socket on my N5 and there it was, jammed into the bottom. Managed to get it out and now everything's working :good:.
Hi guys, I have a very irritating issue with my international Galaxy S6 Edge (SM-G925F) and hopefully someone could help me fixing it. I know that this is the forum for the flat Galaxy S6, but since the main hardware components are the same I guess that both devices could suffer from the same problems.
I'm experiencing frequent lockups mostly when trying to wake up/unlock the phone. The device becomes totally unresponsive to screen or home, back, window button taps and eventually after lots of tries it comes back to life and behaves as normal. The problem becomes way less frequent (almost disappears) if I connect it to a charger.
What I tried up to now with no luck fixing the problem is:
Disabled all the TouchWiz smart features, location services, wifi and radio broadcasts, rotation, nfc, sound, bluetooth, fingerprint scanner,
Checked all the sensors from the *#0*# menu and they seem fine,
Flashed through Odin, Smart Switch, TWRP official and custom roms (5.1.1, 6.0.1),
Tried rooted and non-rooted roms,
Tried odin's NAND erase all option and repartioned the phone using the ZEROLTE_EUR_OPEN.pit file,
Wiped the persistent partitions (sda11, 13) using the ADB commands dd if=/dev/zero of=/dev/block/sda11, dd if=/dev/zero of=/dev/block/sda13, which however gave me:
dd: /dev/block/sda11 (sda13): No space left on device,
so I don't know if it was successful or not,
Updated (PASS) the TSP FW version from the *#2663# menu,
Opened the phone and powered it up after disconnecting all components apart from screen and battery,
Tried different battery.
Does anyone have a similar problem and knows how to fix it? Unfortunately, my device is out of warranty so I wouldn't like to visit a Samsung service centre.
I haven't tried alternative PIT files with hidden partitions of various sizes yet. Do you think that it will make any difference or, furthermore, is there a chance of further damaging my phone?
Could someone please with a similar device dial the *#2663# code and give me the following information? Phone's and part's TSP FW version, TSP threshold.
Is there a Phone's and Part's Touch key FW version available? In my phone I cannot see the Phone's, Part's Touch key FW version paragraph at all and I'm curious if this is related to the problem.
Looking forward for your tips! Thanks!
I had this too, but *seem* to have it solved.
Maybe I did some unnecessary step, but it now flawlessly works for half a day, compared to reboot/freeze every few minutes.
- calibrate battery (use an app from play store, or L Speed (has an option for that, too))
- backup stuff to pc
- re-install stock firmware using Kies (works with knox trip, too)
- don't activate wifi, accounts in first start wizard
- do factory reset
- restart
- again no wifi, accounts in first start wizard
- factory reset again
- restart
- again no wifi, accounts in first start wizard
- go to stock recovery (adb reboot recovery or phone off, then power+home+vol up)
- clean cache
- factory reset
- clean cache again
- reboot
- setup normally (ie with wifi et all)
- profit (?)
- optional: install twrp through ODIN
- optional: flash custom rom (let the aroma installer do the wipe)/or supersu if you plan to stay on stock [I'm on PureStock Extra Lite by ambassadii, mist stable ROM from my personal experience]
- additionally you want to disable account sync or play/galaxy auto updates (known to increase issues, but likely not required once phone works again normally)
I know that excessive factory resetting sounds stupid...
But a single factory reset or single cache clean did NOT fix it for me. Also FXR and other options did not do the trick for me.
You might aswell try with just one factory reset, but mine worked normally again upon third + manual in stock recovery... (might aswell just be bad luck).
I hope my device is over with it.
I hope this may help you to solve your problem aswell.
Gesendet von meinem SM-G920F mit Tapatalk
Thanks for your help mate, but unfortunately it didn't fix the problem. Perhaps it seems a bit better, but not fixed for sure. Could you please dial in *#2663# and give me the info that I mentioned in the first post?
Screenshot.
{
"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"
}
It happened for me again, too, once late at night. But during day it seemes fine.
Might be a deep sleep issue?
Gesendet von meinem SM-G920F mit Tapatalk
It seems an external problem, not a software problem...i had similar issues with Arter kernel (galaxy s3 l9300), then i changed to boeffla and now it works without any minimal lag.
I suggest changing your kernel instead of the rom...
Always do a backup before doing anything!
After finishing all the updates my phone returned back to the unusable condition. It seems that it is related to deep sleep issues, but not sure if it's a software or hardware problem though. As long as I keep my phone "warm", ie browsing, playing or any other sort of activity it runs smoothly. The problem appears when I try to wake it up from deep sleep.
Now, regarding the *#2663# menu, I thought you had the edge variant and wanted to see if you had the "Touch key FW" version menu. As I said, in my phone the "Touch key FW" version menu is not appearing at all, but maybe it has to do with the fact that it is the Edge version and not the flat one. A colleague's "healty" flat S6 reports the same info like yours, so everything seems fine there. In any case try the update thing and see if it helps you solving the issue. In my case it didn't, but you can still try!
Regarding, the kernels I tried plenty of them - stock, custom, 5.1.1, 6.0.1, (un)rooted - and the problem was always there.
I'll check how arter97 kernel with system less root behaves.
Gesendet von meinem SM-G920F mit Tapatalk
Wait... You said this problem almost disappears if you put your phone to charge...
Try changing the voltage settings of your CPU at first higher and then lower...
Try also to turn off some cores and overclock the others...
I'm saying this because it seems the only way to see if the problem is the hardware or the software.
(Always backup first!)
I have to admit that this is something I haven't tried yet. At the moment I have turned my wifi off, removed the sim card and rebooted the phone. 4 hours running on battery with not a single problem. I'll check is behaviour for the rest of the day and then I'll try to fiddle with the cpu settings!
Unfortunately, I didn't manage to get rid of the problem. I tried to overvolt cpus, gpus, busses and it didn't make any difference. I repartitioned the phone with a different PIT file and it didn't help either. If you have anything else to suggest please do so.
I tried that, too and also updated to Pure Stock ROM v5.4 with hacker kernel.
No more issues for me since ~24 hours, compared to twice before. I hope it'll stay like that.
Gesendet von meinem SM-G920F mit Tapatalk
Just a small update for ppl that are having similar issues. The only thing that seems to bring my phone back to normal state is heat: if I heat my phone from both sides with a hairdryer for 10-20 seconds it comes back to life with no problem at all. Nothing else seemed to help.
Apart from that, @Setialpha recently published a ROM that hopefully solves the random lockups, reboots etc. I'll try it and report back.
Give it a go and if it works thank the dev!
Wait...you heat it up and it works?
Could it be the multicore powersave?
(Saves energy shutting off cores)
Sent from my GT-I9300 using XDA-Developers mobile app
Problem found
Hello guys i found a temporary fix for this problem i think its a software bug, a cpu gouvernor related bug.
What i did ??
I flashed a custom rom based on mashmallow then i flashed hacker kernel i tried changing different kernel settings but it didnt fix the problem...what it actually worked was changing the cpu governor from the stock interactive to ondemandplus and the problem never came back ! Please try that and get back to me
PSndemandplus governor drains battery more than stock interactive because it keeps the cpu cores awake.