yashsingh1/xdaforums huggingface dataset:
[Wildfire Android Development] Stone. Cold:
I agree with wasim, we all could take a look at it :)

All cm devs :good: also i almost found a fix for the ICS camera, but within 6 mins it went off.
[Wildfire Android Development] Pator57:
No don't thinks, is only because i don't found an enough good tuto in porting miuiv5
[Wildfire Android Development] faZevoLv:
yeah its a memory leak, that's why it was ddisabled.
[Wildfire Android Development] Stone. Cold:
Yeah, also I've opened up the libs in ICS saw the lib camera, opened that up and saw so many errors xD

Can you take a look at it please? I'm not sure if i can fix those.
[Wildfire Android Development] faZevoLv:
how are you editing the lib?
[Wildfire Android Development] Stone. Cold:
No i'm not editing this, I've used Notepad ++ just opened it a saw bunch of not important stuff at first, so I've searched "Android" Click enter many times till some errors started to show up in the Lib, i'll try post some screen shots later :)

I hope we all can take a look at it ;)

This is for the all the libs with name Camera next to it.
[Wildfire Android Development] faZevoLv:
Ill take a look tomorrow at the camera source code as I'm not at my own laptop right now. hopefully we can fix it:D ill probably upload the source to my github so we can all contribute if you know how to use it:)
[Wildfire Android Development] Stone. Cold:
New to this, would like to learn though.

Also i'll try to fix some bugs :D
[Wildfire Android Development] GeekyDroid:
Hey guys!

As we told much in this thread, which is a but off topic as this is a thread related to CM10.1 :D

But I'll not be angry at you!

Anyways that's why I created this thread: http://xdaforums.com/showthread.php?t=2493084

Now feel free to talk about developments :)
[Wildfire Android Development] faZevoLv:
Could you upload your Local_manifest.xml for cm-10.1 please:)
[Wildfire Android Development] GeekyDroid:
Sure I can.

Wait for some minutes.

EDIT:- I added it in my Google Drive folder where the GApps and the CM10.1 ZIP is placed.Please read the "NOTE:-" I added in OP!
[Wildfire Android Development] faZevoLv:
Thanks!:)
[Wildfire Android Development] Mr.Jay:
How fast is this rom?

HTC Desire X || Android 4.1.2 || mySENSEdx5 RC3.0
[Wildfire Android Development] Stone. Cold:
It's kinda fast, although to be honest the ROM is kinda slow, because the 4.2.2 can't handle the CPU.

Which is why we need a new Kernal for the Buzz, but we should be happy that 4.2.2 is on the buzz, never has, but now is ;)

You can try the 4.1.2 which is has less lags, and is overall good.

Also this, only reason it's not for daily, is because there are bugs that we can't live with and because it's slow.

But still awesome!

Also i wish if this ROM has the same speed as cm7, that would be amazing!

You can try it :good: it's good but kinda laggy.
[Wildfire Android Development] drewniany92:
if it will be responsive and.smooth as ics roms then it will be big success. there is no chances to reach cm7 speed ):
[Wildfire Android Development] GeekyDroid:
Yes, Android 4.2.2 is very slow as Buzz is a low-end device.Also I can't live with the bugs so I'll try to fix them.

Let's hope the best for our Buzz!
[Wildfire Android Development] Stone. Cold:
Yeah let's hope we can make this function well as cm9 or cm7 :D

this ROM may reach cm7 speed :)
[Wildfire Android Development] GeekyDroid:
Hey guys.I'm going off for some days.Now exams started and I can't continue anymore.So I'll make a break of development.Don't worry I'll come back soon!

I hope the best for our Buzz!

All the best guys! :)
[Wildfire Android Development] Stone. Cold:
Take all the time you need, my exams are also coming up within 2-3 weeks or so :)

All the best and all the best of luck from us all ;)

I hope you ace the exams :D
[Wildfire Android Development] GeekyDroid:
Hey Buzzers!

New version is up :D

Version 2013-11-01:

What's new in this version?

-Compiled with Linaro Toolchains

-Fixed Wi-Fi(Thanks to ErwinP)

-Fixed Bluetooth(Thanks to ErwinP)

-Fixed Network(Thanks to ErwinP)

-Compiled with Media-Legacy and Display-Legacy patch

-Hopefully not so laggy anymore

Bugs left:

-Screenshot

-Taskpreview

-Media Lag

Now it can be used as a daily ROM as the main bugs are fixed now.A big thanks goes to ErwinP.

Please hit thanks if you like my work! :)​
[Wildfire Android Development] drewniany92:
how smooth is it comparing to ics roms?(:

Wysyłane z mojego HTC Wildfire za pomocą Tapatalk 2
[Wildfire Android Development] GeekyDroid:
It's not so smooth as ICS ROM's of course.We should be happy that we have Android 4.2.2 for our Wildfire, as it's an ARM-V6 low-end device.
[Wildfire Android Development] drewniany92:
yup, i know it never will be smooth as ics, just asking if there is big difference between those ones (;

Wysyłane z mojego HTC Wildfire za pomocą Tapatalk 2
[Wildfire Android Development] GeekyDroid:
Well, test it on your own. ;)

I can just say for me it's okay.But ICS has much better performence.
[Wildfire Android Development] arjunrk67:
Forgot to edit bug list at the OP
[Wildfire Android Development] GeekyDroid:
No, these bugs are still left! :rolleyes:
[Wildfire Android Development] Pator57:
Camera is'nt working ? :o

If yes, have you try to add some camera lib from other device cm10.1 like the galaxy mini ? :o
[Wildfire Android Development] GeekyDroid:
No, I didn't try.

Let me check it when I get time!
[Wildfire Android Development] Stone. Cold:
Wow I'm amazed o.O congratulations on the new build :D
[Wildfire Android Development] GeekyDroid:
Thank you! :D
[Wildfire Android Development] Stone. Cold:
No problemo :D
[Wildfire Android Development] Pator57:
Don't forget to change the title of the rom, to see that you make a new build.
[Wildfire Android Development] GeekyDroid:
Thanks for reminding me!
[Wildfire Android Development] arjunrk67:
Bro hows the camera progress is going did galaxy mini libs worked
[Wildfire Android Development] GeekyDroid:
Can't test right now, sorry!

I'm busy with school and other projects.

But I think it'll not work with other device's lib!
[Wildfire Android Development] Stone. Cold:
Take your time :)

Also I've got some school work to do, got to hand in my GSCE art work in tomorrow
[Wildfire Android Development] disaster2009:
this rom have overclock option ? :p
[Wildfire Android Development] drewniany92:
it should have this option as every cyanogenmod rom (;

Wysłane z mojego Wildfire przy użyciu Tapatalka
[Wildfire Android Development] arjunrk67:
I wanted to ask weather this rom has the same media lag as all other cm 10.X builds have and if it has is there any chance to be fixed
[Wildfire Android Development] Wasimk32:
see this.

http://xdaforums.com/showpost.php?p=45143058&postcount=16
[Wildfire Android Development] disaster2009:
more clock may help :D
[Wildfire Android Development] Pator57:
For when cm11 ? ;)

Hope you can fix the bug on this rom too.
[Wildfire Android Development] arjunrk67:
Hey Wasimk32 i wanted to ask will it allow us to play videos and all stuff and also streaming??
[Wildfire Android Development] Wasimk32:
sadly no.
[Wildfire Android Development] arjunrk67:
Then what does it do
[Wildfire Android Development] Wasimk32:
it does remove the lag between skipping two music tracks.When i tried it,the lag was unbearable,and doing as I said removed that lag completely.

Use some cm9 based rom instead,if you want more things working.
[Wildfire Android Development] GeekyDroid:
Yes, it's overclockable, because it's compiled with a kernel that hace OC as a feature.

Yes, it has a media lag and it's not fixable if you overclock the CPU more.

And I think there is no chance for CM11 as it's very different from CM10.1 and we only have CM10.1 device tree.We need someone who is good in updating device trees.I can't do this task as it's very hard and I'm so advanced.I'll need to learn a lot pros like ErwinP.
[Wildfire Android Development] disaster2009:
Good to have some rom 4.2.2 with time and help of others maybe MORE stable ...
[Wildfire Android Development] GeekyDroid:
Yes, now christmas is coming and then I have a break from school, I can make another build which will be more stable! :)
[Wildfire Android Development] arjunrk67:
Hey i wanted to ask that why cant we libs of galaxy fit or any other similar device's libs cause galaxy fit has got a stable and bug free cm10.1

Can someone port that cm10.1 on our willy??

P.S. ,I tried to port but i dont have any knowledge about porting ,cause I'm not a dev and also somehow i cant extract the zip file of this cm10.1 rom for our willy ,so that i can try to port,but no help

It say that the updater script and the latin IME apk is not compressed in proper way and it also stucks at 85% of extraction
[Wildfire Android Development] disaster2009:
Hi,camera dont work ,but with other aplicacion camera from market work ? :laugh:
[Wildfire Android Development] GeekyDroid:
Try with Camera ICS, it should work!
[Wildfire Android Development] GeekyDroid:
1.We need a ROM as base to port ROMs.And if we have an unstable base ROM, then how we can get a stable port ROM?

2.Porting GB and ICS ROMs is very easy, but porting JB+ ROMs is very hard and it mostly causes into bootloop.

2 Reasons why we don't port CM10+ ROMs from other devices! :p
[Wildfire Android Development] arjunrk67:
But its armv6 and it might be stable, cant we just try because galaxy fit has a stable cm 10.1 and it is armv6 so i think it might work
[Wildfire Android Development] Wasimk32:
Porting won't work wonders coz the real difference in our phone and other armv6 devices is the gpu! Almost all of them have a gpu, which makes a lot of difference to overall performance. And yeah, porting jb roms is difficult. That's because of extraction errors, jb roms have different files with same exact names in single folder, this confuses the extraction software. If one wants to port, he should do it without extracting zips.
[Wildfire Android Development] GeekyDroid:
Yes, you are completely right.I flashed CM10.1 on ZTE Blade which has 600 MHz CPU and it was still smooth and on Wildfire it's very laggy.I think to that it's because of the missing GPU!
[Wildfire Android Development] arjunrk67:
hey Wasimk32 i wanted to ask cant we use mx player in s/w mode to run videos or any other way because in s/w mode it does not require gpu

Also i wanted to ask that if i am not able to extract the zip of this rom but i extracted the cm 10.1 of galaxy fit and there was no problem in extraction the problem came only in the rom of buzz
[Wildfire Android Development] antivirtel:
Bootloop

I've just flashed in for my Wildfire, and it reboots automatically in every 1-4 minutes. I was using this CM10 based ROM before, and it was pretty stable. You wrote, that we could expect a new release - can you predict when?

Thank you very much for your work!

Ps. I had a Java course on the university, and if you want, I'll try to logcat, and send the logs, and maybe help in development - but I'm not involved in the Android development at all, so this is very new to me! Tell me if you want the logcat otherwise!
[Wildfire Android Development] GeekyDroid:
Hi,

Well, okay, for me it was pretty stable.Maybe I uplaoded the wrong file. :mad:

Because in one build I had this problem, but I solved it by removing media-legacy and desplay-legacy as it's very unstable.

But I deleted my CM10.1 source so it's 100% not aynmore on my harddrive.I was running a build a week ago but it didn't boot up, I can upload it here but it's useless.It won't boot up.

I don't know why it didn't boot and I tried everything so I gave up.

And now I'm busy with my builds for Samsung Galaxy S3.So I left this development here.

Thanks for your support!

EDIT: Well, I was thinking of it, maybe I'll do a last build if I have some time.If it boots up and everything is okay, I will upload and release it as a final build.
[Wildfire Android Development] antivirtel:
Ok, I'm looking forward to see a new release of CM10.1. Thank you! :good:
[Wildfire Android Development] GeekyDroid:
No problem.It's my duty to give you a stable CM10.1, as I began this project, so I have to complete it! :angel:
[Wildfire Android Development] antivirtel:
Is there anything new? I'd like to try it soon!
[Wildfire Android Development] GeekyDroid:
Today is my last day of resting.Tomorrow I must learn for school...

I'll try my best to upload today a new build so you can test.

Have a nice day!
[Wildfire Android Development] Pator57:
Great to see you back SasaKovic, for a day :D

Hope you will did a new build if you have time :highfive:
[Wildfire Android Development] GeekyDroid:
The new build is complete and I flashed it now.Let's see if it boots.I hope it does!

I will upload it if it boots! :good:

Be ready for a new build! :D
[Wildfire Android Development] GeekyDroid:
I think this thread is already dead but a new build is up! :D

The good message is: It's more stable then the previous builds(Everything working and random reboots are fixed).

The bad message is: It's extremely laggy! :rolleyes:

Sorry for that, but it's not my fault that HTC didn't build a GPU in.This build is a evidence that higher version will not run on HTC Buzz.Flash it and see yourself!

What's new?

-Resynced source

-CM updates

-More stable

-Compiled without media-legacy and display-legacy

Hit thanks if you liked it! :)
[Wildfire Android Development] methuselah:
so i am downloading right now and trying. it

well i am going to try this ROM it because of your efforts that its been possible....:good:

sasa well we have working JB can't we make good and best ROMS out of them ??

---------- Post added at 04:14 PM ---------- Previous post was at 04:10 PM ----------

well is the upload is up because my download speed is slow like hell i can't take risks of wrong links :cowboy:
[Wildfire Android Development] methuselah:
Well it reboots still

well it is still rebooting again and again.after each and every step it is rebooting
[Wildfire Android Development] Stone. Cold:
Awesome to see you back :D can't wait ;)

---------- Post added at 04:12 PM ---------- Previous post was at 04:10 PM ----------

Gonna try it tomorrow got to sleep ;)
[Wildfire Android Development] jody04c:
This thread is most definitely alive and kicking ass. Thanks a million for the Jelly Bean shamazeballs for Wildfire!! Keep up the efforts, much much appreciated for my little backup phone.
[Wildfire Android Development] arjunrk67:
So now is the video player working ?????
[Wildfire Android Development] GeekyDroid:
Sorry, but I don't know.I haven't tested it.But video player will work.It just laggs.It's called 'media lag'.
[Wildfire Android Development] neon$$$$:
Can we do a project on halo with cm9 I am too interested.

CURRENT ROM :CUSTOM SENSE3.0 _[HTC WILDFIRE]

KERNAL:------

GALAXY MINI: CUSTOM

ANDROID 4.4.2
[Wildfire Android Development] arjunrk67:
can u please test it cause right now i don't have my wildfire thats why
[Wildfire Android Development] GeekyDroid:
Is this still alive?

I want to start building a new build, as now I'm done with school(temporary), so I can start something :D

I want to make this build as stable as the first build. As we know the first build was stable but there were BT and WIFI bug. The second and the third build were bug fixed but very unstable! I think I know the reason. That's why I'm back. I think I'll start a whole new project for Wildfire! CM10.2! If it's stable, I'll start working on KitKat!

Hope the best guys. Maybe our Buzz will be of new life soon! :D
[Wildfire Android Development] Familienpapi:
That's a great idea. I'm looking forward for a stable CM10.2 for the Wildfire S.

Could you look for the Wi-Fi Hotspot as well? This doesn't work now.

gesendet von meinem Samsung Note 3 via Tapatalk
[G2 Q&A, Help & Troubleshooting] fr3quency:
Title says it all. Anyone got the problem? Is it the camera's fault? Do I need to return it? Or it's just the software/type of camera?

Thanks!!
[G2 Q&A, Help & Troubleshooting] Mightym83:
I get that too. On Auto mode.
[Galaxy Note 3 Q&A, Help & Troubleshooting] sehooo:
(Region lock - sim lock - Knox - warranty - custom Rom - full backup)

help us link all these expression together :eek:

1- if i jumped from stock rom of unlocked area TO custom rom or stock rom of locked area , What will happen ?lock ? warranty ?

2- what is the difference between simlocked and region locked ?

3- if i make a full backup to my phone + EFS backup ,is that make me in safe place with warranty or i need to backup the certificate of Knox? and if how can i backup it ?
[Nexus 7 (2013) General] Hnk1:
Hi there

I am thinking of making a new Rom for Nexus 7 2013 WIFI (flo) and I would like to see what I can do for you. However, I am doing a little survey before I start developing the Rom. Kindly tell me what do you need in a ROM.

The rom will be build from source of 4.3 most probably but it's not set to stone yet. I might start working when 4.4 comes for our device.

Do you want to see specific softwares or specific modification or anything ?

Things like prerooted, custom boot animations,some softwares?

If I can do that, I will happy to do that for you all.

What do you like to see in the ROM, write your requests!

UPDATE :

Currently working on Xperia L, SP & Galaxy star so this project may be delayed till 4.4 is released
[Nexus 7 (2013) General] Muikkuman:
One think I like is that it's already rooted.
[Nexus 7 (2013) General] NekroWolfen:
Unofficial Carbon with Tablet UI, Carbon has so many customizing features, however, what are you aiming for? swiss knife full-featured ROM or a slim stock-like ROM?
[Nexus 7 (2013) General] Vaykadji:
I really love halo and piecontrol to use full-screen all the time.

I would like a real multitasking like split the screen in half for example, with 2 different apps running.

I would also like a fully translated rom (in French) because ppl who develops roms usually forget about other languages than English for their new menu entries for example.

I'd also advise you to keep the stock bootanimation, Devs like to change it for a custom name, but it usually is not as good as stock (like PA, which I love, but hated the bootanimation).

Prerooted is always welcome.

I would also like a way to use different languages for voice recognition (not at the same time but easily changeable). I use French as much as English and it pisses me off that I can only use one voice recognition language.

An aosp browser of course.

Get rid of native apps other than gplay and Google search and maps, such as music, books,...

USB connection other than MTP would be nice for Linux users.

Stickymount like option built-in for USB keys, hard drives,...

An "advanced options" menu with startup apps & services, voltage control.

Maybe a modified gplay that can reach freedroid repos.

Built-in adblock plus to get rid of the annoying persistent notification (under "advanced options" maybe?)

That's rather an app but... A keyboard with advanced soft keys like ctrl-c ctrl-v and many others.

As many gpl licensed codes as possible (ideologically important for me)

... That's all I can think of right now :p
[Nexus 7 (2013) General] Old-school:
Just one: audio over USB. This is the only thing tying me to CM and their CAF. If only someone would show me how to port their USB portion I would jump ship to AOSP immediately.
[Nexus 7 (2013) General] RKight:
I'd like to see something completely different. Every single ROM is AOSP plus this feature or that feature. I was excited for Multi-ROM for this device so I could try some new ROMs but they're all exactly the same plus or minus a few features. I find myself returning to stock 4.3 every time.
[Nexus 7 (2013) General] Hnk1:
Noted down. Now I am looking at suggestions and out of all those, what is possible for me. I will update you all after looking at each one in detail.

Maybe two versions. One with just needed features while the otherone with loads of them. I am not sure how much time it will take me. I have already ordered a new hard disk as it will take loads of space!
[Nexus 7 (2013) General] player911:
I'm easy.

I just like Center Clock. Theme Support. Navigation bar Height. Transparency.

The Status Bar Data Speed is handy.
[Nexus 7 (2013) General] NekroWolfen:
Thanks, it will probably take a lot of time. :)
[Nexus 7 (2013) General] hagensieker:
Request kernel module loading for usb 3G with PPPWidget

Also USB DAC support and the ability to simultaneously charge with an OTG Y cable while hooked to DAC

John
[Nexus 7 (2013) General] Hnk1:
I have already requested files from different devices that I might be able to port to nexus. What you are asking could be done! Noted down !

I am not sure if I can do that. It seems unlikely I am afraid!
[Verizon Samsung Galaxy S III] wcsd106:
To make a long story short, my wife dropped her Samsung Galaxy S3 i535 phone a couple weeks ago and shattered the front glass. I ordered the replacement glass on eBay and proceeded to get it installed this past week.

One of the things I noticed was that none of the repair videos adequately documented how to route and attach the button for the home keys at the bottom of the screen. I was finally able to get the old home button ribbon cable detached from the phone and pulled free from its location. I noticed that there was still quite a bit of adhesive left on the resting location for the home key pc board (located a few mm in front of the ribbon cable that connects to the lcd assembly.)

I made the mistake of thinking that the adhesive consisted of some form of double sided tape, so using a small blade and a pair of forceps I began removing the adhesive. Turns out, the adhesive was attached to a felt-like material that was covering the back of the LCD. Once removed, I noticed that the section of the screen from which the felt had been removed was slightly discolored.

I proceeded to reassemble the phone

with the new glass

, and it is working correctly, with one exception:

The

entire screen

(not just the area where the felt was removed) appears to have a

greenish tint

to it. This is most notable when booting the phone. The SAMSUNG logo appears as almost a neon green (My wife assures me this should be white) and the booting animation is mostly green (She assures me it was multicolored)

A couple of questions here:

Did the piece of material I removed from the back of the LCD cause this problem, or should I be looking at something else for a solution?

Is there any chance this felt-like material contained the backlighting for the LCD Screen?

If not, could just a small section of missing felt allow enough light to escape to discolor the entire screen?

Also, since I obviously can't replace the felt, would coating the expose area with some form of paint or something work to restore the proper coloring to the phone?

I am currently looking at other replacement lcd assemblies which, from what I can tell, simply involve moving the motherboard from the old phone into the new assembly, connecting it, then putting the back cover onto the phone. If I can afford spending the $100-150 that these cost, I would like to avoid it. If this is my only suitable solution at this time, I would like a definitive answer so that I can make the purchase and get her phone back to working order.

Thank You all for taking the time to read my post, I can post pictures later to elaborate on what I am describing, but my wife and I are both at work at the moment and I don't currently have her phone to take a photo of.
[Verizon Samsung Galaxy S III] screwyluie:
Pictures would be nice. However your back light shouldn't discolor your screen. My guess is you loosed a cable or something else causing the screen to discolor.
[Verizon Samsung Galaxy S III] wcsd106:
I will get pictures posted this afternoon. After taking a little more time to look at it earlier today, it appears that Green and Blue colors are working, I just haven't got any red.

Do you know where to find a diagram of what ribbon connectors control what aspect of the phone?
[Verizon Samsung Galaxy S III] wcsd106:
Pictures

A little late, but here are the pictures of my wife's Galaxy S III (i535)