yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] RalphUp:
hi Pawitp, stupid me I flashed both mine with the 20140510 I have heimdall and the boot.img you posted please can you someone guide me to recover these two handsets...

I tried command > heimdall flash --kernel boot.img

but I get:

Session begun.

Downloading device's PIT file...

PIT file download successful.

ERROR: Partition "kernel" does not exist in the specified PIT.

Ending session...

Rebooting device...

Releasing device interface...
[Galaxy S I9000 Android Development] DerRomtester:
Have you installed the libusb driver?

This may work:

heimdall flash --KERNEL boot.img --no-reboot
[Galaxy S I9000 Android Development] RalphUp:
Thanks DerRomtester both i9000's back up and running! you are a LIFE SAVER!! ;)

NOTE TO SELF... Check here before firing up new nightly

2nd NOTE TO SELF... Dont do both handsets at same time!
[Galaxy S I9000 Android Development] pawitp:
Sorry I just saw your logcat. Next time, please post any update as a new reply because I rarely check old posts for edits.

- Please get a dmesg together with the logcat

- Is there an app which causes this to happen often?

- Can you try restoring your apps one by one? When does this problem start to occur? (e.g. doesn't occur without apps installed, started to occur after 20 apps restored, started to occur when a specific app is restored, etc.)
[Galaxy S I9000 Android Development] ST3MC:
Hi Pawitp i recently flashed snapshot M6 and i have a problem with the camera app that problem also existed to me in a nightly prior to m6 but only happened after awhile

Freash install, wipe system also

When i try to open the camera app it says "unfortunately ,camera has stopped."

I want to post a logcat so i downloaded the app aLogcat but wonder on what settings i should post it?
[Galaxy S I9000 Android Development] evilspawnas:
Thanks you both saved my day... my phone is back to life :D
[Galaxy S I9000 Android Development] pawitp:
I've never used the app so I don't know (I normally take logs via adb). Just take it and post it, I'll tell you if it's okay or not. (But before that, try clearing the data of your camera app)
[Galaxy S I9000 Android Development] idCyber:
1. How can I get a dmesg at the same time with the logcat? From PC, using adb commands I can only do a command like "adb logcat > name.txt" at a time. Can't do "adb shell dmesg > storage/sdcard0/name.txt" at the same time with logcat (I've seen this command on the net, haven't tried it, maybe it's not correct for dmesg). Can u explain how to get them and in what order? Or how to get a proper dmesg what is the command?

2. No "special app" . It can be triggered by exiting a game, an app, a call, or sometimes when in an app and pulling the statusbar. Example : I can be in Angry Birds , exit the app using back key or pressing the home key and then pulling the status bar ; I can be in Tapatalk or Youtube browsing and I can go back to homescreen and pull down the status bar ; or during or after ending a call and pulling the status bar.

3. I will try with no apps restored tomorrow when I get a bit of time when I don't need my phone to receive time for a while.
[Galaxy S I9000 Android Development] joaogalvao89:
Ah ok had not noticed. how can I send logcat?
[Galaxy S I9000 Android Development] idCyber:
get a logcat in a txt file and post it here or post the content of the logcat on pastebin.com and share it here.
[Galaxy S I9000 Android Development] pawitp:
You can get the dmesg after you get the logcat. (dmesg command's output is not continuous)
[Galaxy S I9000 Android Development] idCyber:
ohh ok. so "adb shell dmesg > storage/sdcard0/name.txt" is correct right? I've seen on the net that it can't be saved on the pc and only to the phone's storage.
[Galaxy S I9000 Android Development] pawitp:
If you're using adb on your computer, you can save the file on the computer all right. Just do it like you do the logcat. (Make sure you run "adb root" before though)
[Galaxy S I9000 Android Development] idCyber:
ok. ty, will report back tomorrow when I flash a recent nightly
[Galaxy S I9000 Android Development] ST3MC:
Already tried cleaning the data aswell the gallery data but no go

Heres a couple od screens on different settings

(Im on the phone and dont know how to attach a file)

Hioe this helps
[Galaxy S I9000 Android Development] pawitp:
You need to run the logcat as root (I can't help you there, if you were to ask me, I'd recommend adb on a computer) and attach the log as a text file. If you don't know how to attach a file, you should find out how to.
[Galaxy S I9000 Android Development] ST3MC:
hope this helps
[Galaxy S I9000 Android Development] geckoas:
com.android.systemui was stopped

Hello Pawitp,

i also had the chance to get a logcat and dmesg (see enclosed) after my phone rebooted and showed "The process "com.android.systemui" was stopped"

Actions before the reboot:

- Browsing with Next Browser to a site with a linked pdf document.

- selected the pdf dokument to view it.

- A popup window occured to confirm the download was shown.

- After confirmation of the download the screen got black with the statusbar remaining light.

- As after a several seconds nothing happend, I pressed the home button.

--> soft reboot

- After the reboot --> "The process "com.android.systemui" was stopped"

- If I press "OK" the message returns again and again.

- As long as the screen is on I can select "Reboot" by longer pressing the On-Key.

- When the screen gets of it can only be rebooted by long pressing the ON-Key.

I hope this information helps you to find a solution.

Thanks for your great work.
[Galaxy S I9000 Android Development] pawitp:
Does third party camera apps work?

Thank you for the logcat, but what nightly are you using? Next time, please use the bug report format in the first post to make sure all the relevant information is provided.
[Galaxy S I9000 Android Development] ST3MC:
One app works out of three i downloaded

While the other 2 open and show image they say the sd card is full however its not
[Galaxy S I9000 Android Development] pawitp:
Strange. What are does apps? Can you get logcats?

Also, have you ever tried a full data wipe? Something must be quite wrong if apps are reporting sdcard as full when they aren't.
[Galaxy S I9000 Android Development] geckoas:
Sorry for that. Here are the missing informations:

What is your

Phone model: I9000

Radio (baseband): I9000XXJVT

CM version: 11-20140503-Nightly-galaxysmtd

CM Download url: CM download site

Gapps version: 2014-01-05

Did you

wipe: Yes. And built up from stock 2.3.6 XXJVU

restore with titanium backup: Yes. User apps and -data

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: Nova launcher. Launcher background from gallery

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

Systemui was stopped. See above post with logcats.

sent from my galaxy I9000 running CM11 with tapatalk
[Galaxy S I9000 Android Development] marcedli:
pawitp FYI

since 10th of April all cm nightly and snapshots have this systemui crash/no response, freeze and ui 'reboot' to lockscreen (considered as memory leak) bug on gt-I9300 as well.

They say it's caused by the new theme engine.

You can check in the sgs3 nightly thread, the last some hundred posts are about this issue.

Tapatalk-kal küldve az én GT-I9300-el
[Galaxy S I9000 Android Development] pawitp:
How often does it happen? The system appears to be in a strange state because many processes were killed. If the original problem which lead to the processes being kill was fixed, this would probably be fixed it.

I also think it's from the theme engine. The system's definitely low on memory, but I don't see SystemUI using much memory either (in the logs).

What I'm looking for now is a way to reproduce the problem. If anyone has instruction how to go from a fresh wipe to constantly having the issue, it'd greatly help.

Also see https://jira.cyanogenmod.org/browse/CYAN-4047. It seems like someone else has started working on it, so I'll wait and see for a bit. (Though issue reproduction instructions are still welcomed).
[Galaxy S I9000 Android Development] tomasso32:
M6->M5

Went back to M5 from M6. FC every day or two. Tom.
[Galaxy S I9000 Android Development] idCyber:
Don't want to say anything rude but CM team knows since it was implemented that the new Theme Engine is the fault of SystemUI crashes and refuses to revert it. The CM 11 ROM had a working liver and CM introduced cancer to it and it doesn't want to remove and cure it. CM 11 is my favorite ROM and but I am disappointed now and a bit mad because people are stubborn. I am sticking with M5 or other ROMs based on other sources until this is fixed.

For CM Team: If after whole month you can't make the new ThemeEngine work properly with the SystemUI , then remove it ! Don't release M6 making people think it's a more stable release when it's not. This is the Highest Priority : stable system and because of UI crash, it's not !

CM 11 cannot be considered a stable ROM or base beyond M5 or the nightly when the old ThemeEngine was replaced.

Attempts were made to revert it until it was fixed and better implemented, they were denied even if it's making the SystemUI crash. http://review.cyanogenmod.org/#/c/62366/

Ty pawitp for trying to find a way to fix it, hope you succeed.
[Galaxy S I9000 Android Development] pawitp:
No one except me reads this thread, if you want to complain to other CM members, please use a different channel.

Though IMO, the only real fault is releasing M6 with the bug (and to be fair, it only visibly occurs on low memory devices and I still can't reproduce it). In your link, "Markus Menzel" who posted a rude comment is just a random commenter and is not affiliated with CM in anyway. Of course, the way to fix bugs is not to revert but to fix things properly. Reverting one random patch not only may not fix the issue, but also cause other things to break. On JIRA, you can see that Clark, the author of the new theme engine and a Cyngyn employee, is looking at the bug and is trying to fix it.
[Galaxy S I9000 Android Development] tomasso32:
Not an auditable trail, but as simple as uninstalling facebook, then tried to re-install, got " insufficient storage available" error, not much later a forced close. [I had done almost nothing with M6. Even restored apps via titanium backup after five or so days].

Tom.
[Galaxy S I9000 Android Development] nexzor:
as addiion to the systemUI crash. had it last night on nexus 5 and galaxyS after killing the facebook app by longpressing the back button.

so it realy semes to be verry random
[Galaxy S I9000 Android Development] Onliner09:
I am running M6 since its release, I noticed no severe issues or FCs until now, all stable and fine.

Thanks and regards, Onliner09

Gesendet von meinem GT-N8010 mit Tapatalk
[Galaxy S I9000 Android Development] kiro67:
Is any way to set transparent statusbar in this rom? Black statusbar is so boring for me :P
[Galaxy S I9000 Android Development] zakitheracer:
Performance>Enable high end gfx
[Galaxy S I9000 Android Development] kiro67:
I haven't got "performance" in settings. I'm using latest working version-05.08.14
[Galaxy S I9000 Android Development] AreXe:
Go to Settings -> About Phone and click 7 times on Build Numer. Then in Settings Menu new options will appear - Developer options and Performance.

EDIT:

Dunno which kernel support those high frequencies, you can check yourself, but for instance Neo kernel support 1320 MHz - and I think that's enough for this phone...
[Galaxy S I9000 Android Development] kiro67:
heh good trick. Now i have transparent statusbar. I have one more question-how to overclock cpu over 1200mhz? Example 1500mhz like on glitch kernel. Is any kernel for kit kat that support frequency over 1200mhz?
[Galaxy S I9000 Android Development] idCyber:
Mackay Kernel supports up to 1400 MHz
[Galaxy S I9000 Android Development] kiro67:
I have random reboots on 1200mhz and up ehh ;/
[Galaxy S I9000 Android Development] idCyber:
that's because of the voltages used for each step of the OC . Every phone is different in a way and only specific voltages are stable when you OC. For example : in Mackay Kernel , with Stock Voltages, I can't OC stable not even at 1100 MHz ... but after I play a bit with the voltages (ok it takes a long time of testing with reboots) , I can get up to 1400 MHz stable (played Asphalt 8 for half an hour with Medium Graphics and my phone did not reboot)

Sorry for the offtopic pawitp.
[Galaxy S I9000 Android Development] devloz:
Hey guys, i want to ask about "force High-end graphics" options.

Why we have it unmarked, when (at least) i don't notice any performance decrease with this option enabled? Additionaly, i noticed statusbar transition slower with completely black background than with grey (when changing statusbar notifications/toggles). I believe you're right with disabling it, but i don't understand why.

Best regards.

PS: If wrong thread, then sorry (members #UP# inspired me to ask).
[Galaxy S I9000 Android Development] pawitp:
High end graphic has higher RAM usage, so it's off by default for low-ram devices.
[Galaxy S I9000 Android Development] nexzor:
here is a commit for a temporarry fix.

in the comments are steps to reproduce the bug http://review.cyanogenmod.org/#/c/63034/

this commit seems to be relevant also http://review.cyanogenmod.org/#/c/63806/

sorry for not contrebuting more informations, but my knowledge is fare away from such things.
[Galaxy S I9000 Android Development] marcedli:
pawitp, it seems sort of fix appeared:

http://review.cyanogenmod.org/#/c/63806/

Tapatalk-kal küldve az én GT-I9300-el
[Galaxy S I9000 Android Development] geckoas:
System data reduced in /datadata

Hi Pawitp,

I found a way for me to reduce the size of System data in /datadata, at least temporary from before 120MB to now 45,5MB - see enclosed screenshot.

I uninstalled and reinstalled some of my frequent used apps, such as NTV, Next Browser, Idealo, Amazon Kindle, Tapatalk, Worldscope, Youtube, BBQ Log, Amazon, Tripadvisor.

With every uninstallation the size of System data in /datadata decreased significantly and stayed there after the installation and launch of the respective app.

Even such a small app as BBG Log (600kb) released tens of MB of System data.

It seems to me that memory blocks which were occupied by the app are not released when they are no more needed, and only uninstallation of the App does them release.

I ask you and others, who have the same System data issue, to give this a try and uninstall and reinstall frequent used apps.

By the way, I'm happy as a child that my OneNand is not physically damaged as you suggested.

:good::)

What is your<br />

Phone model: I9000<br />

Radio (baseband): I9000XXJVT<br />

CM version: 11-20140503-Nightly-galaxysmtd<br />

CM Download url: CM download site<br />

Gapps version: 2014-01-05<br />

Did you<br />

wipe: Yes. And built up from stock 2.3.6 XXJVU<br />

restore with titanium backup: Yes. User apps and -data<br />

reboot after having the issue: Yes<br />

<br />

Are you using<br />

a task killer: No<br />

a non-stock kernel: No<br />

CMSettings/Performance settings (other than stock): No<br />

ART Runtime: No<br />

other modifications: Nova launcher. Launcher background from gallery<br />
[Galaxy S I9000 Android Development] Samga:
[MENTION=3117667]pawitp[/MENTION]: do you know any reliable method to check for bad blocks?

I haven't found anything that would work on our ROM. I have 60 MB system data in datadata.
[Galaxy S I9000 Android Development] pawitp:
Strange. Well, if it doesn't balloon up to a very large size and goes down once in a while, then it's probably legit yaffs system data.

For the record, system data has nothing to do with Android, it's the space used by yaffs for wear leveling and bad-block marking.

If you perform a wipe of /datadata (erase_image datadata), blocks marked as bad will be printed to the console.
[Galaxy S I9000 Android Development] ST3MC:
i did a clean install when i flashed M6 including formatting system.

well here's a logcat that i o:)pened all camera apps 1 after 1 the last one was the one that worked i believe

the name of the app:

1.google camera- didn't work

2.camera ics - didn't work

3.HD camera ultra-worked

however all of a sudden the camera apps all work perfectly, i didn't change anything in the phone so i dont know what made it work all of a sudden but the problem aswell existed in previous nightlys so...

either way if you still want to try a figure out what was wrong i hope the logcat helps.

onto a different bug sometimes when i try to open the notification bar it freezes the phone for half a minute and then closes the app that was open (if i was running an app at the time) and usually restore the default wallpaper and sometimes reboots bootloader and then system keeps fc and forces me to reboot the phone.

i saw that other user's experience this aswell

to me the problem started in the last 2 nightlys prior to the release of M6.

anyways thanks for the help on the previous subject
[Galaxy S I9000 Android Development] AusMatt:
In my experience the first nightly that was unstable for me was the 4th of April.

I think I found the 2nd of April nightly to be stable but I no longer have a copy of that so I'm currently back on the 28th of March which is fine.

So I'd be looking at the 3rd or 4th of April nightlies to find out what changed.

P.S. I was testing on an I9000.

P.P.S. And yes I did reformat and wipe my SD card to try and get my device stable.
[Galaxy S I9000 Android Development] abobobilly:
I dirty flashed the latest Nightly (cm-11-20140512) over the Mackay 4.1.5 (Android 4.4.2) because of that notorious "Delay in Screen Lighting up while incoming call" ... but its still there.

I wanted to ask, if its because of Dirty Flash? Or is this issue still there?

If its just me facing this problem ... what would be the best way to solve it? I don't want to flash a new ROM because of too many apps, and because i am busy with my exams these days so can't spare enough time. But i am annoyed because that "delay" is becoming a major pain.
[Galaxy S I9000 Android Development] idCyber:
This is happening in all of the KitKat ROMs (Android 4.4.x) . Only way to stop having it, is to go lower than Android 4.4
[Galaxy S I9000 Android Development] abobobilly:
Thanks for the reply :) I waited for more than a month hoping a fix will be available, but apparently it isn't. Oh well, we can still hope for one. Can we? :confused:

------

Btw, i am also facing another strange problem. Somehow, i messed up the Google Services on my phone. I think when i flashed the CM ROM, it removed may apps including some of the Google Apps from "system/app" location. Now, i can't even add a Google Account in Settings.

Any idea what would be the reason of this? And if i can solve it?

EDIT: Wait a minute, I didn't flash "GApps" thinking there is no need for it. But i just found out that two apks are missing from the "system/apk" ... and i think those are causing the problem.

The missing files are:

GoogleContactsSyncAdapter.apk

GoogleCalendarSyncAdapter.apk

I'll install the latest GApps package and report back :)
[Galaxy S I9000 Android Development] cesar65:
I finally decided it is time for a new phone. Purchased an Xperia Z1 Compact. Great device! But I'm not gone completely. My wife now uses my SGS and I'll continue to maintain it. So I am also waiting for the systemui fix.

BTW, I today installed the CM nightly from 12th on the new Z1C (yes, I am already on CM) and incallui crashes persistently. I hope the SGS is unaffected.

Thanks Pawit for all your work so far!
[Galaxy S I9000 Android Development] abobobilly:
Congrats for your new device :) Enjoy

I have used many phones but i just can't stand the music quality of the Snapdragon DAC. For the price you pay for them, they sound horrible. And if you want that sound to become awesome, you need to invest in some uber expensive ear plugs. This is another reason i hate.

The only device which pleased me greatly with its sound quality, was the Galaxy S4 (i9500 Exynos variant), but now that S5 is here ... i am hoping for the Exynos variant to have Wolfson DAC ... i haven't checked if it does support it).

Anyway ... just felt like putting it out there :)
[Galaxy S I9000 Android Development] idCyber:
All devices are affected by this.
[Galaxy S I9000 Android Development] abobobilly:
FLAC files are not working. I have checked with Google Play Music. Is it normal?
[Galaxy S I9000 Android Development] Samga:
There are 3 bad blocks. Does anybody know the block size? What I've found was 256KB or 512KB.

Anyway the 60 MB system data can't be the 3 bad blocks.

My steps to check for bad blocks:

Boot to recovery

Backup data

Mounts and storage, Format /datadata

Show log

Restore data
[Galaxy S I9000 Android Development] geckoas:
The 3 bad blocks you saw after formating are really bad. The other 60 MB are as "bad" marked blocks which you backuped and restored again with your data. Only fresh Installation of apps from play solves this issue.

sent from my galaxy I9000 running CM11 with tapatalk
[Galaxy S I9000 Android Development] octolith:
For me, boot.txt in the filesystem root says something about bad blocks, but I'm not sure which partition, etc. What I'm trying to say is that you may not need this whole process to get that data.
[Galaxy S I9000 Android Development] tomasso32:
Could this be fixed by Settings/Apps/Move to SD Card, then Move to Phone?

T.
[Galaxy S I9000 Android Development] :
System UI crashes

Recently moved to M6 from M5. Phone has random soft reboots resulting in system ui crash. The wallpaper gets replaced by default wallpaper after reboot. Have to reboot phone to fix the issue.

Never had this issue in M5.

What is your--

Phone model: I9000

Radio (baseband): XXJVT

CM version: CM11 snapshot M6

CM Download url: get.cm

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): None

ART Runtime: No

other modifications: None

Logcat attached.

Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
[Galaxy S I9000 Android Development] geckoas:
" Merge "Avoid SystemUI crash due to NPE" into cm-11.0" is integrated in current nightly 2014.05.13.

You should give it a try.

sent from my galaxy I9000 running CM11 with tapatalk

---------- Post added at 07:27 AM ---------- Previous post was at 07:18 AM ----------

Please try it and report in this thread.

sent from my galaxy I9000 running CM11 with tapatalk
[Galaxy S I9000 Android Development] tomasso32:
I went back to M5, and too busy right now to go to M6 and have crashes.

[My M6 was fine for a few days then started crashing, then more frequent crashing].

Tom.
[Galaxy S I9000 Android Development] pawitp:
Downgrading without wiping does not always work and is not supported.
[Galaxy S I9000 Android Development] tetakpatak:
[MENTION=4795242]kiranbedre[/MENTION] try to format: system, cache, dalvik cache

And then flash rom and gapps
[Galaxy S I9000 Android Development] :
I think you misread my post. I didn't downgrade. Moved from M5 to M6. :)
[Galaxy S I9000 Android Development] pawitp:
In that case, it is a known issue from the new theme engine. See https://jira.cyanogenmod.org/browse/CYAN-4047
[Galaxy S I9000 Android Development] :
Thanks Pawit. I've added comments on JIRA as well.
[Galaxy S I9000 Android Development] DerRomtester:
[MENTION=3391555]pawt[/MENTION]ip is your kernel size commit conflicting with twrp?

Do you know that?

If not, i made some mistakes in my source code
[Galaxy S I9000 Android Development] pawitp:
I do not know how other recoveries are built and cannot provide any more help than this:

If the standard CM build procedure is used, then it should work without problem. If non-standard method of ramdisk integration is used, then it will need to be modified accordingly. The extension is changed from .img to .cpio, and the file is no longer gzipped.