yashsingh1/xdaforums huggingface dataset:
[G1 Android Development] quangminhquang:
Thx a lot. Now I'm using CM 4.2.6 and ofcause I've flashed the base img. I did a wipe and flashed to 4.2.12.2 everything's ok but when I tried to sign in my G acc, there's a error on sim card (G1 show me that) but with this sim I can sign all the rom before. I got a new sim but nothing's changed. I'm using the lastest radio and Danger SPL. Thx 4 your help!
[G1 Android Development] _aMUSEd_:
Microphone bug?

Hello,

since upgrading from 4.2.11 to 4.2.12 on my HTC Magic other people complain that they hardly can hear me.

This issue was not present in 4.2.11 - any suggestions?

Thanks in advance!

Kind regards
[G1 Android Development] snottily:
blame mobilkom. i get that complaint all the time, NOT starting with 4.2.12.2.

redialling helps most times.

oder schrei einfach mehr ;)
[G1 Android Development] _aMUSEd_:
@snottily:

I work at mobilkom, and I do not have this issue on a Nokia N97 and it started definitly and reproducable with 4.2.12 and I did not have this issue with release 4.2.11

Kind regards!
[G1 Android Development] rich0:
Keep up the good work!

Just wanted to post a short note of feedback that I really appreciate the work Cyanogen has put into making a stable and usable Dream ROM.

Sure, there are lots of great bleeding-edge ROMs, and I'm happy to see people pushing the envelope (including Cyanogen). However, a day-to-day usable ROM requires a lot of patience and discipline, and I appreciate that the team behind this ROM has that. Tracking down some force close bug three menus deep in the dialer probably isn't as exciting as multi-touch on the maps, but it is essential to a clean user experience.

I think that in time we'll see android development mature further along those lines, but until we have the equivalent of ubuntu for android we need people like Cyanogen!
[G1 Android Development] _zygo_:
Here you go, people. I haven't posted in the last couple of days, so bring on the flame.

No, greensnow, you are wrong. The last stable version was not 4.2.5, It was 4.2.12.2. If I were you, I wouldn't use the ROM if it was that buggy. You may have to go back to stock. But, rather than disparage the ROM developer, do some troubleshooting on your own. If you are having FC problems, very-frequent browser crashes, lockups, and reboots, you will need to do the following: wipe, reflash defanged base, flash 4.2.12.2, then start loading your apps one at a time until your problems start again. These instructions are clearly spelled out in the link from the first post in this thread. Tell us how your phone is configured, which apps you are running, if you are running compcache or a mem hack. Did you wipe between fashes, etc. Come back and tell us how your browser is working after a wipe and reflash.
[G1 Android Development] no6969el:
I wanna start off by sayign I love these roms, I have noticed one always reoccuring issue though. It seems after a few updates (or perhaps whenever a certain file in the system is being updated) the phone will be running very slow and sluggish and will require a FULL update flash (HTC image and cyan rom) in order to start working at top speed again.

Ive tried everything I could to fix the issue without fully rewiping and flashing htc base image and cyan but no luck.

I feel that this "new" way of flashing the phone because of googles issue is causing GREAT performance issues. And then to fix it requires me to consistently wipe the way I have my stuff setup.

I see that other threads still have the use of the full rom and need no base, Can a combined release be made and released on ANOTHER THREAD so we can have one flash. As long as cyan makes them separate he has no worries from google so someone else can merge it like one guy did a few months ago.

If not cause that might break some rule then we need to consider making EVERY dev make and distribute their rom THIS WAY.
[G1 Android Development] jotusery:
Thanks

4.2.12.2 runs perfect! Stable and fast. I'm not sure what you guys having issues are doing, but I have no idea what I am doing (I still have no idea what an "SPL" is:)) and my phone runs great. Thanks, Cyan. This is a great release. The browser is great and the call log rocks.
[G1 Android Development] ZilverZurfarn:
I understand your thinking, but really - Rethink.

Due to a spontaneous eject of my SD card, my phone started acting up (the sad story described in detail a few pages back) and I started trying this and that, spending hour upon hour to fix the problems that arised. Finally I gave in, and did just that - complete wipe, reinstal of base 1.6, install of latest CM - And my phone went back to its old fast stable self. The whole procedure incl. downloading, backing up and reinstalling all my apps and all took less than an hour. Pinpointing and fixing the exact cause if a problem might be fun as an etude, but a broad spectrum cure like full wipe+reinstall is unbeatable.

/Mats
[G1 Android Development] ScotterMonkey:
Moving SD from rooted G1 to non-rooted Nexus1

I have a G1 Rooted and working great with Cyanogen 4.2.9.

I set up class 6 16GB card “ext3″ to set up apps-to-SD, which works great.

I just ordered a Nexus One. Is there anything I need to do to move my 16GB card to the new phone? Should I format it or leave it as is?

How does your advice change if I intend to root or not root my new Nexus One?
[G1 Android Development] no6969el:
Maybe you didnt understand what my main intentions were.... It was not to try and figure out the problem..... I was saying to combine the files to one update... so that its a wipe then flash. not needing two files.. just one.

that would prevent most of the issues I feel is happening because when you just flash cyans over top all the time I have a quicker time before I would need to wipe and reinstall than if it was a whole image.
[G1 Android Development] no6969el:
Are you stuck on that 500 minute plan?
[G1 Android Development] Cresho:
It was buggy for me until

I was using the 4.2.5 rom for a long time and ran really good until i decided to try out 4.2.12.2 and it was a disaster. Then i went back to a nandroid backup and tried 4.2.5 and i was fine.

I liked 4.2.12.2 alot but it was buggy. so i backed up ext and did a nandroid backup and whiped ext3 and also the internal. I was a clean start and installed 4.2.12.2 and guess what? It runs just fine on a fresh install.

NOW! I wanted to go back to my 4.2.5 and install 4.2.12.2 on top of that and guess what? When I whiped the ext3 that had a zipped apps or directories from 4.2.5 on the sd, I could not restore my 4.2.5 that I had originally working....so im using 4.2.12.2 on a clean slate and it is flawless.
[G1 Android Development] no6969el:
Almost EXACTLY what im trying to say in my post a few above! This remains true for EVERY user.. and we could prolly prevent this from hving ONE ROM to flash not two.

NOTE: how can I say that you ask?.....well before when cyan had one rom these "need to wipe and reflash" was maybe after every 3-4 roms.. now its about every 1 or 2 flashes I would recomeend reflashing it all.. thats too soon though.

Its NIGHT AND DAY of how it feels updating with flashing the 1.6 and not.
[G1 Android Development] ZilverZurfarn:
That was exactly what CM was before, until Google told Cyanogen to stop distributing their applications, or meet them in court.

/Mats
[G1 Android Development] no6969el:
yea.. thats what I was saying in my above posts... I know that.. and I also know that there were LESS issues during that time when it comes to speeds after a flash/upgrade

Also i mentioned in my above posts that SOMEONE ELSE (someone else meaning anyone else including me) should put it up on ANOTHER THREAD... to avoid that issue, since it seems the REST of xda isnt concerned since they use one file for EVERY OTHER ROM on this site.

To save issues though.. honestly... If I could be pointed in the direction that would INFORM me HOW to do this myself (combine the 1.6 base image and cyan rom to one .zip) and I will gladly learn and be that person to put it up.
[G1 Android Development] ScotterMonkey:
I'm not sure yet.

I had purchased my G1 originally full cash price so I could be month to month with Tmobile.

I've been on a 900 minute plan since then.

I intend to talk with a Tmobile rep to get on either unlimited minutes or at least 900 minutes plan.
[G1 Android Development] samsci:
There are different areas in the autostarts application where you need to disable the offending application. So far, in using it, I have found it has worked pretty well. Apparently, the apps start in different situations when the phone starts, gets a call, etc...
[G1 Android Development] no6969el:
Only reason I ask is because I was talking to tmobile and mentioned that on the nexus one site from google they mention you MUST get the 500 minute plan. But if you bought it in full then you can do what you want.

Congrats on your purchase!!! I cant wait till I can get my nexus one, or the experia x10 depends on when I can get a new phone!....
[G1 Android Development] BopChie:
ahhh, thanx... this morning it seems on point again lol
[G1 Android Development] ScotterMonkey:
OK. I meant 1000, not 900, as what i HAD on my G1.

Let me be clear I bought my G1 full, not subsidized so that I could get my next phone, my dream phone, the Nexus One, subsidized.

You are correct that when I ordered the Nexus One they set me up with the 500 minute plan. A call to Tmobile changed that asap. But it bumped me up from $79/mo to $89/mo, which is fine with me.
[G1 Android Development] jedinger:
One more follow up question about flashing amon ra:

I was able to get it connected to the computer for fastboot, but where do I put the recovery image such that fastboot can see it? I tried /data on the internal mem, but I can't actually write the file to that location using any of the android file managers.

Also, RE the Nexus One:

You can't actually buy the phone from t-mobile; you have to get it from google.com/phone. That said, if you want get the subsidized price, you MUST open a new contract and suffer through the 500 minute plan. There is NO other plan available for that price. If you pay the $529, you can do whatever you want w/it on your current plan, though. Kinda lame if you ask me.
[G1 Android Development] :
Just put it on the root of the sdcard.
[G1 Android Development] no6969el:
Exactly my friend.. correct on all points. As for your question about teh recovery image, on the root of the SDcard.
[G1 Android Development] javon27:
you're probably using a keyboard other than the standard Android keyboard. Switch keyboards before starting the terminal
[G1 Android Development] jedinger:
I, in fact, am. Using HTC_IME (I hate the stock one).

And I fat-fingered the image name. :( Apparently, my fingers thought there was no 'y' in 'recovery'...

Thanks all. Will try shortly.
[G1 Android Development] PsychoI3oy:
Fastboot is run from the computer, so the recovery.img needs to be on the computer (not the root of the SD as someone else suggested).

The common practice is to dump the recovery.img in the same dir as fastboot, e.g. sdk/tools so the command would be something like:

fastboot flash recovery recovery.img

from your homedir in linux:

fastboot flash recovery ~/recovery.img

the root of the c: drive in windows:

fastboot flash recovery c:\recovery.img

etc.
[G1 Android Development] Zei:
Sad to say the X10 is gonna be a Canadian ONLY phone
[G1 Android Development] Proxin:
How can you move the dalvik-cache *off* the SD card?

Cyanogenmod has been odexing whenever I reboot, so it recreates the /system/sd/dalvik-cache if I remove it.
[G1 Android Development] renegadedj:
i'm on 4.2.12.2 since last night and i've had a random reboot every hour pretty much. i did a no wipe update from 4.2.11.1 so now im gonna try a complete wipe update to 4.2.12.2 again. very disheartening tho as i havent had random reboots since before 4.1.1.111111111111 you know the long numbered updates haha.

im on a g1 btw.

other than the reboots tho the rom is incredible. the bluetooth is flawless now IMO. oh one question: didn't notice until i took a road trip this past weekend but where'd the Zoom go on the camera? i mean i know upon initial release of android there was no zoom, but wasn't it in the 1.6 donut update? i know it's in the hero camera software. *shurgz* no big deal just remember having zoom in a recent CM rom like around 3.9-4.0...
[G1 Android Development] jgato:
after another test, now, I am more sure about the problem happens when I charge the battery with mobile switched on. Please, if this is no the right thread, let me know where to talk about this estrange issue.
[G1 Android Development] linuxluver:
Camera ZOOM

Paid app Camera ZOOM FX has a zoom. Maybe you had that app? The zoom just delivers a crop subset of the CCD capture, though. The more you zoom, the smaller the output pic.....but it has what you want.
[G1 Android Development] larrygates:
I've been talking about this for a while now, I wish I could pull the data and dalvik off the SD card, but there's a script that just puts it right back or they're melded using union fs or bfs or whatever. It's a let down, since I have a class 4 and I'd bet a class 6 wouldn't be that much better anyway once it starts getting filled up. I tried out the stock ROM with the expsetup, that was one of the best ROMs I've ever used, and I've been at it since the JF days.

I would really like the dalvik back on the G1's internal, but even in that other ROM if you have an EXT partition, game over, it's going to the SD, lucidREM or no other method works to get it off of there.
[G1 Android Development] samsci:
I had the random reboots before 4.2.12.2 repeatedly. It drove me crazy. I could be talking on the phone, downloading an app, typing, doing anything and poof, a reboot happened. Since updating to 4.2.12.2 when it came out, I have not had one reboot.

One thing I have heard however, is that some people have had issues with widgets causing issues and some apps that might be causing some issues with the random reboots, so you might want to look into these.

Hope that helps.
[G1 Android Development] ebbysaja:
i use the latest cynogen.when i play music with headshet n i received a sms.my sound is gone.the music n ringtone like silent.to solve the problem is reset my device.how to solve this problem
[G1 Android Development] Proxin:
There should be an option for those of us who want it back on the internal memory. Since we already have apps on sd, what else are we going to do with that extra space? It makes no sense to put it somewhere else, then.
[G1 Android Development] renegadedj:
since this newest update i have started keeping the new power control widget on, and have had reboots. but i love that widget since i got my car back with bluetooth radio oh man! hahaha wish i could add a bluetooth on/off shortcut... maybe with better cut. or maybe ill just try d/ling the bluetooth on/off single widget app fromt he market.

thanks for the help tho! two heads ARE better than one!
[G1 Android Development] GordoMan:
Touch Problems

I am on Cyanogen 4.2.12.2, but I have had this problem on prior ROMs as well.

After a while of using the phone (I can't seem to pin down exactly what causes the problem) my touch sensors fail to the point where my clicks register elsewhere on the screen. I'll click OK on a dialog only to have it cancel. I'll create a contact and click save only to have it discarded. It's SUPER annoying.

To try and remedy my problem I reformated my SD card, wiped my data and started from scratch on 4.2.12.2. I have also run fix_permissions a number of times.

A reboot temporarily fixes my problem, but it always seems to come back.

Does anyone have any ideas? I have not yet seen this in Cyanogen's bug tracker.

Thanks,

Gordo
[G1 Android Development] mr2t32:
for those that are having connection problems with ebuddy or data, what ver. of cm are you on, phone model, and which provider do you have? I'm starting to think it's the provider. Anyways, i'm on mt3g with tmo on cm 4.2.8.1 and having connection problems again. I went from 4.2.9.1 to 4.2.12.2 back to 4.2.8.1. 4.2.8.1 was solid for the past few days and today I'm getting the connection problem, so i'm thinking it's just a problem with tmo's service.
[G1 Android Development] Stumc10:
I have been having major issues with the 'HOME" button, it takes an age to fully load up the home screen and is unresponsive for a while, once loaded it is fine. I sometimes get a message regarding the activity home and have option to force close/wait. any ideas?

I dont have that much on the home screen, nothing i haven't had in the past with no issues. Also i don't use a home replacement or a theme.
[G1 Android Development] mygti02:
so im not sure if anyone else is experiencing this, but when i try to use the BT on my care system (Nissan Altima coupe with Navi) it syncs no problem, but when i make a call it sounds like its under water or breaking up. i hear it and the person i call hears it. It makes the phone un-usable with my car BT. Any suggestions as to why this might be happening? Or maybe this just proves that my crap Nissan really is that, a piece of crap and just another thing not working :(

any feed back would be great thanks!
[G1 Android Development] ScotterMonkey:
bugs or widgets?

I've stayed with 4.2.9 because I read so many issues people are having. I've never had any of these issues. I also do not run *any* widgets, power management apps, or taskiller. The only app I run that seems like it might "mess with" things is a CPU overclocking app. But that doesn't seem to mess with anything. So... what I'm postulating here is: I wonder if people who are having all these issues with reboots, force closes, and other things not working - I wonder if they are running widgets or other apps that interfere with the OS in a way that is causing these issues?

I propose that when you post some issue with random reboots or "____ not working" you also post a list of the non-standard apps you are running as well as any widgets you are running. Then maybe we will see some patterns... ?
[G1 Android Development] jedinger:
Just out of curiosity, how long does the flash recovery command take to complete?

EDIT: getting the following: FAILED (remote: not allow)
[G1 Android Development] williamthrilliam:
Same problem with my tracks. I reverted back to 4.2.9.1 for now and am not having that problem. I noticed in that version changelog an APN list for AGPS fix is mentioned. Maybe it needs to be addressed again?
[G1 Android Development] Lone Shepherd:
I've been noticing some bugginess in the past few Cyanogen mods -- not sure what's going on here.

(1) Browser randomly crashes; takes me back to home screen. Often, the browser will crash immediately after opening -- I press the browser link, a white screen comes up, then a second later, bam, back to the home screen. Do it again and it comes up, with only one window, fetching the home page.

(2) Android IRC exits from server (remote host closed connection) when I try to use another application for more than a few seconds. This is very annoying. For example, if I'm connected to a server and then I switch to Messaging or Browser, a few seconds later I see the icon in the notification bar go from green (connected) to gray (idle / server closed). Not sure what's going on.

These may not be related to the build specifically, but I only started noticing them in the past week or so. I may go back to an older build to see.
[G1 Android Development] tnpapadakos:
jesusfreke to cyan on a tmobile g1 rooted

so my friend has a rooted g1 running jf 1.5

i'm gonna hook him up with cyan, amonra, ramhack and partition his sd

correct me if i'm wrong-i dont think he has a recovery boot mode in that thing, i tried earlier today and it got stuck on a screen with a ! and what looked like a phone laying flat.

1. flash amonra to his device using terminal emulator

2. then copy cyan to sd, and update any zip in recovery mode

3. then partition his sd with amonra

4. then do the ram hack

right? he's already rooted and his radio is updated to 2_22.19.26I, so i'm not gonna use drc83 defanged
[G1 Android Development] Chosen_on184:
still need to use the base rom before flashin cyan rom .....

oh yea also partion first

so 1. flash amonra

2. partion sd card

3. put drc83 and cyan zip files on card

4. flash drc83 first ( do not let it reboot ) hold home button to get back to recovery ...

5. flash cyan

6. If you have apps on the phone run fix_permissions in console

7. Reboot

8. Enjoy

5.
[G1 Android Development] tnpapadakos:
thanx alot worked great
[G1 Android Development] woodie:
Went from 4.2.9.1 to 4.2.12.2 today and my phone kept rebooting every few minutes, as well as general slowness trying to do anything at all. Reverted to my 4.2.9.1 nandroid backup and will try again next release.
[G1 Android Development] rubensun:
MT3G Camera Causes Reboot.

Hey Folks,

Wanted to see what I could do to help fix this bug.

Two out of three times I use my camera my cyanogen 4.2.12.2 mt3g reboots.

Is there a way to capture a log of what's causing the reboot?

R
[G1 Android Development] no6969el:
just to maybe help.. almost every issue Ive had has been resolved by wiping, flashing base rom and then cyans again on top. Fresh! Ever since we have been getting only a top layer update separate from the base rom the performance of the rom starts to degrade by the 1st or 2nd update you flash from there on out. Once I figure out how, im going to start combining the base rom + Cyanogens update and flash my phone with that. Im sure that it will make the full wipes and flashes down to a minimum.

Anyone feel free to test what I am claiming to see for yourself.
[G1 Android Development] tmhung:
I want to have the classic IM of andoid original rom ............. after i update Cyanogenmod rom ......... i don't have it . Please help me . Tk
[G1 Android Development] Janis:
There are links about 100 posts back in this very thread.
[G1 Android Development] SugarMouth:
4.2.12.2 After many many many force “home” closes, 12 second waits to return back to Home from web browser or market, major lag even with something as simple as scrolling through contacts… I un-rooted and went back to bone stock. Nice to have a phone that operates again.
[G1 Android Development] SugarMouth:
http://forums.t-mobile.com/t5/Opera...ficial-1-6-quot-Donut-quot-update/td-p/199763
[G1 Android Development] xtenpeben:
you will need 3 apk files to have those...

I don't have them, u can try and search the forums. or ask cyan.

and also, why were u having problems with 4.2.12.2? mine runs well, haven't had force closes on it... can u tell us what u did when u were rooting? was this ur first root? or u upgraded from cyan's old versions? or from other roms?
[G1 Android Development] _zygo_:
Yeah, not everyone can flash a ROM properly. Enjoy that.
[G1 Android Development] SugarMouth:
I rooted from Vanilla. Rooted exactly as instructed on Cyanwiki. Went straight to 4.2.11.1 then 12.2 and had force closes and sluggishness on both. Did 3 or 4 wipes / re installs with no success.
[G1 Android Development] halr9000:
There is a reason they call it the bleeding edge. :)
[G1 Android Development] SugarMouth:
If you feel I flashed my ROM improperly then you had better tell Steve you know better and you will re-write his Wiki page for him.
[G1 Android Development] djmasque:
I've also gone back to 4.2.9.1, mainly because I keep missing SMS notifications. I know this is on the to-fix list, but hopefully this previous version doesn't have the bug. I think 4.2.9.1 is overall faster than 4.2.12.2 as well.
[G1 Android Development] Infinite76:
i am curious. are you running a MT3G or a G1? i am running a MT3G and rooted my phone for the first time with 4.2.11. I had problems rooting it but once i got past that. i havent had issues with any of the final stable ROMs. I have gone as far as theme 4.2.12.2 and its still running fine.

the different issues people have intrigue me because the resolutions help me understand how the OS and phone are working.