After the ROM upgrade to the latest stock version (BLFB) I ceased to operate the "device nearby" function. It is simply not active all the time and cannot be clicked.
I did wipe the cache already and Dalvik cache ... I also have installed ROM from scratch again but no result.
When I did downgrade to previous version (ALF2) - everything was OK, but after flashing to the latest - the function is inactive again.
After asking other people using this update it seems that there is no problem with this function in general i was just prompted to wait 5 seconds untill it became clickable but it wont work.
Related
I used a few versions of Lite-ning ROM successfully without problems... on one occasion I unfortunately neglected to put it on USB debugging mode and went ahead and flashed via Odin as normal...
At the time, I started to get force closed in so many applications (stock email was the worst)... I flashed it again correctly but still had lots of them
I have since tried other ROMs which has reduced the frequency but not entirely... as a last resort have now done a full factory wipe/reset followed by using Exynos 3.0 however I still seem to be getting quite a few force closes... it mostly seems to be when filling in a form or typing message etc, if I move the cursor and hit backspace it just force closes which ever app i am in...
How can I resolve this permanently? Do I need to wipe and flash an official firmware version? Would XXKG3 be ok even though its beta? Cheers
Would XXKG3 be ok even though its beta Who says ???
Use recovery wipe cache factory reset wipe Dalvik . Mounts and storage format system data etc .
Use Odin to flash a stock rom should clear up problems .
I never use USB debugging mode with ODIN 500+ flashes .
jje
Thanks for the advice... Lite-ning ROM instructions state to put it in debugging mode, I assumed having skipped that step it might be the cause?
The site I found the offical KG3 firmware on stated it was beta and might be bugs...
Will try what you advise anyway, thanks for your help!
Hello
I ported the JoyOS from ZTE to the SGP4.
I used the lastet beta of cm7.2.
Known issues of CM7:
Reboot into recovery does not work yet
Setup wizard doesn't run properly, just skip it
Bluetooth won't scan properly
Deep sleep is still disabled
Installation:
Originally Posted by tdmcode
When you install the ROM, the first thing it will do is flash the kernel and backup your data (efs, dbdata, data, cache). Then it will reboot.
Note I don't have it set to automatically reboot into recovery yet, so you'll have to hold VOL+UP to get back into recovery in the new kernel. Note the strange looking initlogo -- I haven't figured out why the framebuffer format isn't correct. Just ignore it for now.
Aot this point, the system doesn't know whether the device is US or INTL because efs has not been restored. So the home key won't work on US devices. Use the menu key to select.
Now install the ROM again. This time it will restore the data directly on MTD/yaffs2 and do the actual install. When it's done, reboot. You should have a functional system and the home key should work on US devices again, since the efs data is now available again.
Finally, wipe data and cache.
Click to expand...
Click to collapse
Download
Nice to see yet another ported ROM from you! One more, and you will have surpassed all the 4.0 Roms combined (sgs ports excluded). Keep up the good work chaoschris!
Awesome rom you have there. I don't have a SGP4 but keep up with the good work. I like your Google Doc/Drive storage.
Dude, your spitting out roms left and right! Keep it up!
Sent using Tapatalk
im using carbon rom on my xperia s. i clicked on the update section in the settings and says it is up to date. when i looked at the forums it is already updated and my beta version is already outdated. do i need to do a manual update? and how?
yunamunchy said:
im using carbon rom on my xperia s. i clicked on the update section in the settings and says it is up to date. when i looked at the forums it is already updated and my beta version is already outdated. do i need to do a manual update? and how?
Click to expand...
Click to collapse
Could be the OTA Updater is broken, or they have not uploaded it to their servers to push the OTA out. Whether or not you NEED to depends on if you are having issues that should be fixed in the update or there are some new features that are listed in the Changelog for the update that you want to try. The installation instructions are right on the first post of the first page of the thread for Carbon Rom here on XDA. Download. Backup. Wipe. Install Rom+Gapps. Reboot. If you want, you can try and be lazy and just wipe the cache and dalvik cache then install the rom and gapps without factory resetting. Benefit: Not needing to reset up phone completely - called dirty flashing. Downside: You can't complain or report issues if you dirty flash. You have to wipe and reinstall rom and then have the same exact issue to make sure it's not an problem with leftover data that is corrupted or otherwise interfering with normal operations.
Hi Guys,
Yesterday I had flashed my Galaxy S3 i9300 with a custom ROM from Flashing Droid. below is the link to it.
http://forum.xda-developers.com/galaxy-s3/development/rom-flashingdroid-v2-2-gs5-bug-fix-t2767784
After the flashing, the device worked well for sometime. Then i Started facing below issues.
1. Keyboard gets minimized while typing and doesn't come up. Noticed one thing during this is that my notification panel keeps refreshing.
2. Device hangs for sometime then resumes. Need to restart the device sometimes.
3. To open any app it takes time - message, call, settings, it is not as fast it is shown in the review video on the above link.
4. Music Player stops suddenly and while playing the tracks stick for a second in between multiple times.
5. Video Recording doesn't work and gives a failure message after few seconds.
6. Cannot turn off mobile data from the notification panel.
7. Also i am not able to change the clock speed of the processor.
Before flashing i ensured i had wiped the device, cleared the cache and followed the exact procedure as mentioned.
i have restarted the device almost 10 times since the flashing of the ROM. In fact i had flashed twice yesterday since it did not restore my contacts and messaged during the 1st restore option.
please help me understand what did i do wrong and please help me solving this issue. Do i need to reflash it?
What rom are you coming from?
Did you do a complete clean install?
What process did you follow?
Darke5tShad0w said:
What rom are you coming from?
Did you do a complete clean install?
What process did you follow?
Click to expand...
Click to collapse
I am coming from Stock ROM Jelly Bean 4.3. Yes I did a complete clean install. Followed the entire procedure as mentioned on the thread.
I am using CWM recovery. Did wipe factory/data reset. wiped cache and dalvik cache a few times before flashing. Then installed the ROM from the sdcard.
Yesterday the device was hanging every now and then. Later at night i decided to install some other ROM i.e GlamourzS4 which again didn't work at all. Followed the same procedure as above. The installation was successful. But the after rebooting I could only the 1st flash screen i.e. device model no. and thats it - the device goes blank. i waited for more than 30 minutes. Later I again reflashed it to Android Revolution HD 52.0 - a custom JellyBean Rom. Lets see how it works.
Hi everybody,
I'm using a Redmi Note2 Prime with MIUI 8 7.4.27 Beta (weekly). The phone was running very smooth, fast and reliable - battery life was always several days.
Yesterday I tried to root it using method 4 from here using recovery.img from TWRP 3.0.2-2.zip and UPDATE-SuperSU-v2.79-20161211114519.zip (SuperSU app was already installed). After several attempts (installed MI PC Suite twice until it worked on Win10) it finally worked.
I rooted since I wanted to try dual boot patcher and a MM ROM as second.
But after phone booted again it was nearly unusable. No smooth reaction I had to wait several seconds until screens changes when just scroll through them. Also apps and settings now need lots of time more before they start. Wifi is always turned off after reboot (while it was on during shutdown) and Google sync starts automatically after reboot while it is deactivated in all settings. Also background image of lock screen was changed. Google Play Services are now constantly crashing (need to click away these message requesters all the time) and Play Store does not even start anymore. Meanwhile I removed SuperSU app again since it never asked for granting root access while it was set to do so.
Installing a second ROM using Dual Boot Patcher finally also did not work (patching worked - installing not). Details are provided here.
I am still puzzled what happened here and do not have any clue since I rooted already several devices without any problems so far. Even this one some time ago IIRC.
Does anybody have any idea how I can get the phone back into a stable, usable mode? Do I have to completely reflash the MIUI8 ROM? Or do I have to use another SuperSU zip?
Any help is highly appreciated!
Thanks guys!
You can try wiping data/factory reset.
To easily install TWRP, you can use the Fastboot Install Method described here:
https://twrp.me/devices/xiaomiredminote2.html
Thanks. But doesn't this wipe/reset delete all apps and data (which I try to avoid)?
Would reflashing complete MIUI8 (version which I already have installed - without any system/data wipe) cure the problem?
TWRP app is already installed - but either TWRP recovery or SuperSU.zip crashed the Google Services (Play Services or even more) for whatever reason.
Does anybody have some idea why this might have happened? Maybe due to dalvik cache wipe which was requested?
I think that the phone become unusable a Google Services/Play Services is crashing because of wrong settings or data corruption.
That's why I said to do a factory reset.
You can try deleting just cache and data for Google Play Services and Google Play Store apps. Data are on cloud and should be restored automatically when needed.
Seems I got it working again - thanks to post #2. Used TWRP app to install another TWRP, afterwards I got a reboot loop. Then I deleted cache and dalvik cache and now everything works fine again!
Thank you!
Well Dual Boot still does not work but progressed a little bit further - but this is a different topic.
Try do delete your Rom (Backup all with Titanium backup before) and try to install latest Dev from mi-globe ! Prerootet and very smooth and good ROMs!
Thanks. But as said - got it working again (see above). The only thing which is not working is flashing a secondary ROM using Dual Boot Patcher (already opened another thread and posted it into the PATHCER thread - but seems nobody knows about some solution...).