yashsingh1/xdaforums huggingface dataset:
[8125, K-JAM, P4300, MDA Vario Software Upgrading] bittermormon:
can anyone whos was running faria's rom and is now running this one comment on missed calls. Were you missing them with Faria, but not now? thats teh only issue I have had with faria's rom
[8125, K-JAM, P4300, MDA Vario Software Upgrading] jongoz:
I've been using FARIA's and MOLSKI's and I don't have this missed call problem. Probably it's only US Wizard's that is having this issue
[8125, K-JAM, P4300, MDA Vario Software Upgrading] faria:
all the aku3 roms even 3.5 suffer this phone problems ,the problem has been fixed in crossbow.its nor just the wizard rom.
[8125, K-JAM, P4300, MDA Vario Software Upgrading] bittermormon:
Hmm, thanks Faria. I'm currently running your RC1 that you released a few weeks back, before it hit the fan. Thanks for the time you've put into this.
[8125, K-JAM, P4300, MDA Vario Software Upgrading] blazoner:
:( This, unfortunately, means I'm in search of a good, stable, AKU 2.3 ROM until Crossbow finally gets leaked.... Too many missed calls while I'm trying to do business.

It's the weekend, so I won't have much time to look for one until Monday or so, unless someone has a suggestion. I'm still getting used to all the goodies in Faria's wonderful ROMs, so I'll probably be looking in that direction. Any guidance would be appreciated.

Thanks,

-Robert

p.s. NM the suggestions, lets not get further off track....
[8125, K-JAM, P4300, MDA Vario Software Upgrading] markgamber:
You can't go wrong with Molski's 2.3s, if you ask me. lightening fast, very stable, not too fat and not too lean.
[8125, K-JAM, P4300, MDA Vario Software Upgrading] HansMarius:
Exactly why are we missing calls when using aku 3.(?) ROM's? Explanation anyone? :-p
[8125, K-JAM, P4300, MDA Vario Software Upgrading] mikey411:
yup i've been using molski's 2.3 rom for a few weeks now and it's been working like a charm!!
[8125, K-JAM, P4300, MDA Vario Software Upgrading] renegade1:
eversince i did not have this problem.
[8125, K-JAM, P4300, MDA Vario Software Upgrading] faria:
can you please be a bit more precise?

eversince my rom?

or eversince this rom?

thanks
[8125, K-JAM, P4300, MDA Vario Software Upgrading] renegade1:
sorry, my bad.

eversince i was using your rom faria, the RC1 i did not have any missed call problem.
[8125, K-JAM, P4300, MDA Vario Software Upgrading] renegade1:
i take my hat off zeroXtreme. this ROM you make is quite fast. too darn fast. :D
[8125, K-JAM, P4300, MDA Vario Software Upgrading] imisim:
Can anyone comment on how much memory is available for the system to run after upgrading? TIA
[8125, K-JAM, P4300, MDA Vario Software Upgrading] renegade1:
Free Storage memory= 41.23 (total = 47.46)

Free program memory= 24.75 (total = 44.01)
[8125, K-JAM, P4300, MDA Vario Software Upgrading] ZeroXtreme:
Glad to be of service. I originally put together this ROM just for personal use, I'm glad that it is also benefiting other people too.
[8125, K-JAM, P4300, MDA Vario Software Upgrading] jwzg:
Very well done. I like the concept of a "lite" ROM because too many apps. spoil the speed and make it hard to find the stuff I need.
[8125, K-JAM, P4300, MDA Vario Software Upgrading] pabent:
8525 ROM on 8125...

I am completely new to the modified ROM issue...But I am trying to get a definitive answer on if it is possible to put (Cingular) 8525 ROM on the 8125...And a HOW-TO on how it is done exactly...

Thank You For your Help...
[8125, K-JAM, P4300, MDA Vario Software Upgrading] imisim:
@pabent

Why on earth do you want to do that? Putting the 8525 on the 8125 won't turn your 8125 into a 3G device.

Anyway, it won't work. Since you are new and asking this kind of question I suggest you should do a lot of reading (Wiki.) Otherwise, you won't have to worry about upgrading your 8125, because you will turn it into a brick and have to buy a brand new 8525.
[8125, K-JAM, P4300, MDA Vario Software Upgrading] ZeroXtreme:
best advise is to read through the forum and get yourself geared up towards fiddling with our device.

there are too many possible scenarios that could cause you problems, so you cant really base it on one post or tutorial, its usually a combination of a lot of information.

So read through the forums thoroughly before attempting anything.
[8125, K-JAM, P4300, MDA Vario Software Upgrading] webpatrick:
Mmm... clean ROM???

Why put a buggy MagicButton in a ROM, where SmartsKey is a nicer solution...

Good luck cooking ROMS
[8125, K-JAM, P4300, MDA Vario Software Upgrading] ZeroXtreme:
To each his own...
[8125, K-JAM, P4300, MDA Vario Software Upgrading] manfly9884:
Your Rom

Never mind what the other guy says. We all appreciate your hard work. It is YOUR Rom and you can put what you want in it. If he does not like iot then he should not download it and keep his sarcasm to himself.
[8125, K-JAM, P4300, MDA Vario Software Upgrading] stefanve:
Thanks for your rom

just installed it, I will report if it is ok (in my opinion :) )

any way thanks for your time to make this rom
[Android Q&A, Help & Troubleshooting] djipey:
Hi,

Since a few weeks, I've been facing a very annoying problem. I have a samsung Galaxy S3 mini with cyanogen mod 11.0.

When I lock my phone, the screens lights off (as it is supposed to). But about every 30 seconds, it lights on, displaying the lock screen. Then it lights off, and starts the process again. Finally, my battery is being drained. It takes 4 hours to use 50% of my battery.

So I installed Wake lock detector to find the problem, but I cannot find anything relevant, so I cannot really debug by myself.

Could you give me a hand and tell me what I have to look for ?

Thanks.
[Android Q&A, Help & Troubleshooting] djipey:
UP. This issue is really annoying.

Am I in the right section at least ?
[Android Q&A, Help & Troubleshooting] djipey:
Ok, actually the bug is occuring only when the phone is not on AC.

When plugged, it behaves normally. So I wonder, is there a way to make the phone believe that it is on AC ?
[Galaxy S 4 Active General] fratealberto:
Hello everybody,

yesterday I contacted Samsung since my S4Active screen cracked while being firmly hold in my hand.

I grasped the phone together with my wallet and my tablet in one hand with the screen of the phone exposed to my

fingers (index and medium) and after few meeter I felt a light noise. The screen had cracked.

The mobile, at the time of purchase, was publicized as extremely resistant to any stress. In one of the promotional

video it was shown in a kindergarten and subjected to several misuses as hammering by children. I contacted the

Samsung assistance since this break was very strange and I supposed the damage being covered under warranty.

First I showed to the local support store, who delegated me to contact the national assistance, secondly I contacted them

through the website and I received the response that I attached below. (in Italian Language).

Samsung claimed that after being inspected by their expert (in one authorized center) the damage was

considered as an abuse and it is not covered by standard warranty. They explicitly claims that these are

damages due to user intervention (such as fall, smashing, unproper supply or liquid expose).

The answer is clearly a standard answer they send to everybody, since this device is liquid proof and no in depth

attention was given before giving me an answer. But what is strange is that samsung claimed the mobile to have been

inspected in an authorized center. This never happened.

Finally I would have accepted a generic answer that they do not cover any mechanical damage to the screen, but I

found quite offensive that the fact was associated to an "abuse" from my side which never happened.

I hope not to have over-ruled, I tried to share with other my experience (without offending).

Lesson taken:

* The device is as fragile as any other mobile phone

* Find a cover that protects the screen also (as they are for the standard S4)

* Do not believe the cost you pay is proportional the quality

Regards

Alberto

---

in merito alla sua segnalazione, sono spiacente per quanto comunicato.

La informo che, a seguito della perizia effettuata dal Centro Assistenza Autorizzato, non è stata riscontrata anomalia alcuna sul prodotto.

Nello specifico, i nostri tecnici hanno rilevato che il danno riscontrato è dovuto ad abuso o utilizzo improprio del dispositivo.

Tengo a precisarle che per abuso o utilizzo improprio del dispositivo si intende tutta la casistica di danni non imputabili ad un vizio del terminale stesso, ma ad un intervento improprio dell'utente, come ad esempio danni da caduta, da schiacciamento, da errata alimentazione, da infiltrazione di liquidi.

Mi dispiace confermarle che il prodotto potrà essere riparato in seguito all'accettazione del preventivo indicato dal City Point.

---
[Galaxy S 4 Active General] sartana:
I Never heard a case in which screen cracked was passed in assistance without a specific dedicated insurance.

I mean, nor only Whit sammy, but Whit every company.

It's really difficult for someone demonstrate that he don't abuse phone.

Sad but true.

By the way, apart from spots, this phone cannot be defined extremely resistant.

Just a little more than some other. Mine fall from 1 meter, and now i can see the sign on plastic in the corner ...surely your glass was defective.
[Galaxy S 4 Active General] fratealberto:
I understand your point.

When I decided to go for this device I was conscious of the fragility of the other, but their advertising

(https://www.youtube.com/watch?v=z5EWhZL4tEU at second 30 it was hammered by children),

convinced me about the extreme robustness of the device.

However, the screen of the S4 was pressed by me the right amount to have three objects not falling from the hand and on

the other side I was pressing the screen surface of an ipad2. For a basic physic law, they were pressed with the same

amount of force. Given the much larger surface of the latter, I may conclude one screen is much more resistant than the other.

Coming to the damage it was clear for me the evidence of a defect, since the damage was just a single line-crack on the screen

surface, much different from that classic spider-net like cracks due to fall. And for the same reason I send them a couple of

pictures that showed the damage and the integrity of the rest of the device.

I was in good faith writing to them, and, as I said, I would also have understood from samsung a generic answer like your, which

explains that for the difficulty of the assessment they have the policy to not cover any damage to the screen. However this did not

happened and they claimed immediately for an abuse from my side, which, according to them, was determined after a phantom

investigation in their authorized center.

This was not correct at all in my respect.

I made this clear in a second answer to them, and they replied that even having not assessed the device, "they just look to the pictures

I sent to them, and considered the fact that the glasses do not broke when kept in the hand" (??). However this happened to me, and

in the presence of several friends.

My conclusion hence was not motivated by the lack of support by itself, or by the fragility of the device, which as you said it could be

the same for most devices on the market. I got offended by the way they treated me, which went beyond the correct client-customer

relationships.

Thank you anyway for your comment. More or less I came to the same conclusion you did. The glass manufacturer is the same for all

these types of devices (Gorilla XX), and it does not matter what they claim on the robustness of the device, these are only marketing

claims.
[Galaxy S 4 Active General] TwoStroker37:
The S4 Active was never advertised or rated for any more physical abuse than a standard cell phone. It's just IP67 rated.
[Galaxy S 4 Active General] jot82:
check youtube.com/watch?v=BGusN5-l1JA and dozens of other commercials
[One (M8) Q&A, Help & Troubleshooting] FormaldehydeSon:
So I got an M8 recently, unlocked bootloader with HTCDev and flashed a rom without upgrading the firmware, so later I restored my stock backup and downloaded the OTA update which was for 2.22.401.5. But my recovery wasn't stock so it wouldn't flash then long story short I soft bricked and did a factory reset from hboot.

So now I flashed stock recovery but since I factory reset my original backup was gone, and for some reason Wi-Fi does not turn on at all after I did the factory reset. I downloaded a TWRP backup from here http://xdaforums.com/showthread.php?t=2710735 (The Telus one, I am with Telus) and when I go to download the OTA update it gives me the option to download and install 1.55.661.4 instead of the more recent version.

I am S-On and I have read that flashing an RUU for a firmware older than yours will hard brick your phone and I definitely don't want that, so what I'm asking is can I download and install this 1.55.661.4 OTA then install a more recent one afterwards or will that brick my phone? And if so how should I go about updating firmware?

Thanks
[One (M8) Q&A, Help & Troubleshooting] redpoint73:
Factory reset (wipe data, Dalvik and cached) by definition does not delete internal storage where nandroids are stored. Either you specifically went into TWRP Advanced Wipe settings and wiped storage (which wasn't necessary) or you did a factory reset in bootloader which on a modded phone may corrupt internal storage.

WiFi not working is a known issue with outdated firmware + 2.22 Sense ROM. So updated firmware will fix this.

This is not correct. With S-on, flashing an older RUU will flash (version check will fail). With S-off, it will not brick the phone, and will actually work correctly (re-image the phone to the older RUU).

But its not clear to me whether your phone even has firmware/software that is "newer" than the RUU or OTA you are referring to. If the hboot and radio was never changed, and the ROM and recovery were returned to the "older" version, then nothing is in fact "newer" anymore.

RUU is actually a safer proposition than OTA in my opinion. But do you know for fact that an RUU exists for your version (not many versions do)?

OTAs with S-on, should work, but do you know for a fact that everything on the phone (ROM, recovery, hboot, radio, etc.) is now restored (or never changed) to whatever software number directly preceding 1.55? If not, with S-on the OTA will fail version check and not install. Further, if OTA is not installed in sequence, this actually

is

a brick risk (in contrast with RUU). Although the last part is probably only possible with s-off.
[One (M8) Q&A, Help & Troubleshooting] FormaldehydeSon:
Thanks for the reply, how can I check the version of my recovery to make sure it matches my rom version number? I am using recovery downloaded from here http://xdaforums.com/showpost.php?p=52734619&postcount=14 but the recovery doesn't mention a version number. Is it safe to assume that the recovery and nandroid backup linked in that post are for the same version, since they both came from the same person's backup?

In phone settings it shows my software version number as 1.12.661.17, and in hboot my radio is 1.16.2133156, hboot version is 3.16, but am I correct in assuming that my radio or hboot versions could not have changed, since I don't have s-off and haven't flashed anything other than the recovery and TWRP backup in the linked post? Do these version numbers match up properly for me to try downloading the OTA? Thanks again
[One (M8) Q&A, Help & Troubleshooting] redpoint73:
I don't know how else to confirm recovery. But if you used the nandroid from that same post, its probably safe to assume they go together.

You are right that with S-on, you can't have modified hboot or radio. So if you haven't gotten any OTAs, and you were originally on 1.12 when you got the phone, those should be okay.

In this instance S-on is kind of a good thing. If the OTA finds anything amiss, it will just fail whatever security check and fail to install. Although S-on is the whole reason you're at this point in the first place.
[One (M8) Q&A, Help & Troubleshooting] FormaldehydeSon:
I was able to install the OTA without problem, as well as download and install the 2.23 OTA, thanks for all your help!
[Moto G Q&A, Help & Troubleshooting] Giugo:
The specs of a charger that is good to charge a Moto G are 5.0V, 500-1500mA. In my house I have many microusb chargers (5V 1A, 5V 550mA, 5V 700mA) and I charge my phone once with a charger once with another one. Should I use always the same charger or is it indifferent if I use one or another (all the chargers are within Motorola's guidelines)?
[Moto G Q&A, Help & Troubleshooting] dethrat:
It doesn't make any difference your phone will take as much or as little as it needs.
[Galaxy S 5 Q&A, Help & Troubleshooting] deswong:
Ok, so I got over excited and have changed something critical to the way applications run. I can run most applications but there are a few, Smartpoint (which controls my wi-fi power switches) and Speedtest (Broadband speed test) now wil not run. They will start up but then shut down without any indication what is happening.

There was something in a diagnostic log saying that there was not enough memory to run the application, but that does not seem to make sense to me.

I am not sure if it is related but quite often I lose the ability to get to the WiFi settings and it does not show that I am connected to WiFi, but I am.

Any ideas how to revert changes or are changes logged that are done through System Tuner Pro?
[Galaxy Note 3 Q&A, Help & Troubleshooting] bryan2015:
I just update from ND1 to NG1 for 3 days , but it seems NG1 firmwire still unstable, my device temperature easily getting hot ,sometimes It reached 42 degree celcius in standby mode. So I'm downgrade to ND1 which never caused overheated. So anyone have this problem too or just I'm not lucky with this new firmwire:confused: ?
[Galaxy Note 3 Q&A, Help & Troubleshooting] guiso98:
I went to NG1 from 4.3. Working fine and no overheating
[Galaxy Note 3 Q&A, Help & Troubleshooting] AO7:
42 degrees is sleep is normal depending on outside temperature.
[Galaxy Note 3 Q&A, Help & Troubleshooting] ShadowLea:
A, does it go into deep sleep, and B, what's the ambient temperature?
[General Questions and Answers] bullet1520:
Hey everyone, I have a Samsung Galaxy S4 Active (AT&T i537) running android 4.2.2

I've had this phone for a long time, and I'm feeling ready to root it. BUT every guide I've found on rooting it is either incredibly sketchy and unreliable, OR it's outdated by about a year. I have heard of Towelroot, but will it work correctly and safely on my device? Are there better/safer ways of rooting my device? I'm not too experienced with rooting, though I do respect its value and want to do it with this phone as I did with my previous one (Galaxy S3).
[General Questions and Answers] 1102.Xmen:
Im going to do
[General Questions and Answers] bullet1520:
Um... what exactly are you going to do? It seems your message cut off.
[General Questions and Answers] 1102.Xmen:
I'm creating all:)
[General Questions and Answers] baudbox:
Hi Bullet1520,

if you check Towelroot thread (http// xdaforums.com/showthread.php?t=2783157)

so better to check twice.

Otherwise the good old method to root via Odin :

1) switch off the phone

2) start in download mode (press volume down + home + power) then volume up

3) Connect your phone to your pc with the standard USB cable

4) start Odin

5) select CF-Auto-Root-jflte-jfltexx-gti9505.tar.md5 in the filed name PDA. I guess if you search around xda forum you will find it easily

6) check that tick is NOT set on "Re-partition"

7) clic start

Wait until your phone reboot ... et voilà

hope it helps
[Amazon Fire Phone] SafinWasi:
Disclaimer:I am not responsible if using anything I've made or provided suddenly deep-fries your device or causes thermonuclear war leading to alien abductions.

Hey guys!

It's been a while that I've been seeing people having problems to enable USB debugging and setting up the Android SDK to recognize the device. So,I've made a guide to help you enable USB debugging and set up the Android SDK accordingly. So let's begin!

What you'll need:

Setting up Android SDK and drivers:

Enabling USB debugging:

Thanks a lot for reading my guide. If this was useful to you,please hit the thanks button. Feel free to comment,post or report anything. Thanks.
[Amazon Fire Phone] I am M3:
Excellent!! I can confirm this is working.

Bin4ry's root method was unsuccessful. Tried all options including the pwn binary. Very nice to have adb working though. :good:
[Amazon Fire Phone] I am M3:
[MENTION=5609616]SafinWasi[/MENTION] - Could you take a look at getting ADB to recognize the device in recovery? I can test sideloading the update file to roll back to 3.5. Problem is ADB stops recognizing the device once it goes into recovery.
[Amazon Fire Phone] SafinWasi:
Could you try in a Linux distro live CD? It should detect the device without a hitch

Sent from my device running CyanogenMod 11
[Amazon Fire Phone] Euneiro:
If you're using Windows here's how I did it on Windows 7. Once you open ADB and reboot it into recovery mode remove it from Device Manager. Reboot you PC if asked. Never unplug or remove your phone through any of this. You may need to remove it a second time from Device Manager after a reboot. It'll eventually show up under Other Devices with the Model Number as the device name (at least mine did). Once it's there then go and update the driver. Tell Windows you want to pick from a list of all the devices. Scroll down until you see Amazon listed on the left side. You'll then see "Android Composite ADB Interface" listed on the right. Choose that. Then it should be recognized again and you can sideload to roll back. Once you roll back you'll probably get a lot of errors but it will work and it will root using the towelroot APK that's posted in the other forum here. I had to have my phone services so I had to do a factory reset on my phone because it broke my phone services. But the roll back process itself was very easy to do once I figured out how to get it recognized again while in recovery mode.
[Amazon Fire Phone] mnknight:
I did what the directions say, but I don't see the fire phone listed in the sdk.
[Amazon Fire Phone] B1ackByte:
You have to choose the correct driver in Device Manager

On Windows 8/8.1 you may have to activate unsigned drivers
[Amazon Fire Phone] mnknight:
Kindle drivers don't seem to be working for me!
[Amazon Fire Phone] B1ackByte:
In Windows 8 and newer you have to activate unsigned drivers.

And please choose driver in device manager!
[Amazon Fire Phone] Grizzly123:
Kindle driver not working for me on windows 7

Kindle driver not working for me on windows 7
[Amazon Fire Phone] SafinWasi:
Try using a Linux distro
[Amazon Fire Phone] munir84:
hey, first sorry for my bad english. isnt my native language.

ich have installed all i need (Windows/Linux/Mac OS X with the Android SDK installed,Android SDK installed,adb and fastboot working[but i dont really know what fastboot working means.])

i have no problem with step 1-5 but i dont understand step 6. i google it but i dont understand. can you please update pictures? that would be very nice.

i have a sec question. my fire phone is netlocked(german). is where still a netlock after install andoid?

again, sry for my bad english :/

thanks for help

munir
[Amazon Fire Phone] rbeavers:
Step 6.

In windows device manger, remove all the fire phone devices listed.

Then run the KindleDivers.exe listed in step 7.

When you plug the phone back in windows "should" find and use the right drivers.
[Amazon Fire Phone] mazay2:
Thank you
[Amazon Fire Phone] tr00st:
For reference, the drivers have now moved. The following is an extract from the latest release notes:

They're installed with the package Extras / Kindle Fire USB Driver and will be located at: android-sdk\extras\amazon\kindle_fire_usb_driver

Other than that, instructions work fine, thanks :)
[Amazon Fire Phone] azheng:
hello op, i got as far as step 4, when you mention add the link, mine shows new, everything after step 4 is different. can you please help?
[Amazon Fire Phone] Junn21:
Stuck on recovery

Solved it