Android Lollipop (AOSP builds) - Galaxy Note 3 General

This thread can be in violation of the XDA rules, but those were not clear in this regard I have therefore still opened this thread and I would like to ask the MODs to close this thread if it does appear to be in violation of the rules. I also would like to mention that this thread does not have the intention to disrespect any developers and that I appreciate the work every dev has done for the Note 3.
What I would like to be discussed in this thread is the stability of the different Android Lollipop roms. Since most of the devs have not made a seperate thread for their (at this stage alpha) builds of Lollipop. I would like to collect the experiences of the users from these alpha's.
At this stage there are 3 builds of Lollipop that I know of in alphabetical order:
Slayer (it is said to be a port, but since the original rom was for the HLTETMO. I think that it is mostly only a change in the 'device checking' file. The dev has himself stated that he does not intend to make any more builds in the near future it was more a proof of concept. The unofficial thread for Slayer's rom: http://forum.xda-developers.com/gal...m-cyanogenmod-12-lollipop-build-1-16-t2942687
Temasek: this is just an experimental build this dev has posted. I do not have any statement regarding support. Now on preview 2: http://forum.xda-developers.com/showpost.php?p=56934897&postcount=6046
Zion: also just an initial build (I think). Also no statements regarding support. The build from ZION: http://forum.xda-developers.com/showpost.php?p=56900235&postcount=542
I would like the structure of the posts in this thread to be:
Device: hlte/hltespr/hltetmo/hltevzw/hlteatt/hltexx/hlteusc/hltevan
ROM: Slayer/Temasek/Zion
What works: WIFI/Calling/etc.
What does not work/bugs: Random reboots, no network
Other remarks:
Again, if I have offended anyone in anyway I would like to apologise and I didn't intend to do so. Mod's could you then remove this thread.
And most importantly I would like to thank the devs for releasing these builds.

I can't even get temasek's build to boot.

speedyjay said:
I can't even get temasek's build to boot.
Click to expand...
Click to collapse
Booted and with LTE.

temasek said:
Booted and with LTE.
Click to expand...
Click to collapse
Share and share alike my good friend?? Lol

I've been using android 5.0 from slayer por as daily driver, I have HLTE and I have wifi, LTE, bluetooth and all works so nice and beautiful. The main problems are the camera and there are a lot of apps that not work
Today I will to try Temasek's port

Miniprepumen said:
I've been using android 5.0 from slayer por as daily driver, I have HLTE and I have wifi, LTE, bluetooth and all works so nice and beautiful. The main problems are the camera and there are a lot of apps that not work
Today I will to try Temasek's port
Click to expand...
Click to collapse
Port? It's built from source and not a port.
PREVIEW 2 is up.

temasek said:
Port? It's built from source and not a port.
PREVIEW 2 is up.
Click to expand...
Click to collapse
Sorry mistake
Downloading !!

Miniprepumen said:
Sorry mistake
Downloading !!
Click to expand...
Click to collapse
It's a preview so don't get so excited.

temasek said:
It's a preview so don't get so excited.
Click to expand...
Click to collapse
Works very well, LTE works normal, wifi too, I can do calls without any problem, and very very smooth and fast.
Problems for now: There are apps that not work, but very very good job. Thanks really
Edit: camera not works.

Wait where is zion's build? How's google now on all these builds? On Slayer's it's broken / causes reboots

My two cents on the port and on temaseks build.
The port is quite stable and random reboots usually come from incompatible apps or missing libs (as i read). I have managed to rest a lot of apps causing me trouble, but a lot of them are not yet optimized for L. The rom also has anomalies, strange stuff like closing all apps will close system ui (which is a bug not a feature, just in case i confused you). Weird stuff crash, such as Documents, which seems to be the mother of all other apps since it uses it to pick files for attach and e.t.c..
where as temaseks is very fragile. Not sure why but i barely made it to the homescreen, it kept on crashing a lot and rebooting prior to the homescreen.
Both are sort of proof of concepts, the port however is quite damn stable for an initial preview build, and yea, both surprised me with their early appearance

PlutoDelic said:
My two cents on the port and on temaseks build.
The port is quite stable and random reboots usually come from incompatible apps or missing libs (as i read). I have managed to rest a lot of apps causing me trouble, but a lot of them are not yet optimized for L. The rom also has anomalies, strange stuff like closing all apps will close system ui (which is a bug not a feature, just in case i confused you). Weird stuff crash, such as Documents, which seems to be the mother of all other apps since it uses it to pick files for attach and e.t.c..
where as temaseks is very fragile. Not sure why but i barely made it to the homescreen, it kept on crashing a lot and rebooting prior to the homescreen.
Both are sort of proof of concepts, the port however is quite damn stable for an initial preview build, and yea, both surprised me with their early appearance
Click to expand...
Click to collapse
Preview 2?

Tema prev 2 fixes the touch button wake for me. But WiFi + Google now still cases reboot. Google now hotword doesn't seem to work which it does on slayer. All camera apps fc. And the home button still doesn't wake the device. Aside from those it seems near perfect. Thanks a ton!
Sent from my SM-N9005 using XDA Premium HD app

temasek said:
Preview 2?
Click to expand...
Click to collapse
Actually no my friend, i just read it 10 minutes ago and am downloading as i write.
I did not want to spam around and used this thread exactly for expressing opinions, as i know both roms are early stage builds and none of the devs should be bombarded with requests anyway.
Will report back.

I just need spotify working them I'm happy as Larry lol

temasek said:
Preview 2?
Click to expand...
Click to collapse
One hell of a ROM at the moment, havent had a single crash and loaded loads of apps that used to crash in nearly all Lollipop builds. Too bad your ROM doesnt have the flashlight in the notification drawer, was very useful.

Right I must be blind. I can only find the ROM thread that is a cyanogenmod 12 PORT.
Can't even find any other Lollipop ROM!
can someone share the links please?
Hope their compatible with the international Note 3

Suggestion
hom.hom said:
This thread can be in violation of the XDA rules, but those were not clear in this regard I have therefore still opened this thread and I would like to ask the MODs to close this thread if it does appear to be in violation of the rules. I also would like to mention that this thread does not have the intention to disrespect any developers and that I appreciate the work every dev has done for the Note 3......
At this stage there are 3 builds of Lollipop that I know of in alphabetical order:
Slayer (it is said to be a port, but since the original rom was for the HLTETMO. I think that it is mostly only a change in the 'device checking' file. The dev has himself stated that he does not intend to make any more builds in the near future it was more a proof of concept.
Temasek: this is just an experimental build this dev has posted. I do not have any statement regarding support.
Zion: also just an initial build (I think). Also no statements regarding support.
I would like the structure of the posts in this thread to be:
ROM: Slayer/Temasek/Zion
What works: WIFI/Calling/etc.
What does not work/bugs: Random reboots, no network
Other remarks:
Again, if I have offended anyone in anyway I would like to apologise and I didn't intend to do so. Mod's could you then remove this thread.
And most importantly I would like to thank the devs for releasing these builds.
Click to expand...
Click to collapse
We can assume there will be a ton of reports here of what is working and what isn't (probably duplicates or even 5 times the same report as we saw in Unnofficial CM12 Port from Jamal's thread...). I would advise everyone to post phone info after every report. Because there is a confusion of what is working on which model.... You might wanna add this to OP so people can actually see since my post will be long forgotten after pages and pages of comments.
Plus you might add link to Jamal's thread and download links for Zion and Temasek's ROM... Not everyone has those since they are buried in an ocean of posts over at Jamall's thread. @AndroidInsanity here they are:
1. @jamal2367 thread
http://forum.xda-developers.com/gal...m-cyanogenmod-12-lollipop-build-1-16-t2942687
2. @ZION959 cm 12 unofficial
https://s.basketbuild.com/devs/Zion959/L/HLTE/
3. @temasek Build
http://d-h.st/users/temasek/?fld_id=41330#files
SM-N9005 (would be an example, so people know what phone is about. I know some have details listed in signature but not everyone).

and as always noone cares about exynos note 3...

ereneren564 said:
and as always noone cares about exynos note 3...
Click to expand...
Click to collapse
And rightfully so, if you buy an exynos device you should know that developers do not support these devices. Because the documentation of exynos chips is practically non existent. I am sorry, but with regard to custom aosp roms and devices with exynos chip consider this an expensive lesson. For support for these devices complain to Samsung.

Related

[ROM] Unofficial Thread For CyanogenMod 7 Nightlies Discussion (Final OP Update 7/21)

Well guys, it's a sad thing to have to say, but I've finally made the decision to move on from the Hero. Currently, I now own an EVO 3D and loving it to pieces. The Hero has been a ridiculously resilient phone. What's been done with it is nothing short of incredible. It's gone through and will probably continue to go through every version of Android that we've thrown at it.
It's been a great deal of fun being at this section of XDA, but now I must take my leave. Thank you to everyone who made my phone experience what it was.
The links in this thread should remain accurate with no need to change them, but I will not be updating it when major versions come out or if RCs come out.
Click to expand...
Click to collapse
** These CyanogenMod builds are highly experimental and unsupported. [/FONT]
**
** Please refrain from submitting bug reports for any issues
** you may encounter while running one of these builds.
**
** Submitting bug reports on nightly builds is the leading
** cause of male impotence.
Links
ROM: http://mirror.teamdouche.net/?device=heroc
Gapps: Universal GApps Package
Changelog: cm-nightlies by appspot
F.A.Q.
What is this?
CyanogenMod is an aftermarket firmware for a number of cell phones based on the open-source Android operating system. It offers features not found in the official Android based firmwares of vendors of these cell phones. It is community built, and open source, the heart of what Android stands for. The current version of Android that CyanogenMod is built on is 2.3 (Also known as Gingerbread)
DISCLAIMER: This is not my work. I did not help build CyanogenMod in any way, shape or form. Do NOT donate me or thank me with the assumption that I had any part in dev'ing this. I simply created this thread to help you keep track of the nightlies.
Any accidental donations given to me because of this thread will be promptly returned.
The real people you should be donating to is jaybob (if you can help us convince him to add a donate link for his hard work), Decad3nce, and of course, Darchstar himself.
Darchstar!? and Deca? and jaybob? and possibly some asop on the side?
oh man, these CM7 nightlies are gonna kick ass.
MrDowntown12 said:
Darchstar!? and Deca? and jaybob? and possibly some asop on the side?
oh man, these CM7 nightlies are gonna kick ass.
Click to expand...
Click to collapse
I know, I can't wait to see what comes out of it
LiquidSolstice said:
I know, I can't wait to see what comes out of it
Click to expand...
Click to collapse
thanks for this and for what is to come. is this going to be the thread we need to follow for 2.3 gb for now on.
so I don't have to weed through a million pages, how functional are the current builds (even non CM) at the moment? i.e. will I be on my 6.1 for a while yet? I can't imagine we can push these phones much further. Much faster and better than stock for sure, but still laggy for what I do.
danibri82 said:
so I don't have to weed through a million pages, how functional are the current builds (even non CM) at the moment? i.e. will I be on my 6.1 for a while yet? I can't imagine we can push these phones much further. Much faster and better than stock for sure, but still laggy for what I do.
Click to expand...
Click to collapse
Nightly builds of CM7 for the heroc have not been released yet, this page is more of an anticipation/preparation thread for when they do.
I just want to say "thanks" in advance to those of you who are working to make my phone better. This has been a fun ride so far...
Pete
danibri82 said:
so I don't have to weed through a million pages, how functional are the current builds (even non CM) at the moment? i.e. will I be on my 6.1 for a while yet? I can't imagine we can push these phones much further. Much faster and better than stock for sure, but still laggy for what I do.
Click to expand...
Click to collapse
From my experience the 2.3.2 rom posted by aosp has everything working save the camera (this can be fixed by using a third party camera such as camera 360) and there is a small issue with streaming videos that only allows one to watch a few videos before a reboot is needed.
damiandarkwater said:
From my experience the 2.3.2 rom posted by aosp has everything working save the camera (this can be fixed by using a third party camera such as camera 360) and there is a small issue with streaming videos that only allows one to watch a few videos before a reboot is needed.
Click to expand...
Click to collapse
The camera works, refer to:http://romrepo.info/wiki/index.php?title=Main_Page for the most recent releases to date among a wealth of other information.
silberj said:
The camera works, refer to:http://romrepo.info/wiki/index.php?title=Main_Page for the most recent releases to date among a wealth of other information.
Click to expand...
Click to collapse
Camera 360 improves the picture quality but the stock camera works fine too.
Glad to see CM7 coming, I'll have to watch for the official thread and see how it goes. I'm loving the aospCMod version right now though, smooth as butter and absolutely no issues at all so I'll stick with it for now.
Sent from my sexy aospgingermod Heroc
LiquidSolstice said:
If you're having issues with the other Gingerbread build here, or are just interested in a pure CyanogenMOD ROM straight from the source, I'd figure I'd reassure everyone that the official CM7 builds are coming soon, and darchstar will maintain them. I've opened up this thread in anticipation of his first nightly.
For those who need proof that darchstar is indeed coming back, I quote this post from the CM Forums, by Moderator ciwrl:
Source for the above post is located here.
Here are the links listed. NO NIGHTLIES ARE UP AS OF 2/17/11. They are here for when the nightlies do go up, so you can check them.
** These CyanogenMod builds are highly experimental and unsupported.
**
** Please refrain from submitting bug reports for any issues
** you may encounter while running one of these builds.
**
** Submitting bug reports on nightly builds is the leading
** cause of male impotence.
Download: http://mirror.teamdouche.net/?device=heroc
Gapps: http://android.d3xt3r01.tk/cyanogen/gapps/gapps-gb-20110120-signed.zip
Changelog: http://twitter.com/cmsrc
I will be checking the CM7 forums every day for updates from Darchstar and will update this post as soon as I know more.
DISCLAIMER: This is not my work. I did not help build CyanogenMod in any way, shape or form. Do NOT donate me or thank me with the assumption that I had any part in dev'ing this. If you'd like to thank me for keeping you upadted, that's your choice, either way, it does not bother me.
Any accidental donations given to me because of this thread will be promptly returned.
Click to expand...
Click to collapse
Darch is coming back! This is huge news!
since i can't (and no one else) seems to be able to figure out how to get data2ext to work on a sense rom........i'm going to switch to gingerbread once the default camera has just as good as quality or better quality than the sense camera i'll be making my switch then. but until then i'm with the setup in my signature
Can't wait. Just came back to nightly #188 thi king we'd have more love here.
I'll be looking for an official thread posted by Darchstar.
Mmm... I knew that we would eventually get cm gingerbread. I can hardly wait!
Sent from my HERO200 using Tapatalk
It looks like the first nightly is up: http://mirror.teamdouche.net/?device=heroc
BlaqkAudio said:
It looks like the first nightly is up: http://mirror.teamdouche.net/?device=heroc
Click to expand...
Click to collapse
Yup, dl'ing now.
Thread updated.
So, what will be the difference between this and aospCMod? Will it take a while for darchstar to get to where aosp is now? I just want some distinction between the two.
c00ller said:
So, what will be the difference between this and aospCMod? Will it take a while for darchstar to get to where aosp is now? I just want some distinction between the two.
Click to expand...
Click to collapse
From what I know, the dev is totally independent, but darch had the kickstart of help from Deca and jaybob, both extremely talented devs themselves, so we'll see where it goes.
EDIT: Flashing the first build now, we'll see how it goes

CM10 JB nightlies for Skyrocket - Unofficial

Since I'm a new user, the forums won't let me post links until I've posted 10 times, so until then: Download links are in the text file below
Hi Everyone,
I've noticed a lack of nightlies available for the Samasung Galaxy S2 LTE (rogers: SGH-I727r) / Skyrocket(AT&T: SGH-I727) for us flashaholics to get the latest and greatest from the guys down at CyanogenMod. So, I've decided I'll be running nightly builds with merged fixes (official ones, my own and anything anyone else wants to contribute) for everyone to share.
OK, I now realize the above is wrong. More accurately I will say a lack of developers helping to iron out the bugs and merge new things. So I'm contributing by building nightlies and developing fixes and hopefully others will contribute as well. The more the merrier right?
Download nightlies here
I am running these nightlies as my daily driver and so far everything is running very stable.
Working:
-too many to say, just look at what is not working
Known Issues:
-Bluetooth audio out of the box, read fix below.
-USB mass storage out of the box (see fix below)
-Occasional SODs (Sleep of Death a.k.a. doesn't wake up after locking screen)
Bluetooth fix:
This is confirmed to be working by myself. Connect to bluetooth audio device and make a call. If audio is still coming out of your phone then while still on the call, disable bluetooth and then re-enable it. Once it reconnects the audio should now be coming out of the bluetooth device and will continue working no matter how many times you reboot, shut off your bluetooth device(car) etc...
Click the link below to download an app to easily switch from MTP USB mode to USB mass storage mode
USB fix
Contribute:
If people could post their bugs up here, that would really help since I don't use every single feature of Android so some people may experience different issues than others.
When posting bugs, please post what other things you have installed that could potentially be relevant. Also, say what you were doing when said bug occurred.
If it is not on the known issues list, it is worth mentioning. If it is on the known issues list, post anyway! Maybe your post will lead to a fix.
Installation:
-you must have either TWRP or Clockwork mod recovery on your phone, I use TWRP but I'm sure CWM will work as well.
-from recovery, make a backup of your current set up in case these nightlies aren't for you.
-wipe cache, dalvik cache, /system and factory reset 3 times each (there have been weird reports of remnants of files after single wipes)
-flash the nightly of your choice
-flash Google apps if desired. I usually do this after the first boot just in case there are any issues so that debug is easier.
-reboot device and let sit for a few minutes to allow the system to initialise for the first time
-LTE and APNs are net set correctly after boot so you will have to go into system settings->More...->Mobile Networks and set Network Mode to LTE / GSM / WCDMA and select the appropriate Access Point Name as well. I know for Roger in Canada it should be ltemobile.apn
-enjoy your rom!
Upgrading from another one of "my" ROMs:
-download new nightly to your phone
-reboot into recovery
-no need to do any wipes unless you are experiencing difficulties
-flash new nightly from SD card
-boot for the first time. If some things aren't working, reboot and see if it fixes things. Sometimes after an upgrade I have no cell service until I reboot.
Note: It is possible that certain updates may break things as they are nightlies, not stable releases. Flash at your own risk, I do not take responsibility for anything that may go wrong, but I will try to help.
A special thanks to the CyanogenMod team and s8terwitskil
ThomasPSK said:
Since I'm a new user, the forums won't let me post links until I've posted 10 times, so until then: PM me for download URL, or someone pm me and post link below
Hi Everyone,
I've noticed a lack of nightlies available for the Samasung Galaxy S2 LTE (rogers: SGH-I727r) / Skyrocket(AT&T: SGH-I727) for us flashaholics to get the latest and greatest from the guys down at CyanogenMod. So, I've decided I'll be running nightly builds with merged fixes (official ones, my own and anything anyone else wants to contribute) for everyone to share.
Download nightlies here: I'm not allowed links PM me for DL URL... sorry
I am running these nightlies as my daily driver and so far everything is running very stable.
Working:
-too many to say, just look at what is not working
Not Working:
-Bluetooth audio (this is a common issue, there are fixes available. I will merge a fix in one of the upcoming nightlies)
-USB mass storage out of the box (see fix below)
Click the link below to download an app to easily switch from MTP USB mode to USB mass storage mode
Pm me...
Installation:
-you must have either TWRP or Clockwork mod recovery on your phone, I use TWRP but I'm sure CWM will work as well.
-from recovery, make a backup of your current set up in case these nightlies aren't for you.
-wipe cache, dalvik cache, /system and factory reset 3 times each (there have been weird reports of remnants of files after single wipes)
-flash the nightly of your choice
-flash Google apps if desired. I usually do this after the first boot just in case there are any issues so that debug is easier.
-reboot device and let sit for a few minutes to allow the system to initialise for the first time
-enjoy your rom!
Note: It is possible that certain updates may break things as they are nightlies, not stable releases. Flash at your own risk, I do not take responsibility for anything that may go wrong, but I will try to help.
A special thanks to the CyanogenMod team and s8terwitskil
Click to expand...
Click to collapse
I think rpr69 has unofficial nightlies. See here: http://forum.xda-developers.com/showthread.php?t=1871261
Unless I misunderstood your post...
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
You are right, however, apparently things like camera are broken(unles they've been fixed). I haven't tried them to be honest but it can't hurt to have someone else building and making fixes, right? Plus it looks like he has a flashable bluetooth fix which will most likely work with my builds. I'll give it a shot.
Thanks
Tom
ThomasPSK said:
You are right, however, apparently things like camera are broken after September 25th. I haven't tried them to be honest but it can't hurt to have someone else building and making fixes, right? Plus it looks like he has a flashable bluetooth fix which will most likely work with my builds. I'll give it a shot.
Thanks
Tom
Click to expand...
Click to collapse
Camera worked for me when I flashed 10-1
Unofficial nightlies have been out for awhile now.....plz search or at least read the forums before posting sumthing like this
Sent from my SGH-I727 using xda app-developers app
ThomasPSK said:
You are right, however, apparently things like camera are broken(unles they've been fixed). I haven't tried them to be honest but it can't hurt to have someone else building and making fixes, right? Plus it looks like he has a flashable bluetooth fix which will most likely work with my builds. I'll give it a shot.
Thanks
Tom
Click to expand...
Click to collapse
Oh there is nothing wrong with someone else building and developing for sure. I'm just saying that there was another thread. Once you can post URLs, you might drop your build server URL in the unofficial nightly thread. Like you said, never hurts to have more people working towards solving problems.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
jyazzie110 said:
Unofficial nightlies have been out for awhile now.....plz search or at least read the forums before posting sumthing like this
Sent from my SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
With everyone complaining about new users coming in and demanding devs to make their phone cool, this new user comes here with a substantial contribution right outta the gate and this is how you repay him?
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
ThomasPSK said:
You are right, however, apparently things like camera are broken(unles they've been fixed). I haven't tried them to be honest but it can't hurt to have someone else building and making fixes, right? Plus it looks like he has a flashable bluetooth fix which will most likely work with my builds. I'll give it a shot.
Thanks
Tom
Click to expand...
Click to collapse
The camera has been working for weeks. The only thing right now that is a known issue is the irregular SOD's. I haven't experienced them to the level that some people have, but I have gotten them occasionally. Other than that, it's rock solid, at least in terms of what I use the phone for. Sure, there are little bugs here and there, but there is nothing that is a showstopper. It's been my daily pretty much since Alpha1 was released.
Tom
Thanks, I wasn't sure what stage those builds were at or what modifications were merged. Hopefully we can all contribute to making a solid ROM!
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
plwalsh88 said:
With everyone complaining about new users coming in and demanding devs to make their phone cool, this new user comes here with a substantial contribution right outta the gate and this is how you repay him?
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
Yes! Yes! Scare the newbs away no matter what they may have to contribute! That's the best way to manage a community! /sarcasm
zomgjosho said:
Yes! Yes! Scare the newbs away no matter what they may have to contribute! That's the best way to manage a community! /sarcasm
Click to expand...
Click to collapse
actually you will be making it more confusing for the noobs by having 2 unoffical cm 10 threads where both devs are building from the same source. there is less confusion unifying the threads & builds.
op i suggest you look at the BMP rookie thread in dev section and share your builds there.
ThomasPSK said:
Thanks, I wasn't sure what stage those builds were at or what modifications were merged. Hopefully we can all contribute to making a solid ROM!
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
They are built daily from bone stock CM10/TeamChopsticks sources, the only modification currently is the BT in-call audio fix, until it gets committed to trunk. I leave all the customization/modification of ROMS to people who know what they are doing. For anyone who wants pure CM10, use my builds (or yours assuming they are untouched), for anything else, look elsewhere.
@quikt
Definitely something to consider however I am too new and I am not permitted to post in the dev section.
Also, if we are merging different fixes, then we are not building identical ROMs which then makes my builds relevant (I hope). For noobs, they are presented a choice. Both RPR and I try to present as many details as we can to allow them to make an educated choice. Although you may be right. I'm not a noob with this sort of thing so I don't know if its confusing, I'm just trying to help.
I honestly didn't expect this much criticism contributing to an open source community...
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
ThomasPSK said:
@quikt
Definitely something to consider however I am too new and I am not permitted to post in the dev section.
Also, if we are merging different fixes, then we are not building identical ROMs which then makes my builds relevant (I hope). For noobs, they are presented a choice. Both RPR and I try to present as many details as we can to allow them to make an educated choice. Although you may be right. I'm not a noob with this sort of thing so I don't know if its confusing, I'm just trying to help.
I honestly didn't expect this much criticism contributing to an open source community...
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
not sure how you plan on merging fixes, but if u merge like the rest of the CM devs, the gents here are still going to be building off the same code hence the same builds.
u are getting flak because we have a cm10 unofficial thread here http://forum.xda-developers.com/showthread.php?t=1871261
K maybe merge isn't the right word. I mean compile my own fixes and submit merge requests to the cm stream. So basically changes will be made here before they are uploaded to the cm repos.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
ThomasPSK said:
K maybe merge isn't the right word. I mean compile my own fixes and submit merge requests to the cm stream. So basically changes will be made here before they are uploaded to the cm repos.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
Dude, keep your thread and start pumping them out.
Forget about noobs, they aren't the reason the forum was made and you don't have an obligation to any of it.
Your thread is justified because it isn't the same as rpr and that's all that matters. If people have a problem, they won't download your work and if noobs are confused with choice, they can go back to their trusted old source.
Looking forward to checking out your work. Hopefully you don't waste any more time on this useless discussion.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Bro keep your head up and build your ROMs. Honestly don't know where the criticism is coming from but lots of devs pull from source and make their own fixes to AOSP code. You're good to go and I look forward to seeing your work.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
I wasn't criticising, at least I hope that wasn't how my comments were taken. I am not a developer, I just build, if you can actually fix things, more power to you!
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
rpr69 said:
I wasn't criticising, at least I hope that wasn't how my comments were taken. I am not a developer, I just build, if you can actually fix things, more power to you!
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
No you weren't criticising, thanks for the insight into what you're working on. Much appreciated!
btw I am a dev and will be fixing things if people were wondering. I'll be updating a change log in the main post as I roll along.
ThomasPSK said:
No you weren't criticising, thanks for the insight into what you're working on. Much appreciated!
btw I am a dev and will be fixing things if people were wondering. I'll be updating a change log in the main post as I roll along.
Click to expand...
Click to collapse
Looking forward to your build.

[Q] Google Play Edition HTC One Mini

Has anyone tried to use the Google Play Edition RUU for the HTC One (posted here) on their HTC One Mini? The hardware looks similar enough that I'd think it would work. I'm not sure if the lack of NFC is an issue.
Context:
I am a noob to both this forum and Android. I am ready to make the switch, but I want a vanilla Android experience; I'm just not a fan of the Sense UI from what I've been able to play with. I also value smaller, lighter devices, and the HTC One Mini feels perfect to me. I'm an experienced technologist, I've jailbroken iPhones (admittedly less complicated), and I've been a tester for prototype devices at a mobile company I'd prefer not to name (more complicated), so I feel absolutely comfortable with the process of rooting a phone like this. I also value OTA updates, so a Google Play Edition is exactly what I'm looking for.
Any thoughts or suggestions on the subject would be appreciated. I've already gotten several ideas from other posts here. I do apologize if this has already been answered, but I did search and am pretty confident it hasn't been directly addressed.
No, don't do that. Especially not the RUU since that does more than just installing a stock rom.
wrath0r said:
Has anyone tried to use the Google Play Edition RUU for the HTC One (posted here) on their HTC One Mini? The hardware looks similar enough that I'd think it would work. I'm not sure if the lack of NFC is an issue.
Context:
I am a noob to both this forum and Android. I am ready to make the switch, but I want a vanilla Android experience; I'm just not a fan of the Sense UI from what I've been able to play with. I also value smaller, lighter devices, and the HTC One Mini feels perfect to me. I'm an experienced technologist, I've jailbroken iPhones (admittedly less complicated), and I've been a tester for prototype devices at a mobile company I'd prefer not to name (more complicated), so I feel absolutely comfortable with the process of rooting a phone like this. I also value OTA updates, so a Google Play Edition is exactly what I'm looking for.
Any thoughts or suggestions on the subject would be appreciated. I've already gotten several ideas from other posts here. I do apologize if this has already been answered, but I did search and am pretty confident it hasn't been directly addressed.
Click to expand...
Click to collapse
Google Play Edition RUU is recompiled from source nothing to do with Sense 5 and that's mean different kernel that won't boot the HTC One Mini.
You have to wait for an CyanogenMOD available and after that if you don't like it we can build/port AOSP (pure google android).
xpirt
xpirt said:
Google Play Edition RUU is recompiled from source nothing to do with Sense 5 and that's mean different kernel that won't boot the HTC One Mini.
You have to wait for an CyanogenMOD available and after that if you don't like it we can build/port AOSP (pure google android).
xpirt
Click to expand...
Click to collapse
That's incorrect, the GE rom is actually just visually desensed Sense and can be booted with a Sense 5 kernel. It's nowhere close to being AOSP.
CNexus said:
That's incorrect, the GE rom is actually just visually desensed Sense and can be booted with a Sense 5 kernel. It's nowhere close to being AOSP.
Click to expand...
Click to collapse
That makes good sense to me and, in theory, means the Google Play Edition ROM could boot on the mini since the hardware of the same architecture. I think the question is whether the same drivers can be used for the other internals. In other words, we could be able to boot the OS but be unable to use any of the components.
GSM Arena has the full tech specs of the HTC One and the Mini. When I compare these, I see a GPU that, according to Adreno wikipedia article, supports the same OpenGL, OpenVX, and DirectX versions, so I think this would be fine. The chipsets are slightly different and that worries me a bit since that could imply different radios, etc. I'd feel better if I could see a teardown of the mini, but with how miserable the teardown of the full sized version was I doubt they're clamoring to start that.
wrath0r said:
That makes good sense to me and, in theory, means the Google Play Edition ROM could boot on the mini since the hardware of the same architecture. I think the question is whether the same drivers can be used for the other internals. In other words, we could be able to boot the OS but be unable to use any of the components.
GSM Arena has the full tech specs of the HTC One and the Mini. When I compare these, I see a GPU that, according to Adreno wikipedia article, supports the same OpenGL, OpenVX, and DirectX versions, so I think this would be fine. The chipsets are slightly different and that worries me a bit since that could imply different radios, etc. I'd feel better if I could see a teardown of the mini, but with how miserable the teardown of the full sized version was I doubt they're clamoring to start that.
Click to expand...
Click to collapse
Or just wait. An official CM maintainer has a One Mini and will be working on it soon.
jmz said:
Or just wait. An official CM maintainer has a One Mini and will be working on it soon.
Click to expand...
Click to collapse
Correct. And....ohai!
The partition layout is completely different as are the kernel base and ramdisk offsets. If you flash that RUU...you may be heading back to the AT&T store immediately afterwards.
I have most of the prep work completed for cm-10.2....so sit tight while I work out some kinks. I will make a thread in the original android dev forums once its ready for alpha testing.
Sent from my One using xda app-developers app
CNexus said:
That's incorrect, the GE rom is actually just visually desensed Sense and can be booted with a Sense 5 kernel. It's nowhere close to being AOSP.
Click to expand...
Click to collapse
Really?? So the One users can switch from GE to Sense without flashing kernel? No atleast ramdisk changes nothing?
So if we port a m7 sense 5 we can also port GE in the same way?
That doesn't mean we can also base a CM on sense 5 kernel?
xpirt
xpirt said:
Really?? So the One users can switch from GE to Sense without flashing kernel? No atleast ramdisk changes nothing?
So if we port a m7 sense 5 we can also port GE in the same way?
That doesn't mean we can also base a CM on sense 5 kernel?
xpirt
Click to expand...
Click to collapse
Yes. And this is how I was able to port sense to the First so easily. HTC's "AOSP" roms are purely Sense roms with specific apks replaced with AOSP apks. In 4.2+ a lot of changes need to be made to kernel to boot AOSP. Those changes won't necessarily be compatible with sense
Sent from my HTC One using XDA Premium 4 mobile app
boy am I glad I saw this before trying to flash my mini !
GPE for the Mini
h8rift said:
I have most of the prep work completed for cm-10.2....so sit tight while I work out some kinks. I will make a thread in the original android dev forums once its ready for alpha testing.
Click to expand...
Click to collapse
Sorry guys to bump this up but I could not find any further info on this...
Is there any development or is it a deserted project?
Cheers,
ym
ps. BTW is there AOSP rom available for the Mini? Cyanogenmod seems to have heat issues and the wifey is already hot enough so I don't want to give her anything problematic
yourmate said:
Sorry guys to bump this up but I could not find any further info on this...
Is there any development or is it a deserted project?
Cheers,
ym
ps. BTW is there AOSP rom available for the Mini? Cyanogenmod seems to have heat issues and the wifey is already hot enough so I don't want to give her anything problematic
Click to expand...
Click to collapse
Yeah buddy... Try this http://forum.xda-developers.com/htc-one-mini/orig-development/rom-t2825888
Cheers
I would not install any CM-based ROM (CM/Candy*/PacMan/whatever) on M4 until the overheat issue is dealt with. They all have reports of bricked devices, and it looks like any device can (or will, eventually) get cooked any moment sooner or later (some people got theirs bricked after half a year, mine was lost within half an hour).
In the meantime, bilal_liberty has created a LibertyROM GPE for M4!
GPE is Sense-based and thus safe to install.
* EDIT: According to tr1gg3r84, CandyROM is not CM-based.
excellent, thanks
pure.by said:
In the meantime, bilal_liberty has created a LibertyROM GPE for M4!
GPE is Sense-based and thus safe to install.
Click to expand...
Click to collapse
Excellent suggestion as I was looking for the GPE originally :good:
pure.by said:
I would not install any CM-based ROM (CM/Candy/PacMan/whatever) on M4 until the overheat issue is dealt with. They all have reports of bricked devices, and it looks like any device can (or will) eventually get cooked any moment sooner or later (some people got theirs bricked after half a year, mine was lost within half an hour).
In the meantime, bilal_liberty has created a LibertyROM GPE for M4!
GPE is Sense-based and thus safe to install.
Click to expand...
Click to collapse
EH? There has NEVER been any reports of overheating or bricked devices on CandyRom! So I suggest for you to get your facts right before posting.!
AnGrY sCoTsMaN said:
There has NEVER been any reports of overheating or bricked devices on CandyRom!
Click to expand...
Click to collapse
I'm very sorry if that is the case, then I must be mistaken for another ROM; there were a bunch involved in this issue.
But no reports does not mean it has not happened. As far as I know CandyRom is CM-based *, and overheating issue affects all CM-based ROMs the same. Not sure what makes CandyRom different in that aspect. *
Once again, it may happen or it may not. You can either see it as a lottery or a ticking time bomb. Either way, I better go with the ROM that just does not have that possibility by design.
* EDIT: According to tr1gg3r84, CandyROM is not CM-based.
yourmate said:
Excellent suggestion as I was looking for the GPE originally :good:
Click to expand...
Click to collapse
Glad I could help
If you could find some time in a week or two to report back about stability, performance and your overall experience, that info would be much appreciated!
pure.by said:
I would not install any CM-based ROM (CM/Candy/PacMan/whatever) on M4 until the overheat issue is dealt with. They all have reports of bricked devices, and it looks like any device can (or will) eventually get cooked any moment sooner or later (some people got theirs bricked after half a year, mine was lost within half an hour).
In the meantime, bilal_liberty has created a LibertyROM GPE for M4!
GPE is Sense-based and thus safe to install.
Click to expand...
Click to collapse
Yeah get your facts correct before you post Candy Roms isn't even Cyanogen based like the rest you stated and no bricks have been made by using this ROM either. For a GPE I have a booting GPE over Six month ago before I got rid of my M4 with the help from rmbq with kernel but ever release it coz thought it was pointless.
tr1gg3r84 said:
Candy Roms isn't even Cyanogen based
Click to expand...
Click to collapse
I'm very sorry, based on official description provided in CandyROM's threads I thought it was (partly) CM-based. I'm a user, not a developer, so obviously I can't discuss what's under the hood, I have to distinguish based on information developers provide me.
Obviously, I was wrong, for what I apologize. I will correct my previous 2 posts accordingly right away.
pure.by said:
I'm very sorry, based on official description provided in CandyROM's threads I thought it was (partly) CM-based. I'm a user, not a developer, so obviously I can't discuss what's under the hood, I have to distinguish based on information developers provide me. Obviously, I was wrong, for what I apologize. I will correct my previous 2 posts accordingly.
Click to expand...
Click to collapse
Yeah well I should know what I'm on about, after supporting this device for so long before anyone even cared about developing for it....(well there's a lot of so called (Devs) that like to spread rumors about other ROMs to increase their user base) pretty much sick to death of it tbh. Apology accept and cheers for that. CandyRoms is a great ROM supported by over 30 devices and glad to be apart of the team of working hard developers
tr1gg3r84 said:
For a GPE I have a booting GPE over Six month ago before I got rid of my M4 with the help from rmbq with kernel but ever release it coz thought it was pointless.
Click to expand...
Click to collapse
Good for you.
Thanks God, that bilal_liberty's thought it differently and shared it rather than just posting about it

Whats the most sold KitKat Rom right now?

I'm on Gummy Nightly 4.4.2 and I'm looking for something more stable. Life is a bit hectic right now so I'm not able to constantly flash a new rom.
What has been the best 4.4.2 rom that you've had the most success with?
to each there own .
moderators dont like these types of threads cuz they cause arguments
Beanstalk and Liquidsmooth! Waiting for the Pac-Man release!
If life is to hectic to find a rom I suggest stock.
Sent from my SCH-I535 using xda app-developers app
I'm liking my PA 4.4 pa_d2vzw-4.0-BETA-20131208 that one it seems to be the only one with a functional camera so far.
GlitchMob said:
Whats the most sold KitKat Rom right now?
Click to expand...
Click to collapse
Define "most solid"...
All you are going to get is people's limited opinions. Plus, if someone has only used 1 or 2 different ROMs - vs ALL of the ones available - they really can't comment
hallstevenson said:
Define "most solid"...
All you are going to get is people's limited opinions. Plus, if someone has only used 1 or 2 different ROMs - vs ALL of the ones available - they really can't comment
Click to expand...
Click to collapse
I meant to say "stable" I just want a rom where the basic functions like Camera work and I'm able to use instagram etc without it crashing. Gummy is fine, but not being able to use the camera is a big thing. I would like a multi-window feature that Hyperdrive has, but I'd like to stay at 4.4.2.
Also, no I will never go back to stock. As for those who have used one or two different roms their opinions are still valid. They can say whether it was stable or not.
twistedillutions said:
to each there own .
moderators dont like these types of threads cuz they cause arguments
Click to expand...
Click to collapse
Lol what do all the nerds start typing in caps lock? its a thread dude in the appropriate area.
GlitchMob said:
I meant to say "stable" I just want a rom where the basic functions like Camera work and I'm able to use instagram etc without it crashing. Gummy is fine, but not being able to use the camera is a big thing.
Click to expand...
Click to collapse
A ROM with a non-functioning camera would never even get consideration from me ! Same applies to ROMs with no working data. Does the Gummy thread tell you the camera doesn't work ? I'd hope so !!
For what it's worth, I've tried the following KK ROMs (with my opinion/comments):
Beanstalk (Gideon's build) - good ROM, no complaints that I can recall.
Omni (Gideon's build) - too plain or simple (or boring) for me. Didn't have a few features that I've grown to like (I blame PAC for that !!). It was stable though.
LiquidSmooth (both the LS team version and Gideon's) - my preferred ROM at the moment. Runs fine, everything works, and has many of the features I like. Between two builds a week and a half apart, I see add'l things added too.
ParanoidAndroid (notta's build) - can't recall any details at the moment.
I suggest trying ParanoidAndroid 4.0 BETA. Yes, it is a beta but it is very stable. I have been using it since Notta switched to 4.4.x. The are still working out small bugs (like every other KK ROM), but like I said, it's very stable.
It does not have multi-window. For that I suggest Omni ROM. I've been using that on my ASUS TF300T and it works awesome!
As evident by some above commentary, XDA is not a support site and users are expected to test all Roms to make their own, independent, determinations as to what is stable for them.
Thread closed.

Note 5 Pro development is basically gone

Xiaomi launched poco. It marketed it as a developer friendly device. And then it decided to give the device to some devs.
Who did they give it to? People who had previously worked on Xiaomi phones.
And so it happened. Vasishath, shahah_mik and akhilnarang got it. They definitely deserved it.
But with this Note 5 Pro is utterly f****d. Original development has almost completely stopped. Vasishath and shahah_mik brought up LOS and device trees for RN5 and now all they care about is poco.
Go check AOSIP Pie thread. Till 4th October, Akhilnarang was actively working on Pie for RN5 Pro. Now its over. Only derp kernel updates.
Maybe I'm ignorant but only jhenrique seems to be doing original development. Most others are pumping out xyz rom based on same source with same bugs.
I feel so bad. These devs definitely deserved a great phone but it came at the cost of Note 5 Pro. I don't think we will ever get proper Q roms and leave alone that, I don't think we'll ever get fully stable Pie roms like Oreo roms are stable right now.
RN3 launched with 5.1 and got super stable Nougat and Oreo. We started with Oreo and will remain on super stable Oreo custom roms. Other version roms have low chances of being as stable as Oreo.
I urge some developers to pick up LineageOs for this device. "Super glide butter flow remix" rom is nice but first we should have proper Pie code. Otherwise all roms will have similar bugs.
No offense to anybody.
I'm happy to be corrected.
Besides jhenrique, are there any devs doing Original development for Note 5 Pro?
Firstly what pie bugs are you talking about?
And secondly, we have so many hard working devs here making kernels, recoveries and ROMs. New updates every day, join the telegram group...
in the ever changing competitive market! there are always newer models to replace older ones! but the problem is, now the frequency of happening such is very high!
anyways even before poco! RN5 roms on 8.1 are fruit from same tree and i found many similar bugs after trying 10 different roms!
1. all have whatsapp behaviour issues (low call volume / voice notes screen offs )
2. random ui crashing on derp kernels when trying ending call
3. random restarts when whatsapp tries wakesup screen as you move away your device from ear! (proximity sensor)
4. poor BT Audio and noise
5. switching between 4g/3g (airplane mode on/off) fails to register sims to network (specially on crdroid roms on derp kernel)
6. touchwiz goes non responsive and nothing works accept navbar on , unless you switch off and on screen. (RR and crdroid)
7. Equiliser works ONLY if its activated before music player,
i havent tested custom rom of pie but i am sure i will find many bugs!
so what is my point?
that even if poco wasnt released! these inherited (verson to version of various custom roms) issues were never fixed! and i never expect them to be fixed!
YasuHamed said:
in the ever changing competitive market! there are always newer models to replace older ones! but the problem is, now the frequency of happening such is very high!
anyways even before poco! RN5 roms on 8.1 are fruit from same tree and i found many similar bugs after trying 10 different roms!
1. all have whatsapp behaviour issues (low call volume / voice notes screen offs )
2. random ui crashing on derp kernels when trying ending call
3. random restarts when whatsapp tries wakesup screen as you move away your device from ear! (proximity sensor)
4. poor BT Audio and noise
5. switching between 4g/3g (airplane mode on/off) fails to register sims to network (specially on crdroid roms on derp kernel)
6. touchwiz goes non responsive and nothing works accept navbar on , unless you switch off and on screen. (RR and crdroid)
7. Equiliser works ONLY if its activated before music player,
i havent tested custom rom of pie but i am sure i will find many bugs!
so what is my point?
that even if poco wasnt released! these inherited (verson to version of various custom roms) issues were never fixed! and i never expect them to be fixed!
Click to expand...
Click to collapse
You underestimate the power of good devs. Most of these bugs would have been fixed if major devs had continued to work on our device.
They brought up the tree from scratch and literally fixed so many bugs that users reported. If you don't feel like reading xda threads, go watch rom videos of AOSIP etc on youtube from the march/April month. You'll see that they had so many little and big bugs. All of them were fixed slowly and steadily.
So i dont see your point. Devs and their enthusiasm matters a lot. You wouldn't have a single rom running on your phone if devices trees had not been brought up. And then if they had, you wouldn't be using custom roms because of major bugs that they had in April/May. All the bugs that you report are minor and I'm not even facing a single one of them. Oreo is daily driver material because of the months of original development that was put into it by several devs.
Some of the more famous developers got a Poco device and are now spending time with it.
Some other newcomers have come up and launched ROMs in the last 2 weeks or so. That's a chance. Finally, a roadmap to some change.
1emrys1 said:
Xiaomi launched poco. It marketed it as a developer friendly device. And then it decided to give the device to some devs.
Who did they give it to? People who had previously worked on Xiaomi phones.
And so it happened. Vasishath, shahah_mik and akhilnarang got it. They definitely deserved it.
But with this Note 5 Pro is utterly f****d. Original development has almost completely stopped. Vasishath and shahah_mik brought up LOS and device trees for RN5 and now all they care about is poco.
Go check AOSIP Pie thread. Till 4th October, Akhilnarang was actively working on Pie for RN5 Pro. Now its over. Only derp kernel updates.
Maybe I'm ignorant but only jhenrique seems to be doing original development. Most others are pumping out xyz rom based on same source with same bugs.
I feel so bad. These devs definitely deserved a great phone but it came at the cost of Note 5 Pro. I don't think we will ever get proper Q roms and leave alone that, I don't think we'll ever get fully stable Pie roms like Oreo roms are stable right now.
RN3 launched with 5.1 and got super stable Nougat and Oreo. We started with Oreo and will remain on super stable Oreo custom roms. Other version roms have low chances of being as stable as Oreo.
I urge some developers to pick up LineageOs for this device. "Super glide butter flow remix" rom is nice but first we should have proper Pie code. Otherwise all roms will have similar bugs.
Click to expand...
Click to collapse
You've never had an abandoned device.
Delevoping and modding on our Redmi Note 5 is good enough, just open Redmi 4 Pro's Thread, a 100% valid phone with some high specs (launched 2 years ago), abandoned, why? Redmi Note 4 was released like 1 month later, before Redmi 4 Pro was a best-seller, after few months production of that phone was stopped, no official ROMs with regular support (i can remember like 2/3 developers), now it has two Pie ROMs, it's not enough? Abandoned from Xiaomi with Android 6.0 (it has the same specs of Redmi Note 4), bugs never fixed and zero consideration from main developers (just minor and REALLY GOOD developers helped users with that phone), on Redmi Note 5 you have official Pie ROMs, official LineageOS with weekly update, you will have (i think and i really hope for Xiaomi Image) official Android Pie Update, what else?, i think it's really enough
m666p said:
Firstly what pie bugs are you talking about?
And secondly, we have so many hard working devs here making kernels, recoveries and ROMs. New updates every day, join the telegram group...
Click to expand...
Click to collapse
What telegram group are you talking about? Can u share it? Thank you
Search for...
whyred updates official
And whyredcloud
And hers a few more in the screenshot.
m666p said:
Search for...
whyred updates official
And whyredcloud
And hers a few more in the screenshot.
Click to expand...
Click to collapse
I need the @iD not the names
sad but true thats whats up in the new phone hierarchy to manny new phones in a shortness of time
Letrix said:
I need the @iD not the names
Click to expand...
Click to collapse
You know that you can search for groups in the telegram app right...(?)
https://t.me/whyredupdates
What are you talking about? There are literally new rom updates everyday on telegram channel
N1ck474 said:
You've never had an abandoned device.
Click to expand...
Click to collapse
like most samsung devices redmi note 5 pro I way better than samsung devices with the exception maybe being the S5 or S3
there's some updates in telegram that never got to xda. telegram is the worst thing ever happened to xda community. tons of useful discussion buried under trollish and useless questions because of the lack of regulations, probably never again to be found. and if the group ever gets deleted, everything would be gone for good.
In telegram, questions are not allways replyed because it seem theres no devs. I think guys are compiling roms and this is all, if it is a bug in a rom, no one is able to solve it when you ask about the problem.
There s only 3 fully working roms i have tested ( LOS 15.1, PIE experience and MIUI ), the rest is a simple patch of these 3 roms and only upgrades are bugs.
I fully agreed with 1emrys1 post.
I'm considering to learn about developing a rom. Anyone know where to start? Because you can really depend on yourself
gingerboy92 said:
there's some updates in telegram that never got to xda. telegram is the worst thing ever happened to xda community. tons of useful discussion buried under trollish and useless questions because of the lack of regulations, probably never again to be found. and if the group ever gets deleted, everything would be gone for good.
Click to expand...
Click to collapse
Gotta agree on that
Telegram could be used to obtain feedback for some ROM, kernel or mod quickly, but as it is an instant messaging app, and people really lack any sense or knowledge about proper issue report (info on flashing procedure, current setup, methods to reproduce and logs) it just becomes a complete useless mess where important information is easily lost. Here, at least you can properly search for something and people's tendency to post something might be lower than on IM apps.
I would argue that the development for our device is gone, because there are still devs who are working on it, it might be just slower than usual but not necessarily worse.
On another note, the user base has to be more disciplined and just a bit more educated on how each one of us can contribute to a better development. Posting irrelevant and repetitive crap like fix this pls, this not works, give me links can iritate devs and drive them off, not to make them use another device, but to avoid posting their work with others.
Biggest fail on forums today, and I'm starting to see that all around XDA, is lack of respect for another user/dev/modder/contributor. People do not use the search function, which is the first and most important rule here, do not read the OP and features/bugs section, do not post proper issue report, and demand this or that, and the worst thing is when you point a finger at them and say - you are wrong that's not the way we do things here, they either don't (or pretend) understand and come back at you with insults behaving like they own this place.
EDIT: And there we go, just as I've posted this, someone made a thread in development section asking for kernAl with some features. Just the other day, a dude made a thread in the development section about Arnova's GCam (there is already "official/main" one in Themes and Apps) saying that this works on his device and something else doesn't etc.
I mean, I understand, not everyone has the knowledge about everything, but come one if you come to know about XDA you need to be at least informed about basics.

Categories

Resources