yashsingh1/xdaforums huggingface dataset:
[One (M7) Android Development] gherkin12:
Evening Guys

Having a couple of issues that I'm hoping someone will be able to point me in the right direction with.

Basically I flashed 6.1 over 5.x (i can't remember the version increment) and had issues with the bluetooth in my car (would drop out every 10 /20 minutes). So I though this evening I would wipe everything (except the virtual storage). Had issues with the Google Play 'cannot download due to error 403'.

So after trying to get past this issue using wifi or mobile data I gave up and completely wiped the phone, sdcard directory, the works. Got connected to the wifi and low and behold getting the 403 error again - haven't even managed to get to test the bluetooth yet!!

Anyone have any ideas, don't think its the proxy/apn as all the settings seem correct.
[One (M7) Android Development] crogue5:
So your issue is probably fixed seeing as how the news reported this issue being with Google's servers the other day. Is that correct?
[One (M7) Android Development] gherkin12:
Apologies for not getting back sooner been totally maxed out at work, the 403 error has been solved - didn't realise it was Google's end, however the bluetooth issue I have hasn't
[One (M7) Android Development] rambo69:
i don't get a transparent notification bar:confused:

it's 1 off the features off 4.4.2 gpe right???
[One (M7) Android Development] belek1979:
Full wipe (cache etc), full firmware (ruu etc) and clean aroma 6.1 and there wont be any bugs!!!
[One (M7) Android Development] rambo69:
Full firmware ( ruu etc) ??
[One (M7) Android Development] Jvov:
Yeah mate... For me this looks like 4.3 skinned as 4.4.2, because I don't get a transparent notification bar, nor the arrow on the bottom of the lockscreen, and the unlocking circle only unlocks, no access to Google Now, no matter the direction I drag the circle to. Going back to sense, so disappointed, this looks crap.
[One (M7) Android Development] trjlive:
The transparent notification bar is not a feature of 4.4.2 GPE. It is actually a feature of the Nexus 5 launcher, which is also able to be installed on GPE. It is called the Google Experience Launcher (GEL). A quick search on xda or Google will yield you download links.

As for the Google Now on lock screen, you can add Google Now to the lock screen by swiping to the left and adding the Google Now widget. That's how GPE works. Google Now on the unlock ring is not a KitKat feature, it's been added to the Nexus.

GPE devices are not identical to Nexus devices. There are distinct differences, although people have found ways to make GPE almost like the Nexus version.
[One (M7) Android Development] Jvov:
Thank god someone helpful. +1 Thanks to your meter mate.

Enviado de meu HTC One usando Tapatalk
[One (M7) Android Development] kur1oso:
is there an update coming or something?
[One (M7) Android Development] trjlive:
There haven't been any updates to the GPE base, so there's really nothing to update in the ROM. Superuser has been updated, but that's something you can do yourself and doesn't warrant a ROM update.
[One (M7) Android Development] HjasToneC:
Is there an system application of stock android lockscreen for us to be able to use??? I just don't like Sense5 lockscreen, but I like the functionality
[One (M7) Android Development] rambo69:
I've done it with nova launcher translucent notification bar is in the free version!!
[One (M7) Android Development] trjlive:
Unless you've installed some other lock screen from the Play Store, the lock screen that comes with this ROM is the stock Android one, it has nothing to do with Sense 5.

---------- Post added at 01:49 AM ---------- Previous post was at 01:48 AM ----------

That works too! :)
[One (M7) Android Development] Twohats:
Alright, been using this for only 1 day, and already I'm noticing some things which are seriously wrong with this ROM.

1: Startup time has been significantly increased from 26 seconds on stock tmous ROM, to over 48 seconds with this ROM.

2: After startup, there is an issue where Nova Launcher will not start until I hit the Home button a minimum of 4 times, and after it starts, GO Locker flashes on top of Nova Launcher and will not stop until I lock the phone, unlock it, hit home 4 times. I haven't found another solution yet.

3: BubbleUPnP can no longer find PS3 Media Server, or any UPnP/DLNA device.

4: Battery life has been drastically reduced. On stock tmous ROM, I was able to get about 8 hours of constant use, however my battery has already gone from full charge to 5% in less than 6 hours with the same amount of use.

5: Everything is sluggish. Everything. Opening apps, navigating webpages, literally everything is slow.

6: Xposed Framework causes more issues than it helps solve. Too many to name.

7: During install, I had AROMA do a wipe, and while it didn't wipe the sdcard partition, it definitely made it unreadable and unclearable. That's right, all of the space is still taken, but I cannot access it in order to free up space. This left me with only 7GB of space.

Basically what this means is I will no longer be using this ROM, which is incredibly upsetting because I fracking HATE Sense, and this was supposed to have everything I wanted.
[One (M7) Android Development] trjlive:
Let me say first, there is nothing "seriously wrong with this ROM". There are thousands of people using it everyday without any of the issues you mention.

What is likely, however, is something seriously wrong with your setup. My device boots from cold shutdown to usable home screen in 21 seconds using this ROM. It sounds like you have multiple launchers installed, possibly complicating things. I don't know what to tell you about that, but those launcher's problems have nothing to do with this ROM. Delete them and use the stock GPE launcher.

Most people using GPE get much better battery life than on Sense ROMs, so again something is wrong with your setup. It sounds like you didn't do a full wipe BFORE installing the ROM, and probably came from a completely different ROM, for example a Sense ROM. Yes that will cause problems like you say. But that is not the ROMs fault, it is your fault for not properly preparing your device.

Look through the code of the install routine, the Aroma config, there is absolutely NOTHING that touches your sdcard. So any problems with your sdcard were again caused by whatever all the other problems your setup has. It's just not possible for the install of this ROM to have caused your sdcard to be corrupted, it doesn't even touch it. Did you try to flash firmware before or after flashing the ROM?

Not to be jumping all over you, but as you are new here and you kind of jumped all over this ROM and blaming it for all your problems, I will tell you this is not the way to get help here. If this ROM really, truly caused these kinds of problems, there would be more than just your snarky post about it. This ROM gets tens of thousands of downloads, which are people using it everyday without a single one of the problems you mention. Because they take the time to read the OP completely, correctly prepare their device, including making a backup of important data.

So, if you would like some help trying to figure out what the problems are, submit a logcat of your bootup sequence, error messages, screenshots of FC's, and details about your device, firmware, baseband, hboot, etc. Instead of coming here and blaming the ROM for your misfortune, maybe try to engage the community for some help. Or don't, it's your choice, I don't really care if it works for you or not. But there are resources and people who can help, if you work with them.
[One (M7) Android Development] crogue5:
1. Boot time isn't an issue for me, never timed it.

2. Sounds like GO Locker is causing your issue with nova, whatever that is. I use nova prime and don't have issues.

3. Haven't tried any media server stuff.

4. I get 8 easy on continued use, light use, I get 16-18

5. Everything is smooth as can be.

6. 9 xposed modules running, no issues.

7. This is a known issue with some 4.4.2 upgrades, is recommended to get everything off and do a full clear/format of your SD to get your space back.

Over all, it sounds like you just need to wrote out everything and start over. I have been running this from for over 3 weeks now and I think is the best one i have used of arhd sense, cm11, aokp, and this. Please try again and then let us know if you have other issues.
[One (M7) Android Development] xnknown:
honestly all I can tell you is that if don't know what your doing then you shouldn't even be touching stuff like firmware, custom roms etc Do the research beforehand. Not everyone is suited to be running a custom rom.
[One (M7) Android Development] Twohats:
So I did a full clear, went to reflash using sideload with TWRP... and adb will not recognize my device while sideload is running in TWRP. I made a separate thread for this problem. I've tried several different computers, all of which were running windows 7 with working HTC USB drivers, adb version 1.0.31, all USB 2.0 ports... I must just have the worst luck...
[One (M7) Android Development] xnknown:
which version of twrp are you using? ive found that 2.6.3.4 does not work for sideloading, make sure your using 2.6.3.3, you've obviously done something wrong here as it works for everyone else just fine
[One (M7) Android Development] rambo69:
No problem with this rom everything is running smooth here

Verstuurd vanaf mijn HTC One met Tapatalk
[One (M7) Android Development] crogue5:
I second this. Staying on 2.6.3.3 for my foreseeable future for this very reason.
[One (M7) Android Development] eskimochaos:
L.O.L.

YOU did something wrong. Follow installation procedures.
[One (M7) Android Development] mengtze:
6.1 battery life......

To be honest, I am seeing degradated battery life as well. Upgraded yesterday from 5.1, did a full wipe and I am seeing as much as 5% loss in a few minutes with normal usage. Disabled all 'background' processes I have control over (live wallpaper, data activity etc in GravityBox). I am tracking things with betterbatterystats, but for now cannot pin point the culprit.
[One (M7) Android Development] BouncingObject:
The ROM needs at 1-2 days to get "settled" on your phone. After that, battery life should extend some. I know for me, after the 2 day period I was still getting around 11-14 hours with my Play services hogging all my system usage, around 95% usage or so. Found out through Wakelock Detdctor that it was my Google Now pinging my location every so often, even though I had my location settings set to device sensor only, and had wakelocks for days. Used Xposed module App Settings to go in and disable the permissions for getting fine and coarse location and have had consistent 19-22 hour battery life since disabling those permissions.
[One (M7) Android Development] xnknown:
i would also download the battery calibration app, helps loads
[One (M7) Android Development] mengtze:
Thank you for the advise. I have installed wakelock detector and will see what is going on.

---------- Post added at 12:46 PM ---------- Previous post was at 12:44 PM ----------

Battery callibration app is standard in my stack. But thank you for the comment.
[One (M7) Android Development] mengtze:
Just out of curiosity, what do you mean by the ROM needs 1-2 days to get settled? As I understand OS's, they are configured and 'settled' at the time of install. Is there someting special about Android that does dynamic configuration based on time and performance related criteria; i.e. 'a self healing/correcting' set of configuration processes/files?

BTW, the culprit seems to be Google search...... it seems to drive wakelocks to 60% without me even using it....uninstalled it as I do not use it anyway.
[One (M7) Android Development] BouncingObject:
I don't know the specifics of what goes on when you install a fresh ROM. :rolleyes: I'm not that technologically inclined with the Android OS platform but I remember reading somewhere in the ARHD Sense version thread post that there's indexing and other background tasks, click here for link to post, that go on after the first initial boot up of a new ROM, therefore eating away battery for the first 1-2 days after you've had the ROM. After those 1-2 days, I guess it finishes whatever tasks it needed to perform and then battery follows a "normal", if you will, curve in terms of usage. Then you can start looking for wakelocks, CPU hogs, etc.
[One (M7) Android Development] trjlive:
Most modern operating systems (including Windows, Mac OSX, Linux, Andoid, iOS) are installed into a "lowest-common-denominator most-compatible configuration", and then after installing the OS image, the system begins various tasks to optimize itself based on the device's hardware, available memory, other apps or programs installed, user files, etc. The system is updating and preparing file indexes, some OS's move files around for faster loading, priming caches, etc.

The result is the same if you fresh install OSX on a new Mac, you'll notice a lot of extra processes running for the first little while after booting and the system can feel sluggish immediately after installing. And even Windows 7 and 8 runs extra processes during the first few boot cycles after a fresh install. Android is no different. It's based on Linux, and so there are many of the same kind of optimizing processes going on during the first few cycles after a fresh flash of a ROM.

So if you measure your battery life during this initial period, it's going to seem reduced. But if you wait about 2 reboot cycles, then the optimizing should complete and the system "will settle down". This is why people need to just wait a while before immediately installing a battery stats app and watching the system gobble up more juice than they think it should, and jump ROMs before they've even gone one full cycle.
[One (M7) Android Development] mengtze:
Most modern OS's are optimized during installation, the system is analyzed and the appropriate configurations are written to file. There are OS's (most notably Windows Pre-8 ) that loaded the 'most common dinominator drivers and config files, just in case a new device would be loaded -hence the significant footprint. Mac (BSD derrived) as well as other 'NIX's are configured and kernel tuned at install. Tailored to the HW. If a new device is added, the driver/firmware is loaded (sometimes manually) and made avialable in the HAL/sysctl.

What you experience as sluggish after first install is setting up links, reading config files and confirming settings. I do not believe that relocation of files for faster loading is part of that. This would mean that the system would move files to the middle of the disk / volume onlyhalf the travel distance either way rather than a full sweep of the disk. In the days of OS/2 I used to put the swap file in the middle of the disk so that reading from it was fast (my age is showing yes). This is a moot point on SSD (including phones) as the access is almost instantly. To my knowledge the filesystems we use do not optimize by physical location. BTRFS may do, I have not looked into that just yet.

Waiting 1-2 days seems excessive to and without merrit. It is a slow OS/system to have to do the post install processes over the course of two days. Post install would be a matter of minutes with maybe one or two reboots. So I aprtly agree with the quote above.
[One (M7) Android Development] angramenyu:
So is it mandatory to be s-off in order to install this on my AT&T HTC One? If so, what method do you recommend me to use for my device? Thanks in advance.
[One (M7) Android Development] BouncingObject:
Yes, you must be S-OFF in order to put this ROM on your One. I used rummrunner without any difficulty. The S-OFF process is all automated when you run it so it's relatively low risk.
[One (M7) Android Development] :
Can flash with CWM Touch :D

Hello everyone :highfive:

I came from ARHD, changed to MIUI, then to CM11 and now I am back at Mikes Nr.1 Roms :D

I read ijn OP that you need TWRP 2.6.3.3 for successfully flashing the rom, but I have to state: newest CWM Version works just well, flashed it some minutes ago with latest version (CWM Touch 6.0.4.6 touch) without any hassles.

@ Mike1986: Maybe you can update the OP and state that you can only flash with 2.6.3.3 or CWM 6.0.4.6 (touch) or higher :D

Happy weekend to all :cool:
[One (M7) Android Development] johnsonsimon:
Hi all,

I have had the ROM installed for a couple of days now, and love it. I can't get over how much I prefer the "Stock" feeling than Sense (personal preference I know).

I noticed that the battery was a little poor compared to what I was used to. Last night I decided to charge to 100% and unplug and see what the drain was. It lost 17% percent overnight. Connected to wifi.

So I thought I would wipe and reflash to see if that did anything. I created a nandroid backup in TWRP, did a wipe and then flashed the zip (the MD5 is correct). After booting I got through the setup process, it starts to download all my apps from the Play store and then gets stuck after it has installed 1 or 2 apps. The Play store is just totally unresponsive. I have tried clearing the cache, deleting my google account and re-adding it. But i just get errors 110 or 920 are the two I have seen.

The strange thing is, if I restore the nandroid backup (either of the RevolutionHD 6.1 or of my original Stock Sense ROM) the Play store works absolutely fine?

Any suggestions?

Cheers
[One (M7) Android Development] trjlive:
When you say you've tried "clearing the cache", which cache are you referring to? Generally, Play Store problems can be resolved by clearing the app data and cache for the Play Store app (Settings -> Apps -> All Apps -> find Play Store, delete the app's data and cache). Then sign back into Play Store and it should work. The important one is the play store's app data. I have found occasionally sometimes gets goofed up and the Play Store just keeps updating the same app over and over (most recent was Google Maps, it would download the update and install, then immediately wanted to do it again.). But clearing the Play Store's app data has always resolved the issue for me.
[One (M7) Android Development] johnsonsimon:
Thanks for the info. I have already tried clearing the app data etc, tried removing the google account and re-adding, even a "factory" reset to no avail, I still get 920 errors... but I think I may have at least a small answer...

From looking around on various posts relating to this, it may have something to do with multiple "devices" using the same google account to access the store, now as I have been flashing different ROMs over the past week or so I suspect that Google Play has detected a number of differ devices (even though it is physically the same one). The advice was to let the device sit for a while and try again. so I am going to leave it over night and see how I go.

UPDATE: All was fine after turning the phone on in the morning, I could download all my apps from the Play Store with no issues.
[One (M7) Android Development] :
Hi so i flashed the google edition rom and it kept bootlooping, so i went to recovery and wiped everything but it wiped also the ROM file from the sd card now im left with nothing to flash and only recovery i think i have to transfert the file trough ADB if so can anyone give me a tutorial ? i tried adb but there is no devices listed :'( i think its debug mode it wasnt enabled.
[One (M7) Android Development] johnsonsimon:
Is your device s-off? Pretty sure you need S=off to flash the google edition roms.

I did a similar thing with mine, wiped the internal storage and ended up flashing RUU via fastboot to recover it.

Alternatively you could get USB OTG cable and put a ROM on a USB drive and flash it through custom recovery.
[One (M7) Android Development] Superpulla:
I have problem. I flashed ROM and it works perfectly but.. The quick menu buttons are not quick. When I push them it goes right to that specific buttons menu were I can set up that think. Thanks!:eek:
[One (M7) Android Development] crogue5:
I installed gravity box (kk) and it has an option in there to change from holding on them to quick, just not for all buttons. You have to have xposed framework running for gravity box to work.
[One (M7) Android Development] mohab216:
Hi.

Can i anyway enable nfc icon in this rom?

Tapatalk-kal küldve az én HTC One-el
[One (M7) Android Development] Superpulla:
Noob alert...

hi it is bossoble to install (flash) differend stock to my htc one? I have sense 5,5 but now i have arhd gpe. So can i instal gpe stock to my htc one. I have rooted. S-off. Supercid one. How i get full use to supercid
[One (M7) Android Development] IberianPrince:
I'm not too sure what you're asking for. But if it's trying to convert your Sense Phone to a GPE, then maybe this thread will help...

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

------------------------------------------------------

HTC One: Android Revolution HD Google Edition - S.Off + Unlocked

Nexus 7: Paranoid SaberDroid
[One (M7) Android Development] rambo69:
I was looking for no red on this roms firmware, can someone point me to the right direction?

Verstuurd van mijn HTC One
[One (M7) Android Development] trjlive:
The GPE firmwares don't have red text, they just have a little unlock icon at the bottom (see screenshot attached). The firmware this ROM is based on is 3.62.1700.1, which is linked to in the OP.
[One (M7) Android Development] rambo69:
I'm sure i have a red text with text about this: is only for developers or something,

EDIT I looked in my bootloader >> fastboot >> getvar all >>

(bootloader) version: 0.5

(bootloader) version-bootloader: 1.55.0000

(bootloader) version-baseband: 4A.23.3263.28

(bootloader) version-cpld: None

(bootloader) version-microp: None

(bootloader) version-main: 3.63.111.3

(bootloader) version-misc: PVT SHIP S-OFF

(bootloader) serialno:

(bootloader) imei:

(bootloader) meid: 00000000000000

(bootloader) product: m7_ul

(bootloader) platform: HBOOT-8064

(bootloader) modelid: PN0710000

(bootloader) cidnum: 11111111

(bootloader) battery-status: good

(bootloader) battery-voltage: 3927mV

(bootloader) partition-layout: Generic

(bootloader) security: off

(bootloader) build-mode: SHIP

(bootloader) boot-mode: FASTBOOT

(bootloader) commitno-bootloader: dirty-d2906a15

(bootloader) hbootpreupdate: 11

(bootloader) gencheckpt: 0

all: Done!

finished. total time: 0.063s

Version main is 3.63.111.3 but firmware updates at the same time i flash rom right ??

Verstuurd van mijn HTC One
[One (M7) Android Development] crogue5:
My firmware had the red text until I loaded a firmware that had it removed. See sig for actual version, I am on a old one and just haven't had time to spend on getting the new one
[One (M7) Android Development] BouncingObject:
A new ROM verison doesn't update you phone's firmware when you flash it. I'm currently running the newest firmware, 4.19.401.9, and I have the red developer text while using ARHD GPE 6.1. I had a dark hboot from a previous GPE firmware that had the lock symbol at the bottom of the splash screen so you may just have to look around and find a different firmware to use.

See thread: http://xdaforums.com/showthread.php?t=2391611
[One (M7) Android Development] eskimochaos:
What app have you been using for the IR remote?