yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] abobobilly:
[MENTION=3117667]pawitp[/MENTION]! If i wanted to test this ROM with AVD (Android Virtual Device), can I do it?

I mean i can get an AVD up & running with my i9000's specs, but i can't figure out how to test a custom ROM (which ever i want) with it.
[Galaxy S I9000 Android Development] freakymod2120:
DocumentsUI.apk

What is the app "DocumentsUI" for??? I see this app ,but i have no icon or something in the drawer, how - when will it be used ???

Thanks
[Galaxy S I9000 Android Development] pawitp:
No. You need a special build of CM for the emulator if you want to run it on the emulator. You can't just take a built meant to run on a device and run it on the emulator. (You may be able to configure the CPU, memory, but your emulator will never emulate the s5pc110 board the ROM expects.)
[Galaxy S I9000 Android Development] abobobilly:
HAHA. Thanks for the reply.

Looks like i will have to flash it anyway :D

By the way, i saw a picture somewhere (may be in this thread) ... isn't this ROM using Latest Dialer app? Just wondering.

Apologies for too many questions. Busy days lately :)
[Galaxy S I9000 Android Development] xandas:
Hi pawitp. Me and some other reported that we can't flash any other ROM lower than 4.
[Galaxy S I9000 Android Development] sbnaul:
Hello pawitp...

If you enable vibrate on answer from dialer > settings, it tends to vibrate at many instances while the call is being made instead of just vibrating on answer...

Don't kwn if its a bug or if its like that only in 4.4... here is the bug format though...

What is your--

Phone model: i9000

Radio (baseband): XXJVU

CM version: 20131115-UNOFFICIAL

CM Download url: http://d-h.st/LGN

Gapps version: gapps-kk-20131113

Did you--

wipe: Yes

restore with titanium backup: No

reboot after having the issue: Yes

Are you using--

a task killer:

a non-stock kernel: No

CMSettings/Performance settings (other than stock): Stock

ART Runtime: Dalvik

other modifications: SuperSu

Other info : the log is just after reboot go to dialer and enable vibrate on answer... Pick call... Disconnect...
[Galaxy S I9000 Android Development] jeroendj2:
it redirects me to recovery automatically ty, can flash again -.-
[Galaxy S I9000 Android Development] mamkarah:
yes I had the same problem, I'm going back me to too nightly 20140928
[Galaxy S I9000 Android Development] sanguinesaintly:
Glad to know it's not just me - anyone know what's happening here ?
[Galaxy S I9000 Android Development] pawitp:
If there is no accurate measurement available from Samsung, I would prefer not to list it at all due to the possible legal consequences.
[Galaxy S I9000 Android Development] nexzor:
produce a logcat, i would bet pawitp will see somthing in it
[Galaxy S I9000 Android Development] sanguinesaintly:
Happening on Nexus 5 and Moto G apparently
[Galaxy S I9000 Android Development] nexzor:
steve patched it http://review.cyanogenmod.org/#/c/74279/
[Galaxy S I9000 Android Development] AndroidBR:
So, is it fixed already on today's (September 30th) nightly or do we have to wait until it's merged on tomorrow's nightly?
[Galaxy S I9000 Android Development] sanguinesaintly:
It was today's (30th) nightly that caused the problem. Should be fixed tomorrow I guess ...
[Galaxy S I9000 Android Development] tomasso32:
My experience exactly the same. Tom.
[Galaxy S I9000 Android Development] devloz:
Specific Absorption Rate?

[MENTION=3117667]pawitp[/MENTION]

Okay, i found that I9000 maximum recorded recorded SAR is 0,268 W/kg (where it is relative smaller during normal use). Still not found separate for head and body, but i noticed on Gerrit, that people are putting the same value into head and body. They are taking SAR from Samsung manual too.

Link:

http://downloadcenter.samsung.com/content/UM/201106/20110604091351181/GT-I9000_UM_T-Mobile_Eng_Rev.1.0_110526_Screen.pdf
[Galaxy S I9000 Android Development] tetakpatak:
This is an awsome command.

:)

Is following command correct to revert this back?

adb shell setprop persist.sys.usb.config mass_storage,adb

tetakpatalked from the legendary i9000
[Galaxy S I9000 Android Development] sanguinesaintly:
Latest nightly

All thanks to Steve Kondik for his speedy response in sorting out the systemui issue with the nightly of the 30th. All is now well with 20141001 .
[Galaxy S I9000 Android Development] pawitp:
Thanks for the source. I'll ask around with other CM members for comments.

EDIT: A CM project lead suggested that the value not be added. (It's only intended for the One Plus One, which needs the information displayed to get imported to some countries.) My opinion is also that it serves no practical purpose. Most users won't be interested, and those interested will be able to source it from the manual anyway.

Yes, though if your screen is not broken, setting it in Settings -> Storage -> USB computer connection is easier ;)
[Galaxy S I9000 Android Development] CatalystWon:
If you google "sar rating" you will find lots of info. Try this one:

Why Samsung Cell Phones Are Rated The Lowest Radiation Cell Phones

Be reminded (U.S.) Verizon Wireless, Sprint Nextel are CDMA not GSM. Looks like i(fry your brain)Phone is among the worst.
[Galaxy S I9000 Android Development] Wogz:
is cyandelta broken for everyone? even after flashing the full rom from a few days ago and cyandelta still complains the the delta has failed.
[Galaxy S I9000 Android Development] tetakpatak:
Wonderful article, TY

The phone I'm writing on right now has 0.17W/kg :D

tetakpatalked from N7100
[Galaxy S I9000 Android Development] pitelasssss:
Cant acess superuser settings, forced closed on last nightly
[Galaxy S I9000 Android Development] devloz:
Same problem here, tried with wipe, didn't worked :(

BTW: Anyone know if phone can keep restarting because of near-the-death battery? My one is so damaged, so I can feel smell of this battery [is it dangerous too?].
[Galaxy S I9000 Android Development] pawitp:
Logcat, bug report format
[Galaxy S I9000 Android Development] nameh:
Hello,

I am currently on the latest monthly and am getting Camera has stopped working error message every second time I try to record a video.

Every second attempt of recording leads to the above error. The weird thing is that the "second" try happens every time, no matter if you record a 2 seconds video or a 4 minutes video.

Can anyone else replicate this issue?

Thank you
[Galaxy S I9000 Android Development] nexzor:
temporary fix is to change your language to english! it should be patched in 20141005 by this http://review.cyanogenmod.org/#/c/74572/
[Galaxy S I9000 Android Development] sanguinesaintly:
Superuser settings FC

Anyone else getting this, on both 20141004 and 05 ?
[Galaxy S I9000 Android Development] devloz:
Look one page back. This problem is already noticed.
[Galaxy S I9000 Android Development] nightwing90:
A little help required

Currently I'm on CM 10.0 with stock kernel and I'm planning to upgrade to CM 11. I already followed the instruction from OP to install the rom.

- Upgrading from CM10/10.1?

Do a Nandroid Backup!

Install the ROM from internal sdcard using ClockworkMod Recovery

You will finally see a "set_metadata_recursive" status 7 error. That is normal.

Reboot back into recovery (the reboot is required)

Install the ROM again from internal sdcard using ClockworkMod Recovery

Optionally restore /data from Nandroid Backup (the update will wipe your /data)

Optionally install the Google Addon

But every time when I tried to flash the file I'm getting "set_metadata_recursive" status 7 error. even after when I reboot back into recovery from CWM :crying: So what to do for installing CM 11 ?? :rolleyes:
[Galaxy S I9000 Android Development] pawitp:
But no one has yet posted any logcat.

Strange. Can you upload recovery logs? Get it from /tmp/recovery.log via adb right after seeing the status 7 error (while you are still in recovery).

The easiest alternative way to get to CM11 would be to Odin a stock ROM and flash CM11 straight from 2.3.
[Galaxy S I9000 Android Development] iKillCypher:
Flashing From 2.3 -> CM11 causes IMEI Number Lost and Baseband Unknown

http://xdaforums.com/showpost.php?p=55360831&postcount=6
[Galaxy S I9000 Android Development] pawitp:
The last time I've tried it, it works fine. If anyone is having problem, please file a bug report and include *.log files present in /sdcard/ after the install.
[Galaxy S I9000 Android Development] tetakpatak:
It is strange pawitp, but upgrade from GB to KK on some devices really corrupts IMEI (I suppose it only unmounts /efs but didn't have enough opportunity to check) while on other devices- it doesn't.

CM10.2 as step between 2.3 and CM11 seems to work good in general. IDK why.

tetakpatalked from Nexus 7 flo
[Galaxy S I9000 Android Development] ElmirBuljubasic:
This is a Slimkat bug, cyanogenmod if fine to flash from 2.3.6
[Galaxy S I9000 Android Development] iKillCypher:
I just tested it as of yesterday,if you don't believe me be my guest from what I know it is corrupting EFS folder and no matter what you do it is as good as dead
[Galaxy S I9000 Android Development] tetakpatak:
Yes, but also SlimBean had the same problem, especially the final version. Weird, as SlimRoms are also CM based.

tetakpatalked from N7100
[Galaxy S I9000 Android Development] legend_wok:
What is your--

Phone model: i9000

Radio (baseband): XXJVU

CM version: 20141004-NIGHTLY

CM Download url: CM updater

Gapps version: --

Did you--

wipe: no

restore with titanium backup: no

reboot after having the issue: yes

Are you using--

a task killer: no

a non-stock kernel: no

CMSettings/Performance settings (other than stock): no

ART Runtime: no

other modifications: no

Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:

Go to Settings --> Superuser --> Settings

There is a screen saying that the application has ended.

The problem has not occurred with 20140927-NIGHTLY, but I cannot say with which nightly the problem started.

Logcat attached.
[Galaxy S I9000 Android Development] Wogz:
My ROM was running so slow It was almost unusable it turns out it was low on phone memory card.. After moving many apps to the SDcard the performance improved so much it feels a brand new phone.
[Galaxy S I9000 Android Development] pawitp:
Can you please provide logs? If you've just flashed the .zip (without flashing any other CM zips afterward), then the logs (cyanogenmod_bml.log and cyanogenmod_mtd.log) should still be in your /sdcard.

The CM installer also does not touch the original EFS folder. When coming from Gingerbread, it copies the EFS files into another location which can be accessed by CM, but the files in the original location are not modified.

Should be fixed in the next nightly according to the change log http://review.cyanogenmod.org/#/c/74595/.
[Galaxy S I9000 Android Development] dk147in:
Hello guys,

i have just bought a new sony xperia E3 dual sim mobile.... it is very good mobile in low budget from brand like SONY.....

since new to using its stock rom and other stocks only...where I am missing some CM features that i used to enjoy in my SGS like

Daydream with clock..

cLock - lockscreen widget with weather and calendar... (missing it very much)

trebuchet and other CM stuffs

can anybody please tell me if this can be used in other android phone.. like sony xperia E3 dual

thanks
[Galaxy S I9000 Android Development] pitelasssss:
Everything is fine on last nightly.

Is there a reason to the phone getting slow when wifi is on? Durring the navigation , etc...
[Galaxy S I9000 Android Development] :
M11 snapshot

hi [MENTION=3117667]pawitp[/MENTION], I see that M11 builds are rolling out. When was this branched and which the safest nightly on which M11 can be flashed. FYI, I'm on 20141001-nightly. Thanks.
[Galaxy S I9000 Android Development] pawitp:
Read the notice on CM website.

http://www.cyanogenmod.org/blog/cyanogenmod-11-0-m11
[Galaxy S I9000 Android Development] :
Thanks! I usually follow official blog. I had posted this and had flashed M11 before the blog was published. :) Didn't face any issues after flashing M11 over 20141001 nightly.
[Galaxy S I9000 Android Development] gverma1:
For weather and calendar use Transparent Weather Clock. My N5 with kitkat has daydream in Settings->Display. Maybe xperia also has it.
[Galaxy S I9000 Android Development] tomasso32:
High Battery use 20141007

Went down about 20% per hour, till flat. No usage. Will revert to my previous install (20141005).

Tom.
[Galaxy S I9000 Android Development] andmail:
M11

1% per hour

latest GAPPs http://xdaforums.com/showthread.php?t=2397942
[Galaxy S I9000 Android Development] tomasso32:
That's typically what I get, 1% to 2% per hour. Testing 20141005 now.
[Galaxy S I9000 Android Development] iKillCypher:
I flashed CM9 same issue no baseband it becomes unknown further investigation reveal that efs does not matched the one I backed up at all it is quite odd.. :(
[Galaxy S I9000 Android Development] pawitp:
Without logs, I cannot know what happened and thus cannot fix it.

What do you mean by does not match? Some files are missing? Or the md5 of some files are incorrect? Note that the Samsung modem does modify some EFS files when they run, so the md5 might not always match an old backup.
[Galaxy S I9000 Android Development] iKillCypher:
well let me try to explain I did a EFS backup before flashing like someone suggested I flashed CM9 so that I wont lose IMEI and Baseband but it does not work so does the hardware keys and baseband was reflected as unknown despite I attempt to restore the backup md5 via EFS Professional 1.xx there is still no signal and imei number appears empty(not null) just a pop up with imei empty, no idea if the phone was hacked to unlock etc but I remember back in samsung galaxy s2 days I used to change alot of roms and never had this issue before..

when I got the phone it came with CWM 3.xx recovery with lidroid 1.2 ROM everything works fine but just for some reason flashing cm causes the baseband to be unknown.. the phone seems to be render useless. :( can you check with others cause it seems like a known issue according to various posting on the forums.
[Galaxy S I9000 Android Development] pawitp:
As I don't have the free time to read every ROM posts, if I don't get logs/bug reports in this thread, I won't know about it.

Does flashing the stock firmware fix your issue? CM does not modify the original EFS data store. If flashing back to stock does not solve your issue, then I'm pretty much sure that it's not CM-related. All instances of IMEI-lost on CM that I've seen can be fixed by flashing back to stock.

Also, AFAIK, lost IMEI will not result in "baseband unknown". Baseband unknown is most often caused by a corrupted modem file, which is caused by using Odin to flash a modem. Flashing a modem using Odin is not supported when using CM due to different partition. This can be fixed simply by manually copying a valid modem.bin to /radio/modem.bin, flashing a CM-compatible modem zip, or reverting to stock and flashing CM again (which will install a fresh copy of modem.bin).

If you want to look at your case, do the following:

- Follow the bug report on the first page

- Attach the two requested installation log

- Try flashing a CM-compatible radio zip (an Indian radio should be available from this thread a few pages ago)

- Check the md5 of /radio/modem.bin on your device, and check if it matches the one in the .zip you've downloaded

- Right after booting, get a kernel log (adb root; adb shell > dmesg.txt)

- Get a radio log (adb logcat -b radio > log_radio.txt)

If not, unless someone else file a report proving that there is an issue with the CM Installer, please do not scare new users from following the instruction of installing CM11 straight from stock 2.3. I've tested the installer when I last modified it and there was no issue.
[Galaxy S I9000 Android Development] diaboliku123:
Hi.

I'm currently using your latest CM11 Nightly build with the latest MacKay Kernal version on interactive guvernor and I'd like to know if there are any settings I can do to increase my S1's performance even further. I'm open to any tips & tricks.

Thanks.
[Galaxy S I9000 Android Development] iKillCypher:
sorry for the late reply

the phone is strange is came with a modified ROM call lidroid 1.2 seems It is rooted and has a CWM of 3.XX

I have attached all the logs as needed here

http://pastebin.com/Krt9TRTA SYSTEM,KERNEL,RADIO

maybe this should have a clear pic on why flashing stock cause baseband to unknown and imei disappearing

also this was how the phone I got it I never rooted it etc it came pre-rooted with lidroid rom etc my guess but it has been packaged properly my guess it has been sent to someone in china to modified no idea what has been done to the phone but I sure feel unsafe using it would really love to get Cyanogenmod on it

tell me what else you need and this is already the fourth phone that was replaced and keeps coming back with the same ****ty rom
[Galaxy S I9000 Android Development] pawitp:
Please read my post carefully on what logs I'm requesting. I need the logs on CM, not on stock.

I would suggest you try installing a stock ROM with Odin first to see if the baseband/IMEI is lost or not. If the baseband/IMEI is lost simply by flashing a stock ROM, then it's due to some modifications to the phone and not due to CM (and I can't help you with that).

If, after Odining a stock ROM, the phone still works fine, install CM strictly following the instruction on the first post (using the linked recovery, not the recovery that comes with your phone).

If after installing CM, you've lost your baseband/IMEI, then post the following logs (see previous posts for details):

- /sdcard/cyanogenmod_bml.log

- /sdcard/cyanogenmod_mtd.log

- Logcat (right after boot)

- Radio logcat

- dmesg
[Galaxy S I9000 Android Development] iKillCypher:
yeah I will do it after I get my xperia z back from servicing the button was faulty well it lasted almost 1 year 3 months what more can I ask :D will let you know maybe next week or soon
[Galaxy S I9000 Android Development] Ramnathe P:
[MENTION=3117667]pawitp[/MENTION]

you are such a brilliant dev

please give a solution to turn off capacitive button backight permanently. to disable it from glowing whenever i touch it
[Galaxy S I9000 Android Development] ryanmat:
Hello SGS community, I've come across a new annoying glitch in the stock messaging app and was wondering if anyone else could reproduce it. I'll try to get a logcat, but it happens randomly, so I can't make it happen consistently. Also, I'm on stock CM11 no tweaks, etc.

Scenario:

1) I have the automatically delete messages button checked in the messaging app settings so that after 10000 SMS and 1000 MMS old messages are deleted.

2) Have over 10000 SMS in one conversation.

3) Send a message to that contact.

4) Messaging app force closes and shuts down, sends the message, then when it restarts sends the same message again, so my contact always gets a double message.

Not sure if it has to do with the messaging memory, or the deletion of old messages, I tried the same thing using Handcent and everything worked without an issue. Any help would be appreciated. Thanks all!
[Galaxy S I9000 Android Development] iKillCypher:
never knew certain stuff like this existed well [MENTION=3117667]pawitp[/MENTION] hopefully now you can add a warning to front of your page regrading this

http://xdaforums.com/showthread.php?t=1890667

http://xdaforums.com/showthread.php?t=2573023

thanks

now I know why is this happening on EFS issue etc cause the phone was never GT-I9000 to begin with... terrible
[Galaxy S I9000 Android Development] pawitp:
It's not really the job of this thread to warn about any possible scams, but thanks for the information.
[Galaxy S I9000 Android Development] iKillCypher:
also I did a further investigation and I did flashed back to stock aka how the phone was meant to be SHW M110S firmware do you think it is possible to port CM11 over to this device ? since it is just a carbon copy
[Galaxy S I9000 Android Development] pawitp:
Yes, but as I don't own a device (and have no interest), I won't be doing it. There are probably unofficial CM ROMs for it if you search around.
[Galaxy S I9000 Android Development] jaheshkhan:
CM 11 directly from gingerbread 2.3.3 with CWM 2.5.1.2 failed !!!!!

It is to inform you that you will not be able to install galaxy s gingerbread 2.3.3 to CM1 1 with CWM 2.5.1.2 .

I tried all the the things that mentioned.

Details of my phone is as shown:

Galaxy S GT-I9000

Model No: GT-I9000

Firmware version: 2.3.3

Baseband verion: I9000JXJV6

Kernal version: 2.6.35.7-I9000JPJV6-CL233266 mobilus@MEA-03 #4

Buildnumber: GINGERBREAD.JPJV6

So i think we need to move 2.3.3 to CM 10 or CM9.

I dont know which one will be better to flash.

After flashing i faced the problem mentioned in this forum.

http://forum.cyanogenmod.org/topic/61946-eerror-in-mntsdcardcm-1000-galaxysmtdzip-status-0/

but after restarting as mentioned in the forum it went infinite loop. i didnt do the Mounts and storage -> format /System -> Yes - format"

so in this forum person faced problem with CM 10. so Ill try CM 9 and then ill move to CM 11.

10 or 9?
[Galaxy S I9000 Android Development] pitelasssss:
Install stock rom, install cwm recovery ( root ) and then install cm 10.2. After this install cm11
[Galaxy S I9000 Android Development] jaheshkhan:
but person mentioned in that forum already faced problem with CWM 2.5.1.2 with official samsung stock rom 2.3.3 ? so do you think 10.2 will work in my case?
[Galaxy S I9000 Android Development] pawitp:
If you're using "CWM 2.5.12", then you obviously haven't tried everything mentioned. ;)

Use the recovery linked in the first post, if my memory serves correctly, it should be CWM 5.x. Then you should be able to flash CM11 directly.
[Galaxy S I9000 Android Development] tetakpatak:
No, it is not possible. M110S has locked bootloader, unlike the i9000.

Regarding EFS backup: nearly every sticky thread in Help & troubleshooting section for i9000 explains all you need to know about flashing.

Unlike help threads, this is a development thread and its main objective is ROM development, bug reports etc.

tetakpatalked from N7100
[Galaxy S I9000 Android Development] jaheshkhan:
For your information i already flashed back to samsung stock ROM. and rooted now.

I have ROM MANAGER when i select the option " install ROM from sd card" it says ROM Manager is unable to open this file. please remove spaces from your file and folder path. or run it manually vial clockworkmod recovery."

I tried CM7 to CM11 for ROM MAnager.

but ended up with above Rom manager message

Any way i going to try with CM 10.2 as you said.

Pray for me...
[Galaxy S I9000 Android Development] pawitp:
Please provide complete and accurate information.

You said that you were on CWM 2.5.12, in which case you're not using the recommended recovery. The recommended recovery needs to be installed via Odin (comes with the Semaphore kernel). So what recovery are you on?

The instruction also states that you should install the ROM straight from the recovery booted up from the 3-button combo, not via ROM Manager.

I can only help you if you are strictly following the instruction.
[Galaxy S I9000 Android Development] jaheshkhan:
May be im making mistake.

I installed ROM Manager premium. but i didnt flash semaphore kernal.

im then using ROM manager flashed CWM 2.5.1.2. So do I need to semphore kernal using odin?

the link for semophore is not working also. there is no file in it.
[Galaxy S I9000 Android Development] pawitp:
Use this link http://www.semaphore.gr/kernels/Semaphore_2.7.4.tar.

Unlike other devices, you cannot use ROM Manager to install.

Either follow the tutorial on CM Wiki (http://wiki.cyanogenmod.org/w/Install_CM_for_galaxysmtd) or other tutorials on the forum.

This is a development thread, and I will only make further replies if there is actually a bug in the installation process (The install fails even when strictly following the instruction). I do not have the time to aid everyone through the installation process (of course, others are free to help.)