yashsingh1/xdaforums huggingface dataset:
[Vibrant Android Development] nedlog:
Some of us use Glitch or Neo
[Vibrant Android Development] ew:
Sensor (level) problem - introduced with nightly 124

I believe that I have discovered a problem with the position sensor (detecting the device tilt) that was introduced with nightly 124. I discovered this when installing Screeble Pro - and finding that it did not work. I then discovered that GPS Status (available free in the market) indicated that my device was flat - no matter what position the device was in.

I flashed nightly 104 and all was good. Reflashed 124 (or later) and the problem reappeared.

Can anybody confirm this? If there is a problem, it would be nice if one of the developers noticed and could fix the issue.

Thanks,
[Vibrant Android Development] s0niqu3:
I prefer to see exactly all the changes that have been made to a kernel from stock, and include only a bare minimum for my needs. so I diff bali and neo sources against stock, and then patch in a couple of changes, and compile my own kernel.

(e.g. I want voodoo color, tinyrcu, and cifs, but I couldn't care less to have a million extra governers and schedulers, or extra OC options, since I don't bother with overclocking.)

Plus I theme CWM purple, and use my own boot image :)

Honestly, its pretty simple, if you have a linux or mac computer, you should give it a try. If anyone wants to try and compile their own kernel, you can send me a PM and I'll give you some tips and help when I have time.

And before anyone jumps on this "where's your source crap again" I'm not releasing or distributing my kernel, its purely for my own personal use. And the GPL only requires that I post my source if I distribute it. Plus, its a royal pain, I'm not a "git" master like everyone else seems to be, and I'm unemployed and don't have the money to purchase enough space on github to even host the kernel source (its about ~1gb and github free accounts only give you ~0.3gb space.)

Cheers :)
[Vibrant Android Development] Phateless:
Interesting.... so does 104 give better GPS?
[Vibrant Android Development] beren28:
Battery life keeps getting worse and worse for me.

Went to a baseball game today. Left the car with a full charge. Got back to the car with 49%. 10 minutes of screen-on time, and no apps are listed as using up any battery. Wifi was first, then screen then cell standby.

Battery life is fine hen I am on wifi, so it is something with being on 3g. I tried switching to 2g only for a day, and the battery drained just as fast.

I may have to go back to Bionix just so I can get through a day at work without fear of running out. At work the phone is in my pocket, unused all day, but it is still draining like a mother since I am not on wifi.
[Vibrant Android Development] Oxirane:
Is Glitch working with the lastest couple builds or does that still cause for bootloops?
[Vibrant Android Development] jpcdeux:
Half the Apps I want to install say "not compatible with your device" wtf?! They worked on the last build, not 130
[Vibrant Android Development] nedlog:
Yes, just get the latest v12.
[Vibrant Android Development] knowgood:
Has anyone noticed swype not working? It said I needed to do an update for it to work, so I did an update and I am still having problems. I am on nightly 124
[Vibrant Android Development] krntehknik303:
For android system to be taking up 28% of my battery does it mean that its my phone or a problem with the rom? Just wondering as my battery life is on and off and so seems android system.
[Vibrant Android Development] 12paq:
Awhh sad, ..there are special devs out there and you are in that crowd. I know I miss your kernels and dev work. Why the tease?

Hint: RootzWiki. Lol

.

From a CM7 Nook Color tablet
[Vibrant Android Development] barribow:
same problem for me
[Vibrant Android Development] joshuapurcell:
Swype works fine for me... I'm on nightly 130.

---------- Post added at 02:04 AM ---------- Previous post was at 02:02 AM ----------

I get this for Order and Chaos. It is probably for the better.
[Vibrant Android Development] JediDru:
Question, why not use an app to disable the cells radios when the screen is off. I work 12 hours a day and leave with 50-70% on every rom depending.
[Vibrant Android Development] beren28:
Because then I might as well have a dumb phone. ;)
[Vibrant Android Development] nedlog:
Works for me, I just flashed 131 and used it for this response. You might try getting the installer and trying again.
[Vibrant Android Development] joe98200:
It's been working fine for me.
[Vibrant Android Development] fb_hexedit:
I am on 131. No sensors data either. Gps works once with each update. Then it won't work again until next I try a new nightly.
[Vibrant Android Development] ew:
Thanks for the confirmation. I just was wondering whether the sensor issue could be kernel related. I experienced the problem using the stock kernel. Which kernel did you use.
[Vibrant Android Development] krntehknik303:
So there are issues with 131?
[Vibrant Android Development] PigProtist:
I'm still on nightly 83, but was the 2g/3g toggle bug that caused the phone.apk or whatever it was to force close ever fixed? I'm afraid to try it, haha.
[Vibrant Android Development] beren28:
Never fixed.

But the next nightly has something int he chagnelog about it.
[Vibrant Android Development] s0niqu3:
I've been trying to pin down the battery issues that seem to plague so many of us, and on my phone at least, whenever it won't sleep, it shows that the phone is using the sensor's for hours on end.

So, this might be part of a preliminary fix for the phone not sleeping. Has anyone that's having sensor issues looked into this?

Also, I checked the latest kernel source, and there's very little different from the last version, and zero changes to the vibrantmtd defconfig, so either the change is in the actual new nightly android code, or the kernel source hasn't been updated on github.

I might try building a kernel with sensor's turned off to see if it fixes my phone not sleeping issues.

Cheers, :)
[Vibrant Android Development] PigProtist:
Okay, thanks. Guess I'll just stick to keeping my data turned off during the day, then.
[Vibrant Android Development] mindstormmaster1:
Three things:

First: I installed 131 and restored with TI and now everything is FC like crazy! Just a warning.

Second: Has anyone else noticed that if they flash CM when they reboot the battery says it is at 5% even if that battery was as 75% when you flashed and then slowly it works back up to what percent it was to start with?

Third: Has anyone ever figured out why Android System now uses a ton of battery?
[Vibrant Android Development] fb_hexedit:
Stock kernel
[Vibrant Android Development] knowgood:
I think i'll just reflash to the latest cm7 and see how that works. I've tried downloading the swype installer multiple times. It's not really a big issue its just annoying to try and text.
[Vibrant Android Development] krntehknik303:
hmmm hmmm h mmmm
[Vibrant Android Development] knowgood:
Found a solution, well at least found something that fixed my problem with swype. I had to completely uninstall the previous version of swype and the uninstaller, and then install the new version. Hope this helps out.
[Vibrant Android Development] notverycreative:
Disabling my GPS (renaming the binary) got rid of my no-sleep issues. Nothing of value was lost because my GPS never really worked.
[Vibrant Android Development] SuperJMN:
What file did you rename? Thanks!

Enviado desde mi SGH-T959 usando Tapatalk
[Vibrant Android Development] creepinm3:
Does anyone get a "hang" while trying to send a MMS?
[Vibrant Android Development] zmattmanz:
Nope. Sometimes I get it when texting with Google Voice though.
[Vibrant Android Development] Blars1206:
I also installed 131 and used titanium backup and no problems at all. I also did not have any battery problems or the issue with the Android system using a lot of battery. Sounds like you should wipe and clear davlik and try again. But don't use titanium to restore system settings, apps only.
[Vibrant Android Development] a2296455:
You can fix the sleep issue by rebooting after uplugging the charger. Don't ask me why, but the phone goes into deep sleep when I do this.
[Vibrant Android Development] beren28:
2g/3g widget seems to work
[Vibrant Android Development] notverycreative:
Not sure! I used this apk and it works like a charm. Just run it and reboot after each flash.

http://db.tt/YuDfqqq4
[Vibrant Android Development] Xenoism:
Glitch is working great - i'm on

build 131 with a glitch kernel
[Vibrant Android Development] krntehknik303:
I have tried that multiple times and that doesn't seem to solve the issue.. Maybe I will try renaming the GPS binaries sometime when I go back to CM7.
[Vibrant Android Development] zmattmanz:
Sweet, looks like were getting a fix for the Share scroll bar in the next build.
[Vibrant Android Development] SuperJMN:
USB tethering?

The Remote NDIS based sharing device is showing up in the Device manager (Windows 7 x64), but it states that "the device cannot start (code 10)".

What do I need in order to use USB tethering?
[Vibrant Android Development] swa2k4:
Sticking with 84 on my Vibrant but will jump when there is a finally fixed 911 calling out??!? can someone help on how to fix it, thanks all!
[Vibrant Android Development] cokester:
......... ..
[Vibrant Android Development] barribow:
Do you guys know how we can reset the battery usage diagram?
[Vibrant Android Development] }{Alienz}{:
I want a good battery life with this. It's been so many months! I hate Samsung. Dumb source code tree huggers.
[Vibrant Android Development] notverycreative:
Fully charge your phone.
[Vibrant Android Development] lawalty:
I'm trying to install CM7 nightlies on my wifes Vibrant.

I purchased Rom Manager Premium, and have her phone rooted with CWR installed.

CyanogenMod 7 Nightlies are not even listed in the "Download Rom" list.

I see a bunch of free roms to try, but nothing in the Paid section.

What can I do??

I tried to flash CM7 (latest nightly) via CWR by downloading the rom, and entering CWR and install from sd card. But, it goes into some weird install loop.

What can I do?
[Vibrant Android Development] }{Alienz}{:
If that's the case, ODIN back to stock and redo it. I've had something similar happen. CM7 will not always recognize the ROM and phone you're trying to install it on if you're running something custom. Hence the loops you're getting.

ODIN to stock

Reboot to recovery

Try it again, will work.
[Vibrant Android Development] barribow:
Did you try Vibrant (mtd) and then 3.x.x.x? otherwise you may not see it.

---------- Post added at 11:36 AM ---------- Previous post was at 11:36 AM ----------

as a separate issue

my phone doesn't go to sleep very well, is this a kernel issue?

When I had glitch or Bali it was better than now.

Or is it issue with 132?
[Vibrant Android Development] androidmonkey:
Has the issue with the /data/data folder been resolved with CM7 ROMs yet?
[Vibrant Android Development] lawalty:
I'll give it a try. I'm assuming you mean in the Rom Manager?? Is it some type of drop down list to select from?

Edit: okay guys! Don't everyone be bust'in down my door to help... ok ok ok I figured it out. I just re-flashed another version of CWR through rom manager picked Vibrant MTD.

Thanks Barribow.
[Vibrant Android Development] syl0n:
Is it just me or does Compass not work on latest nightlies? I have tried calibrating but still no-go.
[Vibrant Android Development] notverycreative:
Doesn't work for me either.
[Vibrant Android Development] barribow:
You're welcome glad you fixed it :)
[Vibrant Android Development] creepinm3:
I heard that the latest nightly is 2.3.7, is that true?
[Vibrant Android Development] hurtz777:
Yes I am running it right now and it is fast and stable so far. Check Gekkekoe123's thread.
[Vibrant Android Development] creepinm3:
How battery life? Usually if I unplug when I wake up (6am) I am dying by (9:30am) just by sending a text and such
[Vibrant Android Development] beren28:
Your battery is broken.
[Vibrant Android Development] hurtz777:
I am running cm #136 gb 2.37 with Neo17R16 and it is fast and stable.
[Vibrant Android Development] KWKSLVR:
I agree. I usually go 10-12 hours on 3G with moderate use. Grab some spare batteries off of Amazon. You can get Samsung OEM batteries for like $2 or $3 each.
[Vibrant Android Development] Oxirane:
An external charger will also work wonders. I think I got mine for $10 or so on Amazon?

Very happy with CM7, it really does put Samsuns based roms to shame. :)
[Vibrant Android Development] iwillkillyou:
How has battery improved? I haven't used CM7 in about a month.
[Vibrant Android Development] asatnik11:
I can easily get 18 hours with moderate-low use with wifi on the whole time with the wifi sleep policy set to 'never'. Id be lucky to get 12 hours with 3g connected the whole time.
[Vibrant Android Development] seojuhwan:
How do I get rid of the FC problem with any GB ROM? I only restore apps and not system data using Titanium yet I get repeated FCs after an hour of flashing any GB ROM (even after ODIN-ing)!!!

Also, why do my wifi and phone signal icons turn white?
[Vibrant Android Development] treleung:
Utterly confused.

I've tried the last 10 nightlies thinking it was an issue with the roms, but no matter what I do, I get bootlooping when I try to install CM7.

I'm coming from a Froyo rom with froyo bootloaders.

It says "Checking BTN/MTD state" then restarts, shows the CM logo, then goes into an ugly bootloop.

I have no way of getting out of it (not even to clockworkmod) so I have to pull the battery, get into download mode and flash back to stock.

Ideas?
[Vibrant Android Development] lifehijack:
Market force closes

Hi, I m on nightly #136 and the market keeps force closing. I have tried deleting the cache but it still force closes. The market version is 3.1.5. How do I fix this?
[Vibrant Android Development] igor.ibit:
Guys, im sorry in advance for this question :)

Where do i get drivers for CM7 that let me use ADB?

I tried all sorts of Samsung drivers with CM and none seemed to work. "adb devices" comes empty every time.

I moved to 2.2 for now because i need my DDMS working, and 2.2 sucks!
[Vibrant Android Development] lawalty:
My wife's phone kept doing the same thing.. this is how I solved it.

1. Odin back to 2.1 or 2.2 then root. Or start from a working rooted rom (it must be rooted).

2. Install Rom Manager Premium (come on, it the price of an inexpensive lunch).

3. In Rom Manager Premium, select flash Clockwork Recovery

(Important) - select "Vibrant (MTD)"

It will say that "Vibrant (MTD) does not have an official supported CWR bla bla bla ... just select "OK".

4. Then select "ClockworkMod 3.x".

Then press ok.

5. GO into "Download Rom" and under Premium select "CyanogenMod Nightlies" then select the latest nightly.

6. When prompt, select to download Google Gapps.

7. After download, if your coming from another rom, I would recommend to wipe data and cash (start with a clean slate).

Let Rom Manager do the hard stuff, then BAMB! You got your self CM7 latest nightly on you Vibrant! :)
[Vibrant Android Development] IT Rider:
I flashed my wife's vibrant this morning with #136 and had the same problem. I fixed permissions and it did the same thing. not sure what the problem was (all google based apps were acting like this)...so i restored my nandroid backup from #132 and she was back working. try flashing a different nightly to see if that fixes it.
[Vibrant Android Development] thethirdeye:
Is anyone else having problems sending MMS, I can receive just fine, but I cannot send them unless i'm connected through my home wifi
[Vibrant Android Development] Phateless:
Wipe data and format system in clockworkmod recovery before you flash.
[Vibrant Android Development] jay661972:
Its better to dl the rom and gapps from rom manager. It wont give you fc on market. I dl mine from rom manager (make sure you are in premiuim).
[Vibrant Android Development] jay661972:
+1
[Vibrant Android Development] ew:
I tried flashing 136. I did not have the issues that others have posted about, but the sensors are still not working. I wish there was a solution to that problem. I would really like to get past 104 (the last nightly with working sensors).
[Vibrant Android Development] nedlog:
You need to download and install the Nexus drivers from Google SDK and make sure you install as Administrator on your computer.
[Vibrant Android Development] avelec:
Hi, wonder if anyone having problem with the back lights staying on with the 4 buttons below the screen (back, menu, search, home). The problem started a few nightly ago. Currently on the latest nightly. Thanks in advance.
[Vibrant Android Development] Oxirane:
I've never had a FC issue with CM7/MIUI/other AOSP GB roms. Are you wiping data/cache/dalvik before installing? Using the kernel cleaning script prior to flashing other kernels?

As to turning white, that means not connected to Google Servers. Green/other colors = connected*.

*Some themes break this.
[Vibrant Android Development] treleung:
I think the core issue was selecting MTD and 3x. After an hour of messing around I finally got that to go.

And yeah, I purchased Premium haha.

Thanks.
[Vibrant Android Development] Nabeel10:
Is 911 calling fixed yet?

Sent from my Vibrant on Ultimate 2.2.1 :D
[Vibrant Android Development] nedlog:
No not as far as I know; I haven't even tried since about two months ago. I haven't seen anything on the change logs either.
[Vibrant Android Development] Cesarp 24:
Off topic. I'm looking for an app that is a shortcut to general sync making it easier to toggle auto sync or background data. I used it before but I can't remember the name. Thanks in advance.

Sent From My Pocket Decepticon.
[Vibrant Android Development] SimeonAS89:
Can anyone confirm if the volume issue has been fixed since #101? This is an issue I've been noticing and its kind of annoying.
[Vibrant Android Development] creepinm3:
Anyone found a working kernel working with 2.3.7 nightly?
[Vibrant Android Development] hurtz777:
Neo17R16 works flawlessly for me with cm#136 2.37.
[Vibrant Android Development] Oxirane:
Glitch V12 B3 has been working great. Quite sure the latest Platypus also works, but haven't used it yet. And I don't use Bali/others so I can't give input there.
[Vibrant Android Development] wcouri:
Hey guys, I'm in a dilemma here. My friend wanted me to install CM7 on his vibrant, so I successfully flashed the latest nightly and all was well. For some reason, his phone randomly shut off, and will not turn back on. Could it possibly be a bad flash? Although everything worked perfectly for three days. By the way I have good experience with flashing as I have a CM7'd Samsung Mesmerize. Any suggestions would be greatly appreciated.
[Vibrant Android Development] nbhnohome:
ODIN back to Stock and Start all over again.
[Vibrant Android Development] lifehijack:
To get the market working properly, delete marketupdater.apk from system/app and then download and installed Market version 2.3.6. This way, the market will remain on this version and it will work absolutely fine.
[Vibrant Android Development] jay661972:
just flash the new nightly 138, coming from 136, need to flash gapps again and gmail fc so many times. need to uninstall and install from the market. hop
[Vibrant Android Development] bigtom624:
Is anyone else not seeing the latest nightly # 138 in Rom Manager? I checked for updates and in the download section and it isn't in either one. I had to go to the CM7 mirror site to d/l it.
[Vibrant Android Development] jay661972:
that's where i got the 138
[Vibrant Android Development] bigtom624:
From Rom Manager?
[Vibrant Android Development] jay661972:
form cyanogen mirror. 138 is not in rom manager. dont know why
[Vibrant Android Development] funeralthirst:
hmmm. flashed 136 last night coming from 126. it worked basically overnight. i woke up this morning to an email notification, so i grabbed my phone in time to see it shut off. i turned it back on and it shut off again after fully booting up. then when i turned it back on again: boot loop. tried reflashing 136, boot loop, tried reflashing 126 boot loop. cleared caches, boot loop. factory reset and reflashed 136 and it booted up, but now titanium backup is freezing (and i'm only restoring apps, no system). any ideas that aren't heimdall?
[Vibrant Android Development] KWKSLVR:
The lights being illuminated are message notifications.

If you're having force close issues then wipe and restore just apps and NOT app data or system data. That solved my issues. Try that and if there are apps you need data from, then restore them one at a time to be sure you don't have issues.
[Vibrant Android Development] bigtom624:
I think it might be like that with all the phones on the last few nightlie's. My daughter has a Cliq XT ( Zeppelin) and it was not in Rom Manager either.
[Vibrant Android Development] Demetris:
+1 is annoying
[Vibrant Android Development] ChristoA1:
Yes, this has been fine for a bit...
[Vibrant Android Development] joe.kerwin:
+1 on this
[Vibrant Android Development] avelec:
bump! Please if someone could help.
[Vibrant Android Development] Kaik541:
it's called LED notifications. clear your notifications to have them turn off. or disable them using CMSettings->Interface->LED notifications
[Vibrant Android Development] KWKSLVR:
And search. The same tiresome questions are coming up over and over. If you can't RTFM, don't flash a beta rom. ;)
[Vibrant Android Development] Phateless:
Agreed!
[Vibrant Android Development] defconoi:
Getting terrible battery life on #136 any tips on improving? Does renaming GPS module help?
[Vibrant Android Development] barribow:
I installed #136 and my phone suddenly became too dark, anyone experienced this?
[Vibrant Android Development] s0niqu3:
Did you have another kernel installed prior to 136?

If you had a kernel with voodoo color installed, then your old settings haven't been changed, but the new "RGB tuning" in the default kernel is pretty radically different from voodoo color even though it uses the voodoo control app to configure.

So, try launching voodoo control, and resetting the color settings.

Cheers :)
[Vibrant Android Development] avelec:
Thank you.
[Vibrant Android Development] syl0n:
My GPS is hit and miss with CM7 - sometimes it just dies and needs reboot to get it to work. The fix here http://xdaforums.com/showthread.php?t=1199613 that uses the older gpsd solved it. I am now getting instant locks for a hot start and even initial cold lock is under 1 minute without A-GPS and even faster with it. Also it doesn't just break down randomly when switching between apps, it locks again almost instantly.

Any idea why CM7 is using the new gpsd when the old one seems more reliable?

Read the problem i was having here http://xdaforums.com/showpost.php?p=18105657&postcount=207
[Vibrant Android Development] barribow:
Yes in fact I used voodoo and reset and it came back, but you know I thought maybe a little darker would hep the battery, doesn't it?
[Vibrant Android Development] s0niqu3:
Hey again everyone,

So for anyone still having sensors/compass problems, it seems the latest nightly builds for the vibrant don't include the /system/vendor/bin/geomagneticd and /system/vendor/bin/orientationd files necessary for the compass to work.

Honestly, I have no idea how this is even possible, since whenever I build CM on my laptop, the make will error if it can't find both those files.

Regardless though, I dug the files out of an old nightly and made a quick flash-able zip.

Cheers :)
[Vibrant Android Development] igor.ibit:
my phone just wont stay in debug mode! this is so frustrating!

Im working on an app, and i cant push it to the device. it goes offline all the time. Anyone know how to fix this?
[Vibrant Android Development] CTown:
The compass finally spins, thanks for the fix. I just had to callibrate it (by rotating the phone all over).