Database Develop

[ROM][Pre-Pre-ALPHA] Droid A855 ICS Build Attempt

new build: http://www.mediafire.com/file/guo6leourklgzgq/cm-9-20120703-UNOFFICIAL-sholes.zip
gapps: http://www.mediafire.com/?ax46kp0yrl85ynn
___________
Don't flash any other kernels. they won't work.
changes:
hexed defy camera libs
HD profile 854x480 green lines in gallery, plays fine on pc
SD profile 640x480, plays fine via gallery
* camera saving null jpegs fixed
* camcorder working
* enabled TLS register user in kernel and userspace
* enabled 1% battery charge display
* lid switch reporting fixed again (haha)
* updated wifi drivers and firmware
* usb storage and adb work
* probably something i forgot
compiled kernel with gcc4.5, userland with linaro gcc 4.7 and -O3
still broken:
camera flash
gps (it was working before. RDS_SOCKET permission issue??)
speakerphone and bluetooth mic routing
HW decode
native tethering
if you like my works, feel free to buy me a beer

Validating file 'device/motorola/sholes/sholes-keypad.kcm'...
No errors.
made a new kcm file according to googles migrating to ICS docs.
also hacked nf_qtaguid from googles ICS kernel into 2.6.32, it probably won't work right though

progress update
MMS is working. alos noticed that red and blue are swapped.
starting pvrsrv via init.sholes.rc causes graphics to be black.
starting after boot via adb doesn't. weird.

You sir, are my hero, even if it's not fully functional you have made it farther than anyone else, so far only one other person has tried over on droid forums and he gave up so far

sdcard works, adb root doesnt. teh process never respawns probably usb related.

so I booted it up and was confused at first by the lack of touch screen and yellow colors

I'm trying to get teh ts working still, using this changeset as a guide
https://github.com/Evervolv-ICS/and...3e2048019764a298ae9e6b6aad02ff52d75453#diff-1

Any progress in ICS should be appreciated!
Looking forward to ICS for milestone.

new build, touchscreen fixed.
bootanimation is disabled for testing.
keyboard is still weird, alt and B keys aren't working
www.mediafire.com/?k4c4mhb8pq37gjj
also, for a good laugh check settings->apps->running->memory
http://www.mediafire.com/?m3yjdp2e329cknb
boot_EGL_broken.img -<only difference is this starts pvrsrvinit in init.sholes.rc
i tried with and without gralloc.omap3.so in /system/lib
boot.img can be flashed easily like this:
[email protected]:~/android/kernel$ ~/Desktop/sbf_flash -f -r --boot ~/Desktop/build/boot.img --recovery ~/Desktop/recovery-clockwork-2.5.0.1-sholes.img ~/Desktop/MC1_A855_1282081087_Recovery-Only_SPRecovery_0.99.3b.sbf
if installing gingerbread gapps do this through adb:
255|[email protected]:/ # mount -oremount,rw /dev/block/mtdblock4 /system
[email protected]:/ # rm /system/app/SetupWizard.apk

You are a monster, you are making great progress I'm going to half to load your latest build up later
Sent from my CushZero using XDA App

is that also for milestone
thx

So I flashed your newest build and stayed on it for 20 minutes exploring everything now that the touch screen was working.

I installed it on my droid. Very nice progress you have going on here. A lot of things work and of course a lot don't. For people who are too afraid to flash, heres a list of what I noticed is working.
Working:
Phone Calls (Speakers don't work)
SMS
3G works great
touchscreen
sms
downloads from browser (installed facebook.apk but couldn't log in because alt key doesn't work on keyboard)
doesn't work:
screen properly, no blue, the yellow looks kinda cool though
screen orientation, to get portrait view you need to slide out the keyboard otherwise its stuck in landscape mode
no onscreen keyboard, only physical works, except like mentioned alt and b dont for some reason
wifi wont turn on
bluetooth wont turn on
gps, couldn't find on googles homepage but browser still works without it
camera
usb doesnt work, mac won't detect it at least when i plug it in
network doesn't display proper network, T-CDMA 64 instead of Verizon
music app doesn't work, its froyo's music app, i think its because the speaker doesn't work not certain
no vibrate mode? only silent mode and ringer doesnt work
neither speakers work, nor does the microphone i believe
anything else i mightve missed probably doesn't work
overall this is amazing progress and it really doesn't run that bad. give it a shot and play around with it for a few minutes, just don't forget to nandroid!

Ammika13 said:
I installed it on my droid. Very nice progress you have going on here. A lot of things work and of course a lot don't. For people who are too afraid to flash, heres a list of what I noticed is working.
Working:
Phone Calls (Speakers don't work)
SMS
3G works great
touchscreen
sms
downloads from browser (installed facebook.apk but couldn't log in because alt key doesn't work on keyboard)
doesn't work:
screen properly, no blue, the yellow looks kinda cool though
screen orientation, to get portrait view you need to slide out the keyboard otherwise its stuck in landscape mode
no onscreen keyboard, only physical works, except like mentioned alt and b dont for some reason
gps, couldn't find on googles homepage but browser still works without it
camera
usb doesnt work, mac won't detect it at least when i plug it in
network doesn't display proper network, T-CDMA 64 instead of Verizon
music app doesn't work, its froyo's music app, i think its because the speaker doesn't work not certain
no vibrate mode? only silent mode and ringer doesnt work
neither speakers work, nor does the microphone i believe
anything else i mightve missed probably doesn't work
overall this is amazing progress and it really doesn't run that bad. give it a shot and play around with it for a few minutes, just don't forget to nandroid!
Click to expand...
Click to collapse
also no hardware acceleration, screenshot force closes the UI. but it is much smoother than I thought this really proves to all those people saying that ICS wouldn't work at all, someone has it booted, I can't wait to see the progress this guy can make. so far he is doing an extremely good job.

durandgir said:
also no hardware acceleration, screenshot force closes the UI. but it is much smoother than I thought this really proves to all those people saying that ICS wouldn't work at all, someone has it booted, I can't wait to see the progress this guy can make. so far he is doing an extremely good job.
Click to expand...
Click to collapse
whats the button combo for screenshot? i tried volume up+power and volume down + power, neither did anything i just couldnt remember what it is for nexus

I'm pretty sure i'ts power button+down

Some of these problems are simple:
Rotation error is /data/system permission error
Adding this to init.sholes.rc fixes it
Chmod 775 /data/system
Alt and b problems are errors in /system/usr/keychars/sholes-keypad.kcm
The patch I used to fix graphics has a define to ovverride EGL config, this might fiz colors
I've seen several patches for legacy audio support floating around, haven't tried any yet.
Virtual keyboard missing is because sholes device makefile inherits from core.mk instead of one of the more complete ones. A complete build will require a larger system partition or other trickery.
Other things will probably be harder

Some of these problems are simple:
Rotation error is /data/system permission error
Adding this to init.sholes.rc fixes it
Chmod 775 /data/system
Alt and b problems are errors in /system/usr/keychars/sholes-keypad.kcm
The patch I used to fix graphics has a define to ovverride EGL config, this might fiz colors
I've seen several patches for legacy audio support floating around, haven't tried any yet.
Virtual keyboard missing is because sholes device makefile inherits from core.mk instead of one of the more complete ones. A complete build will require a larger system partition or other trickery.
Other things will probably be harder

something else I noticed with signal and data, it stayed gray. but other than a few quirks it's still impressive I don't stay on it because I only have one phone but I can't help but to flash just to mess around with it

I Love You

Rom cm11 xperia v lt25i - q&a, discussion, etc..

Greetings, i open a new discussion and Q&A thread as i notice many has spam the cm11 development thread. Also as there is no other thread open for Xperia V regarding of cm11 in this section so i might just open a thread so we can discuss our problem here, and leave the development thread clean for our device maintainers.
PLEASE, PLEASE, PLEASE, move to this thread to discuss problem, bug, and many others problems at here, only post to development thread if you have found a solution.
THANK YOU...

Does somebody encounters the lost sound after using phone for long time?
I notice my V running CM11 have this problem randomly, some time the sound just disappear, and there is no sound if somebody is calling, or message me..weird....

davidtkf88 said:
Does somebody encounters the lost sound after using phone for long time?
I notice my V running CM11 have this problem randomly, some time the sound just disappear, and there is no sound if somebody is calling, or message me..weird....
Click to expand...
Click to collapse
just notice the problem, whenever i adjust my clock manually (cause i play game) the ringtone and notification will randomly go out, and reboot will bring back the sound again, the in game music/sound does not get infected..sound bug maybe??

Using 20140107 nightlies till now, so far all is fine, except for camera, the picture taken is a little yellowish..i have change to Camera JB+, and the picture seem better compare to stock camera app

For those that using CM Gapps, PA Gapps, or others, you can go to( http://forum.xda-developers.com/showthread.php?t=2012857 ) as the Gapps provided is really up to date, and most of all, the General Package is ART Runtime compatible, at least i have no problem till now
The Credit goes to BaNkS for sharing this wonderful Gapps..

battery drains quite fast. That's the only problem for me.

cnkhanh said:
battery drains quite fast. That's the only problem for me.
Click to expand...
Click to collapse
if compare with cm10.1 and 10.2, the battery drain problem is really much improved..i cannot go full day with cm10.1, 10.2, but in cm11 i can last till 11pm and charge when go to bed..

On nightlies 20140111 ART suddenly increase the random reboot, have to roll back to Dalvik also, i notice the transparency notification bar introduce since CM11 also cause random reboot, have to use other launcher ( APEX,Nova ) and disable transparency to get stable daily use..( APEX not ART compatible ) will try other setting see can get less random reboot or not

Since i saw many talking about wifi connection on few latest nightlies, i decided to try configure my wifi setting on both router and phone, my router setting only support 2.4ghz wireless n connection max( D-Link DSL-2750e ), so i configure my phone with the same frequency..
And to my notice, the wifi connection is indeed not stable, i get a lot of disconnection whenever i go far with my router, like going up stair, no problem with my laptop, but if i set my frequency band to auto, the problem gone..
Changing security key either WEP, WPA, WPA2, i did not notice any difference, but if i choose WPA, WPA2 with combination of TKIP or AES, problem occur, my phone wifi will spend lot of time on authenticating and hard to get a connection, and if i choose auto mode, problem gone..
So to my conclusion, best setting for router is use:
Wireless Mode: 802.11n
Channel: 1-11
Authentication Type: WPA2-PSK / WPA-PSK
Encryption: AUTO
Phone wifi setting:
Leave the setting intact, with all AUTO for best performance..

After trying many other setting and apps on the 20140111 nightlies build, i found out condition that will increase changes for blue screen reboot, i test it with ART enabled, here is what i found:
- Transparency Notification Bar ( When entering app, the notification bar will become solid, and when exiting app, just after the transparency bar return, reboot occur. Use Nova launcher, close the Transparency bar setting, no random reboot again )
- Live Wallpaper ( try many live wallpaper, all the same result, increase random reboot. Use normal wallpaper the problem gone )
- Apps that access Camera ( Whenever apps want to access the camera, some time it will cause reboot )
- Set CPU ( Don't set cpu frequency for apps, as this result many random reboot, set min/max have no problem )
- Bluetooth ( use A2DP and transfer file at the same time, random reboot increase. If just listen to music, or transfer file at a time, no problem )
Well, this is what i found during my test, i notice under ART, many apps that i use always FC. The other day when i switch back to Dalvik, the apps is running fine, miss the feeling with no FCs..but app really snappy under ART, hope app dev can support more ART at future..
Also, when i use Dalvik, no matter what app i open and close, there is not a single reboot for a whole day, ART does some time have reboot, maybe this will be fixed when ART get stable..

Uploaded.net
People who have trouble downloading from Uploaded.net can use the following info:
Google Generator link premium
Open the first link in the list
Paste the uploaded.net file link
In the link instead of "http://" type "https://"
Type the code
Hit Generate
Download the file

[Q] Xperia T automatically crashes all foreground apps

The issue started as a result of a crash while my phone was moving newly updated apps from the internal storage into /system (an option commonly known as Move Into System ROM). The next time I restarted the phone, and ever thereafter, the phone will not properly load the home launcher. The screen is black besides the notification bar, which I can also extend to fill the screen. Every app I manage to initiate immediately crashes. Mind you, I can only attempt to open Settings from within the notification bar and any of the apps from the Small Apps Launcher. Interesting enough, it looks like all background processes are working fine. I see the usual notifications for phone calls, texts, emails, app updates, etc. in the notification bar. As well, when I bring the notification bar down to fill the screen, the main screen will appear in the background, and go to black again when I minimize the notification bar again.
I have restarted the phone numerous times, including several hard resets, to no avail. With no other options in sight, I decided I needed to just re-flash the phone clean and go from there. The phone is no longer detectable by any pc running Windows 7/8 or Linux. I tried PC Companion, Sony Update Service (they only support the Z series now, terrible decision by Sony), Emma, Flashtool, etc. all using the latest Android SDK, and a few miscellaneous tools that used their own copy of adb. I also ran some commands directly on the adb daemon, and it does not see the device as well.
This is quite frustrating knowing that the hardware is just fine, software runs in the background, yet regardless the phone is rendered non-functional because of some lousy software hiccup.

sebzag said:
The issue started as a result of a crash while my phone was moving newly updated apps from the internal storage into /system (an option commonly known as Move Into System ROM). The next time I restarted the phone, and ever thereafter, the phone will not properly load the home launcher. The screen is black besides the notification bar, which I can also extend to fill the screen. Every app I manage to initiate immediately crashes. Mind you, I can only attempt to open Settings from within the notification bar and any of the apps from the Small Apps Launcher. Interesting enough, it looks like all background processes are working fine. I see the usual notifications for phone calls, texts, emails, app updates, etc. in the notification bar. As well, when I bring the notification bar down to fill the screen, the main screen will appear in the background, and go to black again when I minimize the notification bar again.
I have restarted the phone numerous times, including several hard resets, to no avail. With no other options in sight, I decided I needed to just re-flash the phone clean and go from there. The phone is no longer detectable by any pc running Windows 7/8 or Linux. I tried PC Companion, Sony Update Service (they only support the Z series now, terrible decision by Sony), Emma, Flashtool, etc. all using the latest Android SDK, and a few miscellaneous tools that used their own copy of adb. I also ran some commands directly on the adb daemon, and it does not see the device as well.
This is quite frustrating knowing that the hardware is just fine, software runs in the background, yet regardless the phone is rendered non-functional because of some lousy software hiccup.
Click to expand...
Click to collapse
Do you have an installed recovery?

St.Jimmy90 said:
Do you have an installed recovery?
Click to expand...
Click to collapse
Ah, I forgot to mention the phone was rooted with CWM for Locked Bootloaders. And no, I cannot access recovery whatsoever, for some odd reason. The blue recovery light does not show either.

I read somewhere that the touch interface, I believe it's called Timescape UI, might be the culprit. Anyone have any thoughts?

bump

did you move your apps to the internal memory or to the sd card?
after 4.3 update I read a lot of sd killed by the os, I suffered of that, so when the sd crash all the app moved to it will crash...

[Ref] Google Nexus 5 tips & tricks with important info to know

Hello everyone, i see here to collect and post some known and maybe unknown tips and tricks with some important information, hoping this will be useful for noob users.
Any more tips, tricks and suggestions from users are always welcomed. And please feel free to make corrections for any wrong or missed information in this post
{
"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"
}
Preface:​
The Nexus 5 (codenamed Hammerhead) is a smartphone co-developed by Google and LG Electronics that runs the Android operating system. The successor to the Nexus 4, the device is the fifth smartphone in the Google Nexus series, a family of Android consumer devices marketed by Google and built by an original equipment manufacturer partner. The Nexus 5 was unveiled on 31 October 2013, and released in black and white colors (and lately in red) the same day for online purchase on Google Play, in selected countries.
The Nexus 5's hardware is similar to that of the LG G2, with a Snapdragon 800 system-on-chip (SoC), and a 4.95-inch 1080p display. The Nexus 5 is also the first device to feature version 4.4 of Android.
As of December 2013, a revised version of the Nexus 5 became available, featuring bigger speaker and microphone holes to allow louder audio, and better fitted buttons and SIM card tray.
Nexus 5 is the first Android device to ship with Android 4.4 "KitKat", which has a refreshed interface, improved performance, improved NFC support (such as the ability to emulate a smart card), a new "HDR+" camera shooting mode, native printing functionality, a screen recording utility, and other new and improved functionality.
The device also ships with Google Now Launcher, a redesigned home screen which allows users to quickly access Google Now on a dedicated page, and allows voice search to be activated on the home screen with a voice command.​
OTA 4.4.3 (KTU84M)
OTA 4.4.4 (KTU84P)​
Below is a quick list of all the changes that Google has made with the Android 4.4.3 update and which are clearly visible on the Nexus 5:
-A tweaked Dialer app with a colored Action bar.
-People’s app now placeholder images are now similar to that one used by Gmail.
-Fix for mm-qcamera-daemon bug. (not been fixed properly, as reported by some users).
-The ability to pause a download of additional files required by large games on the Play Store.
-The hissing sound while recording videos on the Nexus 5 is fixed. However, there is now a strange echo in the recorded audio.
-Fix for LTE connection dropping bug.
-Lot of other under-the-hood camera, Bluetooth and other system related bug-fixes.
-LED notifications are still not working for missed calls.
-Fixes of some security issues, small changes to the Chromium web browser and WebView (4.4.4)
Source​​
Questions & Answers​
Q1) Can i make a screen shot on stock firmware?
A Yes you can! user doesn’t need to root the device or employ third-party apps just to take a photo of what's happening on screen. Taking a screenshot is simple, just press the volume down and power buttons together. The device will quickly take a snapshot of the screen and you will find it in your notifications.
Q2) What is Barrel Roll?
A As part of Google's regular antics, it had introduced a "barrel roll" trick for desktop browsers. Type "do a barrel roll" as a search term, and Google would demonstrate the power of modern browsers by flipping everything around on your screen. Your Android device can also do a barrel roll if you speak out the same command. Again, It's great fun to show off.
Q3) How can i uninstall an app. without going to setting?
A Long-pressing on an app within the app drawer pops up a couple of menus along the top of the screen. App Info gives you the boring technical stuff about how much memory it's taking up, or you can fling it off the other way to uninstall it.
Q4) How can i go directly to the quick settings menu?
A expand notification bar by sliding two fingers.
Q5) How to control music from the lockscreen?
A If you’re using Play Music you’ll see music controls and full screen album art on the lockscreen. You can skip tracks and pause in here, but you can also now scrub (skip within a song) through tracks by holding one of the music controls to get the track preview to pop up and then dragging the circle to where you want to play.
Q6) How to add widgets to the lockscreen?
A If you just slide left on the lockscreen you’ll see the option to add widgets, so you can glance at your email, or see the latest tweets, without having to unlock your Nexus 5. Remember that you’ll have to enable widgets via Settings > Security > Enable widgets first.
Q7) What is inverted rendering?
A Inverted rendering is a posh way of saying it makes the pages black and turns the text white, so it looks like you're reading the internet from 1997. It also supposedly saves battery, plus is easier on the eyes if you're reading in the dark. It's under the browser's settings tab, within the accessibility area - and there's a contrast slider, too.
Q8) How can i reboot into safe mode?
A Safe mode, the savior of so many Windows PCs! If you are experiencing a problem with your N5 and you want to determine whether it is being caused by a third-party app, long-press the power button, then long-press the Power off option. Choose OK to reboot in safe mode, which completely disables all third-party apps on your device. If the problem goes away when you’re in safe mode, you should reboot your device and start removing recently installed apps until the problem goes away.
Q9) What does reset app. preferences means?
A Android gives you loads of different options for each installed app, and on the whole this is a very good thing. Sometimes it can be a bad thing, though: you may find your phone playing up because a crucial app has been disabled, or you've changed the notifications for something important like emails. In the apps drawer, you'll find Reset app preferences under the settings. This resets all your apps on a global level, returning actions and data settings to their original levels.
Q10) How to Use Emoji in the Android 4.4 KitKat Keyboard?
A Emoji, Japanese pictographs and smileys commonly used to convey letters and words in electronic messages, are becoming more mainstream for smartphone users. Historically, Android users had to download a separate app from the app store and add it as a keyboard “language” in order to use emoji. With Android 4.4 KitKat, Google has built emoji into the default Android keyboard, making it easy to communicate with these pictorial tools.
- Open Google Hangouts.
- Tap “Send a Message” within a conversation.
- Tap the Smiley Face button in the bottom-right hand corner of the numeric keyboard.
- Tap the Icons in the black bar at the top of the emoji keyboard to scroll through different types of emoji. Each section has several pages of emoji to choose from.
- Tap an Emoji to add it to your message, then click send to transmit that emoji to your contact.
Q11) I can not see messaging application?
A Hangouts application, which now supports text messaging, is used as the default text messaging application.
Q12) How to capture photos while recording?
A The Nexus 5, like nearly any device capable of capturing video, has little trouble capturing still images while recording video. Simply tap the screen while recording a video to capture a photo, which your smartphone will then instantly save in your photo gallery as the camera continues to record.
Q13) I can not see Developer Options in settings?
A Google hide this option, to enable it just go to settings---->about phone, tap 7 times on "build number" and it will be shown in settings.
Q14) What is ART runtime?
A Android uses something called Dalvik to run apps. Dalvik works by compiling an app each time it is running, which minimizes installation times and disk usage, but also makes apps slower to start up. In Android 4.4, there’s now an alternative – ART.
ART instead compiles all apps before execution, allowing them to start more quickly and get things done faster, it can also improve battery life. ART is still experimental. You can try enabling it in Developer Options. If any app doesn’t work, it’s easy to switch back to Dalvik again.
Q15) ADB can not recognize my N5. What should I do?
A Download and install Android SDK, if you already have it on your PC just update tools and platform-tools. you must have latest ADB version. If you do not want to install Android SDK, download attached file.
Q16) How can i make my N5 feel snappier?
A By speeding up (or disabling) the animated fade-in effects you see when switching between tasks, you’ll see a boost in performance and faster screen transitions. Start by unhiding “Developer options” as described above. Once in “Developer options,” scroll down to the “Window animation scale” and “Transition animation scale” options and set both to .5x. You can even turn each of these off and transitioning between apps and pages will be almost instant. If you ever want to go back, remember the defaults for both of these settings are 1x.
Q17) How can i improve my gaming graphics?
A If you are a hard-core gamer, you probably already know what 4x anti-aliasing is. First, enable Developer Options as described above, then go to Settings and click on Developer Options and enable Force 4x MSAA. Multisample anti-aliasing (MSAA) is a technique used to improve image quality. Since the N5 has a GPU capable of supporting MSAA, this setting should make your graphics look more detailed when you are playing advanced games. Keep in mind this will also cause your GPU to work harder and your device may get hotter and consume more power than normal. It’s also possible that all games may not support this.
Q18) I want to see "KitKat" on my screen, can i?
A Yes you can, go to settings---->about phone tap quickly 4-5 times on android version, then touch and hold, you will see the KitKat logo.
Q19) 2 new sensors on my Nexus 5??
A Android 4.4 supports two new types of sensors – step counters and step detectors. So far only two apps are optimized for the Nexus 5 Moves & Runtastic Pedometer.
Q20) How can i customize my LED notifications?
A A free app called Light Flow Lite allows you to take control of the colors of your notification LED. It also makes your N5 flash one color after another. This app allows you to set the notification color for over 250 applications and system events including missed calls, low battery, no signal, voice mail, calendar reminders, Gmail messages, email messages, SMS messages, MMS messages, Twitter notifications and more.
Q21) How can i put my N5 in fastboot/recovery mode?
A Turn off your phone, press and hold down Volume Down + Power button at the same time until fastboot (bootloader) mode (image of an Android with Start) appears then release the keys. Press volume up or down and select recovery by pressing power button. (For stock recovery, when you see an android logo with exclamation mark, press volume up to see the recovery menu).
Q22) How can i put my N5 in download mode (for LG flashtool)?
A Turn off your phone, hold volume up and plug your usb cable into pc while holding the volume button.
Q23) How to wirelessly charge my N5?
A In case you didn’t know already, the Nexus 5 comes equipped for charge wirelessly right out of the box. Consider purchasing a magnetic Wireless Charger to utilize the feature, and if bought, place the smartphone directly atop the device for wireless charging.
Q24) My N5 screen is turning on by itself, what is happening?
A It is caused by an application, usually by live wallpapers, try to find it and delete it, or install an antivirus app., there is a lot of antivirus apps available (avast, eset, ....). Personally i recommend Dr.Web Anti-virus, scan, delete, wipe cache and dalvik (optional).
Q25) sometimes i lose packet data, i reboot my N5 to enable packet data again?
A There is no need to turn your phone off and on to re-enable packet data, just long press on power button, enable airplane mode for 3-5 seconds then disable it.
Q26) I rooted my N5, what to do next?
A It is recommended to make a nandroid backup immediately.
Q27) I rooted my N5, made a nandroid backup, but i can not find my backup folder?
A If you used cwm recovery, with any root manager, enable root option, your backup folder is located in data/media/clockworkmod or mnt/shell/emulated/clockwordmod.
If you used TWRP, your backup is located in sdcard/twrp/backups/serial number.
Q28) The kernel does not support "Sweep2Wake" or "DoubleTap2Wake", is there a solution?
A change the kernel, or install intellicover application.
Q29) Do i need to wipe cache partition when flashing a new custom rom?
A No, there is no need to wipe cache, because when you wipe data/factory reset, cache is wiped automatically. i see to wipe cache and dalvik after flashing a new custom rom.
Q30) Do i need to wipe cache partition before flashing a new Kernel?
A No, there is no need to wipe cache, boot partition has nothing to do with cache.
Q31) What about my N5 storage?
A See @rootSU thread.
Q32) My N5 won't start, i can not get into fastboot mode, only i can get into download mode?
A Take a look here.
Q33) What is the easiest way to install driver?
A Take a look here.
Q34) How to install driver on window 8?
A See @efrant post.
Q35) How can i flash stock image on my N5?
A See @abaaaabbbb63 thread.
Q36) How to properly post a kernel bug (LAST_KMSG)?
A See @ciprianruse88 thread.
Q37) What is the best kernel/Rom for my N5?
A There is no something called "best kernel/Rom". You must try many kernels/Rom and decide what suit your rom and your need.
Q38) What is the difference between D820 & D821?
A Things are almost identical. You'll find the same spec sheet for the screen, processor, RAM, sensors, Wifi and everything else. All indications are that both the D820 and D821 run the exact same software build as well. The only tangible difference between the two models is mobile network bands. D820 for North America, D821 for the rest of the world.
Q39) What is the difference between CAF & AOSP?
A Actually, there are two main baselines for support of Qualcomm devices:
-CodeAurora (CAF) - These are Qualcomm's reference sources for their platform. This is what they provide to OEMs, and what nearly all OEMs base their software off of. As a result - nearly all non-Nexus devices are running kernels/display HALs/etc. that are derived from a CAF baseline.
-Google's software baseline, or AOSP - Usually when Google starts working on a new Android version, they'll fork from CAF at the beginning. Very often Google will be adding "new" features specific to the new Android version, while Qualcomm will continue with performance enhancements and bugfixes against the "old" baseline.
*So when a new Android revision comes out, you have two baselines: CAF which is usually "ahead" in performance but "behind" in features, and AOSP which is the opposite.
Starting with 4.3, CM started mixing code between CAF and AOSP. They put some CAF features/capabilities into their baselines for AOSP-supported devices (Nexus devices), and started putting AOSP patches into their baselines for CAF devices.
Beware when flashing custom kernels. A CAF based kernel is not compatible with AOSP based Rom and vice versa.​
Rooting:​
Rooting is often performed with the goal of overcoming limitations that carriers and hardware manufacturers put on some devices, resulting in the ability to alter or replace system applications and settings, run specialized apps that require administrator-level permissions, or perform other operations that are otherwise inaccessible to a normal Android user. Rooting is similar to jailbreaking devices running the Apple iOS operating system. On Android, rooting can also facilitate the complete removal and replacement of the device's operating system, usually with a more recent release of its current operating system. Rooting enables all the user-installed applications to run privileged commands that are typically unavailable to the devices in their stock configuration.
Legality: The Free Software Foundation Europe argues that it is legal to root or flash any device. According to the European Directive 1999/44/CE, replacing the original operating system with another does not void the statutory warranty that covers the hardware of the device for two years unless the seller can prove that the modification caused the defect.
On July 26, 2010, the United States announced a new exemption making it officially legal to root a device and run unauthorized third-party applications, as well as the ability to unlock any cell phone for use on multiple carriers.
Safety: I Have always said that the person should learn the Android OS before rooting. It is a good idea to have an idea of what rooting is doing and what it will affect. I would say spend your time really learning the OS which is not a small task. Then, if you still feel like it, go ahead and root. While rooting can help you learn many things about your device, it also can reap very bad consequences, such as:
-Bricking your phone (or in an easier way to explain, making your phone a pretty paper weight).
-Corrupting core files.
-Stopping OTA updates from going to your phone.
-Voiding phone warranty.
-Have your phone open to malicious software and applications that can do serious harm to your phone.
As you can see, it can reap very negative things. I have read/seen people who have literally had to buy brand new phones because they tried the latest and greatest rom. Rooting is essentially something that you must take at your own risk & caution. Generally, if you follow exactly the procedure of rooting made by developers, you will be more likely on the safe side.
Root process: See @Chromium thread.
What to do after rooting?: 1) make a nandroid backup via custom recovery 2) backup efs partition (save your IMEI and NV_DATA):
Install "terminal emulator" from play store, open it and type the following (enter after each line):
Code:
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/modemst1 of=/sdcard/efs1.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/modemst2 of=/sdcard/efs2.img
Then copy/move efs.img to a safe place on your pc.​
Problems can happen:​
-Stuck into a Bootloop: Bootloops are mainly caused by system files interfering with each others which cause instability and/or crash at the boot sequence. so what to do??
Long press on power button then press volume down together, boot into recovery, wipe cache and dalvik, reboot. If not, format data, reboot. if not restore your backup (supposing that you did a nandroid backup before). if you don't have a backup to restore, flash any custom rom from your sdcard after formatting system & data & cache. If you don't have a custom rom in your sdcard, push one from your pc using adb (supposed that you have adb file or sdk on your pc): boot into recovery, connect your phone to the computer open command prompt where your custom rom is present and write the following command then hit enter:
Code:
adb devices
adb push name_of_rom.zip /sdcard/
Then
Code:
adb reboot recovery
once done, go to your phone and install the rom.zip from recovery, reboot.
Or you can use "adb sideload" command: boot into recovery, choose "install zip from sideload", connect your phone to the computer open command prompt where your custom rom is present and write the following command then hit enter:
Code:
adb devices
adb sideload name_of_rom.zip
If none of above methods works, then flash stock image for your N5 using fastboot commands here.
-N5 is quietly dead: If your phone did not respond to anything, it won't turn on, can not boot into fastboot or download mode, black screen, try holding power button for 30 seconds, if not, you need another motherboard.​
N5 secret codes:​
*#*#4636#*#* Testing menu(Phone, Battery & Wifi Info, Usage Statistics).
*#06# MEID number(Display's your IMEI).
*#*#2432546#*#* Checkin(Manually check for System Updates).
*#*#8255#*#* For Google Talk service monitoring.
*#*#786#*#* Hard Reset(Wipes/Resets Data/Profile & internal storage!) (think before you do it! no warning, no go back).
*#*#1234#*#* or *#*#7873778#*#* Open superuser application.
*#123# then press dial. Shows you if you are in your home network or not (only across networks in USA/Canada).​
Recommendations:​
-Too loud wallpapers may sometimes disturb the look of your home screen and make the icons quite invisible, simple or a less-colored wallpapers are always suggested as to be the best choice. But your choice is what matters.
- Use only essential widgets on your home screen - each widget consumes memory and processing power which can slow down your phone.
- Uninstall apps that you don't use - after awhile your phone can get cluttered as some Apps are designed to always run in the background. If you rarely use an App, then uninstall it to free up memory and CPU resource.
- It is best to avoid task killers such as Advanced Task Killer. Android is designed to automatically pre-load certain applications, even if you don't load them yourself. If it starts to run low on memory, it will smartly unload the oldest running apps automatically. Manually killing tasks will only mean they get loaded in memory again. Task killers can make the phone slow, laggy, or drain battery life more quickly.
- Always use latest CWM or latest TWRP recoveries.
- Disable USB debugging when it is not in use. Leaving USB debugging enabled makes your phone vulnerable (e.g. lock pattern can be reset).
- Avoid putting your N5 in direct sunlight, it may affect touch screen & your battery performance.
- Learn how to use ADB & FASTBOOT commands instead of using toolkits, the last could not function properly.
- Check rom/kernel.zip md5 before flashing if it is convenient.
- Always update applications, if available, for better performance.
- Make a backup of your data, applications, contacts...always ready to restore from your computer.
- Read, read and read before you mess with your N5.
- Always be sure that you are flashing the right thing for your N5 variant.
- If you do not know what you are doing, so don't do it .​
Did you finish reading? Press Thanks button & consider Rating the Thread

Backup and Restore your applications and their data + your sdcard​
Backing up your apps and their data and sdcard is an essential process to keep them safe in case something goes wrong with your phone and need to be wiped.
In addition you need to make the backup when flashing new custom roms that need a factory reset before flashing.
There is a lot of apps available on play store that can do the job (Titanium, MyBackup, Helium,....).
But here i would like to show you how to backup and restore your N5 with a well known method (familiar to many users), using "adb" commands. This method is safe, easy, reliable and works on stock and rooted devices.
First you need to have Android SDK installed in your pc, or download the zip attached in first post.
Backup & Restore Apps and Data​
Backup:
Go to Settings>>>>Developer options and enable "usb debugging".
Connect your device to pc.
Open a cmd (shift + mouse right click) in "sdk platform" or in the folder downloaded from OP, and type (ENTER after each command):
Code:
adb devices
You must see your device serial number.
Code:
adb backup -apk -noshared -all -nosystem
Now look at your device and accept backup process.
Wait until finishing.
This will backup your apps and their data to the pc (a "backup.ab" file will be created).
Restore:
Go to Settings>>>>Developer options and enable "usb debugging".
Connect your device to pc.
Open a cmd (shift + mouse right click) in "sdk platform" or in the folder downloaded from OP (the backup.ab file must be there), and type (ENTER after each command):
Code:
adb devices
You must see your device serial number.
Code:
adb restore backup.ab
Now look at your device and accept restore process.
Wait until finishing.
This will restore your apps and their data to device.
Backup & Restore sdcard​
The following processes will backup and restore your whole sdcard, including obb folder, music, pictures, videos,......
Backup:
Go to Settings>>>>Developer options and enable "usb debugging".
Connect your device to pc.
Open a cmd (shift + mouse right click) in "sdk platform" or in the folder downloaded from OP, and type (ENTER after each command):
Code:
adb devices
You must see your device serial number.
Code:
adb pull /sdcard/ /sdcard/
This command will pull your sdcard (not move or cut) to "c" directory under "sdcard" folder.
This process will take time depending on the size of the sdcard, so be patient.
Restore:
Go to Settings>>>>Developer options and enable "usb debugging".
Connect your device to pc.
Open a cmd (shift + mouse right click) where the "sdcard" folder is located in your pc , and type (ENTER after each command):
Code:
adb devices
You must see your device serial number.
Code:
adb push sdcard /sdcard/
This command will push the "sdcard" to your device.
This process will take time depending on the size of the sdcard, so be patient.​
Battery Conservation Tips​
-Enable Auto Brightness: Brightness can lure a lot of battery if not changed intelligently with time to match the surroundings, KitKat in this case brought the “Auto Brightness” function which uses the light sensor within the device to detect the amount of light in the surroundings and then act upon the brightness level according to it. To enable, go to Settings > Device > Display > Brightness, and tick “Automatic Brightness“. And if you want to save more battery drain, set brightness manually at low level depending on the external amount of light.
-Remove Live Wallpapers: Using a live wallpaper is another battery sucking feature. If you turn out to be truly saving battery, make sure not to use any live wallpaper. A wallpaper with a black background uses less power than a wallpaper with a light-colored background.
-Disable Location and GPS services: Keeping GPS ON at all times, decreases your battery life, so its better to disable it while not in use. To disable, go to Settings > Personal > Location access > and switch it off - note that a nice new feature in the Settings menu can save a bit of battery life without sacrificing much at all. Go into the Location option in Settings, then choose ‘Battery Saving’ as your mode instead of ‘High Accuracy’-.
-Disable Wi-Fi or Mobile Data when not in use: Try to avoid situations when you keep your Wifi or Mobile Data ON even when the phone is set in standby.
-Manage Sync carefully: Keeping the Sync ON all the time is another reason for decreased battery life. Enable it anytime you want, manage your emails or services and again turn it off. For those who are on work and want real-time push notifications are advised not to follow this tip.
-Turn OFF Haptic Feedback and screen sounds: To save a little more on battery, its better to switch off the screen touch sounds and vibrations. To do so, go to Settings > Device > Sound and untick Dial pad touch tones, Touch sounds. Screen lock sound and Vibrate on touch.
-Turn OFF bluetooth and NFC: Disabling bluetooth and NFC when you are not using it, is another way to save battery juice.
-Follow the method of full charge and full discharge (almost): Don’t put your phone on charging when there is the battery remaining it for another few hours unless it’s very important. Charge it when your battery is about to get discharged and when you put it for charging, let it get charged totally.
-Set sleep time: Check the Sleep setting (under Display) and make sure it is set to 1 minute or less.
Keep calls short: This is obvious, but how many times have you heard people on their mobile phone say, "I think my battery’s dying," and then continue their conversation for several minutes? Sometimes, the dying battery is just an excuse to get off the phone (and a good one, at that), but if you really need to conserve the battery, limit your talk time.
-Turn OFF mobile network when not in range: Its very often that you lose the mobile network when you are travelling, so its advisable to turn OFF the mobile network by switching ON Airplane mode. Go to Settings > Wireless & Networks, tick Airplane Mode.
-Turn off unnecessary scanning of wifi services by going to Settings - > Wifi - > Bottom right three dots (menu) - > Advanced - > Uncheck scanning always available.
-Turn off unwanted background data by going to Settings - > Data usage - > and restrict background data for unwanted app.
-You should not have to turn off your phone to charge it. Most battery chargers deliver more than enough current to power your phone and charge it at the same time. Doing so will not lengthen the charge time, and leaving a phone on allows the user to be aware of its fuel gauge, so that you can remove it when the battery is full.
-When using a car charger, do not charge the battery when the inside temperature of your car is hot. Wait until the car has cooled before you plug in the phone.​

Really a helpful thread for beginners , good job the only thing I must back talk is " auto brightness saves battery " , set a low manual value saves more battery as Auto brightness ( my feeling )
Tapatalk Team SlimRoms

Tylog said:
Really a helpful thread for beginners , good job the only thing I must back talk is " auto brightness saves battery " , set a low manual value saves more battery as Auto brightness ( my feeling )
Tapatalk Team SlimRoms
Click to expand...
Click to collapse
thx mate, i mentioned also to set it manually for more battery saving :good:

No problem it's good to see people take some time and create such threads. I am sure it will help the one or other guy
Tapatalk Team SlimRoms

Nice! I just noticed this and I was like wait a minute this is new cause I've read all the stickies lol.
Sent from my SPH-D710 using XDA Premium 4 mobile app

Nice one, very helpfull for both newbies and the more advanced users :good:
Maybe you could include a small tutorial for making different logs like last_ksmg or Dmesg, especialy for the kernel devs to pinpoint and solve issues

gee2012 said:
Nice one, very helpfull for both newbies and the more advanced users :good:
Maybe you could include a small tutorial for making different logs like last_ksmg or Dmesg, especialy for the kernel devs to pinpoint and solve issues
Click to expand...
Click to collapse
Thank you mate. I included a link on "how to" post logs for last_ksmg
Sent from my Nexus 5 using XDA Premium 4 mobile app

Great thread. To add to recommendations.
If rooted, use bootlocker app to keep bootloader locked until you need it unlocked and use flashify or similar to keep stick recovery until you need otherwise. This will make your phone a lot less vulnerable to thieves.
Sent from my Nexus 5 using Tapatalk

I would like to add, move to 2G network when using Wifi or voice calls are more important and you ain't doing any related internet activities. Huge save in battery. If you are rooted use xposed and GravityBox to change it in one click.. Or use Tasker to automate such changes. Whatsapp and fb notification works well in 2g data network.
If rooted, use greenify to stop continuous background apps.. (facebook was one of the biggest battery hog due to this). People with lot of newsreader app can be beneficial
Use an anti theft app. If rooted use rooted mode. I prefer avast anti theft.. You can wipe, and lock if stolen, locate it.. It installs with random name, hides itself from application drawer .. On sim change, it sends out notification to pre set alternative number and you can take control of your phone again.. The user will not know anything..
I bought premium licence just to say thanks to avast because I got back my Nexus after 1 month being stolen.. That too without police help and it went 1500km away...(and in India, least help from police about tracing, they just take a formal complain and throw it afterwards..[emoji20]).. I was lucky that last user didn't knew how to flash factory image.. [emoji14]
Sent from my Nexus 5 using Tapatalk

New useful sticky thread! :good:
Explanations well detailed but I'd like to add my 2 cents on a couple of points:
• I'm not sure that Terminal commands are adapted to beginners to I suggest to add thsi zip flashable.
• Q25 you forgot to mention TWRP backups. (/sdcard/TWRP/Backups/Serial number/<HERE>

Primokorn said:
New useful sticky thread! :good:
Explanations well detailed but I'd like to add my 2 cents on a couple of points:
• I'm not sure that Terminal commands are adapted to beginners to I suggest to add thsi zip flashable.
• Q25 you forgot to mention TWRP backups. (/sdcard/TWRP/Backups/Serial number/<HERE>
Click to expand...
Click to collapse
If users who want to mod and flash are not able to use a terminal emulator, they also should not use adb also imo I think you may underestimate the interested user who wants to learn something.

gee2012 said:
If users who want to mod and flash are not able to use a terminal emulator, they also should not use adb also imo I think you may underestimate the interested user who wants to learn something.
Click to expand...
Click to collapse
lol No I don't. The flashable zip remains an alternative and avoids typos From my actual experience some folks don't like Terminal commands even if it works well.

Primokorn said:
New useful sticky thread! :good:
Explanations well detailed but I'd like to add my 2 cents on a couple of points:
• I'm not sure that Terminal commands are adapted to beginners to I suggest to add thsi zip flashable.
• Q25 you forgot to mention TWRP backups. (/sdcard/TWRP/Backups/Serial number/
Click to expand...
Click to collapse
I want that users avoid using tools, zips... as possible (not offending) for learning purpose. Just 2 simple commands in T. Emulator.
Question 25 is edited :thumbup:
Thnx my friend
Sent from my Nexus 5 using XDA Premium 4 mobile app

Web_E said:
I would like to add, move to 2G network when using Wifi or voice calls are more important and you ain't doing any related internet activities. Huge save in battery. If you are rooted use xposed and GravityBox to change it in one click.. Or use Tasker to automate such changes. Whatsapp and fb notification works well in 2g data network.
If rooted, use greenify to stop continuous background apps.. (facebook was one of the biggest battery hog due to this). People with lot of newsreader app can be beneficial
Use an anti theft app. If rooted use rooted mode. I prefer avast anti theft.. You can wipe, and lock if stolen, locate it.. It installs with random name, hides itself from application drawer .. On sim change, it sends out notification to pre set alternative number and you can take control of your phone again.. The user will not know anything..
I bought premium licence just to say thanks to avast because I got back my Nexus after 1 month being stolen.. That too without police help and it went 1500km away...(and in India, least help from police about tracing, they just take a formal complain and throw it afterwards..[emoji20]).. I was lucky that last user didn't knew how to flash factory image.. [emoji14]
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Some info are added.
Thank you
Sent from my Nexus 5 using XDA Premium 4 mobile app

@samersh72
In battery saving tips you forgot some points..
Here they are
=> Turn off unnecessary scanning of wifi services by going to Settings - > Wifi - > Bottom right three dots (menu) - > Advanced - > Uncheck scanning always available
=> Turn off unwanted background data by going to Settings - > Data usage - > Top right three dots - > Restrict background data
Sent from my Nexus 5 using Tapatalk

Mr hOaX said:
@samersh72
In battery saving tips you forgot some points..
Here they are
=> Turn off unnecessary scanning of wifi services by going to Settings - > Wifi - > Bottom right three dots (menu) - > Advanced - > Uncheck scanning always available
=> Turn off unwanted background data by going to Settings - > Data usage - > Top right three dots - > Restrict background data
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
info added :good:

Nice thread :good: ... Very useful, detailed and well put together.

@samersh72
Nice thread
Keep updating and adding more stuffs

I find it amusing that people post pictures of battery usage of an N5 on standby for 2 hours and its ellegedly dead.......I was repairing devices from 6:10am to 11:30(ish)PM!! and had 32%......maybe I have a SuperNexus!!!
Also, my 2¢.....there's no camera glitch. When you attribute time/date stamps to photos, it engages location and clock stand by. DERP!!! I own my own mobile repair business and deal with N5's all the time aside from my four, never once have I seen a battery drain in stand by with "no background processes running". Send your N5 to me, I'll replace the battery and root/mod it for cheaper than you paid for Photoshopping the "proof of camera battery drain"! Thanks for the awesome thread folks!!!

Droid4 ROM Reviews - SlimKat

SlimKat is a V4 (KitKat) ROM by SlimRoms. It's based on AOSP 4.4.4. Its latest release, build 9.0, was Dec-22 2014 with a 3.0.8 kernel.
Its disadvanatges are that it is no longer supported by the Slim dev team; no custom overclock kernels exist for it; no hand-wave for notifications lockscreen feature of the later 5.0+ versions; and there's no support for altpart Safestrap.
But that's where its downsides end and its upsides begin. With nearly any 3rd-party ROM it's a series of tradeoffs. What works and what doesn't, what do you need and what can you do without. Not so with SlimKat. Everything, and I mean everything, just... works. Flawlessly. Even HDMI. This ROM is feature-rich, yet still so lean you can run it with Slim's normal Gapps package on the stock slot. At 180MB, Slim's normal Gapps package is 15MB smaller than the OpenGapps nano package for 7.1.2. I've been running this as a daily driver for over a month and not a single thing has gone wrong with it. No force-closes. No hangs. No jitters. No crashes. No random reboots. This is as close to a stock ROM's stability and performance as anything I've ever used. It's fast and responsive and handles whatever you throw at it. All that and great battery life too - I typically get about 36-44 hours from a full charge.
Support for 4.4.4 is extensive throughout the app community and I have yet to find an app that doesn't work with it. Custom fonts are easily installed with iFont and there are extensive interface and navigation customizations available in the SlimCenter. Cyanogenmod/LineageOS 11 themes are available for it on the Play Store.
The stock SlimLauncher is extensively configurable, and supports gestures, desktop folders, grid size configuration, icon size configuration, hidden apps, hidden icon labels and much more. I prefer a horizontally paged interface for my app drawer, and this one works exactly as this should work, where you swipe left or right and each page of app icons disappears behind the next, rather than a continuous side-scroll. This is especially important on the Droid 4 because of its TFT screen's limitations that make things difficult to read when continuously scrolling against a dark background.
While most ROMs will let you disable some system apps, SlimKat has a SlimSizer app in the SlimCenter settings that lets you save or fully remove any included system app from a simple checklist. SU is integrated and the ROM is rooted out-of-the-box. Google Voice works seamlessly with it. Voice Search starts up quickly and doesn't hang or crash, and interactions with it are predictable. The built-in WiFi hotspot works flawlessly. It natively supports Face Unlock.
Its sole quirks are that the keyboard doesn't illuminate when you slide it open until you press a key, and direct reboot to recovery doesn't work (just do a standard reboot and activate SafeStrap recovery at startup).
Verdict: Hands down, the overall best 3rd party ROM I've tested for the Droid 4. Rock-solid, OEM-level reliability and performance in a compact yet feature-rich package with outstanding battery life. If you don't require a newer version of Android (5+) for app compatibility or features, and don't want the code-bloat of the later versions, you simply can't do better than SlimKat on the Droid 4.

Thank you for this!
I was hoping there were some posts like this, but it being 2018 I wasn't optimistic...
just picked up a droid 4 to have a backup phone and for a bit of nostalgia - I had an OG droid that I kind of miss using

Update: After six months with SlimKat, I'm moving on. There's only one real problem I've had with it, but it's been really annoying. Frequently it just won't wake up the screen - the soft buttons light up, but the screen stays blank. It can often take several attempts before it works, if at all - usually after the third try I just give up and wait it out until the next time I want to check it. This is especially frustrating when receiving a call, as I've often missed calls just waiting for it to wake up the screen so I can answer it. Never been able to track down the cause or figure out a solution.
There's also a strange problem in the file system that there are "ghost" files throughout. Blanks show up randomly throughout my gallery, and duplicates of music and videos also work their way in, confusing the database and making it difficult and sometimes impossible to play back these files. I tried clearing app data for the Gallery and rescanning, even moving files to new folders, but it would only fix it temporarily and eventually these would come back. My gallery would show I had 1200 pictures when I had at most 350, and my music library would also show five copies of the same song, only one of which would actually play. I thought maybe these were ghosts of deleted files, but could never be sure. I used an alternate gallery app, QuickPic, and it worked normally without the blanks.
The hotspot feature had issues as well. It would pass the traffic for the connected devices, but after a while it would stop working for the apps on the phone itself, until I shut it off.
I'm not sure if it's a possible problem in my phone either, so I'm trying something different.