yashsingh1/xdaforums huggingface dataset:
[Verizon HTC One (M7)] Fu5ion:
Yeah I came over from the S4 originally too. I'm on a GE ROM now, and I get better battery life than my S4 did on touchwiz, so I'm happy.
[Verizon HTC One (M7)] ctyonthehil:
I really should do this, but it's difficult to have to wonder if I'll make it to the end of the day or not. :eek:

But out of sight, out of mind would probably make it better.
[Verizon HTC One (M7)] donatelli:
I was getting really great battery life on stock, but I've since changed to a custom ROM. Battery would last me about 11-12 hours with 4G/GPS always on, and some heavy browsing 2 hours a day or so at work. When not at work it would last even longer.

The One's battery life has been one of the big positives for me.
[Verizon HTC One (M7)] brholt6:
This ship has kind of sailed, but since I haven't been completely stock until last week I wasn't sure what I could pull off. Managed to get some decently impressive numbers yesterday.
[Verizon HTC One (M7)] TheloniousMunch:
My wife and I both have Ones, mine is rooted and S-off etc., and hers is stock as can be. She's probably a good example of an average, every day, non power type user.

Before we got the Ones, she had a Blackberry Curve.

She gets work email on her phone, a lot of email, and mostly uses it for that and actual talking to people. She's connected to wi-fi at home, and nowhere else. As far as I know she hasn't downloaded an app, although the kids may have put some on her phone since last I looked.

My battery life is pretty good, usually 35%+ left at the end of a day (6AM to 10PM) of surfing, game playing, running apps, changing settings, messing with fonts, using widgets etc.

She gets two full days, easily - 48 hours plus, on one charge, if she needs to.

(I think users like her are part of the reason "power" users are always asking why smart phone manufacturers can't put longer lasting batteries in phones. As long as some percentage of users gets a couple of days of use, the stats can look good.)
[Verizon HTC One (M7)] DeerSteak:
Well I went to stock around the time that the first non-Developer versions got KitKat and I've gotta say, the battery life is pretty good. If you leave it completely alone and never turn it on, I get around 10 hours on 7-8% of the battery, equating to about 3 days of standby no-use time. It's only when you turn on the display that the battery gets drained. Fortunately I can get just enough information out of BetterBatteryStats on an un-rooted 4.3 install to see that I get around 4 hours of screen-on time and about 17 hours of off-the-charger time in a day, and it hits around 10-15% (depending on how much screen-on time is games vs. Facebook, for example) at bedtime. I have absolutely zero complaints because I work in an office. If I want to plug it in for an hour before I leave for the day, I've got almost a full battery to play with for 6-7 hours and I have no problem making it last. I do NOT have the option to turn off data when unused for long periods checked, and I never play with radios. Everything is on all the time - Bluetooth, NFC, wifi.

My wife's SGS4 still does not get that good battery life after being updated from 4.2.2 to 4.3. She's getting a solid 12-13 hours with the same screen-on time. It just either uses more for the screen or doesn't do as well at idle. Not sure which.
[Android Q&A, Help & Troubleshooting] rafatz:
Hi devs,

I've started to port CM11 4.4 to my beloved Original Padfone (A66).

The first step was to compile the kernel sources that ASUS made available (Kernel 3.4), which as far as I understand will work with KitKat.

Am I correct to assume this?

Also, if the kernel compiled correctly what will be the next steps to test it (flash) in my device? The bootloader is unlocked, but I'm still with the original recovery. I think I will have to flash CWM or simmilar, right?

Thanks!
[Android Q&A, Help & Troubleshooting] shimp208:
The 3.4 kernel should work with KitKat. In order to properly test any CM11 builds you'll have to compile Clockworkmod Recovery for your device first by pulling your stock recovery.img and then compiling Clockworkmod Recovery using that. Additionally to test your kernel the best way is to take the zimage that's produced from compiling the kernel and make a boot.img out of it and boot it using fastboot. Let me know if you still have questions I'll be happy to answer them.
[Android Q&A, Help & Troubleshooting] rafatz:
I've follow the XDA University guide for building CWM, at http://xda-university.com/as-a-developer/porting-clockworkmod-recovery-to-a-new-device

But the second step is failing:

Step 2 : Now that the otatools are ready, we need to get a dump of our current boot.img. To do this, use ‘adb shell’ and launch this command

“ dump_image boot /sdcard/boot.img “

This command do not exist in my phone.

Do you have any tip on this?

Thanks in advance!
[Android Q&A, Help & Troubleshooting] shimp208:
You have a couple of options of obtaining your stock recovery image (It's better to use your stock recovery.img rather then boot.img when compiling recovery as the recovery.img has more information in it that will make process of building an actual working recovery image easier) the easiest way is to boot into stock recovery, wipe cache in recovery, then reboot the phone. Then from adb run the following command:

cat /cache/recovery/last_log

This should give you an output, if you read the logfile you will see that one of the partition blocks is called /recovery. Record the name of the recovery partition block and then run the following command:

su
cat /dev/block/{name=of-recovery-partition-block} > /mnt/sdcard/recovery.img

This will dump a copy of your stock recovery.img to your internal storage. That you can then use to continue in the CWMR compiling process. By all means if you still have questions let me know I'm here to help.
[Android Q&A, Help & Troubleshooting] rafatz:
OK, I was able to successfully compile CWMR, but when booting to recovery I only get a blank screen and the devices reboots to Android. Is there a way to find any information on the error?

I know that TWRP works in padfone, but I'm not sure if they are compatible.
[Android Q&A, Help & Troubleshooting] shimp208:
It's possible that something is wrong with your recovery's graphics. Try taking the zimage of the kernel sources you compiled and swapping that zimage with the one in your CWMR recovery.img (Replace the zimage in your CWMR .img with the one you obtained when compiling the kernel source from ASUS). You could also try compiling TWRP and seeing that results in the same problem there are times on devices TWRP has been working before CWMR was working properly.
[Android Q&A, Help & Troubleshooting] rafatz:
No way :( Simply not working

But TWRP is 100%

I've tested the original recovery back and it is perfect as well.

Only CWMR is not working :(

I've even used the builder tool without success.

I've followed this guide:

http://www.imajeenyus.com/computer/20130301_android_tablet/android/unpack_repack_recovery_image.html

and this

http://xdaforums.com/showthread.php?t=1877807

Anyway, do you think that TWRP will work to flash my CM11 (if I ever build one)?

I think that the next problem is related on how to get the proprietary binaries from the phone to place in the vendor/asus/padfone folder.
[Android Q&A, Help & Troubleshooting] shimp208:
The CWMR builder tool has been not working for a while now. If you were able to compile the latest version of TWRP and you said it was working 100% then that will be fine to test your CM11 test builds. For getting the vendor files I would take a look at this guide on the Cyanogenmod wiki regarding porting and pull vendor files. A extract-files.sh script for a pre-existing device such as the Sprint Galaxy Nexus is a decent place to start for getting an idea how to setup extract-files.sh.
[Android Q&A, Help & Troubleshooting] rafatz:
Yes, TWRP is 100% working :D

I've checked the extract scripts but my main problem is to identify in the filesystem which files I should pull.

Anyway, I tried to use the "chipset" method and "guess" based on the system information which files/drivers I would need, but that was not very helpfull (http://specdevice.com/showspec.php?id=0429-3576-ffff-ffffa98be330).

Well, I'll continue my studies on this :)
[Android Q&A, Help & Troubleshooting] shimp208:
Another suggestion would be to take a look in the /vendor folder on your device to extract the proprietary files and use that as a starting point to build off. Then you could try and compile a test build using that. Studying other devices device tree's is like you said another way to gain hints about what to do for your own device.
[Android Q&A, Help & Troubleshooting] rafatz:
HURRAY!

This saved the day :D

https://www.codeaurora.org/cgit/qui...tree/proprietary-blobs.txt?h=aosp-new/idea133

It is not for Padfone, but it is close enough.

:D
[Android Q&A, Help & Troubleshooting] shimp208:
Awesome! Glad you could find a very similar device, best of luck on your CM11 builds :good:.
[Android Q&A, Help & Troubleshooting] rafatz:
After a few attempts I was able to finish a build for CM 10.2, but it will not boot :(

I found that maybe I did something wrong with the fstab.padfone, using the new standards with 5 settings instead of only 3.

Well, in order to eliminate these kind of problems, I will make a CM10.1 building, which still uses the old standards.
[Android Q&A, Help & Troubleshooting] shimp208:
Does it not boot at all or does it get to the boot-animation at least? Did you try pulling a log to see if you could get any information on the problem? But best of luck on your building :good:.
[Android Q&A, Help & Troubleshooting] rafatz:
SO far I couldn't even flash the ROM :(

TWRP is build with name A66, and the ROM is based on padfone.

I tried to change it, but the build fails :(

I think that I need to continue my efforts to make a working CWMR. So far the issue is the same, I can build and flash the recovery, but it simply do not enter the recovery. I get a flash on the screen and the phone automatically reboots to enter android.

I wonder if there's any way to get logs or more information from this error, so I can at least start to understand why CWMR is not booting.

fastboot boot recovery.img fails as well.

:(

Bad day :(
[Android Q&A, Help & Troubleshooting] shimp208:
To clarify the ROM fails to flash in recovery what is the error it gives you when it fails to flash? To get ADB working on your CWMR build so you can pull log information add these lines in the correct place to your init.rc file in your recovery ramdisk:

service adbd /sbin/adbd recovery
disabled
socket adbd stream 660 system system

# Always start adbd on userdebug and eng builds
on property:ro.debuggable=1
#write /sys/class/android_usb/android0/enable 1
#start adbd
setprop service.adb.root 1

# Restart adbd so it can run as root
on property:service.adb.root=1
write /sys/class/android_usb/android0/enable 0
restart adbd
write /sys/class/android_usb/android0/enable 1
[Android Q&A, Help & Troubleshooting] rafatz:
Thanks man! I was able to get a working CWMR.

The GITHUB I created for the device is at:

https://github.com/rafatzbr/android_device_asus_A66

I was able to build CM10.1 to Padfone, but it simply wont boot :(

stucked in the initial screen (not the bootanimation).

Any help is much appreciated.

Thanks!
[Android Q&A, Help & Troubleshooting] rafatz:
** UPDATE **

Still stucked in boot screen :(

Any ideas?
[Android Q&A, Help & Troubleshooting] shimp208:
The ROM build? If it's still stuck pull a log file and post the upload of the log here.
[Android Q&A, Help & Troubleshooting] rafatz:
Thanks!

The problems is that the device is not in a bootloop. It is stucked in the first screen (on nexus devices it's the first google screen).

How I can get any logs from there, and which logs I would need?
[Android Q&A, Help & Troubleshooting] rafatz:
I I'm out of ideas and about to give up :(

Here's the recovery.img I've build:

https://mega.co.nz/#!RQEBALRJ!zPUKyWXWMiwoQAhzgmO6x02VAuEHkKsQ7Htsl5woCh4

and here is the CM image:

https://mega.co.nz/#!0NFBiKJJ!D-CLBv0P2fHkHXxspi1JVLKya8d8uVETkYaBKSRO1xk

Recovery works like a charm, but not the CM. It is not booting. so DO NOT FLASH CM.

I've posted here so you can check the ROM and try to find anything that I might have missed.

So, very important:

0 - Make sure your bootloader is unlocked

1 - DO NOT FLASH THE ROM! IT IS NOT WORKING!

2 - Make sure you have a backup or you current ROM and recovery!

3 - I take no responsibility if this bricks your phone.

4 - Make sure to have backups.

5 - THE ROM DO NOT WORK!!!!!!!!!!

Let me know if you find anything useful while trying to debug this ROM or checking the zip file contents.

Thanks for any help.
[Android Q&A, Help & Troubleshooting] msantosm:
Hi guys. I have successfully flashed the TWRP but now I would like to get back to the stock ROM with stock recovery. I have flashed the stock ROM modifying the script but it did not flash the stock recovery. I wonder if anyone can give me stock.img file (for the A66) so that I can do it with goomanager. Thanks in advance.
[Android Q&A, Help & Troubleshooting] watio217:
Hey [MENTION=544472]msantosm[/MENTION], i have a stock Padfone A66, if you could tell me if there's a way to get the files that you need from it, tell me and i'll try to help you. Regards
[Android Q&A, Help & Troubleshooting] meuro86:
Petition

Hi guys,

I'm not a developer so I've created a petition to ask Padfone A66 official update at Asus.

Here the link:

ww w.change.org/it/petizioni/asus-north-america-last-firmware-android-update-for-padfone-a66-the-first-model-of-padfone-series

Sign and share it.

Thanks to all for your support and your time spends for Padfone A66 support.
[Android Q&A, Help & Troubleshooting] lilfarhad94:
pleace dont give up we need your help!!! :(((
[Android Q&A, Help & Troubleshooting] rafatz:
I no longer own a Padfone, so I am no longer working on this.
[Android Q&A, Help & Troubleshooting] snuk182:
Have incomplete CM13 for padfone A66. Cannot go on with it for personal reasons. Anyone wants to continue?

It boots (with second boot, first one fails after dalvik-cache build, need to pull out the battery and boot again), has working screen, station (partially), speaker, sdcard. Nothing else works.

https://github.com/snuk182/android_kernel_asus_A66/tree/cm-13.0

https://github.com/snuk182/android_device_asus_A66/tree/cm-13.0

https://github.com/snuk182/android_vendor_asus_A66/tree/cm-13.0
[Android Q&A, Help & Troubleshooting] blackjack4it:
I'm starting to cry..I had lost all hopes..thanks to you I can take again my loved padfone with me!
[Android Q&A, Help & Troubleshooting] blackjack4it:
I can test your releases because actually my Padfone is acting as a Kodi media player, let me know if I can help you with testing (no porting skills btw)

BJ
[HTC One X] sathara:
This makes peoples go for apple and windows ....

None of our data s safe
[HTC One X] DeeZZ_NuuZZ:
you really, REALLY think that at apple's OS and windows it's really that safe? :D :D it's mostly the same...if not even worse...with root and xposed we can block them so they couldn't be read...
[HTC One X] and313:
For f*** sake they found code which should not be there (sending info somewhere) in the iphone keyboard app....

Use privacy guard on android. They can only find me via gsm signal now. Which gives me 10m :)

If you are using windows and would like to be safer format the system drive and install ubuntu and for a router use pfsense. I have a 3ghz router now for 50€. Which is awsome antivirus firewall all you need. Even special buttons which brick everything
[HTC One X] 99RedB:
You do of course realise that any phone's OS can do all of that (and far far more) and that Play Services are one of the ways Google updates the OS these days...?
[HTC One X] and313:
1+1=2... Thats all i can say to it.
[HTC One X] Mr Hofs:
And why are people still posting questions in the general section.....
[Galaxy S II Q&A, Help & Troubleshooting] mr.jabr:
Hello there,

I have a problem that may look wired for some but it actually happend to my galaxy s2. I had a stock jeally bean, then I installed a jelly synap rom. I noticed that the display from the sides got smaller than before in the jeally bean. I came back to jeally bean but in vain. The display is not as big as it was. I tried every possible way; installing stock rom and stock recovery but they all failed. So PLEASE I need help.
[Galaxy S II Q&A, Help & Troubleshooting] wulsic:
Well that is weird. But you have now a smaller screen is the resolution also different or you cant see parts of the screen now?. I think your display has some problems then if you have it like that. Can you try this code in dialer on stock *#0*# can you post some pictures? Looks me like a hardware fault
[Galaxy S II Q&A, Help & Troubleshooting] mr.jabr:
Thanks for your reply. I think the problem has to do with the software not hardware as the display was good before installing the new rom. Also, When I tried the rom on another phone, the same happened. The display gets smaller from the sides of the phone. Regarding the code, I tried it and every thing seems good. The problem is in the sides of the phone.I can't post a picture until I get 10 posts.
[Galaxy S II Q&A, Help & Troubleshooting] mr.jabr:
I attached the picture.Please take a look at it and see if it is normal or the screen is smaller (from the sides) than usual.
[Galaxy S II Q&A, Help & Troubleshooting] mr.jabr:
anahisto farmers

Someone help please!
[Galaxy S II Q&A, Help & Troubleshooting] Donnie Sins:
This seems normal to me...:confused:
[Galaxy S II Q&A, Help & Troubleshooting] wulsic:
Looks also normal to me but i cant see much difference if you have the stripes. Could you make on in a brighter light cause those screens from these days can be pretty black.

Download this white background in the attachment and open it. Then take something to measure the distance between the screen and the end of your phone left to right.

It should be something like4mm maybe a bit smaller so say 3-4. Could you measure that? If it is also 3-4 mm then it is good View attachment 2517966

Verstuurd vanaf mijn GT-I9100 met Tapatalk
[Galaxy S II Q&A, Help & Troubleshooting] mr.jabr:
thanks for your reply.I can't see your attachment but I could manage measure the display and find it 5.6 CM. I'm talking about the display width from left to right, the lighted area. Is this normal? if it is, then i'm going to have an eye test:(
[Galaxy S II Q&A, Help & Troubleshooting] mr.jabr:
wiaitng for your reply!
[Huawei Ascend P1] takashiru:
hi, i have a problem with my p1.

i tried to flash a rom nut something went wrong and it bricked. the preblem is that i have the stock recovery that don't allow to install new roms nor restore backups. the other problem is that i cannot acces bootloader (holding volume- and main button and release the main then it vibrates) to connect the smartphone to the pc, install drivers and emulate the cwm.

what can i do?
[Huawei Ascend P1] adrivebb:
If you are installing drives, you are probably using windows. I am not familiar about windows, but I played a lot with this device and I never got it bricked.

You can boot to bootloader just with vol- and power button, when the phone vibrates, you can release the power button and still hold the vol- button for some extra seconds (maybe 10 is enough). Then plug the phone to the PC and try `fastboot devices`. If you can see there you devices, you can than flash the recovery you will need, however if you cannot find here your device, your drivers are not installed correctly or your device is definitley bricked.

---------- Post added at 03:46 PM ---------- Previous post was at 03:40 PM ----------

You wrote, that you have a stock recovery. You are able to get there? Do you know which firware revision you have installed before it got broken?

If you know the revision, you can choose your version or a higher version from this thread http://xdaforums.com/showthread.php?p=40901091#post40901091, put the UPDATE.APP to [SDCARD]/dload/UPDATE.APP and try to flash. Power off the phone, than press both vol- and vol+ buttons, press power button and when the phone vibrates, you can release the power button. The stock recovery should flash your update, or it will complains about version. If you are in this stage, I think your phone is not bricked.
[Huawei Ascend P1] takashiru:
thanx i didn't get that the bootloader was the logo... i thought that it was an option screen like the recovery -.-

and it didn't let me install drivers until i opened Hisuite with admin privileges.

thanx anyway!

cheers from italy
[Huawei Ascend P1] adrivebb:
you're welcome :)

Which ROM are you going to install on it?
[Huawei Ascend P1] takashiru:
i installed the stock b229
[Galaxy S III Themes and Apps] kenny.lee:
Metal Apex Pop 9Launcher Theme download

Dusk Wharf Bay 9Launcher Theme download

Snow Step Air 9Launcher Theme download

Lawn Green Rug 9Launcher Theme download

Lime Aspect 9Launcher Theme download

Paper Clip Toy 9Launcher Theme download

Pocket Bag Hot 9Launcher Theme download

Girl Kitty Yes 9Launcher Theme download

Snow Foreset 9Launcher Theme download

Transparent Ho 9Launcher Theme download

Crystall Flame 9Launcher Theme download
[Galaxy S III Themes and Apps] nhado:
It look great. I'll try. Thank mate.
[Galaxy S III Themes and Apps] kenny.lee:
Hey guys, this theme is designed for Nine Launcher.

Now there is Nine Launcher Free version, just enjoy it.
[Galaxy S III Themes and Apps] Stan_LSD:
Wow, I will try it too.
[Galaxy S III General] LucidSomnia:
Hey there, a friend of mine has given his sgs3 to the repair center, and after receiving it, he is on 4.1.2 and when he tries to update, gets a message like "you have modified sofrware". How can this be solved?

P.s. Sorry for posting here, but i tried to post in q&a and got a message saying "forum closed".
[Galaxy S III General] blazevxi:
Sounds like it's rooted. Did your friend send it in that way?
[Galaxy S III General] LucidSomnia:
No, he never rooted his phone or flashed custom fw. He was always on stock.

Update: i checked it now and its rooted, but i can confirm that he didn't root it himself. Will unrooting and factory reset fix the update issue?
[Galaxy S III General] blazevxi:
A factory reset will unroot the phone
[Galaxy S III General] LucidSomnia:
I know it wont unroot, i said unroot AND factory reset.
[Galaxy S III General] blazevxi:
That will fix it. Then your friend is free to use the ota updates
[Galaxy S III General] LucidSomnia:
Allright, thanks a lot.
[Optimus L3, L5, L7 Q&A, Help & Troubleshooting] IzNoO:
When i try to root my device i asks me for an encryption password...how can i find this password.

also tries to hard reset the device.
[Optimus L3, L5, L7 Q&A, Help & Troubleshooting] TahaX:
Are you rooting your phone with Framaroot? If not, click here. It's much easier and saves you a lot of time and trouble.
[Optimus L3, L5, L7 Q&A, Help & Troubleshooting] IzNoO:
Soooo unlucky! Error #5 Only option is SuperSU. ( Framaroot-1.8.1.apk )

"All errors less or equal to 9 mean your device is not vulnerable."

Hope there is another method.
[Optimus L3, L5, L7 Q&A, Help & Troubleshooting] TahaX:
Try this method.
[Optimus L3, L5, L7 Q&A, Help & Troubleshooting] IzNoO:
The Easy Method requires the encrypted password...

Iam trying the hard method, and i have a question.

iam on step 3. does it matter is i install v20D instead of v10 ? because i want to install CM 11 After and it requires v20.

or i should download v10 and i can change to v20 later?
[Optimus L3, L5, L7 Q&A, Help & Troubleshooting] TahaX:
Yes, you can download V10 and change to V20 later but I highly recommend you to install V20. Otherwise you'll have to install V20 after you install V10 to get CM 11 working.
[About XDA developers] :
Hi I would like to know if someone could delete my xda's account please ?Thanks in advance
[About XDA developers] orangekid:
Please follow the link below to have your deletion processed:

https://www.xda-developers.com/gdpr-data/
[8125, K-JAM, P4300, MDA Vario General] lrentz:
The contacts icon on my 8125 has never shown anything but the generic program icon. Is this correct? How can I change it. I have searched the forums for the contact specific icon with no luck.

Thanks,

Lee