Related
Hey dudes, just installed the teamhacksamsungs ICS rom which is AWESOME btw!
Now to the issue, since my menu hardware button is broken i've been using a app called ButtonRemapper which remapps the hardware buttons. It worked flawlessly on gingerbread roms, since it needs root access i need permissions from superuser, anyone knows how i could get it to work?
Sincerely..
EDIT: Superuser doesen't ask for permission in ICS but it does in Gingerbread.
This sounds like you have flashed the wrong kernel for your phone.
What model is your hardware? It may not yet be supported.
FAQ section of hacksung: http://forum.xda-developers.com/showthread.php?t=1363593
Is there a Captivate/Vibrant version?
A captivate build from the same source (but with captivate config) is available here. We currently lack a developer/maintainer for Vibrant.
Does this work for I9000B?
No, the I9000B requires a different kernel configuration. A build for I9000B may be added later in the process.
If you are infact on the right kernel, then suggest Odin flash to Ficeto's XXJVT base rom from the DarkyRom website (beta section), flash to CM7, then flash to ICS again.
Good luck.
I've got an i9000 international since i'm from sweden, any more suggestions?
build 10 has a bad version of su. There's a fix in the hacksung ics thread.
i had the similar problem when i flashed MyICS the menu button didnt work i just re-flashed and it started to work again
Okay, the menu button is broken, physically.
That's why i need it to work
Anyway, do you guys think i'm capeable using ICS without any home button?
meh.hajj said:
Okay, the menu button is broken, physically.
That's why i need it to work
Anyway, do you guys think i'm capeable using ICS without any home button?
Click to expand...
Click to collapse
There's a market app that emulates a home button with an overlay on screen button...can't recall the name of it though.
Only downside with a broken button is no three button recovery/download.
Hello guys,
I am brand new here,as after 3 years of owning a X8 i decided to jump to other ROM,because i was bored of the simple design of his menu and i was so frustrated to stay back with android market when my friends had messenger for facebook e.g.,i had to refresh again and again my opera..and much more apps and games i would like to play.So,i decided to start searching for new ROMs,and i found MIUI,but i wasnt able to find a stable version to dl for my phone.Then i found JB Mini Project,I succeeded on installing it on X8 but there is one thing that wont work in every version of JB i have tried!THE WI-FI!It is really frustrating for me!I am so begginner to those things,but i understand that its not only me that will have this problem and that developers might be working on it right now(I am 3D designer and i know about beta versions of things,even I have to release again and again my creation because of a bug),but i really hope someone had this problem too and found a fix on it..I tried a fix i found in forums with Titanium Backup,but nothing...
Anyone knows anything..just help me out with this.:crying:
Thanks in advance guys!:cyclops:
so noone knows nothing in here?thats sweet
SrSGr said:
so noone knows nothing in here?thats sweet
Click to expand...
Click to collapse
Patience my friend x)
What wifi problem do you have? Unable to detect Adhoc connection?
Have You tried this Kernel + Rom ? (All JB rom is unable to scan adhoc wifi. Except if you make changes to the source and compile it yourself)
If you want to surf the internet but with not using wifi and using a cable, This is a Post for you.
use back stock ROM (just kidding
CKKnot said:
Patience my friend x)
What wifi problem do you have? Unable to detect Adhoc connection?
Have You tried this Kernel + Rom ? (All JB rom is unable to scan adhoc wifi. Except if you make changes to the source and compile it yourself)
If you want to surf the internet but with not using wifi and using a cable, This is a Post for you.
Click to expand...
Click to collapse
Ok the problem is that i try to turn it on but it wont,the toggle bar just moves to be enabled,but it never gets enabled!It just goes back to off possition..With a few words,i cant enable Wi-Fi..So..as i said my friend,i am newbie here,so please try to explain me what i should do with those rom and kernel you send..should i go back to stock rom,reflash this kernel and install this rom?Is this the JB mini project too or something similar and stable without bugs?
Thanks in advance!
SrSGr said:
Ok the problem is that i try to turn it on but it wont,the toggle bar just moves to be enabled,but it never gets enabled!It just goes back to off possition..With little words,i cant enable Wi-Fi..So..as i said my friend,i am newbie here,so please try to explain me what i should do with those rom and kernel you send..should i go back to stock rom,reflash this kernel and install this rom?Is this the JB mini project too or something similar and stable without bugs?
Thanks in advance!
Click to expand...
Click to collapse
Maybe the rom + kernel combination is wrong or the rom is just being buggy.
I just personally liked nAa's work because he release a stable version of every product.
If you want to change into the recommended rom that I just told you;
1. Flash the latest kernel (06)
2. Follow instruction on the kernel post. (/system wipe at recovery before flashing a rom & etc)
3. Flash the rom. Followed by the GAPPS
4. As it said, this is my recommendation steps. I do not guarantee your satisfactory
CKKnot said:
Maybe the rom + kernel combination is wrong or the rom is just being buggy.
I just personally liked nAa's work because he release a stable version of every product.
If you want to change into the recommended rom that I just told you;
1. Flash the latest kernel (06)
2. Follow instruction on the kernel post. (/system wipe at recovery before flashing a rom & etc)
3. Flash the rom. Followed by the GAPPS
4. As it said, this is my recommendation steps. I do not guarantee your satisfactory
Click to expand...
Click to collapse
Thank you,I am gonna test it and I will keep you informed here soon!
EDIT:It works great!ignore my PM.I flashed kernel 5 not 6 and it works like a charm.Thanks a lot for helping me out!
SrSGr said:
Thank you,I am gonna test it and I will keep you informed here soon!
EDIT:It works great!ignore my PM.I flashed kernel 5 not 6 and it works like a charm.Thanks a lot for helping me out!
Click to expand...
Click to collapse
Replied. It because I forgot to mention that 06 has a little bit changes that will make normal jb rom that is not released pior to the kernel release data will not boot
SrSGr said:
Hello guys,
I am brand new here,as after 3 years of owning a X8 i decided to jump to other ROM,because i was bored of the simple design of his menu and i was so frustrated to stay back with android market when my friends had messenger for facebook e.g.,i had to refresh again and again my opera..and much more apps and games i would like to play.So,i decided to start searching for new ROMs,and i found MIUI,but i wasnt able to find a stable version to dl for my phone.Then i found JB Mini Project,I succeeded on installing it on X8 but there is one thing that wont work in every version of JB i have tried!THE WI-FI!It is really frustrating for me!I am so begginner to those things,but i understand that its not only me that will have this problem and that developers might be working on it right now(I am 3D designer and i know about beta versions of things,even I have to release again and again my creation because of a bug),but i really hope someone had this problem too and found a fix on it..I tried a fix i found in forums with Titanium Backup,but nothing...
Anyone knows anything..just help me out with this.:crying:
Thanks in advance guys!:cyclops:
Click to expand...
Click to collapse
hey i had same problem with jbmp when i used jbmp kernel but when i flashed with nAa jb 05 kernel it worked fine..
There's a known problem for a little amount of Samsung Galaxy S GT-I9000 devices that are getting bluish screen after flashing AOSP Ice Cream Sandwich (4.0.x) and above.
By bluish screen I mean that there's a dark blue color - a blue tint / hue all over the screen.
This bluish screen appears everywhere in the ROM, in the recovery, and even when charging the phone while it's off.
There are videos and screenshots which demonstrates this issue here.
According to @DerTeufel1980 and @pawitp, this issue is caused by the updated framebuffer driver of the Nexus S in the CyanogenMod 9 kernels, and the actual problem is that some devices contain incorrect calibration data.
In this thread I'd like to share the ROMs and apps that I tried in search for the newest and most stable working ROM for problematic devices, and to list useful posts, threads and links.
I hope this thread will help ones with problematic devices, and that it will save them time and effort.
Edit: this issue is fixed by detecting the invalid calibration data and setting sane default values instead.
While this fix is implemented by @pawitp in CyanogenMod 11 ROMs from the cm-11-20140214-NIGHTLY-galaxysmtd.zip ROM and above, not all of the developers implemented it in their ROMs yet.
To know which ROMs we can flash please look at this list.
Ones who are interested might find more information about the fix of this issue here:
This issue is fixed by detecting the invalid calibration data in the CyanogenMod's aries kernel, and setting sane default values instead.
This fix was implemented in the android_kernel_samsung_aries/drivers/video/samsung/s3cfb_tl2796.c file.
The fixed source code can be viewed in:
CyanogenMod's Gerrit Code Review
CyanogenMod's GitHub
In addition, here is a link to the fix subject page in CyanogenMod's Gerrit Code Review.
Note that there was a previous fix, but it caused yellowish screen to users who didn't have the bluish screen.
More information about it can be found in CyanogenMod's Gerrit Code Review in the fixed build subject page and in it's revert page.
I'd like to appreciate @pawitp for being willing to help and solve this issue and for his truly tremendous effort to the community.
If someone is interested to see what ROMs and apps I tried before the fix, and interested in a list useful posts, threads and links that are connected to this issue:
ROMs that I tried (and didn't worked)
stock
Gingerbread 2.3.6 I9000XXJVU with CFROOT 4.3 by @xsenman - working good for us.
Gingerbread 2.3.6 I9000JHJVG# - working good for us.
Gingerbread 2.3.6 I9000XWJWB - working good for us.
AOSP
CyanogenMod
CyanogenMod 7.2.0 (Gingerbread 2.3.7) by @codeworkx - working good for us.
CyanogenMod 9.x (Ice Cream Sandwich 4.0.x) by @pawitp
CyanogenMod 10.x (Jelly Bean 4.1.x and 4.2.x) by @pawitp (links to 10.0.0, 10.1.x, 10.2.x)
Paranoid Android (AOSPA) by @SferaDev
Paranoid Android 3.69 (AOSPA 4.2.2 - JellyBean)
Paranoid Android 3.99 (AOSPA 4.3 - JellyBean)
Paranoid Android 4 beta 3 (AOSPA 4.4.2 - KitKat)
AOSP Jelly Bean 4.2.1 by @pawitp
Google play apps that I tried in order to control the bluish screen (and didn't worked good enough)
Screen Adjuster
Screen Filter
Filter Your Screen - Free!
Related posts and thread by this forum's users who are having the same issue
By @MrCabana
[Q] Samsung Galaxy S i9000B blue screen problem
[Q] Samsung Galaxy S (B) blue screen
[Q] Samsung Galaxy S blue screen error by @kssthomas
[NIGHTLY][ROM][4.0.4][IMM76I] CyanogenMod 9 for Samsung Galaxy S by @HaTeNL
Color Calibration ( Blue tint fix ) - Needs some work though by @-Yaya-
bluish screen? by @djr83
Best CM Colour Settings For Yellow Tinted Screens and Normal Screens by @alb3rtt
YouTube videos which demonstrates this issue
Additional links
Related topics in CyanogenMod Forum
Everything Is Blue
My topics: link 1, link 2
stock ROMs
In this forum
[Tutorial] How to Unbrick, Flash, Downgrade, Root, Update i9000 from Froyo to Kit Kat by @xsenman
[FULL GUIDE][UNBRICK][Root] Flash custom or stock ROMs or kernels [i9000][VIDEO] by @tetakpatak
[Firmwares]Official I9000/I9000M Firmwares collection [Latest: XWJWB, XWJW8, DDJVB] by @[Ramad]
[ROM/KERNEL/MODEM] GT-I9000 - Latest Stock Firmwares - Direct Links - Torrents by @IWillExplain
In external sites
SamMobile
Samsung Updates
modified stock ROMs list @ [GUIDE] Unsure which rom to choose? by @Soryuu
Summarization (note that this was written before there was a fix)
People who are having this issue can use stock ROMs (Gingerbread 2.3.6), CyanogenMod 7.2.0 (Gingerbread 2.3.7), and any AOSP Gingerbread 2.3.7 and below without been affected by this issue.
Replacing the screen digitizer might solve this issue. That did it for @MrCabana as posted here
If you know something that is not summarized here and might solve this issue or help to it somehow, please post it here
Thread's change log
18.02.2014
Added information about the fix of the bluish screen issue.
Changed the thread's topic to [Solved] bluish / blueish screen (blue tint / hue) after flashing AOSP ICS + on I9000.
17.02.2014
Removed invalid link.
15.02.2014
Added tag to the thread's title (there is not enough place for [Solved]).
[*]Updated in the thread that this issue is fixed.
[*]Added a link to videos and screenshots which demonstrates this issue.
[*]Converted profile links with mentions so users will be notified and will be able to comment if they'd like to.
[*]Added proper YouTube tags the the videos can be played directly from the thread.
13.02.2014
Added tag to the thread's title (there is not enough place for [Solved]).
[*]Removed tag from the thread's title since the solution may be temporarily.
[*]Added a note that this issue is being inspected.
[*][*]Added a link to the second fix issue subject page in CyanogenMod's Gerrit Code Review.
12.02.2014
Modified the topic's content.
Added a credit to pawitp for fixing the bluish screen issue.
Added a link to the ROM's build parameters page in CyanogenMod's Dashboard [Jenkins]
Removed tag from the thread's title since the solution caused problems for other devices.
[*]Added a link to the fix revert subject page in CyanogenMod's Gerrit Code Review
11.02.2014
This issue is solved.
Added tag to the thread's title (there is not enough place for [Solved]).
[*]Added information and link to the solution in this main post.
[*]Added links to related topics in CyanogenMod forum.
[*]Added a link to list of ROMs that we can use.
[*]Added a link to the fix subject page in CyanogenMod's Gerrit Code Review.
[*]Modifications
10.02.2014
Created this thread.
Modified the summarization section.
videos and screenshots which demonstrates the bluish / blueish screen issuse
reserved for videos and screenshots which demonstrates this issue.
In the meantime,
YouTube videos which demonstrates this issue
Screenshots that I posted in another post.
List of ROMs that we can flash on I9000 devices with the bluish / blueish screen
AOSP (Android Open Source Project)
CyanogenMod
CyanogenMod 7.2.0 (Gingerbread 2.3.7)
CyanogenMod 11.x (Kit Kat 4.4.x) as long as it's cm-11-20140214-NIGHTLY-galaxysmtd.zip or newer.
Any AOSP ROM based on Gingerbread (2.3.7) and below
Any AOSP ROM in which the bluish screen issue, the s3cfb: tl2796: detect invalid factory calibration data, is fixed.
stock ROMs
In this forum
[Tutorial] How to Unbrick, Flash, Downgrade, Root, Update i9000 from Froyo to Kit Kat by @xsenman
[FULL GUIDE][UNBRICK][Root] Flash custom or stock ROMs or kernels [i9000][VIDEO] by @tetakpatak
By @[Ramad]:
[Firmwares]Official I9000/I9000M Firmwares collection [Latest: XWJWB, XWJW8, DDJVB]
[CWM and Odin][Latest ROM: ZSJW4, XWJW7, XWJW6] Deodexed stock firmware collection
[ROM/KERNEL/MODEM] GT-I9000 - Latest Stock Firmwares - Direct Links - Torrents by @IWillExplain
In external sites
SamMobile
Samsung Updates
modified stock ROMs
[GUIDE] Unsure which rom to choose? by @Soryuu
[FULL GUIDE][UNBRICK][Root] Flash custom or stock ROMs or kernels [i9000][VIDEO] by @tetakpatak
[17.06.2013][INDEX] of all CR`s and Kernels -- JB - ICS - GB - MIUI -- by @driodmaster92
[ROM LIST] Galaxy S I9000 Custom ROM List [06.05.2011] by @splish2010
Notes
@Soryuu posted a great thread which helps choosing a ROM.
@SferaDev announced that he will patch all of the future releases of his ROMs (OmniROM, Paranoid Android and Nameless), so we'll have other great ROMs to flash.
Although the bluish screen issue was fixed by @pawitp in CyanogenMod 11 ROMs, not all of the developers implemented the fix in their ROMs yet.
Therefore if you want to flash a ROM that is not on this list, make sure this issue is fixed in it.
For an easy reference, ask the ROM's developer if he implemented the s3cfb: tl2796: detect invalid factory calibration data fix in his kernel. More information about this fix is available in the first post. If the ROM is indeed suitable for us, please update me so I'll update this ROM in the above list.
Users who know other ROMs who can work for devices with this bluish screen issue, and wish to add them to this list - please notify me (here or in PM) and I'll gladly add them.
Post's change log
08.03.2014
Added information about the bluish screen issue so users will be able to ask specific ROM's developer if the ROM is compatible for us.
Added a note that any AOSP ROM in which the bluish screen issue is fixed is appropriate for us.
18.02.2014
Changed the post's topic to List of ROMs that we can flash on I9000 devices with the bluish / blueish screen.
16.02.2014
Added modified stock ROMs.
Added a note about ROMs that are not on the list.
Added the note about the first CyanogenMod 11 build that we can flash, so we'll know to flash only it or newer.
15.02.2014
Modified CyanogenMod 11 link to link to the official thread.
Converted profile links with mentions so users will be notified and will be able to comment if they'd like to.
Added notes.
12.02.2014
Added a link to SferaDev thread.
Modified this post.
Added AOSP ROMs.
Added modified stock ROMs
Added stock ROMs
11.02.2014
Created this post.
Added a note from SferaDev.
Modified CyanogenMod 11.x link so it'll refer to the information needed to flash it until a newer version will be uploaded.
I saw pawitps commit on gerrit, I'll add it right now. Should be solved on OmniROM, Paranoid Android and Nameless future builds.
See you!
SferaDev said:
I saw pawitps commit on gerrit, I'll add it right now. Should be solved on OmniROM, Paranoid Android and Nameless future builds.
See you!
Click to expand...
Click to collapse
Cool!
Thanks a lot for your great contribution!
Please let us know so I'll update the ROMs list that we can use, so we'll know we have other great ROMs to flash.
List of ROMs that I9000 devices with the blue screen (blue tint/hue) issue can flash
The list of ROMs that I9000 devices with the blue screen (blue tint/hue) issue can flash moved to here.
grrrrrrrrrrrr
Too bad I didn't find this useful post in time before I broke my "uncalibrated screen" and replaced it with a new one.
Glad to know it was NOT a hardware problem, that means my first guess was right.
Thank you very much for the great work, guys !!!!
MrCabana said:
grrrrrrrrrrrr
Too bad I didn't find this useful post in time before I broke my "uncalibrated screen" and replaced it with a new one.
Glad to know it was NOT a hardware problem, that means my first guess was right.
Thank you very much for the great work, guys !!!!
Click to expand...
Click to collapse
Well brother, a lot of credit goes to you since I got a lot of information from you, and it was you who got me realizing that this is a program issue and not a hardware one.
You got me motivated to keep trying and reading and researching, and I'm so glad that pawitp was, and is, willing to help solving this issue.
Thanks a lot!
need4steer said:
Well brother, a lot of credit goes to you since I got a lot of information from you, and it was you who got me realizing that this is a program issue and not a hardware one.
You got me motivated to keep trying and reading and researching, and I'm so glad that pawitp was, and is, willing to help solving this issue.
Thanks a lot!
Click to expand...
Click to collapse
I am glad I was of help for others who face this same problem in the future.
If it's not asking too much, since I got some brain's attention for this device, I have another problem/question to report (I can start another thread if you guys think is necessary).
The problem is ... after replacing the "uncalibrated screen" with a brand new one, the battery indicator stopped working. That means the phone will always report it as 100% charged and won't allow the cable to charge it. I have to wait until it shuts down with no more power and charge it outside the device with a spare charger.
Secondly, the back camera stopped working while front camera is perfect. Both of them are attached with the same connectors to the MOBO, making them just 1 single part. How can one work perfect and the other one just go dead like that?
Thirdly, the USB connection is hard to be stablished with the computer. Even in service mode (i.e. to use odin). It does connect sometimes, but then it freezes even during a ROM update. This is making it impossible for me to mess with it and roll back to Froyo if things go wrong.
Again, those 3 problems CAN be due to malfunctioning hardware, but I believe it 's too much of a coincidence for these 3 unrelated things to happen right after the screen replacement, followed by an update to a nightly build of CyanogenMOD (don't remember exactly which one).
Any help would be greatly appreciated.
MrCabana said:
If it's not asking too much, since I got some brain's attention for this device, I have another problem/question to report (I can start another thread if you guys think is necessary).
Click to expand...
Click to collapse
While I and some other might help you here, it's better for you to open a new thread with appropriate title so others will be able to see your issue and help solve it. In this thread you'll see people who are interested in the bluish screen.
Anyway here are my comment for your device's issues:
MrCabana said:
The problem is ... after replacing the "uncalibrated screen" with a brand new one, the battery indicator stopped working. That means the phone will always report it as 100% charged and won't allow the cable to charge it. I have to wait until it shuts down with no more power and charge it outside the device with a spare charger.
Click to expand...
Click to collapse
Did you try another battery?
Did you tried different ROMs?
What's happening in recovery mode?
MrCabana said:
Secondly, the back camera stopped working while front camera is perfect. Both of them are attached with the same connectors to the MOBO, making them just 1 single part. How can one work perfect and the other one just go dead like that?
Click to expand...
Click to collapse
Perhaps one of the pins in the connector is bad?
Is the connector looking okay for you?
Did you tried different ROMs?
MrCabana said:
Thirdly, the USB connection is hard to be stablished with the computer. Even in service mode (i.e. to use odin). It does connect sometimes, but then it freezes even during a ROM update. This is making it impossible for me to mess with it and roll back to Froyo if things go wrong.
Click to expand...
Click to collapse
Is it happening in the same USB port in your computer?
Is the USB port connected directly to the motherboard, or is it one that is connected to the chassis, and from there to the motherboard?
MrCabana said:
Again, those 3 problems CAN be due to malfunctioning hardware, but I believe it 's too much of a coincidence for these 3 unrelated things to happen right after the screen replacement, followed by an update to a nightly build of CyanogenMOD (don't remember exactly which one).
Click to expand...
Click to collapse
The problems occurred only after the update? If so, revert. (I know that you don't have a USB connection, but you can take your sdcard to another device and copy to it the latest stable ROM)
If not, then if you ask me - it might be a hardware issue. It's very probable since before it you had no issues with the same ROM.
need4steer said:
Did you try another battery?
Did you tried different ROMs?
What's happening in recovery mode?
Click to expand...
Click to collapse
I don't have another battery nor different ROM's. I tried to revert to Froyo, but since USB is malfunctioning, I gave up on it. Recovery mode also reports battery as 100% even if it's nearly dead.
need4steer said:
Perhaps one of the pins in the connector is bad?
Is the connector looking okay for you?
Did you tried different ROMs?
Click to expand...
Click to collapse
Yes, the connector is looking okay to me. I removed it myself very carefully while replacing the digitizer. I'm almost sure it is NOT a hardware problem.
need4steer said:
Is it happening in the same USB port in your computer?
Is the USB port connected directly to the motherboard, or is it one that is connected to the chassis, and from there to the motherboard?
Click to expand...
Click to collapse
I tried many different cables and USB ports. Both chassis front and rear mobo. Even different PC's. Same results. 1 every 30 tries will let me use ODIN, and 1 every 30 tries, ODIN will complete uploading. That's frustrating.
need4steer said:
The problems occurred only after the update? If so, revert. (I no that you don't have a USB connection, but you can take you sdcard to another device and copy to it the latest stable ROM)
If not, then if you ask me - it might be a hardware issue. It's very probable since before it you had no issues with the same ROM.
Click to expand...
Click to collapse
[/QUOTE]
The problems occurred right after replacing the digitizer. Since I had Android 4.2.2 already installed, I didn't insist on trying different ROM's or rolling back to Froyo.
Thanks for the quick reply.
MrCabana said:
The problems occurred right after replacing the digitizer. Since I had Android 4.2.2 already installed, I didn't insist on trying different ROM's or rolling back to Froyo.
Click to expand...
Click to collapse
I must admit that it's not looking good since it's probably a hardware issue. If not, why these 3 things stopped working right after you replaced the digitizer?
However, if you want my advice, do open a new thread with appropriate topic name and include all this information so others will see it. Maybe someone will suggest something that we didn't think of.
In addition, while Android 4.2.2 is already installed in your device, don't forget that you can continue updating to newer versions:
need4steer said:
I know that you don't have a USB connection, but you can take your sdcard to another device and copy to it the latest stable ROM
Click to expand...
Click to collapse
need4steer said:
I must admit that it's not looking good since it's probably a hardware issue. If not, why these 3 things stopped working right after you replaced the digitizer?
However, if you want my advice, do open a new thread with appropriate topic name and include all this information so others will see it. Maybe someone will suggest something that we didn't think of.
In addition, while Android 4.2.2 is already installed in your device, don't forget that you can continue updating to newer versions:
Click to expand...
Click to collapse
Alright, I willl try to update version and see what happens.
Thank you.
need4steer said:
I must admit that it's not looking good since it's probably a hardware issue. If not, why these 3 things stopped working right after you replaced the digitizer?
However, if you want my advice, do open a new thread with appropriate topic name and include all this information so others will see it. Maybe someone will suggest something that we didn't think of.
In addition, while Android 4.2.2 is already installed in your device, don't forget that you can continue updating to newer versions:
Click to expand...
Click to collapse
I just updated to the newest nightly version, Android 4.4. Despite I now have neat KK, the problems persist.
Anyway, thanks for your help and I will follow your advice of opening a new thread.
MrCabana said:
I just updated to the newest nightly version, Android 4.4. Despite I now have neat KK, the problems persist.
Anyway, thanks for your help and I will follow your advice of opening a new thread.
Click to expand...
Click to collapse
First of all, congratulation! I had no doubt you'll do it easily.
These 3 problems will persist in this and in any ROM, since unfortunately it seems like a hardware problem.
However, I might be wrong (hopefully), and posting a dedicated thread for these problems will make them exposed to others so you might get some good solutions for them.
Good luck!
Great effort, @need4steer thank you for announcing so clearly the solution for blueish-screen-bug!
Many people have been reporting this problem in the past, this thread is most welcome!
Thanks
need4steer said:
reserved for videos and screenshots which demonstrates this issue.
In the meantime,
YouTube videos which demonstrates this issue
Screenshots that I posted in another post.
Click to expand...
Click to collapse
Thanks for the help, I thought I will never be a new software!
tetakpatak said:
Great effort, @need4steer thank you for announcing so clearly the solution for blueish-screen-bug!
Many people have been reporting this problem in the past, this thread is most welcome!
Click to expand...
Click to collapse
kssthomas said:
Thanks for the help, I thought I will never be a new software!
Click to expand...
Click to collapse
Thanks a lot for both of you for your appreciation!
I'm glad that I'm able to help others.
Galaxy S i9000 display issue
Oops, Sorry need4steer for sending a PM to you.. I don't know I can post on this thread..
By the way.. I figured what my problem is.. It's Screen Burn In.. That problem on screen I encountered was not only happening when playing flappy bird, it's noticeable on bright displays, tried some apps that can remove it.. I tried the "Screen Burn-In Tool" Tried it for 8 hours of non-stop color switching, but nothing changes at all.. Any remedies to remove the screen burn ins in my Galaxy S GT-I9000?
Thanks for the help!
gameguard025 said:
Oops, Sorry need4steer for sending a PM to you.. I don't know I can post on this thread..
By the way.. I figured what my problem is.. It's Screen Burn In.. That problem on screen I encountered was not only happening when playing flappy bird, it's noticeable on bright displays, tried some apps that can remove it.. I tried the "Screen Burn-In Tool" Tried it for 8 hours of non-stop color switching, but nothing changes at all.. Any remedies to remove the screen burn ins in my Galaxy S GT-I9000?
Thanks for the help!
Click to expand...
Click to collapse
Hi
I'm not familiar with the screen burn in issue.
However, a Google search for i9000 screen burn in site:forum.xda-developers.com or i9000 screen burn in on top site:forum.xda-developers.com shows a lot of interesting threads in this forum.
In addition, since this thread is dealing with the bluish screen issue and not with the burn in issue, I think it'll be the best if you'll post a new thread in this forum so your problem will be exposed to others and they'll be able to give additional and more appropriate solutions.
BTW, it's always better to post screenshots, so be sure to include the ones you sent me in PM.
If you need any help whatsoever please notify me and I'll do my best
Good luck!
Q&A for [ROM][GT-I9305][KitKat][4.4.4] CyanogenMod 11.0 Official
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
GT-i9305 CM11 known issues (or DONE/TODO lists)
Hi all,
I'm interested on CM11 in GT-i9305 (I own gt-i9305, I'm running running CM10 and I would have some new features included in CM11 (i.e.: LowEnergy Bluetooth). Btw I'm afraid about it because CM11 has not a stable release, maybe it will never has a stable(/RC) release... So I'd like to know what features are running and what else is not running... because I'd like to have new (CM11) features but I want my phone to not lose what is ok in CM10...
Looking at Known Issues page (wiki - Known_Issues_page_for_i9305) I see CM10.1 and CM10.2 related issues... but not CM11 ones...
There are any lists that users can see to make a conscious chose? I want to assess what features I'm going to lose upgrading to CM11 (camera was working in CM10... it doesn't work in CM11, I suppose).
I know gt-i9305 CM11 official thread... btw it's more than 100 pages, so Its not useful.
My revious phone was Motorola-Defy (MB525) and CM thread (first message) spoke about features, installing procedure, TODO list, know issues... GT-i9305 CM11 official thread doesn't include TODO (not running list)
Thanks in advance
LOW MICROPHONE VOLUME (videorec - whatsapp...)
how to fix this problem????
low volume on call
Hi,
Can anyone help with the problem of a very low speaker volume during call?
I have read here about changing the numerical values somewhere to increase the volume.
in addition, ther's the problem of low microphon rec.
i run nighitly 11-20141031.
(step-by-step would be much appreciated )
Well from what I have seen. Not sure if its true just yet but maclaw who works on s3 mini and other devices is ready to clone the lollipop repo when it gets released by google
Sent from my GT-N7105 using XDA Free mobile app
---------- Post added at 08:41 AM ---------- Previous post was at 08:39 AM ----------
CNerone said:
Hi all,
I'm interested on CM11 in GT-i9305 (I own gt-i9305, I'm running running CM10 and I would have some new features included in CM11 (i.e.: LowEnergy Bluetooth). Btw I'm afraid about it because CM11 has not a stable release, maybe it will never has a stable(/RC) release... So I'd like to know what features are running and what else is not running... because I'd like to have new (CM11) features but I want my phone to not lose what is ok in CM10...
Looking at Known Issues page (wiki - Known_Issues_page_for_i9305) I see CM10.1 and CM10.2 related issues... but not CM11 ones...
There are any lists that users can see to make a conscious chose? I want to assess what features I'm going to lose upgrading to CM11 (camera was working in CM10... it doesn't work in CM11, I suppose).
I know gt-i9305 CM11 official thread... btw it's more than 100 pages, so Its not useful.
My revious phone was Motorola-Defy (MB525) and CM thread (first message) spoke about features, installing procedure, TODO list, know issues... GT-i9305 CM11 official thread doesn't include TODO (not running list)
Thanks in advance
Click to expand...
Click to collapse
I have been running cm11 since first release. And its been getting better with each release.. The latest nightly with Agni kernel is a good daily driver. I haven't found any problems.
Sent from my GT-N7105 using XDA Free mobile app
Does anybody faces problem with missing calender in latest nightly?
All I got is "missing calendar storage"
guide me
hello sir.,
help me and guide me to update kitkat 4.4.4.
i have samsung galaxy s3 I9305 LTE
AP: I9305XXUEMKC
CP: I9305CCUEMK1
CSC: I9305VDIEMK2
(in my phone i have vodafone applications may be it is vodafone carrier .i have bought in UAE ( dubai) ).
Is there any chance to update kitkat 4.4.4 germany (DBT) official update to my s3 LTE.
if i update to germany 4.4.4 kitkat .any thing will going to brick my s3 LTE.
please suggest me i am kindly waiting for your replay.....
if there is no problem to update kitkat 4.4.4 .please provide perfect procedure sir...
Has anyone started compiling cm12 for the i9305 yet???
Sent from my GT-N7105 using XDA Free mobile app
Moving on...
Just wanted to say thanks for the last years with cyanogenmod for i9305.
Im moving on to the Sony parts of XDA.
Trying to catch a burglar last week resulted in a broken samsung, and I thought I would try something new.
cm12
does anyone know when the CM12 will be available ?
thanks for this awesome rom
no future updates?
Does this mean that there will be no CM11 update for I9305?
Cm11 - any way to turn of charging led notification when screen is on
Hi, is there any way to disable charging led notification light when the screen is on? i have tried many apps from play store but none have option to disable when the screen is on. Even no xposed modules are helpful in this regard.
Secondly please guide me the way to fix led light turns green at reaching 90%, this issue was previously solved in CM10.
Thank you.
please help
please help!
noteespirit said:
Hi, is there any way to disable charging led notification light when the screen is on? i have tried many apps from play store but none have option to disable when the screen is on. Even no xposed modules are helpful in this regard.
Secondly please guide me the way to fix led light turns green at reaching 90%, this issue was previously solved in CM10.
Thank you.
Click to expand...
Click to collapse
WiFi Power Saving Mode
Is there anyway to turn off WiFi power saving mode on CM11, Beacuse i cannot connect to WiFi in any other way for some reason and when i try to it just says (saved and secured > authenticating and then it just goes back and says saved and secured)
And sorry im very new to CM11 and forums in general!
Power off charging animation stuck.
The charging animation on my phone gets stuck when I turn my phone off. Are there any fixes?
Thanks
Samsung I9305 Dock Audio with Cyanogenmod 11 fix
Since installing Cyanogenmod KitKat4.4.4, 11-20150105-NIGHTLY-i9305, the main issue I had was I could no longer use my Samsung Desktop Dock EDD-D200BE to output audio, with the help of TKMAS on the Cyanogenmod Forum, I found there was an issue with the "audio_policy.conf" file, located in system/etc, it was missing a line of text in the devices line under "audio_hw_modules" just adding to the end of the line the following
|AUDIO_DEVICE_OUT_DGTL_DOCK_HEADSET
and saving the file, rebooted my phone and audio now comes out of the dock, I found the audio_policy.conf info here https://android.googlesource.com/device/samsung/manta/+/jb-mr1-dev/audio_policy.conf
CM WiFi power saving mode
Yes. Just go to Settings->Wi-Fi and then click on Menu->Advanced. You'll find here useful options such as "Keep Wi-Fi on during sleep", "Wi-Fi optimization" and "Avoid poor connections"
RunamukOG said:
Is there anyway to turn off WiFi power saving mode on CM11, Beacuse i cannot connect to WiFi in any other way for some reason and when i try to it just says (saved and secured > authenticating and then it just goes back and says saved and secured)
And sorry im very new to CM11 and forums in general!
Click to expand...
Click to collapse
same problem here
Just had my stint with the latest two official nightlies, 0406 and 0412, and the camera is even worse when I first tried this rom in january. FCs, cant connents, even freezes up and reboots the phone, on a few days old, fresh wiped install. The so called "fix" just removed my camera as a whole, even other apps (Insta, Google camera), and full factory reset didnt work after that. I had to reflash from zip.
idk if this is the right thread to ask but...
what is this camera problem, and if there was a fix, why isnt this integrated in CM ages ago?
whats the point of compiling official CM nightlies till its camera is not working flawlessly out of the box? completely useless this way.
how come theres nothing in the developement thread, when almost every week a new compile comes out?
and foremost, who compiles these official nightlies when the OP behind it declared out of the project..???
sorry if im noob, but someone can explain this to me? CM is a huge disappointment for me, as I waited eagerly to put it up as my phone warranty expires. I never thought Id say stock TWiz is much better then this.
but im willing to give another try if someone helps who to get this working properly out of the box, because I liked the speed and simplicity. thx...
---------- Post added at 01:48 PM ---------- Previous post was at 01:41 PM ----------
chrizza710 said:
thanks for this awesome rom
Click to expand...
Click to collapse
sorry to ask, but You still use this rom? Is the camera worked OK for you? What nightly was that then, when you wrote this post, and you still use that, or updated it? thx.
Q&A for [DEV][ROM][4.4]Cyanogenmod 11[WIP][ALPHA-2]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [DEV][ROM][4.4]Cyanogenmod 11[WIP][ALPHA-2]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
saeed_sofi said:
can this rom be installed on gt-s5570i?
Click to expand...
Click to collapse
hello is there made any kitkat firmware for galaxy mini without any bugs I mean is there any firmware for daily use?
Any way to back to stock rom by CMW?
Or another solution? I have problem with video codecs, every video player crash.
my android version 4.1.1. how to update into 4.4.4? i have been try to update trough recovery mode, install zip from sdcard, but its failed. i can't update cwm too,,, helpme please,,,,
Few CM 11 questions
Hello, I've used my Galaxy Mini for more than 4 years, but I hadn't known, that it could run also another OS than the default one pre-installed by Samsung. But suddenly, I've found CM and this forum about it. I've made some research, but because I'm beginner with CM, I have few questions:
1. In the description on the thread for the CM 11 for Galaxy Mini there is written, that the development is currently in the testing/alpha2 state. There is also a wishlist of missing features. But the there is also written, that the last update was in January, 2014. If I compare it to Androidarmv6 download archive and its GitHub repository, is seems there already are newer versions out. My first question is, if the most recent version of CM 11 for Galaxy Mini is more stable than that 1 year old alpha2 release? Which missing features from that wishlist have been already resolved?
2. And if the CM 11 version is not stable enough for everyday use, which older (but still based on Android 4.x) and more stable CM version would you recommend me to use instead (if any - otherwise I'll install official CM 7.2)?
3. I noticed, that there is already the official alpha release of CM 12 (based on Android 5.x) and also ported as a new branch on GitHub. I also know, that Android 5.x is really hardware-demanding. Will it be still possible to run CM 12 on Galaxy Mini phone? And what about CM 11 or 10? Could you recommend me the most stable and the newest one (see 2nd question), but still working on so low-performance device as Galaxy Mini in default is (384 MB RAM, 600 MHz, ...)? And if not, could you recommend me some web article describing how to make the performance of my phone better in order to run that recommended CM version from my previous two questions (if it is possible somehow)?
4. And finally, I want to ask, if I need to root my device before installation of that recommended CM version. Because in the installation manual from the original Samsung firmware to the official CM 7.2 there is no need to root Galaxy Mini during process and in the installation manual from CM 7.2 to CM 11 too. But in the installation manual from the original Samsung firmware directly to the CM 11 there is rooted phone needed. I don't understand, why I don't need rooted phone for indirect installation, but for direct installation I do. Could you clarify me the installation process?
I hope somebody experienced helps the beginner there (but good programmer and advanced Linux user) with the installation of CM by answering these a little bit complicated questions
aleskva said:
Hello, I've used my Galaxy Mini for more than 4 years, but I hadn't known, that it could run also another OS than the default one pre-installed by Samsung. But suddenly, I've found CM and this forum about it. I've made some research, but because I'm beginner with CM, I have few questions:
1. In the description on the thread for the CM 11 for Galaxy Mini there is written, that the development is currently in the testing/alpha2 state. There is also a wishlist of missing features. But the there is also written, that the last update was in January, 2014. If I compare it to Androidarmv6 download archive and its GitHub repository, is seems there already are newer versions out. My first question is, if the most recent version of CM 11 for Galaxy Mini is more stable than that 1 year old alpha2 release? Which missing features from that wishlist have been already resolved?
2. And if the CM 11 version is not stable enough for everyday use, which older (but still based on Android 4.x) and more stable CM version would you recommend me to use instead (if any - otherwise I'll install official CM 7.2)?
3. I noticed, that there is already the official alpha release of CM 12 (based on Android 5.x) and also ported as a new branch on GitHub. I also know, that Android 5.x is really hardware-demanding. Will it be still possible to run CM 12 on Galaxy Mini phone? And what about CM 11 or 10? Could you recommend me the most stable and the newest one (see 2nd question), but still working on so low-performance device as Galaxy Mini in default is (384 MB RAM, 600 MHz, ...)? And if not, could you recommend me some web article describing how to make the performance of my phone better in order to run that recommended CM version from my previous two questions (if it is possible somehow)?
4. And finally, I want to ask, if I need to root my device before installation of that recommended CM version. Because in the installation manual from the original Samsung firmware to the official CM 7.2 there is no need to root Galaxy Mini during process and in the installation manual from CM 7.2 to CM 11 too. But in the installation manual from the original Samsung firmware directly to the CM 11 there is rooted phone needed. I don't understand, why I don't need rooted phone for indirect installation, but for direct installation I do. Could you clarify me the installation process?
I hope somebody experienced helps the beginner there (but good programmer and advanced Linux user) with the installation of CM by answering these a little bit complicated questions
Click to expand...
Click to collapse
Are you sure your device is galaxy mini/pop s5570? There is no "i" at end? If both yes, then go ahead and read my answers.
Answers:
1. The op(member of androidarmv6 group) isn't active. Thats why the thread says alpha. But you can download and install latest tass(galaxy mini) version from androidarmv6 jenkins. And about feature list, everything is fixed from that list, but camera is colorless(black and white type pics). You need tls enabled recovery to flash latest cm11.
2. Cm11 is stable enough for daily usage. But cm11 is resource hungry. I would recommend you to try cm11 and make your own decision about it. Every android version <= 4.2.2 are fully stable and everything works. I use aokp 4.1.2 myself. 4.2.2 is a bit heavy but if you don't use too many apps, you could use it without any problems. Cm9, ics aosp, cm10,slimbean,aokp jb4.1.2 roms are most efficient 4.x roms and less resource hungry. For better results and good performance, you may need to install greenify. See my threads for 4.x roms.
3. Cm12 isn't booting yet. You can follow review.androidarmv6.org for latest changes and progress. Better use aokp 4.1.2 or slimbean or cm10 with greenify and int2ext(to expand internal memory, you need to create 512mb ext4 partition on sdcard).
4. It is not that hard to flash a simple zip. There is a thread here in galaxy mini section which describes how to root galaxy mini. Follow that tutorial. Then flash cwm 5.0.2.8 recovery(search in and download from galaxy mini section) it from stock rom recovery.
Then you are ready to install any galaxy mini roms.
Caution: Don't flash any zips outside galaxy mini section. Our device board name is "tass". So, you'll see tass in filenames and they are for galaxy mini/pop s5570. If you flash wrong zips, you'll end up with bricked phones(a paper weight). So, be careful. Have a happy flashing.
Sent from my GT-S5570 using XDA Free mobile app
Thank you! And one more question below
Venkatesh said:
Are you sure your device is galaxy mini/pop s5570? There is no "i" at end? If both yes, then go ahead and read my answers.
Caution: Don't flash any zips outside galaxy mini section. Our device board name is "tass". So, you'll see tass in filenames and they are for galaxy mini/pop s5570. If you flash wrong zips, you'll end up with bricked phones(a paper weight). So, be careful.
Click to expand...
Click to collapse
Sure! Just S5570 without "i" and just Tass! I know it is older mobile phone, but still I don't want little unusable brick
Venkatesh said:
But you can download and install latest tass(galaxy mini) version from androidarmv6 jenkins. And about feature list, everything is fixed from that list, but camera is colorless(black and white type pics). You need tls enabled recovery to flash latest cm11.
Click to expand...
Click to collapse
Is jenkins the download.androidarmv6.com site? Or jenkins.androidarmv6.com? But on the second site I don't see download link, even if I login with my GitHub account. And what is tls enabled recovery? Does it mean using CWM recovery? Or am I wrong?
Venkatesh said:
I would recommend you to try cm11 and make your own decision about it.
Click to expand...
Click to collapse
I'll try and I'll see
Venkatesh said:
There is a thread here in galaxy mini section which describes how to root galaxy mini. Follow that tutorial.
Click to expand...
Click to collapse
So I need to root my phone before. I wasn't sure, but now I understand clearly.
Venkatesh said:
Have a happy flashing.
Click to expand...
Click to collapse
Thank you for your answers to my questions! Actually many thanks!
And finally one more question:
I've seen more threads about Galaxy Mini roms in this xda section. And in almost all of them is written, that everything works, just there are problems using camera. It looks like this is a global problem. Is this problem only in CM 11 at the moment and group members only aren't active to cross the camera out from the "Don't work" list on threads for roms, which were resolved? Or is it still global problem? In which roms camera fully work without any caveat? You wrote, that everything in Galaxy Mini section <=4.2.2 is fully stable, so I expect it works there, but better to ask...
aleskva said:
Sure! Just S5570 without "i" and just Tass! I know it is older mobile phone, but still I don't want little unusable brick
Is jenkins the download.androidarmv6.com site? Or jenkins.androidarmv6.com? But on the second site I don't see download link, even if I login with my GitHub account. And what is tls enabled recovery? Does it mean using CWM recovery? Or am I wrong?
I'll try and I'll see
So I need to root my phone before. I wasn't sure, but now I understand clearly.
Thank you for your answers to my questions! Actually many thanks!
And finally one more question:
I've seen more threads about Galaxy Mini roms in this xda section. And in almost all of them is written, that everything works, just there are problems using camera. It looks like this is a global problem. Is this problem only in CM 11 at the moment and group members only aren't active to cross the camera out from the "Don't work" list on threads for roms, which were resolved? Or is it still global problem? In which roms camera fully work without any caveat? You wrote, that everything in Galaxy Mini section <=4.2.2 is fully stable, so I expect it works there, but better to ask...
Click to expand...
Click to collapse
Search androidarmv6 jenkins in google.
Camera in cm11 actually works but it uses source built libcamera, not the original samsung libcamera. And it gives a very colorless pics. No, androidarmv6 people are very nice. Just they are busy. And we don't have a skillful developer left.
And yes, every version <= 4.2.2 has got everything working as it should. But the video recording isn't good sometimes(only sometimes, it is not good anyways).
I would recommend you to try my aokp 4.1.2. Partition your sd card, install cronmod int2ext to expand ur internal memory (int2ext only not int2ext+). And install xposed installer + greenify, greenify not so important and ram consuming apps. That's my setup actually.
Good night
Sent from my GT-S5570 using XDA Free mobile app
Venkatesh said:
Search androidarmv6 jenkins in google.
Camera in cm11 actually works but it uses source built libcamera, not the original samsung libcamera. And it gives a very colorless pics. No, androidarmv6 people are very nice. Just they are busy. And we don't have a skillful developer left.
And yes, every version <= 4.2.2 has got everything working as it should. But the video recording isn't good sometimes(only sometimes, it is not good anyways).
I would recommend you to try my aokp 4.1.2. Partition your sd card, install cronmod int2ext to expand ur internal memory (int2ext only not int2ext+). And install xposed installer + greenify, greenify not so important and ram consuming apps. That's my setup actually.
Good night
Sent from my GT-S5570 using XDA Free mobile app
Click to expand...
Click to collapse
Okay, I'll try next week and we'll see
well done
My experiences and impressions
Venkatesh said:
Search androidarmv6 jenkins in google.
Camera in cm11 actually works but it uses source built libcamera, not the original samsung libcamera. And it gives a very colorless pics. No, androidarmv6 people are very nice. Just they are busy. And we don't have a skillful developer left.
And yes, every version <= 4.2.2 has got everything working as it should. But the video recording isn't good sometimes(only sometimes, it is not good anyways).
I would recommend you to try my aokp 4.1.2. Partition your sd card, install cronmod int2ext to expand ur internal memory (int2ext only not int2ext+). And install xposed installer + greenify, greenify not so important and ram consuming apps. That's my setup actually.
Good night
Sent from my GT-S5570 using XDA Free mobile app
Click to expand...
Click to collapse
I haven't time before, so today I managed to install a new ROM to my Mini six months after I wrote here. First of all I spent hours of googling and searching, where to download working package to root my phone and where to download cwm 5.0.2.8 for Mini, because all of the packages for rooting haven't been working at all and all of the download links to cwm 5.0.2.8 I've found were dead, except the links and except the packages here. Googling and searching finally helped, so I had my first cwm on my Mini. Then I've checked first three ROMs from the Mini's section. Concretely CM 10, SB 3.1.0 and AOKP JB 4.1.2.
First of all I've tried Slimbean. I was really confused, when I found out, that there is no keyboard inside the installation! What the h*** (sorry, but I really said that when at that moment)? One of my reasons to leave original Gingerbread was that really bad keyboard, which I need to reinstall by some from Google Play every time I had to reset my phone into factory settings (another reason to upgrade btw). And after upgrade again? But Slimbean looked really well, just a few strings weren't translated to my language, so I decided to try AOKP. AOKP hadn't just keyboard, but also gapps, so I needed to google, where to download it from. I've found this and hoped it can't break my newly installed ROM. And there were more strings untranslated to my language, so I decided to try the third one, CM. It was fully translated, but also there weren't gapps and keyboard. And the patch (if it was a patch) - tether patches.zip - couldn't be applied (some error was thrown during its installation).
Finally, I've found gapps for it too. The winner of these three was Slimbean, the loser was AOKP, but I'm going to test more ROMs, until I find some good one. In order to avoid searching the Mini's section another hours: Is there any ROM with preinstalled keyboard (and possibly gapps too)?
aleskva said:
I haven't time before, so today I managed to install a new ROM to my Mini six months after I wrote here. First of all I spent hours of googling and searching, where to download working package to root my phone and where to download cwm 5.0.2.8 for Mini, because all of the packages for rooting haven't been working at all and all of the download links to cwm 5.0.2.8 I've found were dead, except the links and except the packages here. Googling and searching finally helped, so I had my first cwm on my Mini. Then I've checked first three ROMs from the Mini's section. Concretely CM 10, SB 3.1.0 and AOKP JB 4.1.2.
First of all I've tried Slimbean. I was really confused, when I found out, that there is no keyboard inside the installation! What the h*** (sorry, but I really said that when at that moment)? One of my reasons to leave original Gingerbread was that really bad keyboard, which I need to reinstall by some from Google Play every time I had to reset my phone into factory settings (another reason to upgrade btw). And after upgrade again? But Slimbean looked really well, just a few strings weren't translated to my language, so I decided to try AOKP. AOKP hadn't just keyboard, but also gapps, so I needed to google, where to download it from. I've found this and hoped it can't break my newly installed ROM. And there were more strings untranslated to my language, so I decided to try the third one, CM. It was fully translated, but also there weren't gapps and keyboard. And the patch (if it was a patch) - tether patches.zip - couldn't be applied (some error was thrown during its installation).
Finally, I've found gapps for it too. The winner of these three was Slimbean, the loser was AOKP, but I'm going to test more ROMs, until I find some good one. In order to avoid searching the Mini's section another hours: Is there any ROM with preinstalled keyboard (and possibly gapps too)?
Click to expand...
Click to collapse
I've removed keyboard and gapps intensionally. I use this keyboard. If you really want jb keyboard i'll provide you later(is not better than gb keyboard though). Yourzgapps are best. Google search yourzgapps.
Venkatesh said:
I've removed keyboard and gapps intensionally. I use this keyboard. If you really want jb keyboard i'll provide you later(is not better than gb keyboard though). Yourzgapps are best. Google search yourzgapps.
Click to expand...
Click to collapse
I used this one. Its dev developed JB keyboard too, but it wasn't compatible with GB anymore. Is there any package for this or JB one or I need to install them from Google Play?
I found out that AOKP just needed to restart to be fully translated, so it is a little bit ok than CM (but SB still wins).
I'd like to try some 4.0 ROMs and some 4.2 ROMs (just to try, like yesterday). I saw here some threads about english only ROMs. I'll try them and maybe find my favourite. Is there any chance to build my language version after that? I know there is big red notification This is english only! (You have been warned...!). I don't want to waste your time for so minor things. Feel free to reject my potential request at the beginning.
aleskva said:
I used this one. Its dev developed JB keyboard too, but it wasn't compatible with GB anymore. Is there any package for this or JB one or I need to install them from Google Play?
I found out that AOKP just needed to restart to be fully translated, so it is a little bit ok than CM (but SB still wins).
I'd like to try some 4.0 ROMs and some 4.2 ROMs (just to try, like yesterday). I saw here some threads about english only ROMs. I'll try them and maybe find my favourite. Is there any chance to build my language version after that? I know there is big red notification This is english only! (You have been warned...!). I don't want to waste your time for so minor things. Feel free to reject my potential request at the beginning.
Click to expand...
Click to collapse
You can add your language translations to apks inside the rom. ics,jb keyboards won't work on gb. There is a cm10.1 version from androidarmv6 team, try it. It has all languages. To build only your language, then you need to sync sources and modify build files to get your language.
Venkatesh said:
You can add your language translations to apks inside the rom. ics,jb keyboards won't work on gb. There is a cm10.1 version from androidarmv6 team, try it. It has all languages. To build only your language, then you need to sync sources and modify build files to get your language.
Click to expand...
Click to collapse
Thank you, I'll search the CM 10.1 from androidarmv6 team and try it. The keyboard looks like ICS, but worked fine in factory firmware GB. I think it could work in this CM 10.1 too. If I install it from Google Play to the CM 10.1 ROM, it will work, or not? But I don't know, how to change the apk into the zip, that can be installed from cwm.
Thank you for your all help. Six months ago I thought it will be so complicated, but it is easy if one follows the rules not to make a bricked phone.
Edit: I tried this and it is totally awesome. The best I've tried. I'll test it for a longer period. My favourite keyboard is inside, first time in my Mini's life I don't have to reinstall that bad original GB keyboard. I just hope it won't be so battery and RAM consuming (I'll test it). I ask here if I have some question or problem in the future. Last time huge thanks (in words and in thank buttons too)
aleskva said:
Thank you, I'll search the CM 10.1 from androidarmv6 team and try it. The keyboard looks like ICS, but worked fine in factory firmware GB. I think it could work in this CM 10.1 too. If I install it from Google Play to the CM 10.1 ROM, it will work, or not? But I don't know, how to change the apk into the zip, that can be installed from cwm.
Thank you for your all help. Six months ago I thought it will be so complicated, but it is easy if one follows the rules not to make a bricked phone.
Edit: I tried this and it is totally awesome. The best I've tried. I'll test it for a longer period. My favourite keyboard is inside, first time in my Mini's life I don't have to reinstall that bad original GB keyboard. I just hope it won't be so battery and RAM consuming (I'll test it). I ask here if I have some question or problem in the future. Last time huge thanks (in words and in thank buttons too)
Click to expand...
Click to collapse
try cm10.1 rom from here.
Venkatesh said:
try cm10.1 rom from here.
Click to expand...
Click to collapse
I tried it, the performance is better, but there is a huge problem. I install it in this way:
boot into cwm 5.0.2.8 >
wipe data, cache, dalvik cache, battery stats >
flash cm10.1 you suggested >
flash yourzgapps >
flash int2ext >
fotmat sd-ext >
reboot
After reboot cm10.1 boots and at the beginning works like a charm. Int2ext works as expected, 1/5 from memory used. But after 2-3 minutes int2ext stops working and I have full memory. Reboot or int2ext reinstallation don't work. Why? How could I fix it?
aleskva said:
I tried it, the performance is better, but there is a huge problem. I install it in this way:
boot into cwm 5.0.2.8 >
wipe data, cache, dalvik cache, battery stats >
flash cm10.1 you suggested >
flash yourzgapps >
flash int2ext >
fotmat sd-ext >
reboot
After reboot cm10.1 boots and at the beginning works like a charm. Int2ext works as expected, 1/5 from memory used. But after 2-3 minutes int2ext stops working and I have full memory. Reboot or int2ext reinstallation don't work. Why? How could I fix it?
Click to expand...
Click to collapse
Don't format sd-ext after flashing int2ext. One factory reset is enough.
Try this way:
1. Goto recovery and make factory reset/wipe.
2. Flash rom and reboot system(let it boot first).
3. Again goto recovery, mount all partitions and flash int2ext.
4. You can also flash gapps now. Reboot system now, and start your setup.
Venkatesh said:
Don't format sd-ext after flashing int2ext. One factory reset is enough.
Try this way:
1. Goto recovery and make factory reset/wipe.
2. Flash rom and reboot system(let it boot first).
3. Again goto recovery, mount all partitions and flash int2ext.
4. You can also flash gapps now. Reboot system now, and start your setup.
Click to expand...
Click to collapse
I had formatted sd-ext, because it is written in int2ext installation steps. Finally I tried your suggestion and everything works. I just flashed gapps right after flashing OS, because I want Google's first boot guide. I'm so happy everything works like a charm on that older, but good Mini. I'm also happy I got rid of that buggy GB. Once more thanks.
Err