yashsingh1/xdaforums huggingface dataset:
[Sprint HTC EVO 4G LTE] ultimatelegend1:
jrior i understand that these builds are built from cm right? what if we flashed an older boot.img the wifi problem is also present in the latest cm builds
[Sprint HTC EVO 4G LTE] jrior001:
https://www.dropbox.com/s/xha8jnl46qb0ksu/EOS-full_jewel-20140605.130740.zip

new partition format, Test build #3, includes a potential WiFi fix from cm gerrit.
[Sprint HTC EVO 4G LTE] MexPwrEng:
I just installed. No WiFi. I can toggle on and off but it will not see any network.
[Sprint HTC EVO 4G LTE] jrior001:
After a few days downtime, Nightlies are coming back today, as 4.4.3 :) CM guys are actively working on WiFi issues but are coming up short looking for testers. I'll try to post some test builds if they come up with anything.
[Sprint HTC EVO 4G LTE] jrior001:
OK here's some 4.4.3 love for the new part guys as well. I have also reverted the one suspect kernel commit for jewel headset that came in at the same time WiFi died. This will at least confirm this is the issue moving forward while a fix is worked on.

https://www.dropbox.com/s/jjd1nmfs6lzxexx/EOS-full_jewel-20140607.162425.zip
[Sprint HTC EVO 4G LTE] hondafreak513:
Data will not turn on
[Sprint HTC EVO 4G LTE] jrior001:
What? All I did was remove the recent headset fix commit....nothing should have affected mobile data that be a an working before
[Sprint HTC EVO 4G LTE] hondafreak513:
I tried everything to get it to turn on
[Sprint HTC EVO 4G LTE] iamrubbertoe:
I will be flashing the lastest on new partitions later today. I will post with my findings. Thanks for your hard work! :beer:

EDIT: Flashed last night, data connection would not work. NPL
[Sprint HTC EVO 4G LTE] fizbanrapper:
OLD PARTITION LAYOUT

I decided to build EOS to see what it was all about. So far this has been by far the easiest AOSP ROM to build (outside of CM11). Didn't even need roomservice to get it to build. I flashed the ROM and discovered it's for OPL (old partition layout). I poked around at the features though and, while I'm sure I could easily use roomservice to get it to build on NPL, I didn't see any features that made me want to run it. If you know this ROM and disagree, feel free to build it yourself. I've included build notes below (though they'd only really be needed by someone whose just starting to build ROMs) to help out.

Since it was already made, I figured I might as well upload the OPL in case anyone still on OPL was interested in running this ROM.

OLD PARTITION LAYOUT

https://www.androidfilehost.com/?fid=95747613655047936

OLD PARTITION LAYOUT

Here are some notes specific to building EOS for Jewel.

No roomservice/local_manifest xml needed. Just run:

repo init -u git://github.com/teameos/manifest.git -b kk4.4 -g all,-notdefault,jewel,htc

then repo sync

The only file change needed is adding a "#" sign in front of this line: "$(call inherit-product, vendor/eos/config/cdma.mk)" in the file full_jewel.mk, which is located in the (usual) EOS/device/htc/jewel/ directory.

Old Partition builds perfectly. To build for NPL, you just have to remove the device and kernel projects using roomservice/local_manifest.xml, then replace with CM and resolve any errors that pop up.
[Moto X Q&A] conquesoextra:
Hi guys,

I don't know why but my active display works funky.

It has a delay of 2 or 3 seconds and doesnt Show the clock/hour

I don't know how to explain because my english its poor.

But check this pic:

Enviado desde mi XT1058 mediante Tapatalk
[Moto X Q&A] lulajardim:
Mine does this no-clock thing sometimes but it isn't that often so it doesn't really bother me.

Does the delay occur when you unlock the phone or do you mean the delay is for the "lock" icon to show after you take your phone out of your pocket?
[Moto X Q&A] conquesoextra:
But ¿why happens the no-clock thing?... Mine is never showed :(

The delay is for the lock/no-clock icon after I pick up my phone from the desk or I take it from my pocket.

Thanks in advance

Enviado desde mi XT1058 mediante Tapatalk
[Moto X Q&A] conquesoextra:
Well.. Its seems that my phone has a very rare bug.

The guys from Motorola are surprised.

My case its now whit an "engineer level 3"...

Enviado desde mi XT1058 mediante Tapatalk
[Moto X Q&A] mroneeyedboh:
There is an on going issue with the active display not functioning fully as the time goes on. I seen a post on Google or Motorola and they do know about it
[Moto X Q&A] conquesoextra:
Really? Can you share the link bro?

Enviado desde mi ME173X mediante Tapatalk
[Moto X Q&A] DaRkRhiNe:
LOL they have these levels there :D

Hilarious
[Moto X Q&A] bolo808:
I have the same exact problem. It's weird because it's totally at random when these will happen. Sometimes I'll just have a delay but it'll show the clock fine or it'll just show the lock icon but I'll have no delay when unlocking, or sometimes I'll have both happen to me. I tried wiping the data and reinstalling it before but it didn't help. Not a huge problem since I'm used to it but a fix would be great. Hopefully in a future update.
[Moto X Q&A] mac1996:
I think we should report bugs from the play store.. Same with me shows only lock but no time....
[Moto X Q&A] conquesoextra:
Wow, im not alone.

You should report this... I changed the firmware 3 times and the bug remains, so i think its hardware.

The only thing that i didnt test its flashing a custom rom but im tired.

Im selling this phone to buy another (the same but new).

Enviado desde mi XT1058 mediante Tapatalk
[Moto X Q&A] Arak-Nafein:
That's not what the play store is for. Please don't do this.
[Moto X Q&A] scorpion667:
I am guessing you guys updated active notifications to the latest version? When I had that latest version, pulling the phone out of pocket and unlocking had a lengthy delay. After pulling the ring down there was a 1.5 sec delay to get to homescreen. Not sure if my issue is related to yours.

All I did to fix was RSDlite back to 4.4.2 and keep WIFI off to prevent automatic update. Disable automatic update in play store then enable wifi. No more delay issues for the last two days since I applied that fix.
[Moto X Q&A] Arak-Nafein:
I have the latest version of Active Display, Version 1.2.12 and I do not have any delays.

I have had the no clock thing happen once or twice, in a period of several months....it's so rare I don't worry about it.
[Moto X Q&A] conquesoextra:
At the end i sold the moto x, but now i have another new :)

No more problems! 0 delays and i have the clock allways!

Im still thinking that was a hardware problem but i don't know the cause.

Enviado desde mi XT1053 mediante Tapatalk
[Moto X Q&A] scorpion667:
A quick RSDlite back to stock can usually fix issues like that. Just batch backup all user apps with titanium or ultimate backup (no preference, takes 3 button presses either way), back up sms and ringtones (if you added any via zedge etc) reflash then restore everything. You can have her back up and running same way you had it in about 20 minutes.
[Moto X Q&A] conquesoextra:
I already did that.

I tried whit 3 different firmwares (Brasil, iusacell, Telcel) and the problem persist.

Also i performed 3 diferent factory resets (from the menú, vía recovery and whit fastboot).

Believe me, i did a lot of things.

Enviado desde mi XT1053 mediante Tapatalk
[Moto X Q&A] scorpion667:
Ah ok sorry I was not aware. Well I'm glad your new phone does not have the issue =)
[Moto X Q&A] conquesoextra:
Thanks my friend :)

Enviado desde mi XT1053 mediante Tapatalk
[Xperia Z1 Themes and Apps] adamsmth663:
Hi all

Heres something I always do to my roms to get more screen real estate, I havent really seen it mentioned on xperia forums so i thought i would show people how to do it.

Requirements

Root Access

Root Explorer or similar program which can edit build.prop

4.4+ rom (should also work on older roms, try it and see)

Procedure

find build.prop in root>system

then find the line that says lcd_density= 480

change it to 320 (others users have said 360 wroks well, try both and see what you like)

save and reboot

now your screen should look like:

*updated title

*Disclaimer: I have done this on all my xperia devices without any issue and found it to be a safe tweak to try, but as always if you do this, you do so at your own risk.
[Xperia Z1 Themes and Apps] tomascus:
cool tutorial, although you could change the title to 'how to change screen DPI density' because no screen resolution is changed here( still 1080x1920)
[Xperia Z1 Themes and Apps] raziel123:
screen resolution change

If anyone knows how to change the screen resolution and keep the touchscreen buttons lined up properly including the notification bar,

Would be really handy,

All the apps I tried on the playstore screw up the onscreen buttons alignment...
[Xperia Z1 Themes and Apps] adamsmth663:
thats true

but i thought its changing resolution because you can fit more stuff on the same screen size

but anyway i can stand the normal 480, 320 all the way
[Xperia Z1 Themes and Apps] Why So Serious?:
The resolution; number of pixels displayed will always remain the same as that is part of the display hardware. The Z1's resolution will always be 1080 x 1920 pixels.

You're changing the value that apps use to decide which resources to use. By lowering the density you're making apps such as the system UI think that it should use xhdpi resources instead of xxhdpi resources.

The xhdpi resources are all smaller in size... e.g an xxhdpi (1080p) icon is 144 x 144 pixels in size, whereas an xhdpi (720p) is 96 x 96 pixels in size. Therefore the xhdpi icon takes up less space on on the display and you can fit "more" icons within a 1080 x 1920 canvas.

Summary:

Resolution: Physical number of pixels that a display can produce. This never changes.

PPI: Pixels Per Inch. Again, this is a physical property of the display worked out using the following formula: PPI = No. of pixels in a horizontal or vertical line/the length of that line (inches). This is just maths and the value never changes.

DPI: Dots Per Inch. In this scenario, this is a virtual value that can be adjusted by the user to change the way that apps are displayed. By default it will loosely be in the same region as the PPI of a screen. Eg:

The 5 inch Xperia Z1 1080p screen has a PPI of 443. It's DPI by default is 480.

The 4.3 Xperia S 720p screen has a PPI of 342. It's DPI by default is 320.
[Xperia Z1 Themes and Apps] raziel123:
Does lowering the dpi improve graphics performance?

Also the resolution can be lowered, apps such as nomone resolution changer...
[Xperia Z1 Themes and Apps] adamsmth663:
i dont know but i like the 320 dpi setting, i jsut posted the tutorial for people to try it and see how they like it.
[Xperia Z1 Themes and Apps] 7sen:
on some apps yes it does lowering G P :rolleyes: i change before i had some lag :rolleyes:
[Xperia Z1 Themes and Apps] raziel123:
i tried some apps but it screws up the touch screen button locations and notification bar, so I reverted back to stock res and dpi.

regards
[Xperia Z1 Themes and Apps] babyboy3265:
It seems to have a negative impact on other things... making stuff a bit too small... and if i increase it to say 400 DPI then stuff is totaly messed up :/

I wonder is there is a way to do that trough xposed Appsettings by not affecting anything else but the main DPI...
[Xperia Z1 Themes and Apps] adamsmth663:
go to display options and change text size.

320 with large text seems to suit me best
[Xperia Z1 Themes and Apps] C.Eduardo:
I decided to try 360, 380, 400 and 420. The 360 was perfect but the others were not good.
[Xperia Z1 Themes and Apps] funky0308:
Just make backup, there was many bootloop or random restarting back in the Xperia S days.

DP changing could be cool but could cause problems and apps to FC, so... be careful...
[Verizon HTC Droid Incredible 4G LTE] jrior001:
Welcome to Eos! The Eos project originated with the AOSP release of ICS, and was originally founded by Solarnz and co founded by Bigrushdog. Since then, Eos has evolved into a multinational collaborative effort backed by top Android developers. Our objective is to provide a world class AOSP build with unique features and enhancements. Eos is an ongoing development project in which builds are released on a regular basis. Every release should be considered stable and highly functional.

Bigrushdog - Project lead, Chief Developer [Xoom || Galaxy Nexus || HTC One (M7)]

RaymanFX - Co-leader, AOSP code maintainer [Xperia S || Nexus 7 (2013) || OPPO N1 || OPPO Find7a]

jrior001 - Jenkins/Gerrit Admin, CAF code maintainer [HTC One X]

anders3408 - Frameworks Developer [OPPO Find5 || OPPO N1]

Roach - Frameworks Developer [Nexus 4 || Nexus 7 (2013) || HTC One (M8)]

Connor Baker [Nexus 4 || HP Touchpad]

NX Gesture Navigation Bar
EOS Weather Engine
Custom Quick Toggles Tiles with Brightness & Volume Seekbars
Softkeys Long-Press Actions
Network Indicator
Battery Indicator Mods
Clock Mods
T-Mobile Theme Engine
Force Navigation Bar on any device
Volume keys switch depending on rotation. So the volume up key is always either on the top or to the right of volume down. (Toggle-able)
Default Volume Control Stream (Ring or Media)
Advanced power menu with reboot options.
MORE...

We give love and much respect to Cyanogenmod. The AOSP scene would not exist as it does today without them. We implement some of their branches to support legacy devices and features that users have demanded.

Team EOS Nightly builds

FIREBALL >

G-Apps Package

Because this is an AOSP based rom Google Apps are not included. To install Google Apps please flash the following package after installing the rom:

GApps >

These builds are designed to be installed from your favorite recovery. MAKE SURE YOU HAVE THE LATEST 4.4.x COMPATIBLE RECOVERY.

Detailed instructions

:

Going to EOS4.4.x from a rom < 4.4.x:

Backup everything !

Go to recovery

Make a full wipe / factory reset

format /system

Flash the rom

Flash optional kernel

Flash gapps

Reboot

Updating from EOS 4.4.x #XX to #YY:

You can usually skip the full wipe step.

If ever you encounter an issue make sure you make a full wipe first before reporting though.

All HTC msm8960 devices use a slightly moddified version of the standard CM built 3.4 linux kernel, many thanks to the boys on our CM team who have made most of this possible on our HTC devices.

Contribute

Gerrit Review

Jenkins Build System

Github
[Verizon HTC Droid Incredible 4G LTE] jrior001:
reserved
[Verizon HTC Droid Incredible 4G LTE] psone1:
New kk Rom? Thank you! I'll try when I go back from work

Wysłane z mojego Incredible 4G LTE
[Verizon HTC Droid Incredible 4G LTE] tech128:
I tried to flash the 20th and the 19th nightly with the latest twrp2.7 and philz, but it always errors out when I try to flash.

Twrp complains about error executing updater binary in zip

Hopefully you guys can sort it out because I'd really like to try out the rom :D

OK I see the problem.

updater-script was written for another device in mind.

After ripping out all that stuff, and just formatting and mounting /system myself, I am running the may 20th rom!

I use the stock pa gapps.

After it booted, I couldn't get past the part where you select your language. It hangs on just a sec, then brings you back to language selection.

I just did the 4 corners trick and skipped it.

After updating play services, it seems to be working.

I'll let you know how it goes tomorrow.

Thanks again for the rom!

Just noticed one minor thing, the service signal bars do not work. I just checked in phone status and it says 125dbm

I'm pretty sure that can't be right.
[Verizon HTC Droid Incredible 4G LTE] jrior001:
http://mdmower.cmphys.com/category/fireball/

Grab the newest twrp/cwm from there and that should solve your install issues. ROM uses the new fstab options like the latest CM ROMs.

What makes you feel like script was written for another device? If so that's a big problem we are not experiencing on any other devices.

What is this 4 corners trick you speak of?
[Verizon HTC Droid Incredible 4G LTE] tech128:
Interesting, I didn't know mdmower was still producing twrp builds.

From this only, closed, thread in android development, it looked like he was telling everyone to use teamwin's own builds.

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

That's what I did. I flashed the 2.7.0.0 build.

Thanks for letting me know of mdmower's updated build.

I'd post a new thread telling people about it, but I think he should be the one to do that.

The updater-script has naming conventions for an omap processor which fail on the fireball.

The fireball uses conventions like /dev/block/mmcblk0p22 for the recovery partition, etc.

The four corners trick basically involves touching the four corners in sequence to bypass the welcome screen.

The sequence is top left, top right, bottom right, bottom left.
[Verizon HTC Droid Incredible 4G LTE] jrior001:
mdmower is still actively contributing to CM, just not on xda.

And what you are seeing there is the newer style "by-name" fstab entries instead of the older /dev/block entries. CM recently added the kernel support for this and updates all the fstab files to match. Most new devices utilizes this style now so this just gets us caught up. Grab the new twrp and you should flash just fine :)
[Verizon HTC Droid Incredible 4G LTE] tech128:
Ok cool. I guess I can delete my modded builds now lol.

As of right now, the rom is still humming along fine.

I'll try to reflash the latest nightly with another incredible I have, almost-finished on the repair table a little later.

Two things I have noticed, is that I cannot change the voicemail # from *86

Trying to research how to change it any way possible, looks like I need to switch dialers?

And I can't dial #'s when I'm in a call. Automated systems don't hear them.

Another dialer issue? I'll see if that's the case..
[Verizon HTC Droid Incredible 4G LTE] itrx:
tried this out, installed just fine, but it hung up on restoring my apps, and then when i rebooted, it bootlooped. too bad, seemed buttery smooth aside from this
[Verizon HTC Droid Incredible 4G LTE] tech128:
Nope not the case, with other dialers it is still angry..

And I've tried the latest twrp, it does not boot, tried flashing it through fastboot and through dd

So I've gone back to twrp2.7 and modding the zips.

Bootloops eh? Sounds like the issue of slightly different hardware rears its head again.

Hopefully the devs can sort it out at some point.

Well I just saw mdmower also compiled cwm as well.

Just tried flashing the latest cwm and it seems to work well.

Hopefully he'll be able to compile a new twrp that is able to boot, because I prefer twrp a lot more.

I've had to abandon this rom for the moment because I cannot figure out how to make the dialer send dtmf codes while in a call.

It doesn't appear to be a dialer issue as I've tried several. Not sure what in the rom could be causing it.
[Verizon HTC Droid Incredible 4G LTE] Sum Dumb Guy:
I've had some issues with the keypad while in a call also.

I'm currently using CM11 with Bubba Kernel QV http://xdaforums.com/showthread.php?t=2730005 and it solved my problem.
[Verizon HTC Droid Incredible 4G LTE] tech128:
Hmmm, maybe it is a kernel issue then? I'll have to see when I get a moment.
[Verizon HTC Droid Incredible 4G LTE] megaghostgamer:
Wrong thread, although great Rom! Running it right now.
[Verizon HTC Droid Incredible 4G LTE] flyinjoe13:
This is a great Kit Kat rom, much better than the previous KK rom I was running. The battery life is better and has a wider feature set. I've been using it for a few days now and have had zero issues what-so-ever. The only hint of problems i've had is with the weather app. I can't seem to figure out how to get it to work. I want to set the location manually (since I don't keep my GPS on all the time), but it doesn't seem to give me a way to set it when I choose that option.

Only other problem is not a problem with the ROM, but with trying to theme a few of the stock apps. I was able to change the dialer colors in my old KK rom, but those same steps don't seem to work with this one. So i'm stuck with the ugly blue\red bars on the dialer and I really hate them.

Look forward to trying future updates, although the version i'm using now is so stable that I may stick with it.

Thanks for providing for us.
[Verizon HTC Droid Incredible 4G LTE] bluskyline21:
Randomly won't unlock?

Has anyone had issues with their screen not unlocking after the timeout?

The phone is on the May 31st nightly, latest Bubba kernel. Thank you in advance.
[Verizon HTC Droid Incredible 4G LTE] jrior001:
After a few days downtime, Nightlies are coming back today, as 4.4.3 :)
[Verizon HTC Droid Incredible 4G LTE] GamerOnOne:
4.4.3 is stable, but has a wake issue when calling.

Fix is to download the smash rom post I made and copy and replace the phone apk and the contact apk in this rom and calling works fine.
[Verizon HTC Droid Incredible 4G LTE] bwthor20:
My son is using an old Incredible 4g on Wi-Fi only. He wanted to have Google Now, so I flashed a couple other ROMs and had various issues. Just tried this one yesterday, and I'm impressed. Working very well for what we are doing. Thanks!
[Verizon HTC Droid Incredible 4G LTE] jrior001:
Up to 4.4.4 now, along with some updates to all tele related projects. Please give a newer build a try without you mod and let me know.
[Verizon HTC Droid Incredible 4G LTE] j3grizz:
Okay first, this is a great rom! Haven't been using it long, is there a way to change the battery to a percentage and add extra home screens without changing the launcher?
[Verizon HTC Droid Incredible 4G LTE] jrior001:
Yes and yes.

Settings> interface> status bar is battery.

Drag any icon off the screen to the right and it will add a new screen.
[Verizon HTC Droid Incredible 4G LTE] j3grizz:
Thanks! So far everything is working very well. I'm running the 6-28 rom.

---------- Post added at 09:03 PM ---------- Previous post was at 08:38 PM ----------

Is there lock screen mods?
[Verizon HTC Droid Incredible 4G LTE] j3grizz:
Okay so I'm in to the first few days now and have a few questions.

1. Is there a fix for the phone not waking after being off for a while? I pulled the battery and restarted.

2. Is there a way to change or add to the lock screen?

Thanks for any and all help!!
[Verizon HTC Droid Incredible 4G LTE] GamerOnOne:
The latest 4.4.4 update of cm11 fixes the wake on call but there is still a dial pad while on a call issue.

On was able to fix it by replacing the older version of phone apk from 4.4.2.
[Verizon HTC Droid Incredible 4G LTE] j3grizz:
Thanks! Is the latest nightlie up to 4.4.4?
[Verizon HTC Droid Incredible 4G LTE] jrior001:
Yep
[Verizon HTC Droid Incredible 4G LTE] j3grizz:
I mean have the patches you are speaking of.
[Verizon HTC Droid Incredible 4G LTE] j3grizz:
Thanks for everyone's help. I went ahead and updated to the latest nightlie. Will see how this works out!
[Verizon HTC Droid Incredible 4G LTE] therreid:
Thanks so much for your work on this great rom!!
[Verizon HTC Droid Incredible 4G LTE] GamerOnOne:
It's not a patch, you manually have to unzip a 4.4.2 rom and copy the phone apk and contact apk from system/apps

And replace them in any of the 4.4.4 roms. Zip it up and flash.

Unless cm11 latest nightly fixed the issue.
[Verizon HTC Droid Incredible 4G LTE] j3grizz:
FYI... I updated to the newest nightlie and still have the wake problem. The phone just won't wake, you have to pull the battery. Everything else works. I think the 4g isn't quite as strong as my previous rom (Viper) Thanks again for this rom.
[Verizon HTC Droid Incredible 4G LTE] jrior001:
There's a delay? Or just won't wake at all Is this an all the time issue or just sometimes?
[Verizon HTC Droid Incredible 4G LTE] j3grizz:
Okay thanks GamerOnOne!

---------- Post added at 12:40 PM ---------- Previous post was at 12:38 PM ----------

It won't wake at all. Happens at least one a day.