Related
Hi everyone, I was wondering if any DEVs here could check if the Samsung Rugby Smart i847 source code is compatible with any of the Galaxy W development. I have no experience with compiling and understanding kernels but I do know that both phones should have the same chipset with the exception of the modem and possibly the camera or screen. The partitions are very similar with the exception of two partitions.
I guess not. because having different partitions could mean a lot. Also device drivers are all device specific. Should you try to flash.. say.. stock rom, you might experience bootloops or possibly bricking your phone
The risk of softbrick is large. I've read somewhere on the forum that the hardware on the Xperia Arc was the same of our phone, just the processor clock is lower. SO I decided to flash a ROM and got a hard softbrick that I've took some hours to revert.
Interestingly, the CPU hardware is labeled as I8150. I assume that Samsung took the Galaxy W and slapped some better hardware on top of it .(AMOLED screen instead of TFT) For the modem, I'm unsure if it's the same or different because I noticed on some settings that the WCDMA band were 850, 900, 1900, 2100.
The similar partitions are
# cat /proc/partitions
major minor #blocks name
179 0 3864576 mmcblk0
179 1 106495 mmcblk0p1
179 2 500 mmcblk0p2
179 3 3596 mmcblk0p3
179 4 1 mmcblk0p4
179 5 5120 mmcblk0p5
179 6 20000 mmcblk0p6
179 7 3072 mmcblk0p7
179 8 5632 mmcblk0p8 //boot
179 9 6488 mmcblk0p9
179 10 3072 mmcblk0p10 //rmt
179 11 3072 mmcblk0p11 //rmt
179 12 8192 mmcblk0p12 //persist
179 13 7680 mmcblk0p13 //recovery
179 14 5120 mmcblk0p14 //param
179 15 547840 mmcblk0p15 //system
179 16 204800 mmcblk0p16 //cache
179 17 1136640 mmcblk0p17 //data
179 18 500 mmcblk0p18 //preload <-- this is the only difference besides the sdcard (51200 instead of 500)
179 19 500 mmcblk0p19
179 20 3596 mmcblk0p20
179 21 5120 mmcblk0p21
179 22 20000 mmcblk0p22
179 23 5120 mmcblk0p23
179 24 7000 mmcblk0p24
179 25 5120 mmcblk0p25
179 26 5120 mmcblk0p26
179 27 5120 mmcblk0p27 //efs
179 28 1693696 mmcblk0p28 //sdcard
Click to expand...
Click to collapse
The only difference would most likely be the screen and possibly modem to allow porting from the galaxy w which shouldn't be too complicated from the source code given by Samsung.
Almost works!
wathou6 said:
The only difference would most likely be the screen and possibly modem to allow porting from the galaxy w which shouldn't be too complicated from the source code given by Samsung.
Click to expand...
Click to collapse
I have a Rugby. I went ahead (crazy me) and flashed CM9 Alpha 4 on it. Only one minor problem: no screen display! Totally blank! The screen hardware is fine because I can see it works during fastboot, but Clockwork Mod and CM9 don't display anything.
Anything I could do to help the developers, let me know!
Toughdroid said:
I have a Rugby. I went ahead (crazy me) and flashed CM9 Alpha 4 on it. Only one minor problem: no screen display! Totally blank! The screen hardware is fine because I can see it works during fastboot, but Clockwork Mod and CM9 don't display anything.
Anything I could do to help the developers, let me know!
Click to expand...
Click to collapse
You are crazy! Here's a working Clockwork Mod if you can use adb http://rootzwiki.com/topic/27265-recovery-cwmr-5504-for-samsung-sghi847-rugby-smart/
The screen display don't showing up is a kernel issue since the Rugby uses a different screen (AMOLED). I don't really have a backup for you to restore to though.
wathou6 said:
You are crazy!
Click to expand...
Click to collapse
Apparently I am. I have now hard-bricked my Rugby.
wathou6 said:
Here's a working Clockwork Mod if you can use adb
Click to expand...
Click to collapse
That is cool. Unfortunately I tried to install it like this:
dd if=recovery.img of=/dev/block/mmcblk0p13
It copied into the partition, now the device won't do anything. I'm sure I copied it into the wrong partition. Any ideas how to recover from this point? I can't even get into fastboot now.
Galaxy W i8150 config.gz
Toughdroid said:
I have a Rugby. I went ahead (crazy me) and flashed CM9 Alpha 4 on it. Only one minor problem: no screen display! Totally blank! The screen hardware is fine because I can see it works during fastboot, but Clockwork Mod and CM9 don't display anything.
Anything I could do to help the developers, let me know!
Click to expand...
Click to collapse
Could someone please post their /proc/config.gz file from the Galaxy W i8150? I want to take a look at the differences between the kernels to try to figure out why the screen doesn't show anything on the Rugby Smart.
hope this helps
https://dl.dropbox.com/u/485128/config.gz
(i tried to copy/paste the text but it was too long. so there you go
Ekril said:
https://dl.dropbox.com/u/485128/config.gz
(i tried to copy/paste the text but it was too long. so there you go
Click to expand...
Click to collapse
Thanks man. I just looked at the diff between the two, and there are only a handful of differences. Hopefully I can get this sorted out. I am new to Android development, but have been compiling Linux kernels for ~15 years of so now :good:
anything else i can do?
I am a total noob with android development, but i have a i847 Rugby Smart coming, got it on ebay for 210 $, i will document myself and start android developing because, it seems, this device has close to none support at all, despite the fact that it ws released in march, i might be able to get the stock rom from AT&T too. Being a dedicated AT&T phone i doubt they will release any update soon, so we must do with what we have.
pkkilleru said:
I am a total noob with android development, but i have a i847 Rugby Smart coming, got it on ebay for 210 $, i will document myself and start android developing because, it seems, this device has close to none support at all, despite the fact that it ws released in march, i might be able to get the stock rom from AT&T too. Being a dedicated AT&T phone i doubt they will release any update soon, so we must do with what we have.
Click to expand...
Click to collapse
Any progress on this? I myself have a Rugby Smart and would love to see any firmware updates. I'll even volunteer it to testing.
I also have a good amount of excess cpu / ram / storage if you need help with any builds.
Count me in on this, I plan on getting one and would like to see something other than stock on it.
Sent from my SGH-I897 using xda app-developers app
kemonine96 said:
Any progress on this? I myself have a Rugby Smart and would love to see any firmware updates. I'll even volunteer it to testing.
I also have a good amount of excess cpu / ram / storage if you need help with any builds.
Click to expand...
Click to collapse
I've tried arco's Galaxy W rom many different ways. Tried it just as he packaged it, but w/ the Rugby Smart kernel. And I did several different combinations of arco's rom w/ various libs/firmwares/binaries from the Rugby Smart added in. Unfortunately I have not been able to get anything to boot successfully.
I am still going to keep trying - this has been a good learning process for me, as I have ~15 years experience w/ Linux but never dabbled in Android. If anyone has any tips or can help out, speak up!
nicedream06 said:
I've tried arco's Galaxy W rom many different ways. Tried it just as he packaged it, but w/ the Rugby Smart kernel. And I did several different combinations of arco's rom w/ various libs/firmwares/binaries from the Rugby Smart added in. Unfortunately I have not been able to get anything to boot successfully.
I am still going to keep trying - this has been a good learning process for me, as I have ~15 years experience w/ Linux but never dabbled in Android. If anyone has any tips or can help out, speak up!
Click to expand...
Click to collapse
I read on the Cyanogen forums that the display is different on the Rugby Smart than the normal Galaxy W variants, have you tried changing any kernel options in the Galaxy W variant sources?
I have a stock device currently and if you need anything from proc / sys / wherever I can pass along, just let me know.
Also, if you have any instructions on generating an ODIN image, I may be able to put something together for flashing back to stock.
kemonine96 said:
I read on the Cyanogen forums that the display is different on the Rugby Smart than the normal Galaxy W variants, have you tried changing any kernel options in the Galaxy W variant sources?
I have a stock device currently and if you need anything from proc / sys / wherever I can pass along, just let me know.
Also, if you have any instructions on generating an ODIN image, I may be able to put something together for flashing back to stock.
Click to expand...
Click to collapse
I haven't tried changing any of the kernel options in arco's cyanagen build, but based on the config.gz files from the stock kernels in both of these devices there are very few differences. Here is the output when I diff the two files:
Code:
diff config-i8150 config-i847
4c4
< # Sat Apr 14 09:38:45 2012
---
> # Sat Jan 28 15:23:37 2012
271,272c271,272
< CONFIG_MACH_ANCORA=y
< # CONFIG_MACH_APACHE is not set
---
> # CONFIG_MACH_ANCORA is not set
> CONFIG_MACH_APACHE=y
274a275,277
> CONFIG_HW_REV_USING_SMB328=0
> CONFIG_MICROUSB_DEBUG=y
> CONFIG_BATT_MICROVOLT_UNIT=y
387c390
< # CONFIG_VP_A2220 is not set
---
> CONFIG_VP_A2220=y
1046c1049
< CONFIG_SAMSUNG_FM_SI4709=y
---
> # CONFIG_SAMSUNG_FM_SI4709 is not set
1047a1051
> # CONFIG_AUTO_INPUT_EVENT_GENERATOR is not set
1232c1236
< # CONFIG_INPUT_SECBRIDGE is not set
---
> CONFIG_INPUT_SECBRIDGE=y
1277c1281
< # CONFIG_TOUCHSCREEN_MXT224 is not set
---
> CONFIG_TOUCHSCREEN_MXT224=y
1289,1290c1293
< CONFIG_TOUCHSCREEN_MELFAS_MCS8000=y
< CONFIG_TOUCHSCREEN_MELFAS_FIRMWARE_UPDATE=y
---
> # CONFIG_TOUCHSCREEN_MELFAS_MCS8000 is not set
1314c1317
< # CONFIG_GYRO_K3G is not set
---
> CONFIG_GYRO_K3G=y
1379c1382
< # CONFIG_DCC_TTY is not set
---
> CONFIG_DCC_TTY=y
1500c1503
< CONFIG_BATTERY_ANCORA=y
---
> CONFIG_BATTERY_APACHE=y
1760,1761c1763,1764
< # CONFIG_QUP_EXCLUSIVE_TO_CAMERA is not set
< CONFIG_SENSOR_SR030PC30=y
---
> CONFIG_QUP_EXCLUSIVE_TO_CAMERA=y
> # CONFIG_SENSOR_SR030PC30 is not set
1763c1766
< # CONFIG_SENSOR_SR130PC10 is not set
---
> CONFIG_SENSOR_SR130PC10=y
1837c1840
< # CONFIG_FB_MSM_LCDC_S6E63M0_WVGA is not set
---
> CONFIG_FB_MSM_LCDC_S6E63M0_WVGA=y
1839c1842
< CONFIG_FB_MSM_LCDC_SAMSUNG_ANCORA=y
---
> # CONFIG_FB_MSM_LCDC_SAMSUNG_ANCORA is not set
1863c1866
< # CONFIG_FB_MSM_LCDC_S6E63M0_WVGA_PANEL is not set
---
> CONFIG_FB_MSM_LCDC_S6E63M0_WVGA_PANEL=y
1865c1868
< CONFIG_FB_MSM_LCDC_SAMSUNG_ANCORA_PANEL=y
---
> # CONFIG_FB_MSM_LCDC_SAMSUNG_ANCORA_PANEL is not set
2218c2221
< CONFIG_MMC_MSM_CARD_HW_DETECTION=y
---
> # CONFIG_MMC_MSM_CARD_HW_DETECTION is not set
2221d2223
< CONFIG_MMC_MSM_SDC1_DUMMY52_REQUIRED=y
2224d2225
< CONFIG_MMC_MSM_SDC2_DUMMY52_REQUIRED=y
2228d2228
< # CONFIG_MMC_MSM_SDC4_DUMMY52_REQUIRED is not set
2230c2230
< # CONFIG_MMC_MSM_PROG_DONE_SCAN is not set
---
> CONFIG_MMC_MSM_PROG_DONE_SCAN=y
2685c2685
< CONFIG_CRYPTO_RNG=y
---
> CONFIG_CRYPTO_RNG=m
2771c2771
< CONFIG_CRYPTO_ANSI_CPRNG=y
---
> CONFIG_CRYPTO_ANSI_CPRNG=m
2773,2775c2773,2775
< CONFIG_CRYPTO_DEV_QCRYPTO=y
< CONFIG_CRYPTO_DEV_QCE=y
< CONFIG_CRYPTO_DEV_QCEDEV=y
---
> CONFIG_CRYPTO_DEV_QCRYPTO=m
> CONFIG_CRYPTO_DEV_QCE=m
> CONFIG_CRYPTO_DEV_QCEDEV=m
You can see that there are a few FB options that are obvious differences, which is probably related to the different displays. I haven't had any luck getting it to work though.
Oh and my device is stock now. Well, it's the stock ROM, rooted and with all the bloatware removed. But I am able to query the /proc and /sys directories on my device.
nicedream06 said:
I haven't tried changing any of the kernel options in arco's cyanagen build, but based on the config.gz files from the stock kernels in both of these devices there are very few differences. Here is the output when I diff the two files:
You can see that there are a few FB options that are obvious differences, which is probably related to the different displays. I haven't had any luck getting it to work though.
Click to expand...
Click to collapse
From what I see in the diff you posted, I'd try using the config from the Rugby Smart in conjunction with the rest of arco's build and see what happens. To me it looks like the display options are the key differences to getting his kernel working with our device.
kemonine96 said:
From what I see in the diff you posted, I'd try using the config from the Rugby Smart in conjunction with the rest of arco's build and see what happens. To me it looks like the display options are the key differences to getting his kernel working with our device.
Click to expand...
Click to collapse
I'm going to give that a try when I get a chance, but I have a question about building the kernel from arco's source.
His github repository doesn't have a .config file for building his kernel - so how can I build it with the options he uses for his ROM? I know you can extract the config.gz from a running kernel but I don't have that. If I run make menuconfig, will it automatically get the correct options from the various Kconfig files in the source tree?
nicedream06 said:
I'm going to give that a try when I get a chance, but I have a question about building the kernel from arco's source.
His github repository doesn't have a .config file for building his kernel - so how can I build it with the options he uses for his ROM? I know you can extract the config.gz from a running kernel but I don't have that. If I run make menuconfig, will it automatically get the correct options from the various Kconfig files in the source tree?
Click to expand...
Click to collapse
I do not know offhand, I've never tried to build a version of CM before. I was going to investigate the build process in the coming days, see if I can get my environment setup and ready to go for testing.
I am curious though: how were you able to recover after flashing arco's build back to a working device?
I'm using system tuner by 3c and applied their recommended settings in the "sysctl" tab in the tweaks section, and my phone is much worse off for it. However, there is no way to return it to stock, and i can't find the stock values on the net.
My request is, could anyone running a rooted OneX install system tuner (theres a free version) and post up all the standard values appearing in the sysctl section? I would be eternally grateful via my pushing of the thanks button
Here you go :
fs.file-max - 99902
fs.inotify.max_queued_events -16384
fs.inotify.max_user_instances-128
fs.inotify.max_user_watches-8192
fs.lease-break-time-45
fs.nr_open-1048576
kernel.hung_task_timeout_secs- 0s
kernel.panic- 10s
kernel.panic_on_oops- enabled
kernel.random.read_weakup_threshold-64
kernel.random.write_wakeup_threshold-128
kernel.sched_child_runs_first- disabled
kernel.sched_latency_ns-6ms666us666
kernel.sched_min_granularity_ns-1ms500
kernel.sched_wakeup_granularity_ns-1ms333us332
kernel.threads-max-15612
net.core.rmem_max-0.12MB
net.core.wmem_max-0.12MB
net.ipv4.tcp_rmem- 4095 87380 110208
net.ipv4.tcp_tw_recycle-disabled
net.ipv4.tcp_wmem-4096 16384 110208
vm.block._dumb-disabled
vm.dirty_background_ratio- 30%
vm.dirty_expire_centisecs-2s000
vm.dirty_ratio-0%
vm.dirty_writeback-centisecs - 5s000
vm.drop_caches-0
vm.laptop_mode-disabled
vm.min_free_kbytes-1.88MB
vm.min_free_order_shift-4
vm.oom_kill_allocating_task-disabled
vm.page-cluster-3
vm.panic_on_oom-disabled
vm.swapiness-100%
vm.vfs_cache_pressure-100%
DONE !
Enjoy it ! I hope that this will help you !
Awesome thanks a lot
Hi, like in topic - i've at last installed CM 9.0 FXP 130, but when i enter system info its showing only 360MB of ram, instead of 512 (SEX PRO got 512 as far as i know).
Why is that happening? Is this bug, or i don't know something?
I think you can allocate more RAM to your phone...
That's not bug/issue. 360 mb is user-available from 512
Hello! I haven't posted much here in the Nitro forums, but I got my p930 a couple years ago.
After loaning it out for a bit, I recently got it back, and decided to get Lollipop running on it (jumping straight to 5.1) :victory:
I've had experience porting newer versions of Android with another device (HTC Aria), but I can't say I'm extremely good at it.
I have most stuff working, but I might not be able to get everything working on my own.
Also I'm not very good at making a thread look good, so please excuse everything below being hard to read
It is based on miroslav's open source device trees and 3.4 kernel from github.com/NitroKK, but with the extra stuff removed to make it more like "stock" CM.
Bugs & things that currently don't work are:
- Camera
- Phone radio
- GPS
- Bluetooth is a bit sketchy
- MHL (aka HDMI out)
- SELinux enforcing mode
- Screen does not turn on sometimes - this is really hard to reproduce, so I'm not completely sure why... It doesn't happen too often though
- Probably more
I am releasing this as a "preview" because of the camera, phone, and GPS being broken. Once those are fixed, the preview tag will be dropped
GPS should be pretty easy to fix, but might need the phone stuff working first. Camera and phone I'm not really sure where to go next..
Notes:
LG SU640 support: miroslav's compatibility patch linked in his CM11 thread should work fine.
If it doesn't, let me know (with a log if possible) and I'll see what I can do...
If your recovery asks to fix or install root when rebooting, just hit no - it's outdated and doesn't know the correct place to look for root anymore.
If you need to use root, you'll need to enable development settings by repeatedly tapping Build number in About phone, then turn on Root access in Developer options.
I recommend changing the launcher's app drawer mode to paged, as the effect when scrolling fast on the vertical drawer runs very slow on this device (and not great on newer devices either).
There is only about 90MB free on the /system partition, so Google Apps packages will have to be somewhat light-weight to fit in that.
I have linked to the one I use below, but if you use your own, make sure it's smaller than 90MB after extracting, not just as a zip.
Because of the quality improvements on Lollipop's UI, the performance is a bit worse than KitKat.
A flag can be enabled to give a much better framerate and general responsiveness etc, but at the cost of stability.
Just add this line to build.prop then reboot:
Code:
persist.hwc.mdpcomp.enable=true
It runs much better, but causes really bad screen glitches in some places (and maybe other stuff like the screen not turning on more often).
In the future I would like to fix it, but for now I'm leaving it off by default.
If anyone would like to help fix things, full source on everything I have changed is at the following GitHub organization:
https://github.com/NitroCM
Pull requests, Issues, whatever are welcome, and I can add people to it upon request (as long as I can trust you )
On to the downloads! Pick whichever mirror works best for you.
20150809 - 9bc4906aaa21caa36217d9186bb2bb36
Google Drive: https://goo.gl/sMHQYz
MediaFire: http://www.mediafire.com/download/bcjbs0jpnj1jrpd/cm-12.1-20150809-UNOFFICIAL-p930.zip
Mega: https://goo.gl/e4Q16q
xda dev-db: http://forum.xda-developers.com/devdb/project/dl/?id=13902
Google Apps: https://goo.gl/YxlfU0 or https://goo.gl/Mw9uPt
XDA:DevDB Information
CyanogenMod 12.1 (unofficial), ROM for the LG Nitro HD
Contributors
WinSuk, miroslav_mm
Source Code: https://github.com/NitroCM
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.4.x
Based On: CyanogenMod
Version Information
Status: Testing
Created 2015-08-10
Last Updated 2015-08-16
Holy sweet buttery jesus. you did it.
Thanks for doing this. Finally some some extra life to this device. Unfortunately I get boot-loops when flashing this ROM, but that seems associate with partition sizes on this devices and miroslav's CM11 kernel (mine are the smaller size). I probably have to factory flash the right ICS kdz to fix it. Not sure yet what to do to get the right sizes, but I still appreciate your effort so at least there is a way forward. Keep up the good work!
miji2 said:
Thanks for doing this. Finally some some extra life to this device. Unfortunately I get boot-loops when flashing this ROM, but that seems associate with partition sizes on this devices and miroslav's CM11 kernel (mine are the smaller size). I probably have to factory flash the right ICS kdz to fix it. Not sure yet what to do to get the right sizes, but I still appreciate your effort so at least there is a way forward. Keep up the good work!
Click to expand...
Click to collapse
Hmm... I'm not completely sure which bootloader I have installed, but I think it's the gingerbread one (v10).
Does the boot animation show up? (Cid with a pulsing circle behind him)
If so, the system partition is definitely mounting correctly, and you probably just need to wait longer (the first boot takes a long time).
If not (it's stuck on the LG logo or keeps rebooting to the LG logo), does miro's CM11 ROM work for you? (if you have tried it)
WinSuk said:
Hmm... I'm not completely sure which bootloader I have installed, but I think it's the gingerbread one (v10).
Does the boot animation show up? (Cid with a pulsing circle behind him)
If so, the system partition is definitely mounting correctly, and you probably just need to wait longer (the first boot takes a long time).
If not (it's stuck on the LG logo or keeps rebooting to the LG logo), does miro's CM11 ROM work for you? (if you have tried it)
Click to expand...
Click to collapse
So the device would only show the LG logo then reboot, vibrate, and repeat. It behaved same with miroslav's CM11 but it was just fine flashing and running stock CM11.
my partition sizes were:
Code:
Filesystem Size Used Free Blksize
/dev 371.2M 136.0K 371.1M 4096
/sys/fs/cgroup 371.2M 12.0K 371.2M 4096
/mnt/asec 371.2M 0.0K 371.2M 4096
/mnt/obb 371.2M 0.0K 371.2M 4096
/mnt/fuse 371.2M 0.0K 371.2M 4096
/system 503.9M 352.6M 151.4M 4096
/cache 315.0M 5.2M 309.7M 4096
/data 2.2G 113.9M 2.0G 4096
/persist 7.9M 4.1M 3.8M 4096
/mpt 15.5M 1.1M 14.4M 1024
/tombstones 72.0M 4.1M 67.9M 4096
/firmware 64.0M 22.8M 41.2M 16384
/modem 199.8M 27.3M 172.5M 4096
Here's what I did to fix:
a) debrick with ICS kdz http://forum.xda-developers.com/showthread.php?t=2044645
b) rooted with http://forum.xda-developers.com/showthread.php?t=1886460
b) unlock bootloader with http://forum.xda-developers.com/showthread.php?t=2598278
c) flash recovery (TWRP) then this ROM
and now my partition sizes are:
Code:
Filesystem Size Used Free Blksize
/dev 383.8M 36.0K 383.7M 4096
/sys/fs/cgroup 383.8M 12.0K 383.8M 4096
/mnt/asec 383.8M 0.0K 383.8M 4096
/mnt/obb 383.8M 0.0K 383.8M 4096
/system 495.5M 402.6M 92.9M 4096
/cache 134.0M 4.3M 129.7M 4096
/data 2.2G 245.1M 1.9G 4096
/persist 7.9M 4.6M 3.3M 4096
/mpt 15.8M 1.4M 14.4M 1024
/tombstones 71.9M 4.0M 67.9M 4096
/firmware 64.0M 22.8M 41.2M 16384
/modem 199.8M 27.7M 172.0M 4096
And now your ROM as well as miroslav's CM11 install without a hitch and work great. Lots of work, but well worth it. Thanks for giving me a reason to go through all that
miji2 said:
and now my partition sizes are:
Code:
Filesystem Size Used Free Blksize
/dev 383.8M 36.0K 383.7M 4096
/sys/fs/cgroup 383.8M 12.0K 383.8M 4096
/mnt/asec 383.8M 0.0K 383.8M 4096
/mnt/obb 383.8M 0.0K 383.8M 4096
/system 495.5M 402.6M 92.9M 4096
/cache 134.0M 4.3M 129.7M 4096
/data 2.2G 245.1M 1.9G 4096
/persist 7.9M 4.6M 3.3M 4096
/mpt 15.8M 1.4M 14.4M 1024
/tombstones 71.9M 4.0M 67.9M 4096
/firmware 64.0M 22.8M 41.2M 16384
/modem 199.8M 27.7M 172.0M 4096
And now your ROM as well as miroslav's CM11 install without a hitch and work great. Lots of work, but well worth it. Thanks for giving me a reason to go through all that
Click to expand...
Click to collapse
I see, cool
I don't remember at all what I did, but my partition sizes are indeed the same as what you have now.
sweet..
any updates yet ? am dying to try out new updates :sly:
Loo Ney said:
sweet..
any updates yet ? am dying to try out new updates :sly:
Click to expand...
Click to collapse
Not really The radio is really stubborn.
Bluetooth is better, but still crashes sometimes. Camera is closer to working, but still doesn't.
I haven't been working on it until just a couple weeks ago, so maybe I'll figure something out soon (maybe )
WinSuk said:
Not really The radio is really stubborn.
Bluetooth is better, but still crashes sometimes. Camera is closer to working, but still doesn't.
I haven't been working on it until just a couple weeks ago, so maybe I'll figure something out soon (maybe )
Click to expand...
Click to collapse
GREAT bro..keep up the good work, i will be waiting for an update :good::good:
Update?
thinhx2 said:
Update?
Click to expand...
Click to collapse
I wasn't able to figure anything out except for bluetooth working slightly better as stated in a previous post - anything further would require someone who better knows how things work.
Also, my p930 is currently being used daily by a family member, so I can't try any changes out on it (I wasn't working on it at all before that though).
This will probably forever be a "hey look it boots and you can see stuff" demo
WinSuk said:
I wasn't able to figure anything out except for bluetooth working slightly better as stated in a previous post - anything further would require someone who better knows how things work.
Also, my p930 is currently being used daily by a family member, so I can't try any changes out on it (I wasn't working on it at all before that though).
This will probably forever be a "hey look it boots and you can see stuff" demo
Click to expand...
Click to collapse
Thank for work. And bro can make cm13 or aosp 6.0? My friend use this devicem he can test. Thank bro reply
Lets get Marshmallow running on this device
Maybe if we get Marshmallow on this device, things will be easier to be fixed.
Project Beyond Horizon
After stumbling over through most part of Xda Forums, About Improving Battery Backup, I am here with my interactive governor tweaks for our Very Own Device.
Before explaining more I would like to quote few lines by @soniCron who brought the breakthrough results on which this mod is based on
soniCron said:
This isn't a guide to get 36-hour battery life... provided you never use your phone. That's deep sleep optimization, which is lovely and all, but what good is the phone if you can never use it?! I'm talking about 4-6(should try to make it even more) hour screen on, actual hands-on usage times! Without compromising anything, you can get 7-8 hour screen on usage with regular, no-compromise usage habits: daytime visible screen brightness, both radios on, sync on, network location on, all the regular usage features, the whole kit and kaboodle... all smooth as a baby's butt and snappy as a Slim Jim!
Click to expand...
Click to collapse
So Let's Get Straight Into Action
So what is it Based Upon: This Interactive Governor tweak utilizes the Big.Little technology
Now Some Specs: We have Two Variants with different SOCs Snapdragon 415 and 616.
Snapdragon 415 -
4 cores a.k.a clocked at 998mhz- They are very efficient
4 cores a.k.a clocked at 1363mhz big for high and constant loads -Not Efficient
Snapdragon 616
4 cores at 1209MHz
4 cores at 1459MHz
Requirements:
LENOVO VIBE K5/K5 PLUS
A ROOTED DEVICE
ElementalX kernel manager(Preferred) or Kernel Auditor
A Rom Based on @Harry8242 kernel(I am on aex 5.1; You can try others too but make sure it detects big and little cores(need confirmation for other kernels)
So The Core Idea Behind this was To Restrict As Much Idle Drain as possible and Maintain Best Performance. Our Custom Roms Are Now In a state to give the best possible performance but What I desired was to Maintain Same Battery Efficiency. And Yes, I did to maximum extent possible now.
DOWNLOADS
V2- For Both Variants -Click Here
V1-CLICK HERE
How to Apply It:
For EX Kernel Manager Users(The Easy Way)
Download the file
Open the ElementalX kernel manager app
Under CPU section go to governor options
There click on save and save the profile as "default"
Next go to your file manager find ElementalX folder.
Paste the downloaded file in gov_profiles folder.
Open EX manager app again,under governor option click on load and select BEYOND HORIZON
Enjoy
For Kernel Auditor Users:- You need to manually input these values (Don't forget to toggle the apply on boot).
V2(LATEST)-- CLICK HERE
FOR BIG CLUSTER
Code:
go_hispeed_load: 99
above_hispeed_delay: 60000 400000:10000 533333:70000 800000:80000 960000:90000
timer_rate: 60000
hispeed_freq: 200000
timer_slack: 480000
[B]target_loads: [/B] 90 200000:73 345600:78 400000:86 533333:73 800000:90 960000:84 1113600:98 1363200:99
min_sample_time: 0
boost: 0
boostpulse_duration: 0
align_windows: 1
use_migration_notif: 1
use_sched_load: 0
max_freq_hysteresis: 0
For Little Cluster
Code:
go_hispeed_load: 91
above_hispeed_delay: 0
timer_rate: 60000
hispeed_freq: 200000
timer_slack: 480000
[B]target_loads: [/B] 90 200000:73 249600:65 499200:85 800000:90 998400:87
min_sample_time: 0
boost: 0
boostpulse_duration: 0
align_windows: 1
use_migration_notif: 1
use_sched_load: 0
max_freq_hysteresis: 0
For additional tweaks click here
SOURCES( These were the threads from which I took help for creating this mod. Do Check them out and enjoy reading)
https://forum.xda-developers.com/nexus-5x/general/guide-advanced-interactive-governor-t3269557- @soniCron 's thread
https://forum.xda-developers.com/moto-g4-plus/themes/mod-lightning-blade-t3611513 - @Swapney Raul thread resembles a lot to our cpu architecture
https://forum.xda-developers.com/oneplus-3/how-to/advanced-interactive-governor-tweaks-t3476589 - @Asiier(his help was very important)
CREDITS
@Dreamstar
ocean13 from Vibe K5 Telegram Group
@iamnikkei
@[email protected]
@Dhruv_Agarwal
@Harry8242
Me as well
FOR SD616 USERS
FOR V2- Check First Post. The Profile Is Same For Both Varient
FOR V1(Kernel Auditor users)
[*]For EX Kernel Manager Users: Download Link in OP
[*] For Kernel Auditor Users:- You need to manually input these values (Don't forget to toggle the apply on boot).
FOR BIG CLUSTER
Code:
go_hispeed_load: 99
above_hispeed_delay: 60000 400000:10000 533333:70000 800000:80000 960000:85000 1113600:90000 1344000:95000
timer_rate: 60000
hispeed_freq: 200000
timer_slack: 480000
[B]target_loads: [/B] 90 200000:73 345600:78 400000:86 533333:73 800000:90 960000:84 1113600:98 1344000:100
min_sample_time: 0
boost: 0
boostpulse_duration: 0
align_windows: 1
use_migration_notif: 1
use_sched_load: 0
max_freq_hysteresis: 0
For Little Cluster
Code:
go_hispeed_load: 91
above_hispeed_delay: 0 998400:20000 1113600:60000
timer_rate: 60000
hispeed_freq: 200000
timer_slack: 480000
[B]target_loads: [/B] 72 200000:73 249600:65 499200:85 800000:90 998400:95 1113600:100
min_sample_time: 0
boost: 0
boostpulse_duration: 0
align_windows: 1
use_migration_notif: 1
use_sched_load: 0
max_freq_hysteresis: 0
[/LIST]
Enjoy.....
Changelog
v2-(8/4/18)
1. Performance should definitely improve as per the testing.
2.Our Device should run cooler due to more efficient load on each cluster and frequency based on their voltage
3. Battery Should Improve: I got mixed reviews from the testers. So need confirmation.
v1 ~~~initial release
Nice mate you did it finally... Good guide keet it up..:highfive:
Just for you guys to know all of my ROMs are bases on @Harry8242 kernel and you can use these tweak freely in them.
Great. So now I dont need to install custom kernels and face random reboots, cuz the core tweak is in my hands!
This can be added to an init script or device trees too (init.power.rc) for more convenience
Or a flashable zip can also be made.
Adithya R said:
Great. So now I dont need to install custom kernels and face random reboots, cuz the core tweak is in my hands!
This can be added to an init script or device trees too (init.power.rc) for more convenience
Or a flashable zip can also be made.
Click to expand...
Click to collapse
Thanks mate for your suggestion. I am always looking forward to those. Since I am a beginner now, I have kept things simple. If You are using the sd415 variant you should definitely feel difference. If not please wait for the sd616 varient release As I depending on testers solely for this purpose. Even you can edit the file and tweak more to your desire.
And Yes If everything goes well, I wouldn't take much time to release flashable scripts with cooperation from devs...:good::good::good:
Awesome battery backup on a46 sd 616!!
ROM=AOKP
Thanks Nikish
UPDATE:
Thread Updated:
Added Support for Vibe K5 Plus(sd616) Varient(Check Post 2 and OP)
Moved to Sourge Forge . Select the respective folder corresponding to your device
Enjoy:laugh::laugh::laugh::laugh::good:
Amazing work mate. ?
Edit: Squeezed upto 5hrs ?
Great work @Nikish21 . Really it increased the bb of the device. Got good backup even when I was in train journey.
ROM - AEX 5.1 .
Device - A6020a46
First I would Like to thanks to Nikish for the tweak and all the devs who worked on such perfect ROMs for our device :highfive:
So here , I posted some screenshot of my device !
Device - Lenovo vibe k5 A602040
ROM - AEX 4.6
I applied this tweak on AEX 4.6
and seriously my device good SOT as stock ROM..
you can check the attached screenshot...
I Charged my device around 6 hours ago upto 100 % and after that I used it heavily for 3 Hours and 43 minutes with Medium brightness + Vibration enabled + Heavy multi tasking
Device Got 3:43 hours SOT and more than 6 hours battery backup ..
Thanks again
AmithNRG said:
Amazing work mate. ?
Edit: Squeezed upto 5hrs ?
Click to expand...
Click to collapse
Which rom is this not aex 5.1
iamnikkei said:
Which rom is this not aex 5.1
Click to expand...
Click to collapse
Aex 4.6 final
I managed to get this result from a 95% charged battery. It's pretty decent. Thanks devs!!
ROM: Pixel Experience
Variant: a46
Not #working on my 415 indian variant
[email protected] said:
Not #working on my 415 indian variant
Click to expand...
Click to collapse
Mate, I own the sd415(Indian) variant . So I have been using it from good time now. Can you reiterate the process? How did you come to know it's not working?
If you can elaborate the problem, I will definitely help you...
AmithNRG said:
Aex 4.6 final
Click to expand...
Click to collapse
Oh the mod is not required on that tho
Currently I am using AEX v5.1 [oreo8.1.0]
---------- Post added at 04:52 PM ---------- Previous post was at 04:51 PM ----------
[email protected] said:
Currently I am using AEX v5.1 [oreo8.1.0]
Click to expand...
Click to collapse
Please..send me how to set value and which value are that
iamnikkei said:
Oh the mod is not required on that tho
Click to expand...
Click to collapse
These are just values, which can be set on any rom which has Interactive Governor. So In all roms , these values can be set. Whereas necessity is user's perspective.
[email protected] said:
Currently I am using AEX v5.1 [oreo8.1.0]
---------- Post added at 04:52 PM ---------- Previous post was at 04:51 PM ----------
Please..send me how to set value and which value are that
Click to expand...
Click to collapse
I've tried to simplify the process to make it as easier as possible in the OP. Even if it's not clear, let me help you with it. For these, you need either EXKM or Kernel Auditor. How to apply it : it is explained in the first post. So please go through it. Let me know if it is still not cleared. :good::good::good::good: