Related
I know the issue of people's Captivates turning off by themselves has been discussed a lot and if there is a solution that is already provided, I apologize for cluttering up the forum a little more. If not, I have something that works for me and was wondering if it might be helpful for troubleshooting what the issue is/how to fix it.
For myself, it seems to be an issue when the battery is near full more than any other time. If I just unplug the phone in the morning and come back to it later it will be off. However, I often go running in the mornings. When I do, I like to listen to music and I use Grooveshark to do it. Just opening Grooveshark does not seem to fix the issue, but if music is playing (even if there is no volume) my phone does not turn itself off. I haven't played around to see if the same is true for just playing music through the regular music player, but I was wondering if perhaps accessing audio playback somehow keeps the phone alive.
Again, if there is already a known solution I'm sorry for cluttering things. Maybe I just had to search around some more...
pezx44 said:
I know the issue of people's Captivates turning off by themselves has been discussed a lot and if there is a solution that is already provided, I apologize for cluttering up the forum a little more. If not, I have something that works for me and was wondering if it might be helpful for troubleshooting what the issue is/how to fix it.
For myself, it seems to be an issue when the battery is near full more than any other time. If I just unplug the phone in the morning and come back to it later it will be off. However, I often go running in the mornings. When I do, I like to listen to music and I use Grooveshark to do it. Just opening Grooveshark does not seem to fix the issue, but if music is playing (even if there is no volume) my phone does not turn itself off. I haven't played around to see if the same is true for just playing music through the regular music player, but I was wondering if perhaps accessing audio playback somehow keeps the phone alive.
Again, if there is already a known solution I'm sorry for cluttering things. Maybe I just had to search around some more...
Click to expand...
Click to collapse
My guess is you guys have tried to overclock and your phone really didn't like it and caused some minor damage. I have heard reports from stock 2.1, 2.2 and Cognition, most of them I have talked to have tried overclocking at some point. If you haven't, maybe just faulty hardware out of the box, if you can flash stock and it still happens, take it back and exchange it.
Personally I won't be overclocking again, 200mhz is not working breaking a $500 phone. I find the lagfix isn't even needed on 2.2 stock.
I only had overclocking on my phone once in a sre build and tested it once and found it worthless to me so i disabled it.
Anyways i have never had an issue with shut downs prior to flashing ji6. Now when i leave my phone plugged in over night, on, i wake up in the morning to find it off. This has happened every day so i cant use my phone for an alarm at the moment. Otger than that ive had a few random shut downs during the day. I do want to know what the problem/solution is for the phone shutting off during the night though.
When i flashed over to ji6 i formatted sd odined jf6 then odined ji6. I did try to do tge master clear only to have it start then say FAIL! In a red box. Someone suggested i reinstall my drivers. I do plan on trying that but am getting so sick of flashing and redoing stuff i havent got aroubd to it.
Would a master clear do anything or make a difference you think since i formatted the sd?
Sent from my SAMSUNG-SGH-I897 using XDA App
designgears said:
Personally I won't be overclocking again, 200mhz is not working breaking a $500 phone. I find the lagfix isn't even needed on 2.2 stock.
Click to expand...
Click to collapse
Agree - the extra battery drain and heat buildup in the chip is not worth it... this device works pretty good with stock and/or new FS tweaks applied.
I do hope the OP gets his device recovered with Odin etc.... hopefully just a glitch that can be remedied back to stock....
I've Odin'd it back to stock but currently am running Cognition 2.2. This has been an issue from the getgo, however (maybe I should mention that I SIM unlocked it if that makes a difference). I couldn't return it because I live out of the country and didn't even receive the thing for about 40 days (gotta love Costa Rican customs). I agree that OC seems pretty pointless on this phone and I have avoided OC roms. I only thought it was interesting that running programs doesn't seem to prevent it, but for some reason playing music does seem to prevent the shutdown perhaps meaning that accessing a certain dll or something fixes the issue (I really have no idea why it works). I just thought that info might be helpful to people who understand the OS better than I if it is a consistent problem for people and if no solutions other than "return it" have been found.
Edit: Oh and DG, great work. You'd be one of those smarter than I guys I referenced...
i've never overclocked my phone and i've mostly run it without a lagfix and no matter what ROM i've used (i've been using cognition beta 1 since it came out) i've always had random shut-downs. For a while there on the stock rom it seemed to only happen when my wifi was on but now it doesn't matter. I don't have any special automation software running (task managers, tasker, ..etc). It's the single most maddening thing about this phone.
Same here... i have had my phone since launch... i had random shut downs since launch. I have had less problems now then before and i have flashed every rom that has come out including overclocking.
Sent from my SAMSUNG-SGH-I897 using XDA App
My wife's phone was never overclocked and it developed the random shut down problem about two weeks after she got it. After trying numerous things to fix the problem, some resulting in it working fine again for a few days and then starting random shut downs again, I came to the conclusion that it was definitely a defective hardware problem and had her return and exchange it. The new one is now set up exactly the same as her old one (rooted stock jf6 with the bloatware removed, side loading enabled, and market fixed) and has been running fine, with no shut downs for over two weeks.
I have been in the electronic repair business for over 25 years, and my conclusion is, the only fix is to return it and get it repaired or replaced. Nothing you can do is going to fix your defective hardware.
I had my phone for a month and it was flawless, updated to 2.2 beta and started getting random shutdowns. I replaced the phone and the new one doesn't shutdown at all on 2.2. The one I returned would shutdown at least 5-6 times per day. Again only after installing 2.2, on 2.1 it seems ok. Which could be a software issue, or just more strain on the hardware making the problem happen
Personally I think it's just bad hardware. Replace the phone.
I guess I'll have to see if there's any way of getting the hardware replaced but I don't think I'm going to be able to manage.
I just want to repeat, however, that I have tested this many many times and with numerous iterations of DG's roms as well as stock. I can guarantee a shut down soon after unplugging the phone in the morning, but I have never gotten it when I start playing music (specifically through Grooveshark - I have not tested it with the regular music player). I just think that even if it's a hardware problem, there appears to be a relationship which suggests that a software solution could prevent it (at least given my experience). I just thought it might be helpful information to people who might understand a possible relationship between the two and to see if anybody else can confirm or refute this behavior. If there is any way to trick the phone into thinking it is playing the music without actually playing it, the problem may go away for people who are experiencing it.
If anybody else can refute my observations or back them up, I would be interested to hear. Perhaps if enough people can confirm it, it may be worthwhile to investigate further. If people can refute it, I guess I'll just count myself "lucky" to have only a mildly faulty phone. Either way I'm happy with my phone. I just thought I might be able to help others out.
I actually convinced four coworkers to pick up Captivates here (our company policy is with at&t) and my boss' phone (completely stock) would randomly shut-down four or five times a day. I've been around the community since the G1 dev launch and my phone is definitely not stock but has never randomly shutdown.
I finally convinced him to return it and his new one came in today. With this many reports, it is not a user-induced problem.
+1 to everything im reading here. i tried a few software and hardware 'fixes' so to say and nothing fixed the issue for long term. sent in for a new captivate #3 yesterday. Im sorry its just got to be a hardware problem, its just to far widespread from what im seeing.
I did want to point out one fear that is starting to cross my mind. i got my 1st one off craigslist which is hilarious because im still covered by warranty. HOWEVER. after the first exchange its then 90 days on a refurb *which begs me to wonder if samsung will still honor the 1 year warranty claim*..anyways.. im really really really hoping that i dont get one that seems to last a while and has this issue start up again....because that will be the last captivate for me...obviously lol
Believe it or not, this has been working for me for a couple of days now
http://androidforums.com/captivate-...hone-shutting-off-randomly-5.html#post1572891
I called ATT and was told to call Samsung because I don't have an account. They did tell me, however, that they didn't know anything about a bad production run or anything like that or about many exchanges. Of course I take all of that with a grain of salt...
Out of curiosity, to the people that have had the shutdown issue: Did you SIM Unlock your phone? I have and I use a foreign SIM (just trying to see what is in common).
I understand that it seems to be a hardware-based issue, but there really does seem to be a correlation to software as well. If I'm told by Samsung that there was a bad production run, I'll go with it. But until then, I'm the meticulous sort and will continue testing.
I don't want to beat a dead horse though and I don't want to be one of those guys claiming some fanciful fix to something there is no fix for. I'm still doing some testing on my end. So far the music "fix" has worked for me (although I do not see it as a long term solution) and I just wanted to float it because it seems to work consistently (unfortunately you can't prove a negative). I understand, however, that others have claimed fixes that just plain don't work and so if I hear of anybody trying this and it not working for them I'll move along to focus on other possible correlations. Thanks for all the feedback so far!
Why are people blaming hardware if it is exclusively a Froyo problem?
I've never OC'ed. Learned my lesson on the Evo 4g.
The power-off problem ONLY happens on Froyo builds
Issue happens with the ODIN-packaged 2.2 and all Cognition 2.2 releases
Inexplicably, I do not have the problem with my current Froyo build based on beta 4. Previous installs of Beta4 did have the problem, just not this one.
Odd behavior on a leaked build does not mean bad hardware. Once again, I NEVER have this problem on Eclair.
There is some combination of software and/or settings that causes this.
ZoinksS2k said:
Why are people blaming hardware if it is exclusively a Froyo problem?
I've never OC'ed. Learned my lesson on the Evo 4g.
The power-off problem ONLY happens on Froyo builds
Issue happens with the ODIN-packaged 2.2 and all Cognition 2.2 releases
Inexplicably, I do not have the problem with my current Froyo build based on beta 4. Previous installs of Beta4 did have the problem, just not this one.
Odd behavior on a leaked build does not mean bad hardware. Once again, I NEVER have this problem on Eclair.
There is some combination of software and/or settings that causes this.
Click to expand...
Click to collapse
Blaming the 2.2 builds as the sole culprit is false. I have coworker who has two stock captivates. His had never had an issue, his wife is up to phone #2 and has had power issues on both.
Sent from my SAMSUNG-SGH-I897 using XDA App
It is definitely not exclusively Froyo. It has been happening to people (myself included) for a while.
I just got off the phone with Samsung (general customer support then level 2 technical support). I suggest that anybody else have the problem also call them to at least document the issue (888-987-4357 options 1-6-2-4). They said I can send it in for repairs (yeah right - like I can be away from my phone for that long!) but more importantly that they have not heard of this being a widespread problem but that probably just means that people aren't reporting it. I urge others to call in to at least let them have an idea of how widespread (or not) it is.
pezx44 said:
It is definitely not exclusively Froyo. It has been happening to people (myself included) for a while.
I just got off the phone with Samsung (general customer support then level 2 technical support). I suggest that anybody else have the problem also call them to at least document the issue (888-987-4357 options 1-6-2-4). They said I can send it in for repairs (yeah right - like I can be away from my phone for that long!) but more importantly that they have not heard of this being a widespread problem but that probably just means that people aren't reporting it. I urge others to call in to at least let them have an idea of how widespread (or not) it is.
Click to expand...
Click to collapse
Hmm im pretty sure i just got them yesterday HOWEVER they also sent me to their android support team *wha? really?* pretty much the same level of service but they made sure i was on the newest ota and had me try it for a day and said they would call back after 24 hours to check if the issue persisted.
Why did they tell you to send it in for repairs thou? this is going to be my 3rd and each time they send out the new one FIRST and i rma the bad one back in the box. only reason i havent been so when i have to go through this process
bamonkey said:
I did want to point out one fear that is starting to cross my mind. i got my 1st one off craigslist which is hilarious because im still covered by warranty. HOWEVER. after the first exchange its then 90 days on a refurb *which begs me to wonder if samsung will still honor the 1 year warranty claim*..anyways.. im really really really hoping that i dont get one that seems to last a while and has this issue start up again....because that will be the last captivate for me...obviously lol
Click to expand...
Click to collapse
If you bought a new phone from AT&T, the warranty is 1 year. During this one year, you can have the warranty replacement (refurbs) as many time as you want and your warranty stays as the original (counted from the day you purchased your phone).
If you bought a refurb phone from AT&T, the warranty is 90 days.
bamonkey said:
Hmm im pretty sure i just got them yesterday HOWEVER they also sent me to their android support team *wha? really?* pretty much the same level of service but they made sure i was on the newest ota and had me try it for a day and said they would call back after 24 hours to check if the issue persisted.
Why did they tell you to send it in for repairs thou? this is going to be my 3rd and each time they send out the new one FIRST and i rma the bad one back in the box. only reason i havent been so when i have to go through this process
Click to expand...
Click to collapse
If I lived in the states I probably would have pushed for that myself. Unfortunately getting things shipped to/from me where I live costs money plus customs delays so I'm sort of resigned to the fact that I'm stuck with this handset for now. I was hoping I could just bust into an ATT store and get it exchanged but it doesn't look like that's an option. Calling Samsung was more to just document it with them. I'm glad you have had better luck.
3rd you say though? Has it been the same issue with each?
Maybe we can help. I have several theories regarding people that are are having issues.
1. People do not read or do not understand what they are reading regarding instructions. This has happened to me, so I am not calling people out.
2. Restoring apps and settings from Google. This is a cool feature concept wise, but I believe google has created more problems by allowing people to restore apps and settings across different versions of android.
3. Titanium backup. Same issue as above. I personally love the program, but it has limitations. I believe many are restoring data and in some cases system info from previous roms.
4. Defective batteries. I firmly believe that screen of death while charging is a battery issue.
5. Pushing their hardware beyond its stable limits. It is fun to rack up big scores on benchmarks, but it can lead to instability. Not all hardware is created equal.
For those that have ongoing issues, I would love to help. I am not guru and I am constantly learning new things, but many of us can help with the basics.
When you ask a question, please let us know what rom you are using and what baseband you are using. Let us know what you have tried to correct your issues. The more info you provide, the better chance you will receive an answer that corrects the issue.
Like many, I am tired of seeing the same old questions again and again, but many of those people are new to android or the G2x and so I encourage patience. We need to help our fellow G2x users and make this forum the envy of the board.
I am relying on my fellow xda members to chip in and help those with major issues. I know this happens already, but lets step it up a notch.
I will help too
been around since the g1 and pretty savvy (no coding) but hacking/flashing/fixing/troubleshooting is my forte.
+1 on the OP.
-----------
sent from my calculator with android
This is my first smartphone. Gave up my company provided BB for an honest to goodness smartphone. I don't think I have a "bad" G2X but I don't think I have a perfect one either. Probably on par with what 90% of others have I'd guess. I get occasional reboots, have had to pull the battery a time or two. Nothing more drastic than what I had to do with any BB.
I really don't get the hate for this phone (I do see a bunch of lazies that don't know how to; A: READ, B: Follow instruction), but conversely I don't get the adoration either. What makes it so great? I see "ZOMG SOOOO FAST" comments all the time. I don't find it blazing fast (maybe because it's my first?) but it's not slow (minus the occasional slow-down).
I must say I'm looking forward to an official ICS. Hopefully an honest to goodness dual-core OS that our devs can further improve upon.
G2X=Good Phone.
sidenote: Google desperately needs to improve their email client for business useage.
Dr. Bogenbroom said:
This is my first smartphone. Gave up my company provided BB for an honest to goodness smartphone. I don't think I have a "bad" G2X but I don't think I have a perfect one either. Probably on par with what 90% of others have I'd guess. I get occasional reboots, have had to pull the battery a time or two. Nothing more drastic than what I had to do with any BB.
I really don't get the hate for this phone (I do see a bunch of lazies that don't know how to; A: READ, B: Follow instruction), but conversely I don't get the adoration either. What makes it so great? I see "ZOMG SOOOO FAST" comments all the time. I don't find it blazing fast (maybe because it's my first?) but it's not slow (minus the occasional slow-down).
I must say I'm looking forward to an official ICS. Hopefully an honest to goodness dual-core OS that our devs can further improve upon.
G2X=Good Phone.
sidenote: Google desperately needs to improve their email client for business useage.
Click to expand...
Click to collapse
Something I found to improve the speed of the interface is Spare Parts. It does not change benchmarks, but makes the phone feel much more responsive. Set all the animations to fast in the options.
The problem here is that there really are defective g2x's out there. A small portion of the problems could undoubtedly be user error or as you say. But the vast majority of the original issues were because of defective phones. Period.
I got multiples bad ones. I finally got a refurbed one that was awesome. Then when I broke the screen on that one recently, my (brand new) replacement has performed PERFECTLY as well.
I did nothing different on any of them. Nothing. (Although I have not rooted this new one...it's got the updated oftware).
But it's purrrfect!
This is why I'm now mostly a lurker here. I've nothing to complain about. I love this phone. And I also got a Sensation. Didn't like it as much and sold it.
ickster said:
The problem here is that there really are defective g2x's out there. A small portion of the problems could undoubtedly be user error or as you say. But the vast majority of the original issues were because of defective phones. Period.
I got multiples bad ones. I finally got a refurbed one that was awesome. Then when I broke the screen on that one recently, my (brand new) replacement has performed PERFECTLY as well.
I did nothing different on any of them. Nothing. (Although I have not rooted this new one...it's got the updated oftware).
But it's purrrfect!
This is why I'm now mostly a lurker here. I've nothing to complain about. I love this phone. And I also got a Sensation. Didn't like it as much and sold it.
Click to expand...
Click to collapse
hey ickster. I know what you are saying. I was just hoping to address some the the current problems and present a list of things I know caused me issues. I exchanged my first phone purchased the day of release because of reboots. At this point I think a lot of the issues are user error. I actually have 4 G2x's. My wife and I each have one and I gave a pair away to my two best employees. All four are running flawlessly now after some tweaking. Day after day of thread after thread about problems that can probably be rectified with a few simple steps was making me nuts.
I just want to make this forum the best I can. Maybe I am going about it in the wrong manner. I thought I would give it a shot.
ickster said:
The problem here is that there really are defective g2x's out there. A small portion of the problems could undoubtedly be user error or as you say. But the vast majority of the original issues were because of defective phones. Period.
I got multiples bad ones. I finally got a refurbed one that was awesome. Then when I broke the screen on that one recently, my (brand new) replacement has performed PERFECTLY as well.
I did nothing different on any of them. Nothing. (Although I have not rooted this new one...it's got the updated oftware).
But it's purrrfect!
This is why I'm now mostly a lurker here. I've nothing to complain about. I love this phone. And I also got a Sensation. Didn't like it as much and sold it.
Click to expand...
Click to collapse
I got a refurb that was acting wonky from the get go, did a factory reset and its the honestly the best one yet.
jcbofkc said:
1. People do not read or do not understand what they are reading regarding instructions. This has happened to me, so I am not calling people out.
Click to expand...
Click to collapse
Of course.
jcbofkc said:
2. Restoring apps and settings from Google. This is a cool feature concept wise, but I believe google has created more problems by allowing people to restore apps and settings across different versions of android.
3. Titanium backup. Same issue as above. I personally love the program, but it has limitations. I believe many are restoring data and in some cases system info from previous roms.
Click to expand...
Click to collapse
I've NEVER seen google restore any of my data. Not one iota. I don't think the feature was there when I had the G1 or MyTouch 3G. On my Vibrant, I always ticked the box hoping I'd at least get my wifi passwords, but alas no.
Titanium backup works fine, as long as you don't try to migrate system data. I've NEVER had an issue with it. I even do move data for News and Weather app which "counts" as system data, as well as Wifi passwords, because I have way too danged many of them NOT to move it. As far as moving user apps/data, have never had any issues other than market items not attaching properly.
jcbofkc said:
4. Defective batteries. I firmly believe that screen of death while charging is a battery issue.
Click to expand...
Click to collapse
Maybe. I was having screen of death using MIUI, and when I switched back to an LG build it went away.
jcbofkc said:
5. Pushing their hardware beyond its stable limits. It is fun to rack up big scores on benchmarks, but it can lead to instability. Not all hardware is created equal.
Click to expand...
Click to collapse
CERTAINLY. This is the biggest issue. Undervolted kernels, overclocked kernels, etc. When I had my Vibrant, it couldn't handle even the slightest hint of an overclock without issues. And, of course, the issues wouldn't show up right away, so it was easy to hope it wasn't due to the overclock. But it was. It could undervolt all day long, however. Other phones of the same make were just the opposite. Dunno about the G2X, but that's why manufacturers set things as conservatively as they do -- to take into account the variances in the manufacturing process. Those variances can be a benefit to the crafty, but you can never DEPEND on it to not introduce instability.
jcbofkc said:
When you ask a question, please let us know what rom you are using and what baseband you are using. Let us know what you have tried to correct your issues.
Click to expand...
Click to collapse
I'm curious how many of those with ongoing issues are running the old baseband. I have the July baseband, and always have as I just bought my phone. But if someone who was rooted before the official LG update never got the baseband update, that could be an issue.
jcbofkc said:
Like many, I am tired of seeing the same old questions again and again, but many of those people are new to android or the G2x and so I encourage patience. We need to help our fellow G2x users and make this forum the envy of the board.
I am relying on my fellow xda members to chip in and help those with major issues. I know this happens already, but lets step it up a notch.
Click to expand...
Click to collapse
Still learning the G2X ecosystem. A few differences from the Vibrant, and a much quieter forum overall. Strangely for a US only released phone, lots of posters from outside the US. Not sure why?
Some of the repeated "over and over" questions have to do with lack of a good all-in-one FAQ I think. There's a thread that lists a few key threads, but some aren't on it, and some info just isn't presented super clearly. No offense to Mr. Clown (the moderator that maintains the FAQ thread), but there's just a lot of info you can't get from that thread that really should be there. For the "one and only, don't ask" sticky, it's not the best. How could it be, when the moderator that maintains it doesn't even have a G2X? It's merely a list of links suggested by forum members, and there's no experience shared there that's helpful to newbies.
There's not even an XDA wiki on this phone that I can find... Maybe that would help -- I might be talked into contributing to that.
The majority of problems with the phone at launch were related to a badly programmed OS by LG. The GB update fixed almost all of the related problems. I have minimal screen bleed that can only be seen in a dark room. I can live with that.
Awesome Post, I bought my g2x the day it came april 20, 11 and i never had any problems posted in xda developers beside the backlit bleeding around the corners which is not really a big issue for me. It is really an awesome device. I use hdmi to watch my netflix movies or even to play games on my hdtv, everything performs flawlessly and the battery last a day in moderate use and 2 days in slight use. I think thats pretty good for a dual core smartphone. The only thing i am not happy is the support it got from lg. The gingerbread update took away awesome camera app and the signal bars didnt work according to the connectivity. I think the gingerbread build was incomplete. Waiting for the ICS on my g2x. I get a unexpected reboot probably once in 2 weeks or some which is mainly because of the extensive multitasking and lack of ram, i know 512 is not less however the hd games and livewallpapers consumes huge lot of ram. so those seldom unexpected reboot does make sense as i never switch off my divice. I think it is still an awesome device. The tegra really has some potential, you can play shadowgun to figure out the gpu capability of g2x.
+1 to the OP
@OP I agree with the principle behind what you said, but isn't that exaclty what this whole xda forum is about in the first place, users helping each other out? I'm not trying to put your idea down, but just saying its nothing new really. Maybe I misunderstood what you said and if so, then my apologies.
The problem you identified in #1 is exactly correct -- people don't read or don't understand what they read. They get ahead of themselves and start doing stuff to their phones without understanding the potential consequences if something goes wrong. Then they freak out and instead of searching for a solution to their own problem they just post a new thread saying "ZOMG!!!! Plz help!!! Plz!!!!!!!!!!!!" I've read several threads like that and then found the answer to their question literally 2 threads down.
Anyway, I'm starting to digress. You make a very good point and ideally people will read and follow. Sadly, and realistically, they wont.
Sent from my LG-P999 using XDA App
I was wondering if anyone had any info on the status of roms for the Behold II. I just got one, used but in very good shape, and I am trying to get it to work better. I am fairly sure these phones were pretty popular, and I can't believe they were (almost) completely ignored. I found a pretty nice clean android 1.6 rom that I threw on it, but it has no vibrate.
Does anyone know of any stable gingerbread roms for this phone? If not, anyone know how to get vibration to work? Is there anyone out there willing to work on this phone at all?
Or can anyone point me in the direction of some information on taking the rom apart and figuring out how to get the vibration working? Basically I need to find out how to take apart a rom, then figure out how to get vibration working properly. It's driving me nuts that the phone doesn't vibrate when I get calls/texts.
Isn't that Donut? *throws up*
Couldn't find any ROMs above 1.6 with some googling. Its also likely that you would not be able to fix the vibrate issue, if the Dev couldn't. If you want to "take the ROM apart," just take the .zip file and unzip it.
But I recommend getting a new phone.
Sent from my Nexus 4 using xda premium
It is indeed Donut. That's why I wanted to try and find a gingerbread rom or figure out how to make my own.
I unzipped the rom and dug around in there. I found some other thread on these forums about vibration and the symlinks and vibrate.ko. I checked in init.rc (on the phone) and found some lines about inserting modules relating to VibeTonez and the module "vtmdrv.ko" but I don't know if it is commented properly or turned on or symlinked or whatever. I see nothing about an actual vibrate.ko or anything.
How do I check my updater-script for the correct symlink?
I found this thread that has given me some interesting information: http://forum.xda-developers.com/showthread.php?t=1946614
and also this one: http://forum.xda-developers.com/showthread.php?t=1405366
Thanks for the interest! Unfortunately, I cannot just get a new phone. I am basically stuck with this one for the foreseeable future.
nookle said:
It is indeed Donut. That's why I wanted to try and find a gingerbread rom or figure out how to make my own.
I unzipped the rom and dug around in there. I found some other thread on these forums about vibration and the symlinks and vibrate.ko. I checked in init.rc (on the phone) and found some lines about inserting modules relating to VibeTonez and the module "vtmdrv.ko" but I don't know if it is commented properly or turned on or symlinked or whatever. I see nothing about an actual vibrate.ko or anything.
How do I check my updater-script for the correct symlink?
I found this thread that has given me some interesting information: http://forum.xda-developers.com/showthread.php?t=1946614
and also this one: http://forum.xda-developers.com/showthread.php?t=1405366
Thanks for the interest! Unfortunately, I cannot just get a new phone. I am basically stuck with this one for the foreseeable future.
Click to expand...
Click to collapse
No prob. Always interested in the legacy devices.
I wouldn't try to fix the vibrate, the developer himself states it will likely never be fixed (http://androidforums.com/behold-2-all-things-root/54769-port-galaxy-1-6-behold-2-final.html). I didn't read into the thread, but usually some user asks why vibrate doesn't work, dev explains, etc. You don't know if the problem with the ROM is the same as the issues found in the threads you searched.
If you want Gingerbread, it looks like the device is pretty much dead, however you can port CM7 from a similar device. It would be quite a chunk of work though.
Sent from my DROID2 using xda premium
Yeah, I have been going over all those threads that have that guy's roms. He made a few of them for this phone, and I am trying to find one that is better. Or the best of them.
I think I may have found a pretty major bug in the one I have, though. I got a call, I didn't want to answer it, and I hit the volume down button to silence the ringer, but it force closed android.phone.com and dropped the call. That wasn't cool.
I am also (kind of half-heartedly) pursuing creating my own rom from scratch. It's quite daunting, but I have a lot of time for the next week or so. My sister is having a complicated pregnancy so I am spending a lot of time at the hospital. There are plenty of guides and tutorials for beginners, so I am reading those and trying to figure things out.
Or I can figure out how to work on the rom this guy made, that would make life much easier.
nookle said:
Yeah, I have been going over all those threads that have that guy's roms. He made a few of them for this phone, and I am trying to find one that is better. Or the best of them.
I think I may have found a pretty major bug in the one I have, though. I got a call, I didn't want to answer it, and I hit the volume down button to silence the ringer, but it force closed android.phone.com and dropped the call. That wasn't cool.
I am also (kind of half-heartedly) pursuing creating my own rom from scratch. It's quite daunting, but I have a lot of time for the next week or so. My sister is having a complicated pregnancy so I am spending a lot of time at the hospital. There are plenty of guides and tutorials for beginners, so I am reading those and trying to figure things out.
Or I can figure out how to work on the rom this guy made, that would make life much easier.
Click to expand...
Click to collapse
I wouldn't try to make a ROM from scratch. A better thing to do would be to port. Basically find a ROM made for a phone with similar internals (type of CPU and RAM) and port the ROM. Much easier than making a ROM from scratch which requires knowledge of a few computer languages (mainly java). There are a few porting guides available on the forum.. Lemme find a link
Sent from my Nexus 4 using xda premium
Hey, thanks for your help! It's much appreciated! And believe me, if I could get a new phone I would. This phone is on my parent's plan, and only used for calling and texting family. I can't use data or anything. At this point it's more for the sake of learning about how to build an android operating system than anything else. I just want a nice, stable, useful phone that is better than the old school flip phones (of which I have had quite a few over the years).
Once again no prob. I used a legacy device just last year but it had quite some development so all I had to do was flash Roms lol.
Anyways this is how you compile GB
http://forum.xda-developers.com/showthread.php?t=1183832
And this is how you port. I would port from a similar device like the My touch 3g
http://forum.xda-developers.com/showthread.php?t=1598713
Sent from my Nexus 4 using xda premium
Haha yeah I am in the same boat with my nook. I have been following the devs over in the nook sub-forum for a couple years now. I have had several iterations of gingerbread, a couple of ics, and now a few of jelly bean. I am used to just slamming the rom zip on the sd card and booting into recovery and flashing it over.
For this phone I had to do odin, which was a new experience for me. Went pretty painless, and I figured it out. I prefer the recovery method over odin.
I have one question about the second link, about porting. It says in the first post that if you don't have gb already compiled for your (my)device that guide is useless for you (me). Is that what the first link is for? Compiling specifically for my device? What if my device is not supported at all? Do I just pick a somewhat similar phone, compile, port, make a flashable rom, and put it on the phone and hope it doesn't brick it?
Yep thats what the first link is for. Don't compile and port for a different device, that is a sure way to brick your phone.
Is your device not supported at all? Usually legacy devices are since back then (lol) there weren't a whole ton of Android phones
Sent from my Nexus 4 using xda premium
I don't know if my device is supported or not. I have not got to that part in the guide yet. I will report back if it is or isn't.
Sorry for not getting back earlier, I've been real busy the past week or two.
I finally got ubuntu set up on a computer, and was following the first guide and ran into a few problems.
First, I wasn't able to install all the required packages. If you want to know what ones they are I wrote them down. Not sure how essential they are in the grand scheme, but they weren't available.
Second, I tried to install java and ran into a problem adding the repos for it. The second one, for src, would not work at all. So I went on sun's or oracle's website and downloaded the linux package and installed it. But apparently it didn't work because all I get after trying to lunch are lots of these:
Code:
/bin/bash: java: command not found
Basically anywhere it tries to use java I get those messages. Eventually it gives up and says I have
Code:
version: /bin/bash: java: command not found
and I should have
Code:
version 1.6
Third, after I issue
Code:
source build/envsetup.sh
I see it includes some devices, like htc passion and samsung crespo4g and samsung crespo. Is this normal?
Fourth, When I do lunch I get five options
Code:
1. generic-eng
2. simulator
3. full_passion-userdebug
4. full_crespo4g-userdebug
5. full_crespo-userdebug
Should I just pick generic-eng?
I will be out of town all week for work, and won't have access to the computer I am doing all this on. For the life of me I cannot get unbuntu to install on my laptop. Never did like ubuntu, always favored fedora.
Anywho, thanks for any suggestions.
I have to post a serious "thank you!" to all the people who take the time to come here and help people like me.
Friday I rooted my HTC ONE S. Saturday I installed a new ROM (Miui) and had issues with the WiFi. Long story short, I installed 2 other ROMs and had the same issue. During the day, I somehow (stupid, I know) managed to completely erase everything on my phone - ROM and all. I tried for hours to read everything here that I could and fix it. At one point, I was certain I'd have to just go get a new phone because I had obviously completely screwed mine. But it's hard for me to just give up on a challenge.
During this process, I never had to register here and never had to post a question - search feature is great. Then last night, I finally got it working again. Not only that, but my phone works better now than before I rooted it. It's smoother, faster, more useful. Plus, ever since I got the phone, it's always had a hard time connecting to my home wifi. Now it doesn't.
The point to all of this is that if it weren't for all of you knowledgeable folks coming here and answering questions of people like me, then people like me would be in a lot of trouble and would have to settle for an otherwise bland Android experience.
So -- thanks to all of you!
david251 said:
I have to post a serious "thank you!" to all the people who take the time to come here and help people like me.
Friday I rooted my HTC ONE S. Saturday I installed a new ROM (Miui) and had issues with the WiFi. Long story short, I installed 2 other ROMs and had the same issue. During the day, I somehow (stupid, I know) managed to completely erase everything on my phone - ROM and all. I tried for hours to read everything here that I could and fix it. At one point, I was certain I'd have to just go get a new phone because I had obviously completely screwed mine. But it's hard for me to just give up on a challenge.
During this process, I never had to register here and never had to post a question - search feature is great. Then last night, I finally got it working again. Not only that, but my phone works better now than before I rooted it. It's smoother, faster, more useful. Plus, ever since I got the phone, it's always had a hard time connecting to my home wifi. Now it doesn't.
The point to all of this is that if it weren't for all of you knowledgeable folks coming here and answering questions of people like me, then people like me would be in a lot of trouble and would have to settle for an otherwise bland Android experience.
So -- thanks to all of you!
Click to expand...
Click to collapse
I agree with you completely but not that they want their names mentioned, it would not hurt to mention them or the ones you remember or hit their thanks button cuz I too have had the greatest help by many members but 2 in my case of rooting for almost a week and a half.
Since you're new, here's a friendly tip. You don't need to make a thread with thanks. You can just the thanks button and help others wherever possible.
No "Thank you"-Threads. Use Thanks-Button individually then the ppl that helped you know that they did
From my first CM experience, I remember a time, where I connected my phone to a computer, went to get.cm, click one or two buttons and watched everything else happen automatically. THAT was an experience worth noting! Perfectly simply and jaw-dropping!
Nowadays, I have to read through several pages of an article, click multiple links, concentrate heavily on the contents, do EXTRA research on google, youtube and other how-to pages, use lots of trial-and-error, work though a bunch of frustration and when I'm lucky, after several hours or sometimes days of work, I can get CM working on a phone. This is unacceptable to a medium-experience user in the year 2016! (Note that I'm not your cookie-cutter idiot being able to repair MacBooks, phones and understanding most things quite quickly compared to normal users.)
1st experience: back in 2013, I believe on my Nexus 5 => Perfect!
2nd experience: S3 neo, 2014: => Horrible! (got it to work, however)
3rd experience: late 2015 on LG G4, waited for a new CM supporting my device forever, although a quick CM was promised. Read though pages and pages of forum threads. Decided not to risk my warranty and get a bad photo app by installing CM rather than an excellent one from stock LG android. (overall, a bad experience again)
4th experience: today on an HTC One M7: Just as bad as before with the exception that I quit out of frustration.
It's absolutely incredible how much effort still need to be brought the the table in order to install CM! I mean seriously now:
1) Installing adb and fastboot (not idiot-proof on Mac OSX)
2) unlocking dev mode on the phone
3) using terminal commands to move files on sdcard (didn't work for me)
4) using bootloader commands on trwp
5) and so on and so on (lots of errors and problems on the way)
These are all not things that people know how to do EVEN IF THEY HAVE DONE THAT BEFORE 1 OR 2 YEARS AGO!!!! What happened to all that simplicity from the nexus 5 2013 era? I know what you are going to say in response to this: "Google/Android makes it much harder to unlock bootloaders/root the phone/and yadayadayaaaa...." But in reality all of this could be developed so much easier to reach a much larger user base. Do you not have any benefits from a larger user base? Do you not want to make CM spread to as many phones in the world as possible? Come on now, you can do SO MUCH better than this!
Well, if you want an elite community with only very few noobies bugging you for support, well then I can understand that. But if not, this thing is just annoying and extremely frustrating!
Please review The Purpose of XDA Assist [Please Read]
This is a place for new users to find their way around XDA.
Thread closed
gsstudios