While unlocking bootloader i came across their terms and conditions on motorola website:
https://motorola-global-portal.cust...85047216/redirect/1/filename/Boot_revised.pdf
The part that worries me is section (7) (c):
part of which states "potential to cause serious bodily injury"...
What's this about and I mean I'm obviously a bit concerned now. :/
Wrong place to ask questions. But it could cause bodily harm if you flash something that might overheat your phone to the point where it will burn
Sent from my Moto G using XDA Premium 4 mobile app
YoshiShaPow said:
Wrong place to ask questions. But it could cause bodily harm if you flash something that might overheat your phone to the point where it will burn
Sent from my Moto G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Doesnt it have thermal protection of some sort?
Anyway whats the right place to ask this question then you reckon? I thought this was an issue related to 'android developement' as its certainly not a 'general' issue, only a handful of users who are into ..or thinking of gettin into development (like me) would unlock bootloader.
nope its entirely safe to unlock the bootloader
the only problem you might have is just breaking the warranty but thats it
of course you just have to watch some of the stuff you flash, if something like that mentioned in the op does happen it'd probably be from some experimental/ or in alpha kernel or rom. so dont worry.
shmotog said:
Doesnt it have thermal protection of some sort?
Anyway whats the right place to ask this question then you reckon? I thought this was an issue related to 'android developement' as its certainly not a 'general' issue, only a handful of users who are into ..or thinking of gettin into development (like me) would unlock bootloader.
Click to expand...
Click to collapse
Well, you basically have to unlock the bootloader if you intend to do anything at all with your device, from rooting it to flash all kind of custom rom, kernel and mods... so, yes, your question belong to the general Q and A section, since android development is, as stated in the pinned posts, reserved for posting about development... releasing android roms, launching concrete projects, mods, etc...
WRONG SECTION
Sent from my Moto G using Tapatalk
shmotog said:
Anyway whats the right place to ask this question then you reckon? I thought this was an issue related to 'android developement' as its certainly not a 'general' issue, only a handful of users who are into ..or thinking of gettin into development (like me) would unlock bootloader.
Click to expand...
Click to collapse
Since you asked a question the thread should be posted in Q&A sub forum.
You can post in development once you become developer and develop some ROMs and kernels
Sent from my XT1032 using Tapatalk
Tenroc said:
Well, you basically have to unlock the bootloader if you intend to do anything at all with your device, from rooting it to flash all kind of custom rom, kernel and mods... so, yes, your question belong to the general Q and A section, since android development is, as stated in the pinned posts, reserved for posting about development... releasing android roms, launching concrete projects, mods, etc...
Click to expand...
Click to collapse
Hi thanks for the reply. can you being a senior member move my question to Q&A section please? also yeah i only have superSU installed and given permission to avast and titanium backup only. You don think they might cause problems would they? anyway another thing if you could confirm, how does a fire start i mean i think it can only be if overclocked right? in that case, doesnt moto g have some sort of thermal protection to prevent that in case its heated up too much?
Tenroc said:
Well, you basically have to unlock the bootloader if you intend to do anything at all with your device, from rooting it to flash all kind of custom rom, kernel and mods... so, yes, your question belong to the general Q and A section, since android development is, as stated in the pinned posts, reserved for posting about development... releasing android roms, launching concrete projects, mods, etc...
Click to expand...
Click to collapse
SamsungAdmire said:
nope its entirely safe to unlock the bootloader
the only problem you might have is just breaking the warranty but thats it
of course you just have to watch some of the stuff you flash, if something like that mentioned in the op does happen it'd probably be from some experimental/ or in alpha kernel or rom. so dont worry.
Click to expand...
Click to collapse
thank you. the thing i was worried about was in case i install some experiemental stuff unknowingly doesnt the phone have thermal protection? also from my limited research most of those iphone fires and those samsung fires started by charging or battery.the only reason i rooted to begin wth was cause my phone installed kitkat update and well that stopped my real racing 3 stopped cal recorder etc so rooting is more of a necessity for me really. plus i would like to develop as well maybe an app or two
shmotog said:
Hi thanks for the reply. can you being a senior member move my question to Q&A section please? also yeah i only have superSU installed and given permission to avast and titanium backup only. You don think they might cause problems would they? anyway another thing if you could confirm, how does a fire start i mean i think it can only be if overclocked right? in that case, doesnt moto g have some sort of thermal protection to prevent that in case its heated up too much?
Click to expand...
Click to collapse
Aha yes, I guess your phone would never start a fire no
Matter what (alimentation problems are a completely different thing and can happen with any deffective electrical product I guess). Maybe blow the internal hardware if you flash something really really bad. But I guess the main threat when it comes to flashing is bricking your device, so be careful at what you flash.
No, supersu won't pose any problem, basically, unlocking your device will change nothing in your phone, flashing things will does... So be sure to know what you're doing, to read the threads before flashing, and to know how to go back if something goes wrong.
Regarding the thread move, I'm afraid I can't help you, you'll have to ask to a moderator.
Tenroc said:
Aha yes, I guess your phone would never start a fire no
Matter what (alimentation problems are a completely different thing and can happen with any deffective electrical product I guess). Maybe blow the internal hardware if you flash something really really bad. But I guess the main threat when it comes to flashing is bricking your device, so be careful at what you flash.
No, supersu won't pose any problem, basically, unlocking your device will change nothing in your phone, flashing things will does... So be sure to know what you're doing, to read the threads before flashing, and to know how to go back if something goes wrong.
Regarding the thread move, I'm afraid I can't help you, you'll have to ask to a moderator.
Click to expand...
Click to collapse
Yes.. there r cases of mobile phone exploding..
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Source
This does not belong in the Development Section, read the Forum Rules on posting....Moved here and thanks.
surajkala said:
Yes.. there r cases of mobile phone exploding..
Source
Click to expand...
Click to collapse
was this due to rooting or unlocking bootloader by any chance?
shmotog said:
was this due to rooting or unlocking bootloader by any chance?
Click to expand...
Click to collapse
I'm not even sure why your asking common sense would say no.
The only fires have been due to faulty battery's and/or chargers.
Even over clocking won't do much if it overheats it will just crash long before it would burn.
Sent from my XT1032 using Tapatalk
dethrat said:
I'm not even sure why your asking common sense would say no.
The only fires have been due to faulty battery's and/or chargers.
Even over clocking won't do much if it overheats it will just crash long before it would burn.
Sent from my XT1032 using Tapatalk
Click to expand...
Click to collapse
Why am I asking?
Did you read the link I posted when I started the thread? Motorolas own terms and conditions while unlocking the bootloader state that it might cause physical harm. That's why I was concerned.
However so far I think I agree with your answer as I researched a bit on google and it does appear most problems lie with iphones or samsung galaxy and related to batteries.
Related
This is an updated thread for CM7 for the Inspire 4G.
The original thread by jznomoney was just getting out of date. But, there is a lot of information in its pages
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If you are not currently using CM7, do a nandroid of your current setup in case you do not like it.
Installation:
http://goo.gl/JJ4In (Detailed instructions for if you have never flashed before)
If you've flashed a rom before, read on.
If this isn't an upgrade from cm7 than you must wipe data/cache first
Go here to get the nightly:
http://mirror.teamdouche.net/?device=ace
Gapps: (They package them separately to due to licensing restrictions)
http://goo.gl/r1VoW
Changelog:
http://cm-nightlies.appspot.com/?device=ace
http://twitter.com/cmsrc
Known Bugs:
After first boot must restart to make wifi work.(i think you have to turn WIFI on first or it dosnt work, idk though) otherwise you'll be stuck in a crash loop. (to get out of the loop just quickly do a restart before it crashes again.)
BATTERY DRAIN!!!
if you actually like to have good battery life then you might want to invest yourself in one of these threads:
http://goo.gl/GrUlx (hrkfdn)
http://goo.gl/NyOQH (Mad-Murdock)
and im pretty sure Mad is now using hrkfdn's fix. so i dont think it matters which one you use. hrkfdn just uses a different kernal with overclocking. (i think, correct me if im wrong)
Radios:
After reading about im not sure if there is a right or wrong radio. but here are ones that seems to work:
12.39.60.19_26.06.04.06_M (my current radio)
12.41.60.19_26.06.04.14_M
Thanks goes to everyone who has been working on getting cm7 working right on the Inspire:
kali- Desire HD Maintainer
hrkfdn(awesome kernal/battery drain fix(WIP))
Mad-Murdock(Battery Drain fix(WIP))
Bumbl-Bee
TurboniumX (Correct Sound Fix)
attn1 Original Hack Kit
Neolobster for hosting the Hack Kit
anyone else I forgot
De'javu?
Sent using XDA Premium
MrGarak's 1.3.11 MIUI
symonc said:
De'javu?
Sent using XDA Premium
MrGarak's 1.3.11 MIUI
Click to expand...
Click to collapse
lol yea a little. but i was sorta tired of the same questions being asked on the other. we all know people arnt gonna read an entire thread. they want all the info in the first post. so i decided ill try and keep it updated with info to make it more friendly.
isaacfank said:
lol yea a little. but i was sorta tired of the same questions being asked on the other. we all know people arnt gonna read an entire thread. they want all the info in the first post. so i decided ill try and keep it updated with info to make it more friendly.
Click to expand...
Click to collapse
Isaac,
thanks for stepping in to clean it up, maybe you can insert the tidbit about the recommended radio, it seems like that is one of the more frequently asked questions because a lot of people don't understand why certain things don't work when its all related to the radio.. etc etc. just a suggestion.
alvinswim said:
Isaac,
thanks for stepping in to clean it up, maybe you can insert the tidbit about the recommended radio, it seems like that is one of the more frequently asked questions because a lot of people don't understand why certain things don't work when its all related to the radio.. etc etc. just a suggestion.
Click to expand...
Click to collapse
to be honest, i didnt know there was a recommended radio. seems like everyone says different.
but just to stop the questions, which one should i put?
isaacfank said:
to be honest, i didnt know there was a recommended radio. seems like everyone says different.
but just to stop the questions, which one should i put?
Click to expand...
Click to collapse
LOL, thats true.. I guess I was just reading the Desire HD thread for CM7 and they recommended a certain older radio. but you're right we've all see multiple reports of them working. maybe put a list? like I am using the one in my signature, that seems to be fine, and I'm sure you're using a different one too..
Thanks for getting this more organized. One question I haven't been able to find a satisfactory answer to is the following:
Do the nightlies have the battery drain fix already? If so, which builds? If not, please update the first post when they do.
Thanks!
Sent from my Desire HD using XDA App
I've tried a few different radios (stock, Telus, and I think Orange?) and all three have been great. Granted, I am in a well-covered area where reception is rarely an issue. The radios seem to effect my reception far less than they did with my Samsung Captivate.
isaacfank said:
lol yea a little. but i was sorta tired of the same questions being asked on the other. we all know people arnt gonna read an entire thread. they want all the info in the first post. so i decided ill try and keep it updated with info to make it more friendly.
Click to expand...
Click to collapse
Call me old fashioned, but I've always found the benefit of a bigger thread contains a lot more answers and possible solutions.
"Search This Thread" is insanely powerful.
Maybe a thread on "How to find an answer to your issue before you become the 83rd person to ask THAT question" would be beneficial.
Sent using XDA Premium
MrGarak's 1.3.11 MIUI
symonc said:
Call me old fashioned, but I've always found the benefit of a bigger thread contains a lot more answers and possible solutions.
"Search This Thread" is insanely powerful.
Maybe a thread on "How to find an answer to your issue before you become the 83rd person to ask THAT question" would be beneficial.
Sent using XDA Premium
MrGarak's 1.3.11 MIUI
Click to expand...
Click to collapse
they have that. problem is, people need a post explaining how to use that. then they need a post to explain when to use it. then they need a post to remind them to read the for-mentioned posts.
we all cant act like we've never done it. we were all noobs at one time.lol
3GOD said:
Thanks for getting this more organized. One question I haven't been able to find a satisfactory answer to is the following:
Do the nightlies have the battery drain fix already? If so, which builds? If not, please update the first post when they do.
Thanks!
Sent from my Desire HD using XDA App
Click to expand...
Click to collapse
it has not been implemented yet. but last i heard they are dang near close to a final fix. we'll find out tomorrow im guessing.
symonc said:
Call me old fashioned, but I've always found the benefit of a bigger thread contains a lot more answers and possible solutions.
"Search This Thread" is insanely powerful.
Maybe a thread on "How to find an answer to your issue before you become the 83rd person to ask THAT question" would be beneficial.
Sent using XDA Premium
MrGarak's 1.3.11 MIUI
Click to expand...
Click to collapse
Although I personally believe a new thread was needed, symonc has a point. Isaac, perhaps you should provide a link to the old thread and just state it is for reference purposes at this point? You can remove it within a few weeks, as the information will be long obselete; but for right now it may help .
RC2 had an issue where every time you rebooted, your SD card would be nuked. Has that been fixed?
Sent from my Desire HD using XDA App
TheBassman369 said:
RC2 had an issue where every time you rebooted, your SD card would be nuked. Has that been fixed?
Sent from my Desire HD using XDA App
Click to expand...
Click to collapse
Well mine is still all fine and stuff, but it was fine also with rc2 restarts, so idk what it'll do to you.
good copy and paste from my thread. You could have at least mentioned my name.
Billabong81 said:
Although I personally believe a new thread was needed, symonc has a point. Isaac, perhaps you should provide a link to the old thread and just state it is for reference purposes at this point? You can remove it within a few weeks, as the information will be long obselete; but for right now it may help .
Click to expand...
Click to collapse
Cyanogenmod is a product of cyanogen and teamdouche, who are active on XDA developers forums. It's up to teamdouche, and specifically the device maintainers to decide when it's time to clean up their own threads, and not some random person from the forums. Because the OP has no special access or insight, threads like these are where a great deal of disinformation comes from.
Well I linked to your post. But now your name is in there too.
Sent from my Inspire 4G using XDA app
attn1 said:
Cyanogenmod is a product of cyanogen and teamdouche, who are active on XDA developers forums. It's up to teamdouche, and specifically the device maintainers to decide when it's time to clean up their own threads, and not some random person from the forums. Because the OP has no special access or insight, threads like these are where a great deal of disinformation comes from.
Click to expand...
Click to collapse
And my disinformation is what? Ill gladly change anything. I'm just trying to help the community that wants to run and test cm7.
I said in the last post of the last one. If they want to update the other one then by all means do that and delete this one. But until then I'm going to maintain this thread to help and inform.
I'm not out to get anyone or anything. Its just that this is a relatively new device on the market and has new users all the time.
Just informing my fellow testers.
Sent from my Inspire 4G using XDA app
Not flaming but you guys should've given the op of the other thread a heads up. He does work closely with CM and has insight as attn1 said. He's one of the reasons it was ported over from the desire hd section.
Sent from Desire HD or Inspire 4G or whatever this thing is called via premium XDA app.
I did. I pmed him yesterday while he was online. Also he did have 2 weeks to update. He shouldn't need our request to do it.
Now can we get back to actually taking about cm7
I'm on 22 and I didn't see the wifi crash loop. Can anyone confirm?
Sent from my Inspire 4G using XDA app
This is the discussion /OT thread for JT Inverted Productions JB 4.2 GAPPS. This was created because too much discussion/off-topic posts have been happening in the main thread and the posts over there should be kept as relevant to the app as much as possible.
Main thread for the app and downloads
[APPS]JusTunBean By: JT Inverted Productions JB4.2 aroma 4.1
Support thread
[SUPPORT THREAD] JT Inverted Productions JB 4.2 Gapps+
If you want to ask questions related to a problem with the app, use the support thread above.
This thread is purely for discussion because I noticed a lot of you were having discussions in the main thread and posting off-topic comments. If you want to discuss anything to do with the app then use this thread.
If people carry on discussing things and making off-topic posts in the main thread, I'll start reporting you for purposely trying to derail a thread when you're fully aware you shouldn't be posting there.
Reserved for future awesomeness...
Kinda silly the whole password thing. I think it'll do you more harm than good... But you know, whatever works for you. Just my own 2 cents. Took me all of 15 seconds to find the password without reading the entire OP. (Which I don't usually do unless I have support questions anyway).
karendar said:
Kinda silly the whole password thing. I think it'll do you more harm than good... But you know, whatever works for you. Just my own 2 cents. Took me all of 15 seconds to find the password without reading the entire OP. (Which I don't usually do unless I have support questions anyway).
Click to expand...
Click to collapse
You're a senior member you don't need to read the original post if you have an idea of what you're doing I don't think you realize that thousands I mean thousands of Noobs that come in there say something is not working but didn't bother to read the original post
I hope that touching on this subject doesn't bring sanctions my way, considering I'm a noob to these forums, but I'll ask anyway. With the original thread being locked due to general dickishness--which frankly I don't get, even as a new member I don't have major issues flashing, and it took me minutes to find the first password. I guess people are just lazy--is the entire project on hiatus or will we just see a new thread soon? I love the work you do and appreciate all your effort, so I'd hate to see it ruined just because a few people are acting silly.
P4rz1v4l said:
I hope that touching on this subject doesn't bring sanctions my way, considering I'm a noob to these forums, but I'll ask anyway. With the original thread being locked due to general dickishness--which frankly I don't get, even as a new member I don't have major issues flashing, and it took me minutes to find the first password. I guess people are just lazy--is the entire project on hiatus or will we just see a new thread soon? I love the work you do and appreciate all your effort, so I'd hate to see it ruined just because a few people are acting silly.
Click to expand...
Click to collapse
It's still up on AndroidSPIN. If you'd prefer to remain on XDA, I'll keep the Support thread open and updated as long as people keep calm.
AAs a noob myself, i understand the whole pw deal. But what i dont understand is why it is considered someone elses responsibility if someone doesnt follow the instructions and bricks the phone.
We have all made it to this point by rooting and installing custom roms. I have never seen it taken to this level in any of the development threads. All this for flashing gapps, seems a little over the top imo.
All i have to add is thank you for all the work, and if someone bricks their phone by not following directions, so be it. You did your job
byrdcfmma said:
AAs a noob myself, i understand the whole pw deal. But what i dont understand is why it is considered someone elses responsibility if someone doesnt follow the instructions and bricks the phone.
We have all made it to this point by rooting and installing custom roms. I have never seen it taken to this level in any of the development threads. All this for flashing gapps, seems a little over the top imo.
All i have to add is thank you for all the work, and if someone bricks their phone by not following directions, so be it. You did your job
Click to expand...
Click to collapse
There is no more password please have this thread locked
justin860 said:
There is no more password please have this thread locked
Click to expand...
Click to collapse
Justin, I was not complaining about the password at all, just complaining about all the complaining about it. If someone bricks because they did not read your instructions, it's their fault.
Closed
As per OP request
Thread re-opened as requested by the OP.
YZ.
Back in business
''Absolute power corrupts absolutely, but absolute powerlessness does the same''
Subscribing
Sent from my HTC Sensation using Tapatalk 2
Giggty giggty goo
"Lead me, follow me, or get out of my way. "
I opened contacts on my d2vzw running the 4.1.1 JT gapps... It forced closed. SO, I went on to my computer, opened the 3.2.6a download I last used and pulled the contacts.apk from it. I put it on my ext-sd, uninstalled contacts.apk from system/apps, and installed the contacts from the last working release I used. Then, I fixed permissions in CWM, rebooted, and boom. Success.
I did all of this without googling, searching these threads, or messaging anyone... and guess what... IT FELT GOOD.
More people should take my lead, figure stuff out for themselves before asking the same questions over and over, and in the end: FEEL GOOD.
We'll end android related depression and solve our problems at the same time. JOIN THE MOVEMENT. haha
Your links to the downloads are down
naijaboykev28 said:
Your links to the downloads are down
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
They're working for me.
Is this closed too
- I'm not a Dev, I just flash alot!
¿? ¿? If I've helped you the Thanks button is only 2 clicks away! ¿? ¿?
Well it may as well be.
Sent from my GT-I9100 using xda premium
KidCarter93 said:
Well it may as well be.
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
Ya everybody that matters is on Android spin again and I guess permanently they just couldn't understand the concept of ignoring ignorant people... I joined earlier this month cuz I knew the way things were going it'd end up there... I guess none of these guys have kids... lol... That's the first skill u learn as a parent is blocking out stupid stuff
- I'm not a Dev, I just flash alot!
¿? ¿? If I've helped you the Thanks button is only 2 clicks away! ¿? ¿?
As has been discussed in other forums (http://forum.xda-developers.com/showthread.php?t=2047927), ISIS has gone live with the OTA JB for Verizon. I have discussed my experiences in the above thread, but I am starting this thread in the development section, because what I want to know is more relevant to this forum.
Somewhere along the way installing ISIS, I came across a message saying ISIS will not work on rooted devices. I have heard that elsewhere as well. My question is, how true is that? will it no longer work as soon as I root? even if I just root and stay stock and not change ROMs? Is there any way around that? Perhaps can you deny root access in SuperUser/SuperSU to ISIS?
I know many people are just going to say get Google Wallet instead, but believe it or not, I like ISIS better and what to keep it!
Has anyone tried getting to work on rooted or any custom ROMs?
Until now I haven't had a desperate need to root, but I'm planning on going abroad soon and I'm going to need APN access so I can continue to use my phone with a local SIM.
levilib said:
As has been discussed in other forums (http://forum.xda-developers.com/showthread.php?t=2047927), ISIS has gone live with the OTA JB for Verizon. I have discussed my experiences in the above thread, but I am starting this thread in the development section, because what I want to know is more relevant to this forum.
Somewhere along the way installing ISIS, I came across a message saying ISIS will not work on rooted devices. I have heard that elsewhere as well. My question is, how true is that? will it no longer work as soon as I root? even if I just root and stay stock and not change ROMs? Is there any way around that? Perhaps can you deny root access in SuperUser/SuperSU to ISIS?
I know many people are just going to say get Google Wallet instead, but believe it or not, I like ISIS better and what to keep it!
Has anyone tried getting to work on rooted or any custom ROMs?
Until now I haven't had a desperate need to root, but I'm planning on going abroad soon and I'm going to need APN access so I can continue to use my phone with a local SIM.
Click to expand...
Click to collapse
Dude, this is absolute bull****. You knowingly ignore the rules. You have not"developed"anything! Get this damn post moved! You know better
Via my Google Galaxy S3 running magic beans
neh4pres said:
Dude, this is absolute bull****. You knowingly ignore the rules. You have not"developed"anything! Get this damn post moved! You know better
Via my Google Galaxy S3 running magic beans
Click to expand...
Click to collapse
WOW! calm down! It's very nice of you to jump to conclusions about me knowing better!
Yes, you're right, I haven't developed anything and I explained why I posted this in the development forum, If a moderator still thinks that it does not belong in this forum, move it by all means!
Now, I don't suppose you have an answer to my question do you?
levilib said:
WOW! calm down! It's very nice of you to jump to conclusions about me knowing better!
Yes, you're right, I haven't developed anything and I explained why I posted this in the development forum, If a moderator still thinks that it does not belong in this forum, move it by all means!
Now, I don't suppose you have an answer to my question do you?
Click to expand...
Click to collapse
I assure you, the rules are very very clear. This in no way belongs here.
Via my Google Galaxy S3 running magic beans
Wow calm down no need for this type of attitude just report it. You don't need to dive down his neck an cuss chill out its not the end of the world as you seem to think there's other ways of saying you posted this in the wrong form
the first idiot to brick an go to xda jail
Yeah I know I'm sorry I just concerned of ops feelings it was a little hatch but your right I am making a fool of myself thanks for carrying also if any one ain't gonna help him with a answer then don't post just report it to the mods myself included thanks
the first idiot to brick an go to xda jail
cvbcbcmv said:
Dude chill.. it doesn't belong here but still... You're making a fool out of yourself.
How about: I'm sorry but I don't have an answer to your question. However, I just thought I'd let you know that this forum is meant for development related things, such as roms, mods, etc. Just thought I'd let you know.
And that's how a human being does it!
Click to expand...
Click to collapse
+100 wow someone woke up on the wrong side of the bed.
Sent from my SCH-I535 using xda app-developers app
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thanks I needed that
the first idiot to brick an go to xda jail
levilib said:
WOW! calm down! It's very nice of you to jump to conclusions about me knowing better!
Yes, you're right, I haven't developed anything and I explained why I posted this in the development forum, If a moderator still thinks that it does not belong in this forum, move it by all means!
Now, I don't suppose you have an answer to my question do you?
Click to expand...
Click to collapse
NEVER do question threads EVER go In Development. Read rule 15 about Where to Post.
Thread moved
neh4pres said:
I assure you, the rules are very very clear. This in no way belongs here.
Via my Google Galaxy S3 running magic beans
Click to expand...
Click to collapse
So apply for moderator title, until then STFU and quit being a douche! Just like the other guy said report it.
Now that the threads been moved and the ranting is over, back to my question...
Sent from my SCH-I535 using Tapatalk 2
Since after rooting my HTC Desire S phone and Installing Custom ROM - Fallout_Evolution_V5.0, Everytime I turn off my phone and start it again It comes on and restart itself, It does not reboot from scratch but does something called HOT RESTART (like when logging off a computer). Also it sometimes freezes. I have tried to check for ROM updates but the but it never goes through. Its not worse than ever, Yesterday my phone when through HOT Restart a million times it took all day and I couldn't even use it. and its been like that for a while now.
Device Details
HTC Desire S
Android 2.3.5 - default
Android 4.03 - Current
Software Number - Fallout Evolution V5.0.0
Device History
Originally Android 2.3.5
Unroot
Locked HBoot and S-ON
Unlocked HBoot and S-ON
Rooted using HTC_QuickRoot_1.1.13_Release
Installed SuperSU
Flashed Custom ROM
Installed Custom ROM - Fallout Evolution V5.0.0
Troubleshooting Attempts
Tried looking for a ROM Update -- Failed
Tried Reducing Startup App -- Failed
Uninstalled Some Apps --- Failed
Removed Battery ---- Failed
Replace Battery ---- Failed
Sent Reports to HTC ---- Failed
Please Can someone Help troubleshoot this Problem?
Please Note: Rude Comments are not Appreciated, Every solution given would be useful for me and many other Users experiencing the same issue, and please be clear and precise. I have searched the forum and did not find a solution to this specific problem, Please help out Kindly.and receive a Thank You Notification
I'm going to report this thread anyway. You asked this in the 'Noob Questions' thread, and then opened your own thread for the same question. That is against the rules of XDA.
Pointless Anwser (Not Accepted)
SimonTS said:
I'm going to report this thread anyway. You asked this in the 'Noob Questions' thread, and then opened your own thread for the same question. That is against the rules of XDA.
Click to expand...
Click to collapse
@SimonTS, If you notice, I said no rude comment and also stade in Bold "be clear and precise", your reply is so pointless to my question. and It was Wise of me to create a new thread in regards to my issue. I initially posted under Noobs Thread thinking I would get a quick response But then I realised they are so many request on his thread and since mine was peculiar and more technical I found it wise to create a new thread for better result.
Moreover, I saw your reply to my Request Under Noobs Thread and you didn't even have a Precise solution for me neither could you help me, and not to even talk of it, You are the only one who did make an attempt to give a solution It seems no one else has knows How to resolve it. Please next time before making comments like this, always think twice and see reasons to ones idea.
Topzturvins07 said:
@SimonTS, If you notice, I said no rude comment and also stade in Bold "be clear and precise", your reply is so pointless to my question. and It was Wise of me to create a new thread in regards to my issue. I initially posted under Noobs Thread thinking I would get a quick response But then I realised they are so many request on his thread and since mine was peculiar and more technical I found it wise to create a new thread for better result.
Moreover, I saw your reply to my Request Under Noobs Thread and you didn't even have a Precise solution for me neither could you help me, and not to even talk of it, You are the only one who did make an attempt to give a solution It seems no one else has knows How to resolve it. Please next time before making comments like this, always think twice and see reasons to ones idea.
Click to expand...
Click to collapse
I don't need to see the reasons behind your double-posting - it is against the rules of XDA. If that is too confusing then that's your problem, not mine.
I did reply to you on the 'Noob' thread with a few ideas, but you didn't bother coming back to say whether any of those things had worked or not - you can't expect assistance if you don't provide information. I didn't have a "Precise solution" (as you put it), because 99.9% of the 'problems' that people report on here are caused by them not reading, not understanding or simply diving in and then regretting it.
In one of the other threads you created (about rooting) you stated
I didnt try HTC Dev bcoz its process was a bit confusing and since They said Quick root does it all I thought.
Click to expand...
Click to collapse
If HTC Dev is too confusing and "They said quick root does it all I thought" then you need to do far more reading - HTC Dev is simple and straightforward.
Yes, it is possible that you have a really, really rare fault that only applies to you because you are special, but it is extremely unlikely. As for developing an attitude with the people who have put many, many hours into helping other users on here and also tried to help you - not a good idea.
You signed up to XDA, asked your questions about rooting and then went off-line for a month. You came back, asked these questions about your strange problem and then disappeared for three weeks. XDA is a COMMUNITY, not a help-desk. If you want to pay me (or one of the other guys who know far more than I do) for us to act as a helpdesk then it's not a problem - the standard industry rates are $120 per hour.
Oh, and as a PS - but I'm sure that you searched and found this - HTC Desire S > Desire S General > FAST BOOT have you tried disabling Fast Boot as a lot of apps really don't like it.
Anyone Here to Help?
Hello everyone,
PLease can someone help me here, Please help me resolve my initial Problem. Please see First Post abovehttp://1.2.3.11/bmi/forum.xda-developers.com/images/smilies/good.gif
Please do not mind SimonTS Post, I created a new thread so as to allow experience and expert developers view and help resolve this issue. I initailly posted in NOOBs Help and Troubleshooting Thread, Not until I realised that there were over 100 threads and request under that forum, which I then realised that my request might not be solved due to the technical difficulties involved and I was right No one except simon was able to reply to it (and yet not solved).
Please Can someone Help me Out Here? Its been 3 weeks without a solution. Thnaks
:fingers-crossed:
Be wise and Be careful
@SimonTS, You clearly are naive and lack some essential skills like Wisdom.
You fail to realise, that some people have got other important work aside from their Phones and their work takes most of their time rather than them toying with their phone. If I did know how to troubleshoot my phone properly, I wouldn't have bothered putting up a post on here. And Yeah, I did get answers from wise and expert people on here but not from you. I Never asked for you to be troubled by my post and is My post aches your eyes then take your eyes off my Post. I do not need you to comment on this post if you do not have anything positive to say in regards to my request and if you're Tired of helping people on this forum kindly remove yourself from it. No one forced you to Help out, you volunteered to willingly and if it upsets you in helping people resolve their query, Like you said
because 99.9% of the 'problems' that people report on here are caused by them not reading, not understanding or simply diving in and then regretting it.
Click to expand...
Click to collapse
then deactivate your account and stop helping. It is called "Customer Friendly and Volunteering". You do not need to act unwisely if someone ask for you help, If you can't help then don't help.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hi
1. Hae you tried to reinstall the rom
2. Have you flashed boot.img from that rom ( fallout )
3. Have you tried another rom
4. Do you perform < full wipe > before flashing
5. Have you checked whether your device's battery sits firmly in its place
if there are any movements it is likely to cause reboots
5.may try to update your bootloader and radio to the latest( not directly related but...)
6. You may also try to start from skratch:
- lock bootloader
-flash ics ruu
-unlock bootloader
- flash recovery
-flash superuser.zip ( or a prerooted rom )
Check whether it happens on other drivers ( roms )
try a few...
By the time you'll finish to try all options you'll know whether this is software or hardware issue...
Neither I, nor anyone else, sits next to your phone so only you have a chance to fully test it
Edit: whatever approach of the answers may be,
be certain that we all try to help without any discrimination,
This is a free forum, and the users are ussualy discouraged in demanding anything...
None of XDA members is paid for giving a hand or for their work,
this is free and good will what drives us all here, to learn, share and teach what we know...
this will start a flame war soon. anyway, the members here are helping you. but somehow you are bashing them up their advice. I take it as you are new... people here are generally friendly and knowledgeable. when I bricked my desire s for the first time, it was @SimonTS who helped me got my DS alive and kicking again. just because your issue is more technical, doesn't give you the right to post multiple times. in my few months here, I learnt that this is a dev forum, not a child playground for you to throw tantrums
P. S rooting isn't for you
Sent from my supercharged :tank:
Hi
Let me start by offering you some friendly advice. You are the guy with the one weird problem nobody else seems to have. You are the new member, or 'noob' if you wish. Therefore you would do well to behave in a courteous and non-wise-ass-y manner towards your fellow XDA forum members. You have no rights to demand anything from us, you are asking for our advice and it's only in your best interest to try to get on our good side rather than our bad side.
Now, as for your problem. The most likely reason is that the kernel you're running is incompatible with the modules your ROM is shipping. I.e.: you made a #1 new-user mistake and did not (correctly) flash the boot.img of your new ROM.
A second possibility is that there's genuinely something wrong with either your ROM or your device itself.
To check for both issues at the same time, please do the following:
Reboot your phone
Create a dmesg ('adb shell dmesg') and a logcat ('adb logcat') log
Use your phone until the problem occurs
Immediately after, create a new dmesg and logcat
Post all four logs
Thank you for your co-operation
hisname said:
this will start a flame war soon. :
Click to expand...
Click to collapse
Sadly, you may be right about that...
So now, when our younger member has been given a few pointers,
( moderators seem to be very patient with us this time )
we could draw a thick line under this
and sit back to the table- shall we...
We are all friends here, or should be....
Thanks for your suggestions.
asgardr said:
Hi
1. Hae you tried to reinstall the rom
2. Have you flashed boot.img from that rom ( fallout )
3. Have you tried another rom
4. Do you perform < full wipe > before flashing
5. Have you checked whether your device's battery sits firmly in its place
if there are any movements it is likely to cause reboots
5.may try to update your bootloader and radio to the latest( not directly related but...)
6. You may also try to start from skratch:
- lock bootloader
-flash ics ruu
-unlock bootloader
- flash recovery
-flash superuser.zip ( or a prerooted rom )
Check whether it happens on other drivers ( roms )
try a few...
By the time you'll finish to try all options you'll know whether this is software or hardware issue...
Neither I, nor anyone else, sits next to your phone so only you have a chance to fully test it
Edit: whatever approach of the answers may be,
be certain that we all try to help without any discrimination,
This is a free forum, and the users are ussualy discouraged in demanding anything...
None of XDA members is paid for giving a hand or for their work,
this is free and good will what drives us all here, to learn, share and teach what we know...
Click to expand...
Click to collapse
Thank you @asgardr , When I rooted my HTC Desire S, I followed this guide ( http://forum.xda-developers.com/showthread.php?t=1525100) posted by @n0elite. It was simple and easy and I did flash the boot.img, I have checked the battery and even changed my battery it is certainly not the battery fault. Although, I haven't tried to reinstall the ROM because I didn't want to follow the same guide in case something was missing in it. I have also tried reading other threads on here but I am not sure of which Guide to follow because I came across some negative comments on it. I haven't tried another ROM yet and thats because I do not know of any Updated ROM and most people seem to say the "Fallout v5.0.0" is most recent.
However, I have tried to find an update on the fallout but haven't found one, I also have SuperSU installed but I don't know how to tweak it and therefore haven't tampered with it so as not to cause damage to my phone. I know some losers on here would say why didn't I try any of these or make any attempt to. Well my reasons are well best known to me, I lost some data on my last rooting even though I tried backing up all my data, some of my previous apps failed to work and I lost previous progress on some of my important work in which i was working on due to compatibility issues. Therefore, I am trying to thread carefully and make my research and findings before making any attempts on my phone or I could loose the all phone all together.
I do appreciate your solutions and clicked on the thanks button because only you have been sensible and helpful on this matter and precise without going of point and being rude and insultive.
TO others
@Aquous You have no rights to demand anything from us, you are asking for our advice and it's only in your best interest to try to get on our good side rather than our bad side.
Click to expand...
Click to collapse
Please not I wasn't demanding anything from you, I asked The XDA-developers Forum and no one is bragging rights with you. anyways thanks for your suggestion.
@hisname, this will start a flame war soon. anyway, the members here are helping you. but somehow you are bashing them up their advice. I take it as you are new... people here are generally friendly and knowledgeable. when I bricked my desire s for the first time, it was @SimonTS who helped me got my DS alive and kicking again. just because your issue is more technical, doesn't give you the right to post multiple times. in my few months here, I learnt that this is a dev forum, not a child playground for you to throw tantrums
P. S rooting isn't for you
Click to expand...
Click to collapse
I am a web Designer, and Yeah rooting is not my field so Why force it on me, and If my multiple post disturbs you, why didn't you reply to the my initial post?
Thanks once again @asgardr:good:
asgardr said:
Sadly, you may be right about that...
So now, when our younger member has been given a few pointers,
( moderators seem to be very patient with us this time )
we could draw a thick line under this
and sit back to the table- shall we...
We are all friends here, or should be....
Click to expand...
Click to collapse
@asgardr, Thanks for your humble attitude, Exactly what is expected from all users, Humble and friendly approach. Please can you recommend to me any Custom ROM and Recovery that is very at least 90% or more efficient and most up to date? as I shall try what all your suggestions again. Thanks.
After unlocking bootloader installing recovery, rooting,.....
flashing a custom rom is a matter of rebooting into recovery, flashing the rom.zip
and afterwards boot.img via fastboot- that's all you'd need to do...
Redownloding and reflashing the rom again
( after wiping clean all partitions-in recovery )
very often corrects some errors and bugs, happening within the system,
after the first flash...
This is the link to the kernel thread,
( sense4_boot.img , as well supports fallout rom)
http://forum.xda-developers.com/showthread.php?t=1845039
which may also be an option on the way to resolve this
rather rare device's malfunction
Edit: 4ext recovery is said to be most efficient for our device.
I'am still using clockworkmod touch 5.8.1.5 though, and all is fine on my end....
Most of the time, my device's daily drivers including htc sense in it are:
-ViperSaga ( sense 4.1 full )
-DesireXS ( sense 4.1 lite )
-Endymion 3.5 ( almost perfect- my favorite for a very long time )
These roms are my personal choices...
but, to tell the truth, I did not try every single one from the whole array,
so, among others available, one still may find very nice surprise....
@Topzturvins07 I'm not sure if you are just insanely stubborn or not, but at the same time as I originally reported this as a duplicate thread, I posted a reply to you in the 'Noob Thread' as below;-
Verify the checksum of the ROM first. Carry out a full wipe and reflash, try running with no apps installed and see if the problem still happens.
Disable 'fast boot' from the settings.
Try a different ROM, although I have no problems with Fallout on my old DS.
Make sure you haven't installed any task-killers.
Describe better what actually happens and what you see on screen.
Just a few suggestions.
Click to expand...
Click to collapse
You never bothered to reply to my post and provide more information. The only real description you have given of the problem is (probably because you are not a techie person) very vague and unhelpful. I have worked in customer support and consultancy for 20 years now and the biggest problem when you can't actually see the problem for yourself is trying to get a user to describe exactly and precisely what is going on.
If you want to ask for help then you need to answer the questions that are asked of you by the very people whose help you desire. Communication requires two-way talk, and you will find that the people willing to help on here do not ask questions simply for the fun of it.
Topzturvins07 said:
why didn't you reply to the my initial post?
the reason is simple, you don't deserve it
Click to expand...
Click to collapse
Topzturvins07 said:
Please not I wasn't demanding anything from you, I asked The XDA-developers Forum and no one is bragging rights with you. anyways thanks for your suggestion.
Click to expand...
Click to collapse
Very well, if I misread you I humbly apologize. Writing isn't the easiest medium to convey emotions
Now, if you could post those two dmesg and logcat logs I asked for? I am confident they will shed more light on where exactly your issues come from.
LOG Report
Aquous said:
Now, if you could post those two dmesg and logcat logs I asked for? I am confident they will shed more light on where exactly your issues come from.
Click to expand...
Click to collapse
Well despite not knowing how to generate the Logcat and dmesg, I was able to get a guide from @blindndumb and I came up with loads of Junks I can't interpret. You'll find in attach three txt file,
one is the :
dmesg.txt
logcat1.txt (before sudden logoff)
logcat2.txt (after the first sudden logoff)
logcat3.txt (after the second sudden logoff)
Please help yourself, because I cannot interpret what is produced.
Well, this is peculiar. I was expecting to see loads of '<service> has died' errors in your logcat, because that is usually the cause of a spontaneous hot restart. Your logcat actually looks rather normal.
Was the dmesg log taken directly after a hot restart?
Also, could you please reboot your phone and take another dmesg immediately after the system has finished loading? I'm mostly interested in the log of the boot-up, which has unfortunately been completely overwritten by a slur of error messages (which are completely normal by the way, it's the result of a debugging option that's enabled in the stock kernel sources and the guy who compiled your kernel probably forgot to turn that off).
Aquous said:
Well, this is peculiar. I was expecting to see loads of '<service> has died' errors in your logcat, because that is usually the cause of a spontaneous hot restart. Your logcat actually looks rather normal.
Was the dmesg log taken directly after a hot restart?
Also, could you please reboot your phone and take another dmesg immediately after the system has finished loading? I'm mostly interested in the log of the boot-up, which has unfortunately been completely overwritten by a slur of error messages (which are completely normal by the way, it's the result of a debugging option that's enabled in the stock kernel sources and the guy who compiled your kernel probably forgot to turn that off).
Click to expand...
Click to collapse
I have tried a couple of time to catch all the logcat report but there seem to be a million lines of logs immediately I start the phone and they all run within a blink of an eye, and my CMD cannot hold back so many. The ones you see is what I could retrieve but I could try changing the properties of my cmd and see if I can catch more of it.
I'm a little upset. Other than the very few ROM's such as Omni, there is NOTHING original. 99% of threads in the Original Android Development section have a little paragraph that reads "We are dedicated to optimising performance while trying to maintain battery life" or the other way around yet the dev(s?) do NOTHING to the ROM other than maybe replace a few system apps or add a few init.d scripts and somebody elses kernel. Not only that, but most devs use "we" and yet the chances are there is probably only one "developer".
There should be a rule that states "If you can't bring anything new to the table, don't create a thread."
They are all the same. Nothing new. Nothing different. Pure AOSP builds with no modifications whatsoever.
/rant
abtekk said:
I'm a little upset. Other than the very few ROM's such as Omni, there is NOTHING original. 99% of threads in the Original Android Development section have a little paragraph that reads "We are dedicated to optimising performance while trying to maintain battery life" or the other way around yet the dev(s?) do NOTHING to the ROM other than maybe replace a few system apps or add a few init.d scripts and somebody elses kernel. Not only that, but most devs use "we" and yet the chances are there is probably only one "developer".
There should be a rule that states "If you can't bring anything new to the table, don't create a thread."
They are all the same. Nothing new. Nothing different. Pure AOSP builds with no modifications whatsoever.
/rant
Click to expand...
Click to collapse
Pure AOSP should be in "Android Development" not "Original Android Development". It's compiling not developing. If they add substantial feature improvements over and above what google provides on the project, fair enough - It's "Original" but otherwise, not.
I haven't taken any time to look at AOSP threads myself, because I'm new to the Nexus range so want to see what stock has to offer for a while, but as and when I find something I feel is not original, I'm not shy - I'll report it.
abtekk said:
I'm a little upset. Other than the very few ROM's such as Omni, there is NOTHING original. 99% of threads in the Original Android Development section have a little paragraph that reads "We are dedicated to optimising performance while trying to maintain battery life" or the other way around yet the dev(s?) do NOTHING to the ROM other than maybe replace a few system apps or add a few init.d scripts and somebody elses kernel. Not only that, but most devs use "we" and yet the chances are there is probably only one "developer".
There should be a rule that states "If you can't bring anything new to the table, don't create a thread."
They are all the same. Nothing new. Nothing different. Pure AOSP builds with no modifications whatsoever.
/rant
Click to expand...
Click to collapse
So make something original then.
_MetalHead_ said:
So make something original then.
Click to expand...
Click to collapse
I'm not here to talk about my ability, that wasn't the point of this thread, was it? I was pointing out at the fact the threads out there are just duplicates.
If you don't think any of the ROMs are worth installing, then don't. It's entirely up to you. I do agree with you in a way, a lot of the ROMs are little changed from stock, but sometimes the little changes are nice. Everyone works hard on here for free, I don't think they deserve any complaints
Sent from my Nexus 5
abtekk said:
I'm a little upset. Other than the very few ROM's such as Omni, there is NOTHING original. 99% of threads in the Original Android Development section have a little paragraph that reads "We are dedicated to optimising performance while trying to maintain battery life" or the other way around yet the dev(s?) do NOTHING to the ROM other than maybe replace a few system apps or add a few init.d scripts and somebody elses kernel. Not only that, but most devs use "we" and yet the chances are there is probably only one "developer".
There should be a rule that states "If you can't bring anything new to the table, don't create a thread."
They are all the same. Nothing new. Nothing different. Pure AOSP builds with no modifications whatsoever.
/rant
Click to expand...
Click to collapse
i like to get upset over people spending their free time to create ROMs.
What about ParanoidAndroid? The CM team is also planning amazing stuff for CyanogenMod.
Zepius said:
i like to get upset over people spending their free time to create ROMs.
Click to expand...
Click to collapse
My point is, most people seem to compile AOSP and call it their own. It's not. It's nothing different from the last 10 people that did the same thing. I have a lot of respect for those that do actually create something.
darkgoon3r96 said:
What about ParanoidAndroid? The CM team is also planning amazing stuff for CyanogenMod.
Click to expand...
Click to collapse
Of course. They are actual developers, they get my respect as they bring originality. I'm bothered by those that do nothing and claim to do everything.
darkgoon3r96 said:
What about ParanoidAndroid? The CM team is also planning amazing stuff for CyanogenMod.
Click to expand...
Click to collapse
I think his point is, there are many roms in the original android category that are not original. Compiling AOSP and doing nothing is not original. It should be categorised correctly and put in the correct forum Android Development.
It's pointless separating the 2 forums if people put everything in the original forum, even if its not.
I have to say, right out of the box this phone is pretty fantastic.
Sent from my Nexus 5 using Tapatalk
0dBu said:
I have to say, right out of the box this phone is pretty fantastic.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
It is. That's why I wanted to stay stock. I wanted deodexed though for easy customisation.... and I knew exactly where to get it... "Android development". When people misuse the forums, we end up with neither of them meaning anything
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I agree to an extent, granted the phone has only been out for a couple of weeks so I don't think we'll see original ROMS immediately. I'm hoping we get PA or AOKP support sometime soon though.
Sent from my Nexus 5 using XDA Premium 4 mobile app
I think a lot of the problem is from how easy it is to develop/build for this phone so a lot of aspiring developers can at least start something whereas other phones have loads of stock ROM based ROMs then the occasional AOSP build but because nexus get AOSP support straight away and you can't port proprietary Samsung/HTC etc binaries so we can't have as big a variation of ROMs.
Sent from my Nexus 5 using xda app-developers app
rootSU said:
I think his point is, there are many roms in the original android category that are not original. Compiling AOSP and doing nothing is not original. It should be categorised correctly and put in the correct forum Android Development.
It's pointless separating the 2 forums if people put everything in the original forum, even if its not.
Click to expand...
Click to collapse
The 'Original Android Development' section is meant to be for ROMs based on AOSP code and original work (kernels, mods, etc), the 'Android Development' section is for ROMs based on the official factory images - at least that's what it used to be when the two sections first appeared on here. It now seems to have been blurred a little...
EddyOS said:
The 'Original Android Development' section is meant to be for ROMs based on AOSP code and original work (kernels, mods, etc), the 'Android Development' section is for ROMs based on the official factory images - at least that's what it used to be when the two sections first appeared on here. It now seems to have been blurred a little...
Click to expand...
Click to collapse
I see where you're coming from but the original statement from xda doesn't mention aosp per se.
http://www.xda-developers.com/android/introducing-original-development-forums-for-more-devices/
Reading the statement, aosp would be original but only if:
built from the ground up with significant original development within them
Click to expand...
Click to collapse
So certainly to my mind, a vanilla aosp build is not original. Other than the compiling, its not even the posters own work...
I think there are grey areas as you say but obvious aosp builds with little to no additional development work I see as black and white
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
This is stupid "you worked hard to bring us some options devs, but its not good enough for me.." That's all I see here.. This should be closed.
Sent from my Nexus 5 using XDA Premium 4 mobile app
capcanuck said:
This is stupid "you worked hard to bring us some options devs, but its not good enough for me.." That's all I see here.. This should be closed.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I think you've misread / misunderstood the thread
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
nevermind