yashsingh1/xdaforums huggingface dataset:
[G3 Q&A, Help & Troubleshooting] artipex:
Well, Quick Torch and Quick Music are already developed...Just follow the link i posted.
[Sony Xperia ZR] EndOfDays-Wildfire:
Hey guys, so I just received a notification in Update Center that 4.4.2 is available for my ZR.

I must say,I'm quite happy with 4.3 so I got a few questions:

1. Has the Google Play Services bug with battery drain been finally solved? I checked the thread but there seem to be still some people which have massive battery drain?

2. How much does this new SD card restriction affect the phone(your experiences)?

3. If I decide to root it with Towelroot: Let's say in one week we get 4.4.4. Can I simply update my ZR?

Thanks in advance!
[Sony Xperia ZR] nikhilkaushik:
Answers

Well to answer all of your questions,

1. No, the issue still persists but there are work arounds for it.

2. The restriction can be lifted using different mods as well. (I have personally used xposed module for it)

3. You won't be able to update after rooting the device using OTA. For that you would have to download FTF and then only you would be able to update it.

Press Thanks if I helped....
[Galaxy Note 3 Neo Q&A, Help & Troubleshooting] Gintu:
I have been noticing horizontal lines flickering

when viewing a mostly white screen while on full

brightness at bit closer to my face no flickering is visible at other colors is this a sign my note 3 neo a 3 weeks old has a display complaint or this is a generic thing all of you have ...plz check ur phones and replay me ..Am really sad as this is new phone:crying:
[Galaxy Note 3 Neo Q&A, Help & Troubleshooting] nick99n:
i see something more like a flashing while on really low brightness at a dark room
[Galaxy Note 3 Neo Q&A, Help & Troubleshooting] peRFect!:
Only problem with N3 Neo display I know of is flickering while typing which was later fixed with an update.
[Galaxy Note 3 Neo Q&A, Help & Troubleshooting] Gintu:
this is like when looking at white image closer to eyes I can see some flickering and am really shocked.
[Galaxy Note 3 Neo Q&A, Help & Troubleshooting] peRFect!:
I don't have this issue, better get it checked!
[Galaxy Note 3 Neo Q&A, Help & Troubleshooting] Gintu:
Guys I observed this closely and I found that this flickering occouring oly some times and it's clearly visible only in apps when I set a white wallpaper on homescreen can't see any flickering but at same time its there in browser gallery etc and when I touch screen it disapperas and reoccur when I didn't touch display but this flickering is present only for some time not continuous. I think it's not display problem but software glitch which all of u have and u guys might not noticed it:confused::eek:
[Galaxy Note 3 Neo Q&A, Help & Troubleshooting] peRFect!:
I'm pretty sure I don't have this issue
[Galaxy Note 3 Neo Q&A, Help & Troubleshooting] Gintu:
ok am taking it to customer care
[Galaxy Note 3 Neo Q&A, Help & Troubleshooting] kaushal.k:
I'm having this problem too please tell me what happened after you bring it to home.
[Galaxy Note 3 Neo Q&A, Help & Troubleshooting] kaushal.k:
Hi I got the solution I think its the mura effect of the amoled check this thread

http://xdaforums.com/showthread.php?t=2108073
[Galaxy Note 3 Neo Q&A, Help & Troubleshooting] Gintu:
I took it to customer care yesterday and it was funny that the guy there showed me his note 3 which also have same flickering and they said that it's normal with amoled due to voltage variation at low brightness levels.So I left customer care without replacing display:victory:

Actually I don't want them to teardown my new phone so I thought of changing display after some time if it get more worse
[Galaxy Note 3 Neo Q&A, Help & Troubleshooting] fylim:
Get the latest 4.3 update. Screen flicker problem was solved with the UANF2 rom
[Galaxy Note 3 Neo Q&A, Help & Troubleshooting] Gintu:
am using latest 4.3 update I think it's problem with Indian INU firmware will be solved by 4.4 soon guess:o
[Galaxy Note 3 Neo Q&A, Help & Troubleshooting] Gintu:
I did a factory reset yesterday and kept brigtness above half till now I didnt have ny flickering.

I found this on web

There seems to be a

problem where the phone has problems

deciding if the software or hardware(CPU

vs. GPU) is what should be drawing the

screen… So this indecision causes it to

switch back and forth, redraw, etc….

Over at XDA there are lots of post relating

to this problem. Below is a temporary

solution to the problem

Here are the instructions!!

Temp Fix: (until they find/fix the problem)

1. Go to settings > about phone

2. Click “build number” 6 times fast

3. You’ll see “you’re now a developer” as

a notification at the bottom.

4. Go back to settings, you’ll now see

developer options above ‘about phone’.

5. Go in developer options, and click

“disable hardware overlays” under the

drawing section

This will fix the flickering!! The problem is

with android 4.2.x, the OS gets confused

and can’t decide if the CPU or the GPU

should be drawing the screen, so it flickers

do to it switching between the CPU and

GPU real fast…

Hope this helps anyone out there

experiencing this problem, and spread the

word to anyone else you know to make it

known! Loads of people are re flashing,

returning to stock, even returning their

phones because of this bug! So spread the

word to prevent others from making this

mistake.
[Galaxy Note 3 Neo Q&A, Help & Troubleshooting] nick99n:
i don't think it is software related but i will give it a try though it does not bothers me much
[Moto G Android Development] h2o64:
​

Hi everybody,

I recently work on a port for Ubuntu Touch on android. And I achieve to build something​

#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards, thermonuclear war,
* or you getting fired because the alarm app failed. Please do some research
* if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/

WARNING : This ROM is a "Work In Progress" : this ROM is experimental, flash it only if you know what you are doing​

Downloads

Developpers Informations

The sources is now here : CAF Ubuntu Touch

You can build by yourself thanks to this tutorial

Flash

Do not forget to do a NANDROID backup before flashing anything.

You need to use Ubuntu AND a Motorola Moto G (2013) Unlocked

That's only flashable on Ubuntu/Linux because the rootstock software (flashing tool)

doesn't exist

on Windows OS

Thanks you

Remember that's a community project ;)

Thanks guyw ;) :highfive:

My Github : https://github.com/h2o64​

​

XDA:DevDB Information

[WIP] Ubuntu Touch Port on Falcon, ROM for the Moto G

Contributors

h2o64, h2o64

ROM OS Version: 4.4.x KitKat

ROM Kernel: Linux 3.4.x

Based On: AOSP & CyanogenMod

Version Information

Status: Testing

Created 2014-07-18

Last Updated 2015-06-07
[Moto G Android Development] fermasia:
Can you provide a bit more info about the project? Where are these img taken from? Have you compiled them yourself?
[Moto G Android Development] h2o64:
I've compiled everything in this thread. The img came from my outpout directory :p
[Moto G Android Development] yeshwanthvshenoy:
highly appreciated work. will try to build from monday. and yes u may need to link github to thread as u may violate GPL terms if thread doesnt have one.
[Moto G Android Development] h2o64:
Thanks you !
[Moto G Android Development] Semseddin:
Appricate the work done here. Hope to get a stable release to try on my G. Thanks.
[Moto G Android Development] K3VYNC:
Does it work on dual SIM devices?
[Moto G Android Development] h2o64:
This is build with cm11 source in majority... So why not... But be careful!
[Moto G Android Development] poran123:
so excited about this Project... hope it will boot

EDIT: I want to test but i'm not able to download, mega.co.nz is not working for me anymore
[Moto G Android Development] K3VYNC:
Don't we need to flash "fastboot flash system system.img"? It's not in the OP

EDIT
[Moto G Android Development] h2o64:
No because of Rootstock
[Moto G Android Development] h2o64:
I know... I'm sorry... But my goo.im account isn't ready yet..
[Moto G Android Development] K3VYNC:
root@K3VYNC:/home/k3vync/Downloads/Moto G/Archive-314b# ./project-rootstock-ng/rootstock-touch-install $ROOTFS system.img

please make sure the device is attched via USB in recovery mode

error: device not found

What should I do? it doesn't boot into recovery (Don't worry, I didn't brick my device, just flashed stock firmware now) [MENTION=4792450]h2o64[/MENTION]
[Moto G Android Development] h2o64:
I'll modify a little bit the tutorial.

EDIT : UPDATED
[Moto G Android Development] asdcxz1:
is this booting any one tested this one
[Moto G Android Development] abhifx:
we now desperately need a multirom system. i did asked [MENTION=3418703]Tasssadar[/MENTION] but i guess he is busy and never replied.
[Moto G Android Development] h2o64:
Nobody have tested
[Moto G Android Development] h2o64:
I've done too. And I fully agree ! But [MENTION=4112553]dhacker29[/MENTION] maybe a better dev to contact (for falcon)
[Moto G Android Development] K3VYNC:
I tested :p and no, it's not passing fastboot
[Moto G Android Development] h2o64:
Could you explain with more details?
[Moto G Android Development] xGMERZ:
Would love to see this working!
[Moto G Android Development] LEX404:
Stuck in bootloader unlocked screen.

After installation of system.img I fixed permisions.

I tried again CAF and CM.

Now i saw: Mismatched partition size when flashing boot.

XT1032 Retail GB ( 4.4.4 ). :|
[Moto G Android Development] h2o64:
With CAF most recent one?

Please send me kmseg files ! ?
[Moto G Android Development] LEX404:
Both CM andCAF, the most recent. But, i'm doing this on windows ( because i deleted Ubuntu to have space for Sims3 :)) ):

In CMD as admin:

fastboot erase recovery

fastboot erase boot

fastboot erase system ( i don't remember if I did this first time, but second time i'm sure ^_^, it was 3:30 AM , and i'm not sure if it was ok )

fastboot flash recovery recovery ( the Ubuntu style CWM. It have a bug onmine, don't work. It's booting onit, i can see the menu, I can scroll on the main page but I can't accesany optionby pressing power )

...flash boot boot.img

...flash system system.img ( CM ).

What I don't understand:

I need to erase system or to keep stock?

I have to install both system imges? ( CM and CAF, this lucks weird idea )

Now i'm back to stock because i need the phone, but later today ( asap, 3-4h ) i'm trying again :D

Where I found the kmseg files? I'll use adb ( i will work ) to pull the files. Or, is another simple way to do that? :D

I'm very excited about Ubuntu Touch :))
[Moto G Android Development] h2o64:
Two things.

First : Never flash system.img, use the rootstock thing.

Second : I'll update the main topic to learn you about sending logs.

Remember that the recovery.img isn't obligatory. What does that mean? You can use your current recovery with rootstock. BUT Ubuntu recovery must be installed for upgrade things (in the future). By this way... You can wipe data & system using the recovery.

Thanks for testing guys [emoji3] [emoji3]
[Moto G Android Development] LEX404:
Ooki dooki. I'm gonna try asap from ubuntu. ( 2h ) .

I will test everytime when I can :D
[Moto G Android Development] h2o64:
I updated the installation topic.
[Moto G Android Development] LEX404:
Somethingwent wrong:

alex@alex-X55A:~/utouch$ ./project-rootstock-ng/rootstock-touch-install utopic-preinstalled-touch-armhf.tar.gz system.img
transfering rootfs tarball ... [done]
[B]preparing system-image on device ... mount: mounting /data/system.img on /cache/system/ failed: No such file or directory[/B]
[done]
unpacking rootfs tarball to system-image ... tar: [B]write error: No space left on device[/B]
[B]mkdir: can't create directory '/cache/system/android/': No space left on device
mkdir: can't create directory '/cache/system/android/': No space left on device
mkdir: can't create directory '/cache/system/userdata': No space left on device[/B]
[done]
adding android system image to installation ...
[Moto G Android Development] h2o64:
What?! Do the wipe before...
[Moto G Android Development] LEX404:
I did it! :-/

Now,i'm backing to stock, boot again to Ubuntu, try again to flash...but I need the phone for a few mins ^_^

ps. In CWM after wipe, when ~/utouch$ ./project-rootstock-ng/rootstock-touch-install utopic-preinstalled-touch-armhf.tar.gz system.img, at unpaking my phone shut dowm.

The TWRP and Ubuntu CWM show the upper errors.
[Moto G Android Development] h2o64:
Format /data & /system using TWRP
[Moto G Android Development] abhifx:
now that i have stock 4.4.4 firmware for asia, i could now safely give it a go. lets see what pops
[Moto G Android Development] LEX404:
I hope this is what are you looking for.

I didn't fount "last_kmseg", but a "kmseg".

In the ZIP are two,one for CAF and one for CM. Both made separattely.

The CM is not booting ( stay on bootloader unlocked warning ) but the CAF is rebooting continue.

Hope it helps :D I'm ready to do it again, I just saw following all steps and using CWM, i don't lose "ex-sd" , and here I have mystock ZIP image. :laugh: ( format allpartition except external data,or how it's say.. ).
[Moto G Android Development] h2o64:
Thanks you VERY much guy !
[Moto G Android Development] LEX404:
:laugh: Okay, now i know what I need to found :D Next one :angel:

In how much time do you expect it will be working? ( beta) :cool:
[Moto G Android Development] h2o64:
I clean out everything tonight... So I don't know.
[Moto G Android Development] h2o64:
INFO

I'll get my Moto G back from Motorola France in 2 weeks ... #Madness.

So ... I work on a Github's repository for you guys ;)
[Moto G Android Development] eagleofdeath13:
Yeah !
[Moto G Android Development] Awesomeslayerg:
Whenever i debug it says error device not found or Permisson Denied.
[Moto G Android Development] h2o64:
Don't worry.

I'll work on this project during few days.. And when my phone will come back.. The debugging tutorial will be understabler.
[Moto G Android Development] eagleofdeath13:
Do fastboot on sudo ;)
[Moto G Android Development] K3VYNC:
Does it boot now?
[Moto G Android Development] h2o64:
No. It's not.

BIG UPADATE : I added a nice and clean HOW-TO-BUILD on github for the CAF edition.

If you're interessting, please check it out ! :good:
[Moto G Android Development] eagleofdeath13:
I'll try (don't know when) to do the build one time with my build server, and if i can automate it, i'll launch the "nightly build" thing ;)
[Moto G Android Development] h2o64:
The ony problem is about gps : you need to use two different hardware/libhardware/include/hardware/gps.h and I can't mixed them together :/
[Moto G Android Development] eagleofdeath13:
Why?
[Moto G Android Development] h2o64:
Because one shared library """"need"""" variable in one type.

And the other library """"need"""" variable in another type.

So I'll think about a solution.
[Moto G Android Development] h2o64:
But once the first build has been built. The next ones won't have this problem anymore (until the next $ make clean)

PS : Nightlies are kind of useless after all. Weeklies ?
[Moto G Android Development] eagleofdeath13:
I say nightlies because it's what is usually said, but builds will be trigered by github hooks i think ^^
[Moto G Android Development] h2o64:
New caf build

New CAF build is uploading (10 minutes remain for boot & recovery when I write this)

Changelog :
- update sources (regular way)
- add external/f2fs-tools
- boot & recovery image are based on ext4 & f2fs
- re-managing of the msm8226 & falcon device tree (more CM like)
- new cmdline for boot
- delete a forgotten [I]BOOTJARS[/I]

TODO :
- make it booting :p
- more cleaning on the devices tree
- clean the acces to configs files
- [B]use only one edition (CAF) ?[/B]
- looking for dalvik or FM things in every single files.

Please send me your debugging feedback ! :D

Thanks you
[Moto G Android Development] h2o64:
Strom burnt one of my hard drive ... I loose quiet a bit (190GO) .. So ... Hopefuly I've git push this morning.. So .. You'll waiting for a little bit longer about the next build (I had made HUUUUUGE init script modification ... Only commited ..)

#RageQuit
[Moto G Android Development] abhifx:
oh man... just when we got multiboot.

also the latest touch builds are a bit more stable what lot of basic functionality built into (swipe to close app yay).

cant believe no other dev is helping here, you sir are doing great job and cant wait to see ubuntu on moto g
[Moto G Android Development] h2o64:
I remenbered my commits :D

So I'm in the process of building.

Yeah ... Other devs maybe an huge help :p

Does anyone test MultiROM yet ? That's amazing !!!

I need people de test out my builds ...

EDIT : New build uploaded

EDIT 2 : Changelog --> https://github.com/h2o64 --> phablet-4.4.2_r1-caf
[Moto G Android Development] eagleofdeath13:
Will try right now.

Do you want the promised Virtual Machine with an SSH access? Could be nice and safer? (My Virtual Machines backup aren't yet externalized, but it'll come!)
[Moto G Android Development] Awesomeslayerg:
Any updates?
[Moto G Android Development] h2o64:
When the ROM bwill boot :D
[Moto G Android Development] eagleofdeath13:
I've sent the dmesg to my gdrive ;)
[Moto G Android Development] h2o64:
Could you add kmsg log file please ? :D

EDIT : Your dmesg file is kind of empty :p

Spoiler : Working on another amazing ROM for falcon (and 4G variant too by the way) while waiting for logs
[Moto G Android Development] eagleofdeath13:
I knew i was forgotting something, now i've reflashed CM, so i can't give you right now, and next week will be quite "network-less" for me, but i'll try to see what i can do, sorry :s
[Moto G Android Development] h2o64:
By the way, if you can send me the kmsg with CM11 : it will be highlty apprecieded too :D ;)

That isn't essential. Live your life ;)
[Moto G Android Development] eagleofdeath13:
I switched to CM11 (tried paranoid : not stable enough. And get bugs from Omni, so i'll stay to CM)

I send this to my drive ;)
[Moto G Android Development] h2o64:
Nice ! Thanks you ! (Clean up the directory btw :p )

It used to help me on a comparing process (CM11 & my Ubuntu Touch build uses the same init files ^^)

UPDATE : New build in coming ...

CHANGELOG :
- Few bits and bobs on init scripts, optimisations, etc ...
- [B]New proprietary files with a new VENDOR :D[/B]
[Moto G Android Development] eagleofdeath13:
If it's uploaded before 16 PM i'll try in train ;)
[Moto G Android Development] abhifx:
new build new hope... ^_^
[Moto G Android Development] virajmalia:
But what is it that prevents the rom from booting??
[Moto G Android Development] h2o64:
WIll be upload in 2 hours ! (My new project take a lot of things to download)

I don't know ... That's why I need logs (and logs from CM11 to compair)
[Moto G Android Development] h2o64:
Still unsable ... The device musn't be shutted down.

(The log need to begin at 0s)
[Moto G Android Development] eagleofdeath13:
Yes, but CM 11 don't allow me to get them while device booted on it (so forced to reboot to recovery)

---------- Post added at 03:15 PM ---------- Previous post was at 02:39 PM ----------

Now it should be good :D

I'm downloading last build, will try it ;)
[Moto G Android Development] h2o64:
The last build isn't uploaded ... MEGA has troubles ^^

EDIT : I'll made an special CM11 version for debugging especially for you ! :3
[Moto G Android Development] eagleofdeath13:
I've found the way to backup XD (i was lost between how to backup kmsg and dmesg ^^)

So the files on Mega aren't right? I delete them then ^^
[Moto G Android Development] droider007:
Whats your new project??
[Moto G Android Development] Awesomeslayerg:
Should the new builds be able to boot now?
[Moto G Android Development] eagleofdeath13:
Try and you'll see ...
[Moto G Android Development] h2o64:
Nice ! :D

I'm porting a very famous (AND BEAUTIFULL) ROM. Based on KitKat 4.4.4.

Every time I upload a new build, the chances grown.
[Moto G Android Development] droider007:
Beautiful....??

Miui??[emoji53]
[Moto G Android Development] Awesomeslayerg:
Tell us when uploaded and update the op.
[Moto G Android Development] h2o64:
No problems.

Nearly :laugh:

EDIT : I have LOT OF TROULES AND A HUGE HEADACHE porting this ROM. But tomorrow, it will be done, and functionnal.
[Moto G Android Development] droider007:
Yo...waiting bro....hoping for a new thread by you soon......
[Moto G Android Development] eagleofdeath13:
Waiting for new upload :-p (and this time i'll give good logs XD
[Moto G Android Development] h2o64:
My connection seems to be happy. So I uploading the buid.

PS : Porting the other ROM, I might found file wich block the Ubuntu Touch booting process.
[Moto G Android Development] h2o64:
UPDATE : New build

CHANGELOG :
- Few bits and bobs on init scripts, optimisations, etc ...
- [B]New proprietary files with a new VENDOR :D[/B]

UPDATE :

New build uploaded

Please send me logs !

It may boot.. It may not ... But if it won't : I have an idea of a solution !
[Moto G Android Development] mario156090:
I can flash for recovery ?, it's a zip?
[Moto G Android Development] h2o64:
Every details in the main topic ;)

You NEED to be on Ubuntu OS on your computer (or Linux distribution isn't it ?).
[Moto G Android Development] abhifx:
Its an img file and can be flashed with fastboot.

so basically you need a PC
[Moto G Android Development] h2o64:
New build !

New build uploaded ! :laugh:

Downloadable here !

CHANGELOG :
- edit init.environ.rc [I](should fix the [B]bootloop thing[/B])[/I]

For more changelog and updates, take a look at my Github :laugh:

Thanks for your support !

Don't forget to send me logs !

EDIT : OP updated
[Moto G Android Development] eagleofdeath13:
Fastboot isn't enough, there's an executable that need to be run on Linux

---------- Post added at 10:17 AM ---------- Previous post was at 09:46 AM ----------

New logs are on my Google Drive ;)
[Moto G Android Development] h2o64:
Nice and clean ;)

Thanks you .. Isn't booting ? :'(

Still unusable :

First line (both files)

<3>[ 6.768952,0] msm_iommu_v1: FAR =

Need to be

<0>[ 0.000000,0]
[Moto G Android Development] eagleofdeath13:
Still not booting. But can't get better logs, i'm forced to reboot to bootloader, so i think they're lost here :s
[Moto G Android Development] h2o64:
Maybe using

sudo fastboot [B]boot boot.img[/B]

as last command ? :/

I really need to find a way to get logs easier ..

EDIT : FIND THE BOOTLOOP FIX !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! ,cjhgnsdjfgvbnqslkihvbnzs,pofbnaz,podihbnajmortghbne,zpofzajkfnaofjvhn,zE;POGHBNQkfcnfn ,adgbzqafliszdqbvnicqsbnfosqbnfojnfjnfkjqn,foisqdng,lsdjbnf,golskjghsNFGQKGND,SLDGN,SOQDGJ,KGJ,NSN,FGJSJFHFN,ZSF,kjknfkjNFHJKL FjFHNFiHNJGIU
[Moto G Android Development] h2o64:
New build !

New build uploaded ! (yes, two in the day)

CHANGELOG :
- update cmdline for boot.img
- few bits arround mkbootimg
- [B]see [URL="https://github.com/h2o64?tab=repositories"]my Github[/URL] for more details[/B]

Booting chances : 80%

Don't forget to send logs (& logcats) ;)
[Moto G Android Development] eagleofdeath13:
I'll try it :D
[Moto G Android Development] virajmalia:
Anything?

I saw and used ubuntu touch on my friends nexus 5 yesterday and i am in love with the os![emoji7]
[Moto G Android Development] h2o64:
Nice to hear that. It should boot in fact ^^

Fine
[Moto G Android Development] DustArma:
Does this wipe /data/ in the process of installing? If it doesn't I'll try it.