yashsingh1/xdaforums huggingface dataset:
[G2 Android Development] REV3NT3CH:
im not even pissed....im upset ppl are even doing this....theres potentials to even get permanent screen damage from this or psycho build as its missing alot...plus could lead to other issues...even with GPL though there is rquirements in doing such....its not just oh this code is open let me take it change a few things and upload a build...your changed work needs proof too along with anything tied to the old...its disheartening....i know you all are excited but this takes time from work actually getting done....a big reason g2 already is so mixed up and kernels and such arent really universal is because not alotta people work together orfollow the rules....im fighting for you guys here...not being greedy at all..
[G2 Android Development] DeeZigneZ:
I never said would...pls read...

And i dont wanna start no stress with any of u guys...u all do good work...seems even better than lg their self...otherwise there wouldnt be already ports or builds floating around...
[G2 Android Development] Sashenkablack:
Help to ! At inclusion transgressors all settings , when it is included desktop Navigation No of keys . Without them nykak Perhaps not Work ! Maybe something to know the reason?
[G2 Android Development] Mr_GeGGi:
Dont know why you dont upload your build. You see how much the community wants lollipop. No one will complain about bugs. Seeing it here!. And maybe it would be easier for you to check out the last problems.. But only thing you do is complaining. If you are right or not, that doesnt matter for me. Fact is, this happens because of not having other Chance for small devs to get a working lollipop in the road.
[G2 Android Development] Hid3rs:
[MENTION=5037435]REV3NT3CH[/MENTION] is there any place, like Twitter or G+ where I could follow your and your team's development? It would be nice to see how things are going.
[G2 Android Development] REV3NT3CH:
We won't release it yet because even though we aren't responsible for bricks or hardware damage...we want to prevent it....us actually making the code...know more about what could happen than most seem to think...this can be very dangerous
[G2 Android Development] fma965:
Well I have ran the old build and it was fine no damage, so I think your overreacting but it's up to you and your team
[G2 Android Development] REV3NT3CH:
Pm me on hangouts rev3nt3ch@gmail.com
[G2 Android Development] Mr_GeGGi:
Ah, i see... Sure, logical thing. Even we all should know about the risk of flashing custom roms, people wouldnt be very happy^^. But i think we cant change this here. People want lollipop so much even with bugs and me too^^. I can understand this.
[G2 Android Development] lch920619x:
Rev I second that you and your team should release an alpha build as soon as there is no possible damage to hardware. software Bugs are nothing.

People here will understand as long as you indicate It's 100% alpha and there will be many bugs. A lot of xda devs do that and they have always been welcome. Some of them even release non booting builts but it's OK.

It's much better than wasting time chasing all other unofficial builds out there and ask mods to pull them, and then defend yourself against those OpenSource fighters and those "you shall grow up" teachers.

Your precious time should be spent more meaningfully , and this is not.

Just my 2 cents, you have the final say.
[G2 Android Development] AmalD:
Agreed :good:
[G2 Android Development] fma965:
for what's it's worth I'm not on either side but it just feels like a playground. I have had code that I developed for Windows posted by other people and I have been accused of using someone else's code Google "Fma965 xbian stolen" or something similar.

http://m.slashdot.org/story/175241

my open source github with my windows applications is http://github.com/cyanlabs

so I understand revs point but I don't believe he is handling it in the right way.

release the working code and then these rips can stop.
[G2 Android Development] Energy-X:
agree too sounds good
[G2 Android Development] imDarkyy:
Good job

Ok, I have to say good job to you my little geek, really nice rom, fast and clean but for all who wants to download it I jut have to say that this is not a stable rom and it is not even a daily usage rom , it is full of bugs and even if it hasn't rebooted even 1 time I had to manually reboot more time. I hope to see you continue developing this awesome stock rom ;) :good:

Cya
[G2 Android Development] t-shock:
After, 5 hours non-stop use, I have to say this firmware is very good. A bit unstable (sometime by it self reboots), but it is in alpha stage.

To fix the mount of the internal memory, you must type in the terminal emulator ''su'' and after '' restorecon -FR /data/media/0 ''. Voila.!!!

Thanks to [MENTION=2111525]gardobus[/MENTION] for the fix.
[G2 Android Development] lch920619x:
I didn't mean to attack anyone including you.

Maybe I sound like somewhat aggressive but let's take it easy. Maybe there's no right or wrong here, everyone is contributing and have their reasons, but we all agree this is totally wasting time so I was just trying to figure out a way we can settle this bs asap.

Sorry if I accidentally offended you, I respect you and your work, as much as I respect Rev and his.
[G2 Android Development] Edoardo001:
It's a very good work, for me the bugs that make this rom not for daily use, is that the phone reboot every receive a watsapp message, in watsapp i can't send or receive vocal message. the camera don't work at all. But the must important are that when you receive a call when you use the phone(unlocker) the calls fails
[G2 Android Development] mjwhirly:
I 100% disagree with your post. There's absolutely no reason for them to have to do this to prove anything, most people know their names and the work they have put out for this device. People need to stop whining about having an unofficial build just because other phones have them, when Rev and the team decide their code is up to par with what they qualify as stable then code and builds will be released. If the wait is too long for you then invest in the nexus line or a moto x, don't beat up on the developers because you choose specs over software when you got your phone, because everyone that cares about having the most up to date android version went with those phones....so maybe you should have too :thumbup:
[G2 Android Development] petran_7:
The zip says D805, can I flash it to D802?
[G2 Android Development] InfinitusDesigner:
Yes, sure, D802 D805 and D806 (this one not tested yet) are the same device. I have the D805, ylukasy has the D802 ;)
[G2 Android Development] Edoardo001:
Yes :)
[G2 Android Development] NarrackLove:
NICE JOB!

and can i ask you is it possible to F320x devices?

I'm really looking forward to flash First Lollipop rom
[G2 Android Development] samham998:
stuck at restore

I flashed the ROM and it's now stuck at the "Restoring" screen. i haven't enabled google now or any of the location/backup stuff etc in the setup.
[G2 Android Development] petran_7:
Thank you both my friends!
[G2 Android Development] remio33:
Music and video streaming are not working
[G2 Android Development] InfinitusDesigner:
To get rid of the STUCK, do it: Try to press power until turns off, and right after do Vol - and Power to get in recovery. Seems awful but if you can acces TWRP you wipe and flash it again.

Once in TWRP your are ready to go, install again or use ADB sideload to install other ROM. :good:
[G2 Android Development] hiyouhello:
+1
[G2 Android Development] Roars21:
This is awesome and it looks great and is very smooth and quick but as you say not a daily runner yet, really look forward to getting Lollipop officially and then custom ROMs for it as well. Going to be great! Thank you for this and I will follow it for when it is more stable. :)
[G2 Android Development] imDarkyy:
Ok so every time I open certain apps like whatsapp musicx match and even play store the device stop working and reebok after a minute or so, any fix?
[Desire 816 Q&A, Help & Troubleshooting] terrybear2k:
1st. Just rooted and installed cm11 my htc desire 816 a5_ul single sim version in malaysia, where can i can the stock firmware? which version? india, australia or europe? had not much idea of what i was doing.... so i didn't backup the damn stock rom out from my phone before i flash cm11, now im searching everywhere for my phone's stock rom

2nd. is it becuz of the google camera app orignally designed for nexus devices, thats why we cant change the photo save location?

3rd did anyone else using cm11 on desire 816 facing any battery drain? battery life is kinda bad compared to sense, had to underclock it for powersave
[Desire 816 Q&A, Help & Troubleshooting] mbwambo:
Just follow some link has those stock backup… or Ruu that you can flash into stock rom….. Like this… first check if is the same variant to ur phone

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

Then about photo save location works in google camera if your SD card is accesed… ..
[Desire 816 Q&A, Help & Troubleshooting] terrybear2k:
thx for the reply, i got the stock firmware up using india version. testing it out right now
[Desire 816 Q&A, Help & Troubleshooting] mbwambo:
Ok… ..but your from where..???
[Desire 816 Q&A, Help & Troubleshooting] terrybear2k:
i'm from malaysia, guess the rom worked? so far so good, lets hope it gets ota updates
[Desire 816 Q&A, Help & Troubleshooting] mbwambo:
So the rom worked no any bugz???
[Desire 816 Q&A, Help & Troubleshooting] terrybear2k:
aside from some of the bloatware i can see or not see that wasn't from my region, it worked perfectly fine~:D
[Desire 816 Q&A, Help & Troubleshooting] mbwambo:
Ok… that cool…. Atleat u have it ..now you can keep looking Ruu of ur region…
[Desire 816 Q&A, Help & Troubleshooting] terrybear2k:
just asked my brother who uses the same phone in the same region to get me some screenshot, seems like its the exact same ruu! nice~
[Nexus 5 General] _MetalHead_:
I'm one of those "if it ain't broke, don't fix it" kinda guys and once I get comfortable with something, I am always hesitant to change it. This is the reason why my original Moto X is still on 4.2 and why my Nexus 5 is staying on 4.4.4. Kit Kat runs great on my N5, and does everything I need it to do. I don't like having to deal with bugs in new software, and also don't like having to relearn things that I am already proficient in.

Another huge and probably the biggest reason why I am staying on Kit Kat is the lack of Xposed for Lollipop. I absolutely NEED to have the ability to toggle expanded desktop/ immersive mode on and off, and I also like to have my navbar shrunken to 65% height. There are a few other tweaks that I do here and there, but those are the main things that I cannot do without.

My battery life is great (4.5 hrs SOT average), and everything is butter smooth for me. Sure, Lollipop looks great, but after playing with the developer preview with MultiROM, there just isn't anything compelling me to update. So, I am staying on 4.4.4 for the forseeable future. I might update my 2014 Moto X, but I am still undecided.

So, who else is sticking with Kit Kat? What are your reasons?
[Nexus 5 General] Wakamatsu:
I'm waiting for an F2FS-compatible ramdisk. I'm in no rush.
[Nexus 5 General] peachpuff:
Lollipop is even smoother, its piss smooth i tell ya!
[Nexus 5 General] doctor_droid:
Thats great [MENTION=2705242]_MetalHead_[/MENTION] if u dont want to change .. Lollipop did broke compatibility of few apps i use..other than that its worthy upgrade .. Just need time to let the developers make full use of newer APIs...that will actually unleash the full capabilities of the os...

I made a clean flash to lollipop and i am in no way making a clean flash again ...

However only reason i MAY go back to KitKat is that i hate white ui ...painful to eyes :(
[Nexus 5 General] jsgraphicart:
I wonder if there were people like this who stayed with Gingerbread when Ice Cream Sandwich came out.
[Nexus 5 General] crucialcolin:
Im actually quite torn myself. While everything overall seems good *knock on wood * im allready missing the ability to have widgets on the lockscreen. In my case i preffered the chronus clock with weather compared to the stock one. Im also unsure about all this white as i prefer a dark keyboard.
[Nexus 5 General] GUGUITOMTG4:
Just waiting for my favorite Rom to get updated to 5.0 before switching. Meanwhile I stay on 4.4.4 super stable Rom as some incompatible Apps get updated on Play Store as well.. Hopefully..
[Nexus 5 General] jsgraphicart:
You can still have the original keyboard look. There are 4 themes to choose from.
[Nexus 5 General] Wakamatsu:
Like what? In my case, I'd have to format my sd card back to ext4 to upgrade, then format to f2fs when a compatible kernel becomes available. I'd rather do a total wipe just the one time.
[Nexus 5 General] jsgraphicart:
I have no idea what that means. An external SD card?
[Nexus 5 General] wolfen69:
Lolly is butter smooth for me and no problems, so I'm going to use it. No way I could go back to 4.4
[Nexus 5 General] Stigga:
I am on kit Kat but not by choice
[Nexus 5 General] ps000000:
I like 8 unlock slider targets, Volume button wake , etc.....

I hope all of those KK features come to custom L soon..:p
[Nexus 5 General] crucialcolin:
I didnt realize that. Do you have to install the keyboard app from Google play? I cant find it in setting.
[Nexus 5 General] keplenk:
When Xposed Framework or a similar tech comes out for Lollipop - I'm in.

For now, I'll pass :(
[Nexus 5 General] jsgraphicart:
The default keyboard IS the keyboard from Google Play. The option is in settings/language and input/google keyboard/Appearance and Layouts/Theme.
[Nexus 5 General] crucialcolin:
Thanks. Seems like I either forgetting how to do all this stuff or the newness of lollipop is throwing me off :D
[Nexus 5 General] XeLLaR*:
Why did you buy a Nexus then? Makes no sense lol..

Gesendet von meinem Nexus 5 mit Tapatalk 2
[Nexus 5 General] jetbruceli:
Sticking with CM 11 till they have a lolliversion.
[Nexus 5 General] Rhadamanthis:
im stay, i flash when release android maintenance 5.1
[Nexus 5 General] ps000000:
I am very miss 8 or 4 unlock slider !!!! :laugh:
[Nexus 5 General] _MetalHead_:
I certainly wasn't *****ing. I couldn't care less about updates unless they are specifically to fix major bugs. But that's why I'm on KitKat still- no major bugs.
[Nexus 5 General] fire6water:
Omfg look at the comments on YouTube ratings on the play store. That is why I'm staying on kk. *****ing about lollipop is the point of this thread. Come on ppl. I hate this update.
[Nexus 5 General] Rolo42:
Not quite exact. LCD uses power to turn on the crystals to block the backlight to create black (or as close to black as LCD can get).

With the Nexus 5 (and any LCD screen), white saves battery as the crystals are OFF; white uses more battery (and wears more) on LED screens as black is full off, white is full on.

In the brief period I used it, I liked Lollipop and have been looking forward to the new design; I just can let go of Xposed, mainly for Xprivacy. However, I haven't used it long enough to decide is Android 5 is the new Windows 8, which was the new Windows Me...
[Nexus 5 General] meangreenie:
where ART thou compatibility?
[Nexus 5 General] _MetalHead_:
Edit: Disregard, misread post.
[Nexus 5 General] :
Thanks for adding
[Nexus 5 General] jarhead565:
I wasn't too sure I could give up KK after using Slimkat. I was wrong.

For me, LP is a big step forward. I can't wait for the custom ROM's to come out!

Sent from my Nexus 5
[Nexus 5 General] DonDizzurp:
I thought I'd miss GravityBox and/or CM and switch back to KitKat but Lollipop is too good.. I can't switch back now. It would be too much of a downgrade.

---------- Post added at 06:03 PM ---------- Previous post was at 05:59 PM ----------

White doesn't save battery on LCD. White is just as any other colour and takes power. It isn't 'off'. An 'off' pixel should be the same colour as the display when it is turned off. In LCD, if the pixel is off when the screen is on that means the pixel is dead.

Also, when you say LED what you mean is OLED, which has the ability to show black by not turning on those pixels as each pixel produces its own colour AND light. This is why AMOLED screens won't have light-bleed issues.
[Nexus 5 General] jpcdeux:
I keep going back to KK. Mainly due to the camera not focusing and I kept missing great shots of the baby.
[Nexus 5 General] Rolo42:
Completely incorrect; what you described is OLED (Yes, I forgot the O, forgetting that LED LCD screens are called LED screens for their LED backlight but they are still LCD displays). In an LCD, white is generated by the backlight itself completely unblocked. Colours are generated by switching on one or more liquid crystals offset at rotating angles. These crystals block different wavelengths, letting certain light wavelengths through to generate colour. For an LCD to display black, it must energise all liquid crystals to block all wavelengths and what you see is the backlight bleeding through (hence LCD never generating true black).

A dead pixel on an LCD will be stuck at a particular colour depending on which crystals won't energize; if all crystals in the pixel are dead, the pixel will be stuck white (all crystals off, letting the backlight through always).

cf. http://www.fujitsu.com/downloads/MICRO/fma/pdf/LCD_Backgrounder.pdf pg. 3:

The electrode is hooked up to a power source like a battery.

When there is no current, light entering through the front of the

LCD will simply hit the mirror and bounce right back out. But

when the battery supplies current to the electrodes, the liquid

crystals between the common-plane electrode and the

electrode shaped like a rectangle untwist and block the light in

that region from passing through. That makes the LCD show

the rectangle as a black area.​

cf. http://www.emd-performance-materials.com/en/display/function_of_lcd_technologies/tn/tn.html

The ultra-thin layer of liquid crystal mixture, twisted by 90°, is located between two thin panels of glass coated with clear electrodes. Polarization filters are found on the outside of the glass plates, while on the inside there are color filters, transparent electrodes and a two-sided layer for orienting the LC molecules. The thin layer of liquid crystals, around four to eight micrometers thick, is the heart of every LC display. In conjunction with polarization filters, it works as a 'light valve' for the backlight. The first polarization filter only allows a specific oscillation level of light to pass through. The light then meets the liquid crystals. When voltage is applied, the molecules align themselves perpendicular to the glass plates. The light follows this alignment, but is unable to pass the second polarization filter, which is rotated by 90°. The result: the pixel becomes dark.

If no voltage is applied, the molecules fall back into their original twisted arrangement. The light follows this rotation and is thus able to cross the second filter, too: the pixel becomes light.

​

The caveat here is that most of the power consumed by the display is consumed by the backlight, not the crystals; however, I wanted to correct the technical inaccuracy and IPS LCD becoming the norm for mobiles is why Android went to a predominately white theme (I can't find the Google source where I read that...Google Google..heh)
[Nexus 5 General] _MetalHead_:
That's not entirely accurate. Yes, white is achieved by allowing the light to pass through all the subpixels unblocked, but it is the combination of the red, green, and blue that give you the "color" white, not the backlight itself.
[Nexus 5 General] ritchea:
Like the OP, keeping my N5 on kitkat until Xposed and Gravity Box is working on ART. Running L on my N7, but my N5 is much more important for everyday use, and it's doing close to exactly what I need with kk os.
[Nexus 5 General] DonDizzurp:
You seem to be confusing pigment with light.

When speaking about light we're talking about additive, RGB must all be on to get white

When speaking pigment we're talking about subtractive, RYB must all be together to make black
[Nexus 5 General] DonSolo:
Once PIE commands and ability to disable nav bar is implemented I'm leaving KK for good! Until then I'll dual boot between Mahdi 2.9 and XtraSmooth 2.3.4 .
[Nexus 5 General] Rolo42:
No confusion at all except that additive and subtractive depends on the production process--RGB/additive is light rays (applies to LCD), RYB (subtractive) is paint, as is CMYK. Besides, "blocking wavelengths" is not synonymous with "subractive".

cf. http://www.colormatters.com/color-and-design/color-systems-rgb-and-cmyk

cf. http://en.wikipedia.org/wiki/CMYK_color_model

As the links in my quoted post to the manufacturers who make LCD displays describe: the white is generated by the blacklight; the colours are generated by blocking particular wavelengths of that white. The "white" is always on so long as your backlight is on; altering that requires powering the liquid crystals.

Backlight ---> White ---> LCDs off ----> White ---> Viewer

Backlight ---> White ---> LCDs on to block red/green wavelengths ---> Blue ---> Viewer

I don't see any references to authoritative sources that say otherwise.
[Nexus 5 General] _MetalHead_:
You can disable the navbar in your build.prop and use LMT launcher for pie controls. Or the N5X ROM has navbar resizing baked into the display settings so you could shrink it to 0% and again use LMT launcher.

What I want though, is an expanded desktop toggle in my quick settings that automatically turns on pie as well. That's how my N5 is currently set up.
[Nexus 5 General] _MetalHead_:
I think you are misunderstanding it. When all the pixels are off or open (technically they are on), the light HAS to travel through red, green, and blue filters as there are no clear subpixels. It is the light traveling through the combination of all three filters that produces white. That's physics 101.
[Nexus 5 General] Rolo42:
Reference, please.

White light doesn't travel through "filters"--it is blocked by them--that is what a "filter" does. If what you say were true, your backlight would have to be black and the liquid crystals would filter black to get white. Perhaps that would work with a theoretical LCD fabricated with antimatter. Or a regular LCD monitor in a dark matter universe..? :D

Pixels are not "off" or "open" on an LCD as a pixel is comprised of a backlight and the liquid crystals that block the backlight. If your backlight is off, you got nothing. If your liquid crystals are off, you get white. If all of your liquid crystals are on, you get black (and a greater power drain, which was the reason for talking about Lollipop/Material Design's white vs. black on LCDs). That is LCD fabrication and operation 101.

Subpixels are fabricated the same way with the only difference being in layout: rather than blocking RGB with multiple liquid crystals layered in one pixel, they are separated in a cluster (side-by-side versus over/under). In the context of the topic: white still uses less power than black with subpixel rendering on an LCD display. As for the remaining colours, they will vary in their power consumption depending on how much each subpixel's light must be blocked but white is still cheaper to power than all of them as all the liquid crystals would still be unpowered/off.

cf. http://entropymine.com/imageworsener/subpixel/

cf. https://www.youtube.com/watch?v=k7xGQKpQAWw (2:00 mark mentions power)
[Nexus 5 General] pinoyz:
No.
[Nexus 5 General] _MetalHead_:
No. A pixel is made up of 3 subpixels- red, green, blue. The light passes through them at varying intensities creating different colors. When light passes through all three at the same intensity, white light is created. You can do the research if you want but I'm not going to spend the time to dig it up for you.