yashsingh1/xdaforums huggingface dataset:
[Miscellaneous Android Development] Avinash kodidasu:
Presenting Sony Xperia walkman debate 3 rom for canvas knight & Canvas Gold​

Features

Android 4.4.2

____________________________

Everything working... Themes, camera features etc. etc.!

Let me know if any bugs..​

Download Link

__________________________

DOWNLOAD

Download Link

__________________________

Canvas Gold users DOWNLOAD

Download Link for nitro x script

__________________________

DOWNLOAD

---Installation instructions---

__________________________

First take a full back up of nvram folder in data

wipe all - ( data,cache,system,dalvik)

Install zip from sd card

Reboot

After booting into rom

replace nvram folder

then reboot to recovery

flash nitro x script

then reboot

---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.​

---Credits---

Kodidasu avinash

sh saeed

Rahul baviskar(helped me a lot)

mr.ak & Devrookie,Ap,many people who made this possible

Wen wen

gionee m2 team that ported this rom

K1ks for script

Sony for this awesome rom

________________________

1.

---About KITKAT ROM 4.4.2---

ROM OS Version: 4.4.2 KITKAT

ROM Kernel: Linux 3.4.67

Based On: KITKAT

Version Information

Status: 100% Stable[/QUOTE]
[Miscellaneous Android Development] Mr.Ak:
[/QUOTE]

AWESOME WORK BUD......KEEP PORTING MORE ROMS.....:good:
[Miscellaneous Android Development] Praful Pradhan:
Thanks brother!!!

Is it for V3,????
[Miscellaneous Android Development] Mr.Ak:
V3

---------- Post added at 03:28 PM ---------- Previous post was at 03:26 PM ----------

And Correction;;;;; This Rom Is 4.4.4 Not 4.4.2...

Awesome Rom...........Got Every Xperia Features And Look...

---------- Post added at 03:50 PM ---------- Previous post was at 03:28 PM ----------

Some Bug Fixes--- 1]. If Ur Getting Fc After Setting Effects In Camera Mode Then Use Retrica...

2].If Ur Getting No Call Button In Dailer,Then Just Use Any Dailer App Like Go Dailer..

Alternate Fix* Set Dpi To 410 {Thanks To Sanket For This Fix..}

If U Dont Wanna Change Whole Dpi..,Then Use Multiple Apps Dpi Set Module And Set Only Dailer App Dpi To 410 Else Same To 480..

3].If Ur Getting Lags Then Flash Nitro X Mod..

4].If Ur Facing Google Play Services Fc,Then Flash Any Gapps....
[Miscellaneous Android Development] Mr.Ak:
WTF?

Only 4 thanks for this awesome rom..come on appreciate some hard work guys..
[Nexus 5 Q&A, Help & Troubleshooting] Teeea:
dos any one have this?
[Nexus 5 Q&A, Help & Troubleshooting] parag60288:
I am also facing huge miscellaneous battery drain.

Almost 30% battery drop over night every.

Please help....!!!
[Nexus 5 Q&A, Help & Troubleshooting] Teeea:
Final i Flash the factory image and disable all gapps, it's likes better
[Nexus 5 Q&A, Help & Troubleshooting] parag60288:
I have uninstalled all unnecessesory gapps like fit, earth, etc...

Still same problem.
[Nexus 5 Q&A, Help & Troubleshooting] Teeea:
it's maybe AOSP problem, try to flash factory image.
[Nexus 5 Q&A, Help & Troubleshooting] The Joke(r):
I think it's something that related to the phone. I also have this problem and I'm notice that when I wake up my device a number of times, the miscellaneous theard get more percentages. This is interesting...
[Nexus 5 Q&A, Help & Troubleshooting] parag60288:
Now I am trying factory image to see if same issue exists....!:confused:
[Nexus 5 Q&A, Help & Troubleshooting] Teeea:
edit /system/builr.prop

ro.build.type=userdebug to ro.build.type=user
[Nexus 5 Q&A, Help & Troubleshooting] urushiol:
[MENTION=5922932]Teeea[/MENTION],

Does your nexus have a replacement screen? Mine does and "miscellaneous" is taking up 60% of my battery. I am thinking its a hardware issues with my aftermarket LCD.
[Micromax Canvas Magnus A117] nileshbore:
Hi friends,

I am using mmx a117 and want to upgrade rom.

I have found some roms here in xda, but not completely sure about how to update,

My main aim is to increase internal memory from 1 gb to maximum.

and second aim is to get any update on jellybean like lolipop or Marshmellow

I request you to please guide me step by step to update rom. am new n never did anything recovery mode.

pls guide

thanks
[Micromax Canvas Magnus A117] navtab:
firstly, if u want to update your mobile then there are lots of rom available in this forum. but majority are jellybean. rite now there is no stable kitkat rom due to kernel issue and have battery drain. but still if u want to try for something new u can try it.

for the recovery mode n rom installation guide go to this link.

xdaforums.com/canvas-magnus/general/root-roms-mods-guide-micromax-canvas-t2569049
[Micromax Canvas Magnus A117] nileshbore:
thanks Sir,

One this more, pls help

pls suggest me which rom is the best one among all for a117 / jeallybean 4.2
[C++ or Other Android Development Languages] kshepitzki:
I am developing a camera application were I need to display the camera preview without conceivable latency, so when the user looks at the world and the preview together he shouldn’t conceive a time gap between them.

Every frame needs to be scaled, flipped, rotated and overlaid with a small image before being displayed but all these manipulations add less than 1ms to the computations so no problem there.

The minimal latency I measure on my app, on some example projects and on the built-in camera is 120ms (tested on Note4, Galaxy 4 etc) which is definitely noticeable.

I must reduce it to 60ms. The best frame rate I managed to get is a stable 31 fps. I tried both the old Camera API and Camera2 API both with SurfaceView and TextureView.

The app needs to run only on a single phone model which is based on the Snapdragon 615 SoC and the OmniVision 13850 camera running OS 5.0.2. I need to display the preview on a 1080x608 area of the display. So there is no shortage of CPU power, as can be seen from the attached Systrace the processor is idle most of the time:

https: // drive.google.com/open?id=0B780awz-gp4URDFPXzBNRVMwa0k

https: // drive.google.com/open?id=0B780awz-gp4UVEE2NGRmbEJPdlU

GPU profiling shows me that rendering is well below the 16ms mark. The 13850 can provide 30, 60 and even 120 fps.

If I understand the problem correctly, the limit comes from the camera VSync being capped at 32ms (to a maximum of 30 fps) by the Android system (maybe in the kernel drivers) or from the 13850 configuration.

According to Google Android is using triple buffering so at 32ms that’s 96ms which with some overheads can explains the 120ms.

I assume that if I could increase camera preview fps to 60 my latency will drop to 60ms.

There are many discussions how to achieve 60 fps for drawing graphics on the display but I can’t find much about getting 60 fps from the camera preview.

Is my assumption correct?

How do I decrease the camera preview latency to 60ms? (It’s a dedicated device so I am allowed to make changes to Linux and drivers).

Which files do I have to investigate?

Thanks
[Huawei Watch] Hanger4life:
The compass works on my phone fine. Please if someone can at least install the app to check operation. Thanks a bunch.
[Huawei Watch] Hanger4life:
Compass

All these views and not one piece of advice? Really? 34 people up to this point.......35 for who is reading this now......

And no one cares about a non functioning compass? Ahhhh
[Huawei Watch] bmg1001:
The Huawei Watch doesn't have a compass, so it won't work.
[Huawei Watch] Hanger4life:
Compass

Yes,no magnetic field compass.....sucks.
[T-Mobile Samsung Galaxy Note5] Chord_Hugo87:
what the heck is TDS? never heard of that one, its in your network mode dial *#2263#
[T-Mobile Samsung Galaxy Note5] DJ ELITE:
This is what GOOGLE says about TD-SCDMA aka TDS.
[T-Mobile Samsung Galaxy Note5] Chord_Hugo87:
obviously its not the same thing or else I wouldnt ask.
[T-Mobile Samsung Galaxy Note5] DJ ELITE:
What? You asked a question and I answered it. I provided a link that clearly states what it is:

"Time Division Synchronous Code Division Multiple Access (TD-SCDMA) or UTRA TDD 1.28 mcps low chip rate (UTRA-TDD LCR) is an air interface found in UMTS mobile telecommunications networks in China as an alternative to W-CDMA..."
[T-Mobile Samsung Galaxy Note5] Chord_Hugo87:
did you even look at the service mode?

its two different thing, at least that what it looks like in the service mode.

TDSCDMA and TDS
[T-Mobile Samsung Galaxy Note5] DJ ELITE:
Did you even read my answer?
[T-Mobile Samsung Galaxy Note5] Chord_Hugo87:
Obviously not if you given me something different...
[T-Mobile Samsung Galaxy Note5] DJ ELITE:
It's referring to a "Service Mode" in CHINA that is an alternative to W-CDMA. "TDS" is just the short version of "TD-SCDMA." :eek:

Ugh. I don't have enough "evens" to "can't" with you. :mad:
[T-Mobile Samsung Galaxy Note5] Chord_Hugo87:
......what? I don't even know what you are trying to say.
[T-Mobile Samsung Galaxy Note5] DJ ELITE:
Therein lies the problem. That's what happens when you won't accept help when it's given to you. If you read the info I linked you to, you'd have your answer. In fact I've been reiterating the answer repeatedly in this thread.

I'm done.
[T-Mobile Samsung Galaxy Note5] Spyderlotus:
I think he means the last thing you wrote lol. Which to me makes no sense either. I get the first post and the answer to it but that's irrelevant because I'm sure he means the part where you said " Ugh. I don't have enough " evens " to " cant " with you " lol. I wouldn't worry or get angry though. No need to rage quit here.
[T-Mobile Samsung Galaxy Note5] Chord_Hugo87:
lol apparently i'm not the only one.
[T-Mobile Samsung Galaxy Note5] george241312:
what the hell i cant "even" right now either.
[Galaxy A3, A5, A7, A8, A9 Android Development] jackeagle:
CyanogenMod for Samsung Galaxy A700FD

I will update various changes and updates in this thread until i release CM publicly.

What is the purpose of this thread ?

To keep updated with all changes and stability

lately m getting a lot of PM's asking ETA's and requests so this thread will be answer to them.

So has you all know CM12.1 booted successfully on A700FD so here is the list of things working and not working (not all things are tested since first major stuff)

Working:

Bluetooth

Auto Brightness

Sensors (few)

Screen Recording

Rear Camera (Photos and Videos)

Front Camera

Applications

Hardware Keys

Photos and Videos

Not Working :

WiFi

Audio

Radio (RIL) Calls,Msgs etc

Red Border Flashes (Occasional)

GPS

Thanks to my best buddy @RVR for testing various builds regularly.

FAQ/Notes

May i know ETA of CM ?

No. do not ask ETA's in any form. Its strictly against XDA Rules.

Google released Marshmallow can we have it for our device too ?

Answer is simple. Until CM12.1 is Stable for A700FD do not expect Android M.

Will you develop Marshmallow for A7 ?

Said above until lollipop is stable no Marshmallow :)

Can i have a download link for CM ?

I would have been more than happy to provide but sorry since these are highly experimental builds i would not recommend giving links to it.

So when will you release CM12 ?

Once Major bugs like WIFI and all are fixed i will make a first release :)

​
[Galaxy A3, A5, A7, A8, A9 Android Development] jackeagle:
reserved 1
[Galaxy A3, A5, A7, A8, A9 Android Development] jackeagle:
reserved 2
[Galaxy A3, A5, A7, A8, A9 Android Development] jackeagle:
uptil now only Bugs remaining are

1) Audio

2) RIL

3) WIFI

4) GPS

Rest all is working :) for more info see the OP :)
[Galaxy A3, A5, A7, A8, A9 Android Development] Audioffensive:
Can you give me your roomservice.xml?

I am busy for the A700F but i have to make a device tree from scratch.
[Galaxy A3, A5, A7, A8, A9 Android Development] jackeagle:
you cannot use qcom roomservice for exynos :) exynos is way different and it needs lot different hardware repos and modification its no way near to qcom type :)
[Galaxy A3, A5, A7, A8, A9 Android Development] Audioffensive:
I know :)

Am transforming a7lte device stuff to a7alte.

Am using some stuff from slte which also has the exynos 5340.

Was more qurious to the file itself. I made one with repos on my own giyhub but it won't sync notmally. Real weird.
[Galaxy A3, A5, A7, A8, A9 Android Development] jackeagle:
well honestly dont transform a7lte tree you will hardbrick your device. you have to come up with a tree from scratch. take reference of exynos devices trees and try to make your own. a7lte tree is only for qcom and hence you cannot transform/ref it for exynos :)
[Galaxy A3, A5, A7, A8, A9 Android Development] Audioffensive:
Hmmm good to know. I'll try to get another device to use then. Maybe the slte for this too.

Used to build several ROMs for HTC One S but there i had a normal device tree.

Now i have nothing. And i am not a real expert about that kind if stuff.
[Galaxy A3, A5, A7, A8, A9 Android Development] Audioffensive:
Do you know what device i could use best as base???
[Galaxy A3, A5, A7, A8, A9 Android Development] palimatix:
If it's not ready why will he upload. Even if he does what u will do when u can't use it as a daily driver as RIL functionality is not up. He has made several roms for other Galaxy models in past. Just enjoy the stock lollipop, it'll come with time. :)
[Galaxy A3, A5, A7, A8, A9 Android Development] lamplighter13:
Many of us don't even have Lollipop yet. LOL
[Galaxy A3, A5, A7, A8, A9 Android Development] Audioffensive:
Can you tell me what device to use best as base for a7alte then??

Thanks !!
[Galaxy A3, A5, A7, A8, A9 Android Development] malybru:
Mod Edit

Thread closed at the request of the [OP]

malybru

Forum Moderator
[Mi 3 Android Development] MonoIiths:
[IMG="woof"]http://s28.postimg.org/wopey1ynx/Woof.jpg[/IMG]

Overview

Pure AOSP for Cancro

Features

- No T-mobile theme engine or Layers, It is just stock AOSP.

- No .dat features

Download

Developer-Preview-1

Working

- Everything (unless I missed something, pretty sure I didn't)

Sources

My codebase is uploading.

GPL stuff:

Kernel used can be found here

Extended Information

I created this for firmware developers, It is for forking stock firmware such as MIUI.

If people choose to use this to port MIUI I obviously cannot stop them, but blah blah, beta software, blah.

This firmware uses the structure everyone loved in KitKat; I will not force anyone to deal with the .dat nonsense that we've all come to know and hate.

The codebase aligns very closely to what Xiaomi uses, and this code-base also aligns with many other vendor firmware.

Thx to: Datagutt, Heheda; co-maintainers :<

Thx to: Firmware developers, the source builders for this device
[Mi 3 Android Development] tendulkaradi:
What is this exactly?
[Mi 3 Android Development] mad-extrem:
Works on mi4 ?
[Mi 3 Android Development] MonoIiths:
It's pure AOSP, and yes it's good to work on any device that idents as Cancro

It is designed specifically for use with porting firmware, recovery has been modded in source to allow for this more easily as well.

It is easy to build either CAF or deCAF firmware in this build engine, I designed it to be very easy like CyanogenMod and it does accept CM configs.

HOWEVER IT IS AOSP AND NOT SLIMROM OR CYANOGEN I can't stress this enough, It is AOSP
[Mi 3 Android Development] droidead:
Will work for mi4.?
[Mi 3 Android Development] destz0r:
He already answered this question
[Mi 3 Android Development] contactwajeeh:
[MENTION=6915147]MonoIiths[/MENTION] can you try building the Android M 6.0 (AOSP) with the same tree and blobs?
[Mi 3 Android Development] droidead:
Link not working
[Mi 3 Android Development] vishal24387:
Ivan is already building android M. He will give a base rom which can be used for custom roms.
[Mi 3 Android Development] MonoIiths:
My work is better

Edit: At least with source-build; his AOSP is not useful for porting ROM where mine actually is.

Android M will be the same in that case; when I decide to build it
[Mi 3 Android Development] rreynaldo:
Ir blaster an FM work in this rom?
[Mi 3 Android Development] mig0r:
camera quality, HDR?
[Mi 3 Android Development] droidead:
hdr bug is still present, hdr mode click complete dark pictures, normal mode quality is fine. Can u manage to focus on camera quality .otherwise rom is good ,still haven't tested full
[Mi 3 Android Development] Bitti09:
Source is still uploading?
[Mi 3 Android Development] MonoIiths:
Yes, my build engine is really huge and has multiple GCC forks depending on the firmware used :<
[Mi 3 Android Development] Me_Ashish_:
Neat clean stock ROM. Though meant to for porting and etc stuff. But as a user I like it, it's smoooth.

Everything is great except some minor stuff eg: long Wi-Fi turning on time, WCDMA Only mode reset after reboot, CPU frequency control not working proper with stock kernel.

These are minor stuff and I'm not complaining neither asking you to do anything about it.

PS if anybody has a solution for 3G Only reset would be glad.

Hope I can see a 6.0 ROM by you soon :)
[Mi 3 Android Development] rpjuvvadi:
Also, there's a lag between screen and capacitive keys becoming inactive.. say if I turn off screen and the very next second I touch capacitive keys the screen wakes up.
[Mi 3 Android Development] tendulkaradi:
We already Have [MENTION=4707212]Bitti09[/MENTION] for this...we already have lots of lollipop ROMs...and u are late by a year ?
[Mi 3 Android Development] MonoIiths:
But you still don't have 5.1.1 MIUI v7
[Mi 3 Android Development] Riichard63:
But we have bunch of official lollipop custom roms.
[Mi 3 Android Development] mad-extrem:
It would be awesome if u build miui 7 with 5.1.1
[Mi 3 Android Development] darthkir:
So smooth and responsive! I coupled this ROM with the L Speed v3.0 trinity mod and it flies!
[Mi 3 Android Development] i snort flour:
Got to love them haters out there. He/she did this so anybody could easily port any rom that they wish to have that people like bitti, aniket, audahadi and etc have not already brought to the table. There are lots of roms out there and each suit different peoples needs and wants. Great job on trying to discourage rom development people. It's really nice to see you want to regress the progression instead of supporting it. I truly hope your dreams come true and everybody just quits bringing you these options to optimize your phones and user experience. As far as my feelings go great work Monoliths and thank you for taking the time to making an easy way for us to bring to the table the roms we personally enjoy or just have a barebone aosp. Your effort is appreciated by me and others as you can see.
[Mi 3 Android Development] Skar3:
Thank you [MENTION=2700857]Monoliths[/MENTION]! It's really possibile to build the miui 7 with Android 5.1.1? :eek:
[Mi 3 Android Development] i snort flour:
Shouldn't be too hard. Aniket has a good YouTube video that shows you what files you need to replace to port a rom. From there you just need unzip this file and grab a lollipop miui such as the one for the mi2 and unzip that. Followed by uncompressing the .DAT file in the miui lollipop rom into an img then open the img with ext2fs and save the files to your hard drive (great decompression forum by xpirit here on xda). Swap the files that aniket shows you on YouTube into this roms system folder. Edit the build.Prop. then zip this rom back up and flash it to your phone. Bam you just made the first mi3/4 lollipop miui that you can share after uploading to github and giving proper credits to monoliths, aniket, xpirit and miui.

This is why this rom is so great. Decompression of .Dat is really easy but compressing it back into a workable .Dat file was a nightmare and left me stumped and frustrated even though everything seemed to have gone correctly. This rom will surely bring lots more roms to the table such as liquid smooth and carbon which are great along with tons of other less known roms. I might try this myself in a week or two.
[Mi 3 Android Development] Tomi_Ohl:
There's a tool which directly decompiles dat files.

But this ROM doesn't have them, so no need for compiling them back.

Also, there's a MIUI patchrom released by Xiaomi, anyone can use it.
[Mi 3 Android Development] Skar3:
Please build a miui 7 lollipop! ?
[Mi 3 Android Development] destz0r:
correction: miui 7 marshmallow
[Mi 3 Android Development] Skar3:
I will be happy also with a stock Mashmallow :P
[Mi 3 Android Development] MonoIiths:
It's also intended to be used with FlyMe, IUNI and other 5.1 firmware

People are upset about the slightly longer wifi scan time, but I optimized this especially to maximize battery; when I'm out for the day I use AOSP and there is no need for any part of this device to be CONSTANTLY checking for a signal

Yes I built this intending for superusers/developers to use it which is a little different than how pretty much every ROM is built presently

Here are ROMs that are actually AOSP:

- OmniROM

* Very Pure

* No deep changes that break compatibility regardless of exclusive features

- SlimROM

* Almost Pure

* More modern HW support than Omni to a degree

- F-AOSP

This is the most pure firmware on this list.

* Pure AOSP

* Almost no modern HW support, this must be added manually

- Clover

* Almost Pure

* no .dat

* CAF support

* Very modern HW support

* Dummy init.rc files for adding MIUI text (The windows kernel editor doesn't allow for adding new files like init.miui.rc)

If you don't use one of the above firmware, you will not be able to port vendor firmware easily.

I won't explain why it has to be AOSP, but I will say it has to be AOSP which is a lot more generous with knowledge than how people have been in the past few months

I mean Clover was never even intended for people; It was only intended for people I develop with and myself. It is not pure AOSP in the sense that it does not use .dat compression and changes have been made to recovery; but none of these things inhibit development only help it.

We intended to use it to mass-push things like TouchWiz and I still want to do this, I only made this a public thing because on a personal level I felt the amount of people doing development work had dropped way too much; there are no people porting anymore.

It's kind of sad
[Mi 3 Android Development] MonoIiths:
So here's the thing.

Let's say we have different devices and you build Clover for your device and use it to port uh... Sense 7 or whatever.

Well I like your project and admire it; I want to use Sense too so I'll build Clover and just take your Frameworks; Media... they'll work in my device since our 'base' ROM was built from the same code. Everything is like this

I don't know what Ivan does at Xiaomi; I know the 'AOSP' ROMs he releases are not the same source as Xiaomi builds their MIUI releases on, they appear to be his personal projects.

I already know what they used to generate the base of their firmware for the devices mentioned; I have those code-bases they are not hard to find
[Mi 3 Android Development] Bitti09:
BTW : f-aosp supports modern caf devices and uses cm style device tree. The biggest differences between my aosp rom and yours seems to be the image format and the theme function.