Related
First of all, I expect that mrs. reinbeau doesn't close this post, I feel it necessary in order to solve the main problem of my ROM.
This post is intended to all of you that have the problems so called SoD (Screen of Death), when the phone sleeps but don't awake... and the frozen screen problems too...
It's a new ROM progressively created from scratch in order to determine where is the problem.
Please, use it and comment here if the SoD issues are gone or remains; everything you want to say but ONLY RELATED TO THIS PROBLEM.
The instructions are easy:
- If you come from Test 2, or Test 2.1, simply flash Zeus v5 Lite over it. It won't wipe your data.
- Otherwise, make a wipe data / factory reset before flashing Zeus v5 Lite
- AFTER INSTALL IT, IN BOTH CASES, FORMAT /CACHE (--> mounts and storage --> format /cache).
- Once you have Zeus v5 lite, directly flash Zeus v5.03 over it.
- Zeus Test 2 (full wipe, complete ROM): d7fc02c423df42ecbdc4a9a2a0f7255c - Mirror
- Zeus Test 2.1 (dalvik and cache wipe, complete ROM): a3c20899db2d59e09fab60dd6aeb6094 - Mirror
- Zeus v5 Lite (dalvik and cache wipe, complete ROM): c55155a8aac4e5300b8239c08e739bd6 - Mirror
- Zeus v5.01 Lite (dalvik and cache wipe, update to Zeus v5 lite): 9a2907c9aec64857495fec093495afd1 - Mirror
- Zeus v5.02 Lite (dalvik and cache wipe, update to Zeus v5 lite): eee81e29f285d261fe442a370bb4dffb - Mirror
- Zeus v5.03 Lite (dalvik and cache wipe, update to Zeus v5 lite): f52fc7b9c2534da91c09f937c13b13f5 - Mirror
Changelog:
Test 2: Initial base ROM lightwighted, with original kernel and some opts.
Test 2.1: Fully themed Test 2, additional cleaning and some opts.
Zeus 5 lite: Prerelease, test it please... It has a lite zeus script, txpower, some opts, new Google Play Store...
Zeus 5.01 lite: To flash over Zeus 5 lite. Stock kernel recompiled with Linaro (unaltered, with stock configuration), with a new runtime parameter to enable/disable led dimming (thanks to sergey1369) and with led supply current reduced in a 20% to save battery. Updated zeus script with options to enable/disable led dimming and to change lockscreen. Fixes symlink to 'cp' busybox command.
Zeus 5.02 lite: To flash over Zeus 5 or 5.01 lite. Same features as 5.01 + cache again with ext4, new optimized mount options and fixed the auto enable/disable dimming at boot.
Zeus 5.03 lite: To flash over Zeus 5, 5.01 or 5.02 lite. Same features as 5.02 + new governors(interactiveX, Smartass2 and OndemandX[default]) + deadline + total control of the leds (high intensity, low intensity, enable/disable dim, timer) + txpower stock by default (touch it if you want) + runtime enable/disable fsync() enabled by default + upgraded zeus script... look into it!
Regards and thanks!
About 12 hours with your fix and everything is OK. I have v3.2b.
Pr3dator? said:
Is there a way to fix this on cyanogenmod
Envoyé depuis mon LG-P970 avec Tapatalk
Click to expand...
Click to collapse
What do you understand with ONLY RELATED TO THIS PROBLEM?
pk76 said:
About 12 hours with your fix and everything is OK. I have v3.2b.
Click to expand...
Click to collapse
Hi,
forgot the last fix posted on the other post... this is a new fix. Although you don't have problems with the oder fix, there supossedly are people that have problems...
Regards.
Now I have a worst problem: after the SoD, I did try to restart the phone by pulling out the battery and now it doesn't want to start again! When I push the ON/OFF button, the 4 leds start to blink but the screen remains in black (not off, is there a difference).
Then after 5 or 6 tries, it start and show me the CWM menu, I did apply your fix and still the same thing (doesn't want to pass from the LG logo, and sometimes even doesn't show the LG logo!).
What do you think is happening? I think is something related to the Graphics driver, maybe something changed in the Kernel to give more graphics performance or something, I really don't know...
tsakaji30 said:
Now I have a worst problem: after the SoD, I did try to restart the phone by pulling out the battery and now it doesn't want to start again! When I push the ON/OFF button, the 4 leds start to blink but the screen remains in black (not off, is there a difference).
Then after 5 or 6 tries, it start and show me the CWM menu, I did apply your fix and still the same thing (doesn't want to pass from the LG logo, and sometimes even doesn't show the LG logo!).
What do you think is happening? I think is something related to the Graphics driver, maybe something changed in the Kernel to give more graphics performance or something, I really don't know...
Click to expand...
Click to collapse
Hi,
if i have readed well, first you have the problem, and after that you have flashed my fix, isn't it?
Maybe you have any corrupted at /system, and the fix doesn't fix a ROM, only change certain things in the ROM to look for the SoD problem.
Try to flash V3x, then V3.2x and then the FIX 1.
Regards.
And no, there's no strange changes to kernel to boost anything that can harm your phone.
Regards.
Huexxx said:
Hi,
if i have readed well, first you have the problem, and after that you have flashed my fix, isn't it?
Maybe you have any corrupted at /system, and the fix doesn't fix a ROM, only change certain things in the ROM to look for the SoD problem.
Try to flash V3x, then V3.2x and then the FIX 1.
Regards.
Click to expand...
Click to collapse
Ok, I'm going to try this again from scratch.
Another important thing: I was having the same problem since V2, then I flashed V3 and it was gone by 2 or 3 days, then, yesterday my phone restarts itself and after that is a chaos hehehe
If is not something related to the graphics, then maybe is something related with the way your version commit data in the memory and maybe there is a data corruption that makes the phone behave weirdly.
Anyway, thanks a lot for your big effort, I regained the thrust in my phone after testing your zeus rom (i was just to sell the black and buy a Nexus hehehe).
Regards!
Thread cleaned
No worries, I won't close this thread, let's keep it on topic - and I'm a Mrs, not a Mr.
Huexxx said:
Hi,
forgot the last fix posted on the other post... this is a new fix. Although you don't have problems with the oder fix, there supossedly are people that have problems...
Regards.
Click to expand...
Click to collapse
So, you recommend me to use the newer version "b" fix or i can stay with the older one. Thanks for your great work. :thumbup:
reinbeau said:
No worries, I won't close this thread, let's keep it on topic - and I'm a Mrs, not a Mr.
Click to expand...
Click to collapse
Sorry!!!!!!!!
pk76 said:
So, you recommend me to use the newer version "b" fix or i can stay with the older one. Thanks for your great work. :thumbup:
Click to expand...
Click to collapse
Everyone can do what he want! The "old" fix was a quick attempt to fix the problem. While you don't have the problem, don't try this stuff becuase it's intented to catch the problem; no problem -> no catch...
Someone said that with the "old" fix the problem persists, so I have created this post to progressively approach the problem to know where is it, and then erradicate it!
- If people try this fix and the problem persists, it will be at the ROM itself, not in the kernel/boot.img/build.prop -> then we'll try to find it on the ROM.
- If people try the fix and the problem is gone, the problem is at my latest kernel/boot.img/build.prop, so I'll change progressively that stuff until we get the error again...
There's no other way IMHO.
Regards.
already activated fsyn and flahs ur fix, I ll give my feedback in a few hours, just let my try...
With my fix (THIS FIX, ON FIRST POST) there's no possibility of deactivate fsync because it's a diana kernel feature and wiht my fix you will have the stock kernel...
Thanks!
First of all, I'm not using this rom, I'm using cm7 temasek's build BUT I think somehow is related because this "SoD" is happening at the new builds...
And I wonder why? well I don't know but, it may be something with the rom itself?
Zeus is "official" and cm7 is "mod" but they're both based on gingerbread so there must be some connection.
I'm not trying to complicate things but trying to help, because this is not an isolated issue from zeus, this is present at cm7 new builds too.
Sorry but is not the same IMHO...
- CM7 are constantly changing and for whatever reason the most recent builds have this problem. So, different builds...
- my rom comes from stock rom (that doesn't have the problem, or that's what we hope...) and in a certain moment with some modification (of my own) the problem has emerged, WITH THE SAME BUILD.
When I find my problem, I hope it can allow cm7 people to fix the problem, but I'm afraid there are a lot of reasons why it can happen.
This thread is to test my rom with different things trying to find the bad change made to my rom, not a thread to discuss about Screen of Death.
Thanks anyway.
Hi Huexx!
First of all thank you for your patience and for your excelent work whith this phone.
About all this things of SoD, I whant to ask you something: have you ever faced it?
I don't know but I'am using your Rom since first and have installed the 3.0 then the 3.1 and then the 3.2, and I have never faced the SoD. How offten are this SoD's happening?
I'am using interactivex whit deadline and Fsync enabled.
I also never faced this SoD with your ROM (3.0n) and I'm using it for a while now. I skiped 3.1 patch and installed 3.2 yesterday and no SoD. But with cm7 I had this once don't know what version.
On the other hand a colleague at work have this issue with 3.1n a few days after install. I installed the 3.2n and we'll see.
yesterday I got 2 frozeen displays and have to remove battery,
Today (like about 5 hours ago) flash this fix and until now I dont have that problem at all... I just want to give my feedback, but I ll post again 5 hours later to say if donst get the problem again.
Sry about my pretty bad english.
Hackpb said:
Hi Huexx!
First of all thank you for your patience and for your excelent work whith this phone.
About all this things of SoD, I whant to ask you something: have you ever faced it?
I don't know but I'am using your Rom since first and have installed the 3.0 then the 3.1 and then the 3.2, and I have never faced the SoD. How offten are this SoD's happening?
I'am using interactivex whit deadline and Fsync enabled.
Click to expand...
Click to collapse
I've faced only one SoD, thats the reason i need people that have experimented more sods because their way of use the phone.
Sent from my LG-P970 using XDA App
I was on the [ROM][4.1.2 JB]Ultimate N7000 XXLSC JellyBean 4.1.2 v5 and it was working like a charm... after a few weeks of using it i started getting stuck into bootloops all of a sudden... i managed to keep it going by wiping the dalvik and cache but it seemed to happen all over again... i then changed to AllianceROM N7000 JB XXLSC Alpha 1 thinking that the earlier one had some issues... but again after 2-3 days the same bootloop problem occured again... i dunno wat seems to be the problem... Can any one suggest any steps that i can take... also i wanna be on a TW JB ROM.. any suggestions which is the one that can be used going ahead... currently i have moved back to RocketROM JB v3 which i was using before the Utlimate ROM... Please HELP!!!!:crying:
Try ultimate jb rom v5.1
Did you exactly wipe everything before flashing?mine works fine.it is also a good tw jb rom
Sent from my GT-N7000 using xda premium
All the JB leaks have the boot loop issue. Some or the other time it will get stuck in boot loop and say we have to live with it till the official JB releases.
Try reboot from recovery or do a nandroid backup and restore to get the phone working again
I have bootloops, oops fruitloops for breakfast.
Yes welcome to the club, all the jb leaks have this, those based on dumps more. You really need to get a clean safe install with no restore of apps data for this to run properly.
good rumoured news official jb is just round the corner
The bootloops happen with every JB leak after XXLS7 or XXLSA. I found the cause in my Note: unclear shutdowns (like pulling the battery when the phone is on, or a system freeze). The best workaround I found is to go to recovery, do a backup (nandroid) then restore it right after. It should take some minutes but you will be back up where you were.
dbolivar said:
The bootloops happen with every JB leak after XXLS7 or XXLSA. I found the cause in my Note: unclear shutdowns (like pulling the battery when the phone is on, or a system freeze). The best workaround I found is to go to recovery, do a backup (nandroid) then restore it right after. It should take some minutes but you will be back up where you were.
Click to expand...
Click to collapse
Useful advice.thanks bro
Sent from my GT-N7000 using xda premium
milpro7 said:
I was on the [ROM][4.1.2 JB]Ultimate N7000 XXLSC JellyBean 4.1.2 v5 and it was working like a charm... after a few weeks of using it i started getting stuck into bootloops all of a sudden... i managed to keep it going by wiping the dalvik and cache but it seemed to happen all over again... i then changed to AllianceROM N7000 JB XXLSC Alpha 1 thinking that the earlier one had some issues... but again after 2-3 days the same bootloop problem occured again... i dunno wat seems to be the problem... Can any one suggest any steps that i can take... also i wanna be on a TW JB ROM.. any suggestions which is the one that can be used going ahead... currently i have moved back to RocketROM JB v3 which i was using before the Utlimate ROM... Please HELP!!!!:crying:
Click to expand...
Click to collapse
even i am having the same problem but as mentioned above all roms have this issue and we hope that the official jb release comes out fast:fingers-crossed:
Same issue with me.. i also using ultimate JB v5.1, suddenly happen bootloop "samsung galaxy note Gt-N7000". After reflashing back the rom, ok just for a while.. later happen again, then after i flashing Zip file to remove yellow triangle using Jig & odin, my note completely DEAD & waiting Jtag service :crying:
just happen again on xxlsc do all wipe useless only apply on restore backup solved the problems.
Hi all,
I am having the same re-occuring issue with all pure android jb roms like paranoid android, carbon rom, and CM rom. After flashing the ROM the battery stops charging. After removing the battery and putting it back on the issue is still there and also each time im getting a different battery level reading. The strange thing is that when i flash a touchwiz based rom eg; ultimate JB the battery charges normally without any issues. Has anybody else experienced this issue? I would be very grateful if some could suggest a solution to this problem
Thanks,
Flash these ROMs cleanly with the wipes. I have used CM, Asylum, PAC, Supernexus and other ROMs which have varied bases and have not faced the problem. Clean install of the ROMs should work, and also try erasing the battery stats.
re flashed rom with all neccessary wipes
Varad297 said:
Flash these ROMs cleanly with the wipes. I have used CM, Asylum, PAC, Supernexus and other ROMs which have varied bases and have not faced the problem. Clean install of the ROMs should work, and also try erasing the battery stats.
Click to expand...
Click to collapse
I re-flashed cm 9.1 stable, I carried out all necessary wipes, it is getting charge, but it only charged 10 percent in 1 and a half hours, also the charge drops really fast. I really love the UI of these sort of ROMS but always having the same issues . Might have to revert back to ultimate jb rom.
If you can help me please do, I so badly want an aosp rom.
Try the AOSP based paranoidandroid or supernexus ROM. How old is you battery?
I thing just flash stock jb via Odin..
Then flash ROM with cwm with all procedure..
This may fix or problem..
Be aure that phone charging on other ROM(ICS)
Sent from my GT-N7000 using xda premium
Varad297 said:
Try the AOSP based paranoidandroid or supernexus ROM. How old is you battery?
Click to expand...
Click to collapse
My battery is about a year old, I flashed supernexus yesterday and the issue with the charging was present. So I flashed back to ultimate JB ROM and the phone is charging fine, it also charges fine on rocket rom, so it seems as though the issue is only present when I flash aosp based ROMs
try other kernels
a.mozid said:
Hi all,
I am having the same re-occuring issue with all pure android jb roms like paranoid android, carbon rom, and CM rom. After flashing the ROM the battery stops charging. After removing the battery and putting it back on the issue is still there and also each time im getting a different battery level reading. The strange thing is that when i flash a touchwiz based rom eg; ultimate JB the battery charges normally without any issues. Has anybody else experienced this issue? I would be very grateful if some could suggest a solution to this problem
Thanks,
Click to expand...
Click to collapse
having the same issue with carbon rom. wipe everything reload rom and it is fine for awhile then the battery stops charging again. swap batteries and the still doesn't work. go back to a touchwiz and all is fine. i am using a galaxy s3. funny part about it is that when i plug in the charger, the battery icon (dotted circle with text) starts rotating like it is charging but go into status and it say that it is not and the battery drains fairly fast. faster than normal use. it would be nice to figure this one out as i really like the carbon rom.
I was also having inaccurate battery readings when I'm using CM 10.2. But since I switched to PAC-Rom battery readings are accurate now, and even lasts longer than stock rom. (based on my experience) So you might want to try PAC Rom if you somehow need a custom rom, or flash a touchwiz based rom to save your battery lifespan.
Premise : as I said in the title,I'm not asking 'what is the best rom ?'.
Now,here's my problem and my question :
Since a month I have 2g connecyion problems (YES,I use 2g connection and I switch to 3g only when I need a data connection;I save more battery and my phone can last 30-40 hours from 100 to 15%),very often my phone loose the signal and it won't turn back until I reboot.
I read in the forum that is a cm bug and in some vanir rom the problem is fixed.
Here's what i did trying to fix the problem :
-restore stock firmware through kdz file (v20a)
-root/recovery and unsecure boot flash.
-flash cm 10.1.3 and iodak kernel (clean instal) -> still 2g problem.
-flash vanir stable 4.3.1 with stock or werewolf kernel (clean install) -> 2g problem and sometimes when I lost the signal the phone gets hot and my battery drains really fast. I have also another problem : my phone was at 90%,i turned it off and in the morning the battery was at 0%.
-flash zaiben rom with iodak kernel(really old version that worked correctly in the past)-> wifi problems after some reboots.
-flashed miui 3.12.6 from miuiandroid with optimus prime kernel -> 2g problems.
I don't know what to do,can someone suggest me a stable rom without network problems (wifi/2g,3g/gps/nfc) and maybe with good performance and battery life ?
Yesterday I flashed 4 different rom (always with a clean install) and I'm tired to try different rom so please,don't answer me 'make backup and try this or that rom' and share your experience instead.
Thanks in advice.
stock rom, or any custom 4.2.2+ rom with EPRJ RIL implemented, which you can do yourself. look for my tutorial in general subforum, replacing CM RIL with EPRJ RIL gives rock-stable connection
I already looked your tutorial and the official thread of the tool but afterinstalling java,net framework etc,the tool doesn't work.
It says 'java not recognised' or something similar.
And what about kernels ? Does they (or some of them) create some kind of problems ?
So,if I'll make the tool works and I'll replace the ril,can I use cm 10.1.3 with iodak 8.0 kernel without problems ?
The strange thing is that network worked correctly with cm 10.1.3 for months,but now it doesn't.
BTW,wich rom are you using ? Can it fit for my phone use ?
MEDIACOM SmartPad 810c
ROM : First 4.3 (4.0.3)
moss20 said:
I already looked your tutorial and the official thread of the tool but afterinstalling java,net framework etc,the tool doesn't work.
It says 'java not recognised' or something similar.
And what about kernels ? Does they (or some of them) create some kind of problems ?
So,if I'll make the tool works and I'll replace the ril,can I use cm 10.1.3 with iodak 8.0 kernel without problems ?
The strange thing is that network worked correctly with cm 10.1.3 for months,but now it doesn't.
BTW,wich rom are you using ? Can it fit for my phone use ?
MEDIACOM SmartPad 810c
ROM : First 4.3 (4.0.3)
Click to expand...
Click to collapse
you gotta edit some settings on your computer, if you have issues with java. check out the link in the tutorial to the program i used to extract .jar file, it has the proper troubleshooting ^^
kernels shouldn't have issue with 2g/3g, but i do know some custom kernels have issues with wifi on stock and stock-based rom that appear randomly, and just as randomly go away (wifi stuck on turning on)
and yeah, you should be able to use iodak+cm combination without the issue. and it is strange that the problem just now started appearing, but hey, if this works, you got yourself set for future
atm i'm back on modified stock with iodakv7, i needed proper mhl support. i've however used i think all the roms for our device atleast for a week or so. carbon, slim, omni, vanir, cm, aokp, pac, mokee...
Ok,I'll try to fix java problems and I'll se what happens and I'll report here
MEDIACOM SmartPad 810c
ROM : First 4.3 (4.0.3)
moss20 said:
Premise : as I said in the title,I'm not asking 'what is the best rom ?'.
Now,here's my problem and my question :
Since a month I have 2g connecyion problems (YES,I use 2g connection and I switch to 3g only when I need a data connection;I save more battery and my phone can last 30-40 hours from 100 to 15%),very often my phone loose the signal and it won't turn back until I reboot.
I read in the forum that is a cm bug and in some vanir rom the problem is fixed.
Here's what i did trying to fix the problem :
-restore stock firmware through kdz file (v20a)
-root/recovery and unsecure boot flash.
-flash cm 10.1.3 and iodak kernel (clean instal) -> still 2g problem.
-flash vanir stable 4.3.1 with stock or werewolf kernel (clean install) -> 2g problem and sometimes when I lost the signal the phone gets hot and my battery drains really fast. I have also another problem : my phone was at 90%,i turned it off and in the morning the battery was at 0%.
-flash zaiben rom with iodak kernel(really old version that worked correctly in the past)-> wifi problems after some reboots.
-flashed miui 3.12.6 from miuiandroid with optimus prime kernel -> 2g problems.
I don't know what to do,can someone suggest me a stable rom without network problems (wifi/2g,3g/gps/nfc) and maybe with good performance and battery life ?
Yesterday I flashed 4 different rom (always with a clean install) and I'm tired to try different rom so please,don't answer me 'make backup and try this or that rom' and share your experience instead.
Thanks in advice.
Click to expand...
Click to collapse
Don't use unsecure boot flash' it is.unnecessary
Try optimus play kernel, it is excellent for me (wifi, 3g always on, whole day of battery and more)
Sent from my LG-P880 using Tapatalk
now I'm on miui 3.12.6 with optimus prime kernel and I edited the RIL using flyingbear's tutorial but it's too early to say if it works but first impression seems good.
I'm too busy to check another rom (i'd like to use vanir 4.3.1 or cm 10.1.3) and other kernel but when I'll try it,I'll write my impression
I have similar problem with network on latest miui.When i restart device or just turn it on/off i can find network untill i go to airplane network and switch it off again then everything is fine.Also it happened just 1 time that i lost my network while my phonewas on.I did discovered that this is MiUi problem since i never got this kind of behavior on any previous rom.Last couple of days even fter restart my network is ok no need to use airplane trick anymore.So again i will say this is miui bugg for somereason.
Sent from my LG 4X HD refrigerator.
Trust me,it's a month that I "fight" with mobile network,it's a common problem for all non-stock based roms,sometimes happens and sometimes not.
However you can fix it with flyingbear's tutorial.
MEDIACOM SmartPad 810c
ROM : First 4.3 (4.0.3)
Guys, A little Help!
I am currently using my old Galaxy S I9000, as my HTC has gone to Service Centre for a week.
Last time I left it with JB Custom Rom (C-Rom Bean v1.9.0 Final) which was working quite OK! Now its too much laggy and slow all over while on JB Rom. I have already tried CM11, CM10.2, Slimkat, SpiritRom and Dark Unicorn (all 4.x.x and above).
Currently I am on CM7.2, which is working quite fine, considering its based on GB 2.3.7. I was also looking for working Lewa OS link, as I liked the one that I installed on my HTC, but couldn't find one.
Can anyone help me to understand what has happed to make this phone go soooooooo slow. Even if I am unable to instal Android 4 and above, I would still need the link for Lewa OS. If anyone has it, that'd be most helpful.
samrat_castle said:
Guys, A little Help!
I am currently using my old Galaxy S I9000, as my HTC has gone to Service Centre for a week.
Last time I left it with JB Custom Rom (C-Rom Bean v1.9.0 Final) which was working quite OK! Now its too much laggy and slow all over while on JB Rom. I have already tried CM11, CM10.2, Slimkat, SpiritRom and Dark Unicorn (all 4.x.x and above).
Currently I am on CM7.2, which is working quite fine, considering its based on GB 2.3.7. I was also looking for working Lewa OS link, as I liked the one that I installed on my HTC, but couldn't find one.
Can anyone help me to understand what has happed to make this phone go soooooooo slow. Even if I am unable to instal Android 4 and above, I would still need the link for Lewa OS. If anyone has it, that'd be most helpful.
Click to expand...
Click to collapse
Mainly, the problem is on the way the different roms use the dalvik vm and the way aforementioned roms are unable to leash cache used. So, my recomendation is a good rom which a good preset over dalvik used of memory and applications like App Cache Cleaner to erase the cache every now and them.
For me the perfect combination is:
1. Stable CM10.2.1 rom
2. Kernel Semaphore 3.3.0 (avoid version 3.3.0s because it gives problems with Netflix, besides version 3.3.0 is perfect and you can activate bigmem with Semaphore Manager App, so 3.3.0s is nonsense) (NOTE: You need odin for installing it, follow this instruction)
3. Gapps: gapps-jb-20130813-signed.zip
4. Semaphore manager app. Settings for Semaphore Manager:
- Smartassv2 Governor: Awake ideal freq 900000 / Up rate 10000 / Down rate 99000 / Max CPU 50 / Min CPU 20 / Ramp up 300000 / Ramp down 300000 / Sleep ideal freq 300000 / Sample rate jiffies 2.
- Deep Idle: Enable
- Lock min freq to 100Mhz: Disable
- Active Scheduler: CFQ
- Bigmem: Enable
5. My build.prop to be placed within /system/ (remember to set for this file rw-r--r-- permissions and change owner to root).
6. A launcher like Zeam Launcher or Lightning Launcher
7. And finally an installed App Cache Cleaner Pro to erase the cache every now and them.
Best.
I have flashed CM10.2.with minimal gapps, but now unable to connect to internet. Tried flashing many times after wiping data, clearing cache and clearing Dalvik cache, but still unable to connect to internet.
EDIT: That as a temp problem with my carrier network. So, I have installed CM10.2 with above details. Working fine so far. Will let you know if there is any problem with this setup.
samrat_castle said:
I have flashed CM10.2.with minimal gapps, but now unable to connect to internet. Tried flashing many times after wiping data, clearing cache and clearing Dalvik cache, but still unable to connect to internet.
EDIT: That as a temp problem with my carrier network. So, I have installed CM10.2 with above details. Working fine so far. Will let you know if there is any problem with this setup.
Click to expand...
Click to collapse
Try to flash the final build 2.2 of SlimBean 4.3 with SlimGapps.
It is faster than CM10.2 and has much better battery life (especially if you use TRDS mode)
tetakpatalked from OPO
samrat_castle said:
I have flashed CM10.2.with minimal gapps, but now unable to connect to internet. Tried flashing many times after wiping data, clearing cache and clearing Dalvik cache, but still unable to connect to internet.
EDIT: That as a temp problem with my carrier network. So, I have installed CM10.2 with above details. Working fine so far. Will let you know if there is any problem with this setup.
Click to expand...
Click to collapse
Good to know, enjoy.
tetakpatak said:
Try to flash the final build 2.2 of SlimBean 4.3 with SlimGapps.
It is faster than CM10.2 and has much better battery life (especially if you use TRDS mode)
tetakpatalked from OPO
Click to expand...
Click to collapse
Thanks for your piece of advice, I tried it long time ago but I still prefer a CM10.2.1 + a tweaked Semaphore 3.3.0 + Zeam Launcher + my build.prop + minor removing of CM apps.
Best.
kuskro said:
Good to know, enjoy.
Thanks for your piece of advice, I tried it long time ago but I still prefer a CM10.2.1 + a tweaked Semaphore 3.3.0 + Zeam Launcher + my build.prop + minor removing of CM apps.
Best.
Click to expand...
Click to collapse
Guys, we have got Android Lollipop 5.0.2 for our device, though an alpha build from @humberos. I am using it as of now, though without Gapps. Its Beautiful! And working!
Download Link: https://drive.google.com/folderview?id=0B7hG2LTQDF3ifjhybEs3TGVGNDlsRk1vS05vNGZOdjVDVXRRbVRwNmVJV2dodGEzdDFmVDA&usp=sharing&tid=0B7hG2LTQDF3ifnZrdWk1MXZYTnZ2dlpUb2JSRHE0Z0l6QmpULWh3SFg2bXdjQTNLbGNMZjQ
More Info: http://forum.xda-developers.com/showthread.php?t=2488037&page=96
samrat_castle said:
Guys, we have got Android Lollipop 5.0.2 for our device, though an alpha build from @humberos. I am using it as of now, though without Gapps. Its Beautiful! And working!
Download Link: https://drive.google.com/folderview...Z2dlpUb2JSRHE0Z0l6QmpULWh3SFg2bXdjQTNLbGNMZjQ
More Info: http://forum.xda-developers.com/showthread.php?t=2488037&page=96
Click to expand...
Click to collapse
I have tried to flash the zip last week but it stucked on "extracting system" every time. It just updated my recovery to TWRP 2.8.4.1, but didn't even reboot.
Maybe it is phone that isn't OK anymore. Its internal memory isn't working correctly anmore.
tetakpatalked from Nexus 7 flo
It takes approx 15-20 minutes for installation. You need to be a bit patient with this
samrat_castle said:
It takes approx 15-20 minutes for installation. You need to be a bit patient with this
Click to expand...
Click to collapse
Cool I tought it failed as the installation process never took that long yet. I will try again then.
tetakpatalked from N7100
OK, I 've flashed it. Lollipop on the i9000. It took 19min until the process was finished.
I have also flashed PA Gapps pico by Tkruzz, all other are probably too big.
The Omni LP alone (just Omni 5.0) is extremely smooth, but quite slow.
After flashing of Gapps (which BTW work perfectly fine) my i9000 has turned into the slowest device I ever used. It is way slower than Eclair, actually just same slow like my S8000 running CM7 from externalSD card.
It takes 15sec to open PlayStore, up to 2min to download and install an app (even smaller apps), about 5-10 sec to react on pressing any button and the device is often running out of memory and soft reboots are the result. It takes up to 15sec until the keyboard appears etc.
Otherwise all important functions work fine, but Lollipop is too big a task for the i9000 and except that it just works, there is simply no many people who would like to use a device with auch slowdowns. Even biggest fans of the i9000 (I might be among them) will have to face the fact that Android 5.0 is actually out of the hardware capacity of the S1
tetakpatalked from Nexus 7 flo
I myself am using CM10.2. Which works fine, with just a bit of lag. Its either that or gingerbread. Anyways, omni 5.0 for i9000 is just experimental at this stage, with promise for a more stable build by @humberos. It may be light on the system, but who knows.
I'd say buy a newer model if we need new OS as software is as good as its hardware and vice versa.
Omni is excellent and very stable, although in Alpha stage. That isn't my point.
LP system cannot get smaller, the i9000 is simply too slow for Android 5.0
It was just an info for people who dream to use Lollipop on i9000. It is a huge slowdown.
I have much faster devices but I don't use LP even there.
tetakpatalked from the legendary i9000 running Omni 5.0
Hey,
I suggest you guys to use SlimBean v2.9 with the latest Slim JB gapps. The phone will be quite fast, despite this device is very old... This version of SlimBean is not available on their site but is here:
https://mega.co.nz/#!6xJnVaBY!qhF1g99N0zE1w6XZd3E2IPgvlBgAJWGrYluZehgajNE
I think further versions are significantly slower and this one offers quite a lot of customization as well. Good luck with the i9000 [emoji3]
aToS88 said:
Hey,
I suggest you guys to use SlimBean v2.9 with the latest Slim JB gapps. The phone will be quite fast, despite this device is very old... This version of SlimBean is not available on their site but is here:
https://mega.co.nz/#!6xJnVaBY!qhF1g99N0zE1w6XZd3E2IPgvlBgAJWGrYluZehgajNE
I think further versions are significantly slower and this one offers quite a lot of customization as well. Good luck with the i9000 [emoji3]
Click to expand...
Click to collapse
Which Android version is that Slim build and why isn't it on the Slim server?
Is there a md5 checksum?
tetakpatalked from N7100
It's an android 4.1.2 and SlimBean version 2.9. It's not on the official site because it's not the latest 4.1.2 version they have distributed. That's the 3.1 if I'm not mistaken.
Sorry I don't have an md5 for the file...
aToS88 said:
It's an android 4.1.2 and SlimBean version 2.9. It's not on the official site because it's not the latest 4.1.2 version they have distributed. That's the 3.1 if I'm not mistaken.
Sorry I don't have an md5 for the file...
Click to expand...
Click to collapse
Good to know. How is the battery life there? With CyanogenMod I remember that 4.1 and 4.2 had terrible battery life, while 4.3 was a lot better.
tetakpatalked from Nexus 7 flo
It can last from morning till the evening but of course depends on the usage.
From what I remember Slim on 4.1.2 was real solid, probably one of my favourite roms. 3.1 wasn't that bad either
Sent from my Note 4
Soryuu said:
From what I remember Slim on 4.1.2 was real solid, probably one of my favourite roms. 3.1 wasn't that bad either
Sent from my Note 4
Click to expand...
Click to collapse
I've tried today build 2.9
It worked fine but for some strange reason it didn't recognize my wifi router...all other networks just fine, but not the important one. I couldn't solve it, tried everything.
But I have feeling that SlimBean 4.3 is at least as good.
Hey, BTW I have filmed Omni 5.0.2, I will try to edit it and upload tomorrow
tetakpatalked from Nexus 7 flo
tetakpatak said:
I've tried today build 2.9
It worked fine but for some strange reason it didn't recognize my wifi router...all other networks just fine, but not the important one. I couldn't solve it, tried everything.
But I have feeling that SlimBean 4.3 is at least as good.
Hey, BTW I have filmed Omni 5.0.2, I will try to edit it and upload tomorrow
tetakpatalked from Nexus 7 flo
Click to expand...
Click to collapse
I don't think I ever got around to trying the 4.3 version, I remember the 4.2.2 version was a bit hit and miss when it came to battery (but then again, all 4.2.2 roms save Gamerzrom and a few others were). By the time the 4.4.x version came out I moved onto the S3 so I can't vouch for that, but Slim roms are pretty good
And you legend, thanks a lot