Related
So My girlfriend has Garminfone and there is no info on the internet at all on how to overclock or a custom kernel or anything really so i Have rooted it but would like to do more so i have done a lil research and will like to build Custom Recovery for the phone but before i start i thought i would post a thread here with all my Optimus one family that i trust and love to get some tips and hopefully even some instructions as the instructions online are hard to fallow ??? so anything ???
Can give a clear answer about that, because its different for most phones.
Some phones like our Optimus One have a recoverypartition, a phone like Samsung Galaxy 3 has not. It took some work to port CWM to that phone and mumbozver (an XDA-user on de Galaxy 3-thread) managed to port it to that phone).
Guess it's best to post a question in the main android-section for this
make "cat /proc/mtd" in "adb shell".
If there are error - porting will be hard
_Arjen_ said:
Can give a clear answer about that, because its different for most phones.
Some phones like our Optimus One have a recoverypartition, a phone like Samsung Galaxy 3 has not. It took some work to port CWM to that phone and mumbozver (an XDA-user on de Galaxy 3-thread) managed to port it to that phone).
Guess it's best to post a question in the main android-section for this
Click to expand...
Click to collapse
Ok so how do I figure out if I do our not and then what's next
Sent from my LG-P500 using XDA Premium App running CM7 over clocked at 806
dislplin01 said:
Ok so how do I figure out if I do our not and then what's next
Click to expand...
Click to collapse
Maybe start with telling us which phone we are talking about...
Here some specs that might help you:
Garminfone is the market name from "Nüviphone A50".
- MSM7227 chipset
- ARM Cortex A11 procssesor (ARMv6) @600MHz
- 256MB RAM
- 4GB ROM
- A-GPS
- WLAN b/g
- 3MP camera
- display have 480 x 320 Pixel
with this informations you can go at first to the step from mik, if it works might be
you can adapt a custom recovery for that phone
Oh... Nuviphone A50. I got this junk for free with their navigation. Well, frankly - you are better off throwing that brick away. One of the worst Android phones ever.
andy572 said:
with this informations you can go at first to the step from mik, if it works might be
you can adapt a custom recovery for that phone
Click to expand...
Click to collapse
Do not hold your breath.
http://forum.cyanogenmod.com/topic/5864-garminfone-a50/
doktornotor said:
Oh... Nuviphone A50. I got this junk for free with their navigation. Well, frankly - you are better off throwing that brick away. One of the worst Android phones ever.
Do not hold your breath.
http://forum.cyanogenmod.com/topic/5864-garminfone-a50/
Click to expand...
Click to collapse
Yea I have seen that thread and some other threads on other forums and sites but they dont tell you much thank you tho and thanks for the specs 2 any info I can get is good
Sent from my LG-P500 using XDA Premium App running CM7 over clocked at 806
dislplin01 said:
Yea I have seen that thread and some other threads on other forums and sites but they dont tell you much thank you tho and thanks for the specs 2 any info I can get is good
Click to expand...
Click to collapse
Well, if the guys on the thread I have linked are not even willing to team up to finally produce something after basically having wasted about a year on this without getting it even bootable... good luck with this.
I would personally suggest bricking the phone intentionally and claiming warranty. Pretty sure this junk has been EOLed so you might get a decent phone as replacement. (Though, you might be unfortunate enough to get a brand new replacement brick since the Garmin's stock must be full of these collecting dust. )
andy572 said:
Here some specs that might help you:
Garminfone is the market name from "Nüviphone A50".
- MSM7227 chipset
- ARM Cortex A11 procssesor (ARMv6) @600MHz
- 256MB RAM
- 4GB ROM
- A-GPS
- WLAN b/g
- 3MP camera
- display have 480 x 320 Pixel
with this informations you can go at first to the step from mik, if it works might be
you can adapt a custom recovery for that phone
Click to expand...
Click to collapse
Thank you andy and mik you guys are awesome for this and all the work you put in will let you know how that goes tomorrow
Sent from my LG-P500 using XDA Premium App
Will be another week before I try I have work a newborn baby to take of but will let you know
Sent from my LG-P500 using XDA Premium App
I for one would be very happy I dont have the smarts to even attempt this. But yes the garminfone is very very slow boring.. It would be just wonderful to have a recovery even better a rom mayb some point to bring this phone at least upto an ehhh ok phone status := Im willing to test/help what ever it is . Im not the best in the develoment area but I do have a garminfone and enough sense to try and give a hand.
Hey there!
I have just received a vivo, and I would like to develop for it. The phone's specs state that vivo is msm8255, but when I look into the device tree of the phone, the ROMs use msm7x30 platform. Can someone please explain this to me?
Also, does anyone know the name of chips in vivo. This is a very hard thing to find. For example, the bluetooth is BCM4329.
If no one has this information then it is alright, but I would like to my first question answered.
Thank You. :good:
rqmok said:
Hey there!
I have just received a vivo, and I would like to develop for it. The phone's specs state that vivo is msm8255, but when I look into the device tree of the phone, the ROMs use msm7x30 platform. Can someone please explain this to me?
Also, does anyone know the name of chips in vivo. This is a very hard thing to find. For example, the bluetooth is BCM4329.
If no one has this information then it is alright, but I would like to my first question answered.
Thank You. :good:
Click to expand...
Click to collapse
You should PM Szeszo on this stuff. He is our main developer and has been pretty much our only developer for almost half a year now. He knows this device inside out
100% same chipset as the 7x30 devices, our 8255 is essentially an overclocked 7x30 like on desire z
That's why desire z has same chipset as us
Bcm 4329 is WiFi too, but bcmdhd is used for AOSP and sense 4 which is ported from One V or latest prima
Wikipedia has some good information
Sent from my HTC One using XDA Premium 4 mobile app
Why is it so important? As poondog said, our CPU just an msm7x30 on higher clock. But we have that CPU's board name, why? Qualcomm knows... Like the MSM8225 and MSM8625Q (dual and quad-core Cortex-A5 CPUs) has msm7x27a board names. Why? Qualcomm knows...
Sent from my Samsung Galaxy Express using XDA-Developers app
Hi everyone, im new here and my incredible s is msm7230 i had root the device and get no problem at all.
And now s KK 4.4. Battery last more then 24 hrs.Thanks to Szezso.
Send from HTC Incredible S-*Vivokat 4.4.2 - TESCO-Minimal kernel 3.6.7 (3.0.86, ION)-Radio- 3831.18.00.28_M
Can we just call it Bill for simplicity kthxbye
Sent from my HTC One using XDA Premium 4 mobile app
OK guys. Thanks for your time.
One last question: Is there a 3.4 kernel for vivo?
rqmok said:
OK guys. Thanks for your time.
One last question: Is there a 3.4 kernel for vivo?
Click to expand...
Click to collapse
Lol
Nah not a proper one
Sent from my HTC One using XDA Premium 4 mobile app
poondog said:
Lol
Nah not a proper one
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Not a proper one? Where can I find its source?
rqmok said:
Not a proper one? Where can I find its source?
Click to expand...
Click to collapse
Closed source
nah jk it was my april fools joke by the sounds of it you missed out
Just noticed you're an Aussie too, gday
poondog said:
Closed source
nah jk it was my april fools joke by the sounds of it you missed out
Just noticed you're an Aussie too, gday
Click to expand...
Click to collapse
Alright, I'll look into the 3.4 kernel development myself.
Gday to you too my Aussie brother from another mother
rqmok said:
Alright, I'll look into the 3.4 kernel development myself.
Gday to you too my Aussie brother from another mother
Click to expand...
Click to collapse
good luck with that we have been looking at it for MONTHS
haha so you are in Adelaide, the most boring city?
poondog said:
good luck with that we have been looking at it for MONTHS
haha so you are in Adelaide, the most boring city?
Click to expand...
Click to collapse
This is off topic, but...
Yes, Adelaide is a boring city. Nothing here to look at (can only look at myself in the mirror)
But what I do like about Adelaide is that it is a planned city; it is very hard to get lost here (even if someone tells you to get lost). When I went to Sydney, I got lost, because the roads aren't straight forward. I've also visited Melbourne, but I didn't like it, because the city there is too tight; the roads are very small, and the trams on the road take up too much space. But Melbourne kind of reminds me of my home country (Pakistan).
By the way, I do know somewhat about kernel development. I have tried to port a 3.4 kernel to a previous device, and I got the kernel to boot, but I coudn't get the ROM to boot. The phone died really quickly and now I cannot fully port the 3.4 kernel to it anymore, however someone else with the same device has already ported it, and I know how he did it. So, I am going to try it with vivo. But, I won't gurantee success.
rqmok said:
This is off topic, but...
Yes, Adelaide is a boring city. Nothing here to look at (can only look at myself in the mirror)
But what I do like about Adelaide is that it is a planned city; it is very hard to get lost here (even if someone tells you to get lost). When I went to Sydney, I got lost, because the roads aren't straight forward. I've also visited Melbourne, but I didn't like it, because the city there is too tight; the roads are very small, and the trams on the road take up too much space. But Melbourne kind of reminds me of my home country (Pakistan).
By the way, I do know somewhat about kernel development. I have tried to port a 3.4 kernel to a previous device, and I got the kernel to boot, but I coudn't get the ROM to boot. The phone died really quickly and now I cannot fully port the 3.4 kernel to it anymore, however someone else with the same device has already ported it, and I know how he did it. So, I am going to try it with vivo. But, I won't gurantee success.
Click to expand...
Click to collapse
Yeah haha fair enough it's boring
@szezso has tried but there are like no similar devices with a working 3.4.Y kernel so it's a bit hard.. working with like only one similar 3.4.Y device haha
Sent from my HTC One using XDA Premium 4 mobile app
poondog said:
Yeah haha fair enough it's boring
@szezso has tried but there are like no similar devices with a working 3.4.Y kernel so it's a bit hard.. working with like only one similar 3.4.Y device haha
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
What's that similar device?
rqmok said:
What's that similar device?
Click to expand...
Click to collapse
ZTE Warp
msm7x30
OK. I have started. Wish me luck!
Hello everyone!
This is my first attempt at porting Android Wear to the Galaxy Gear! I am not an experienced dev and this was done fairly quickly using null_23 as a base and the Gear Live system dump. This is not at all ready and definitely not ready to flash. If you do decide to flash it, you risk bricking your device. That being said, I am requesting that a more experienced dev check over my work. If it seems in order, then it will be tested, until such a time, test at your own risk.
Link: http://d-h.st/go2
UPDATE: [ONLY FOR BRAVE PEOPLE INTERESTED IN TESTING]: Since I used null_ as the base, the addons are still available, but please do not flash any of them! And use the stock kernel for the time being!
UPDATE 2: It might be a good idea to try using the custom kernel we have available to us. If I can get an updater script from the gear live or other android wear device and look in to modifying the bootclasspath in the preexisting custom kernel that we have.
UPDATE 3: I have figured out how to modify the bootclasspath, will make the modification shortly. I just need an updater script for an android wear device and we may have a booting android wear port.
UPDATE 4: Link to Attempt 2 coming soon. This has a modified updater script that will hopefully set all permissions correctly. This may be all it needs to boot properly. If not, then I may still need some help getting the Gear Live Kernel to modify our kernel's bootclasspath. If anyone would like to flash this, same as before, I can't guarantee anything will work or that your device will work afterward.
Link: AWAttempt2.zip
UPDATE 5: added my slightly modified updater files from fomey's null_ ROM attached at the bottom. fomey, if we get this working, could you package it in to null_ as a second ROM option?
TekGadgt said:
Hello everyone!
This is my first attempt at porting Android Wear to the Galaxy Gear! I am not an experienced dev and this was done fairly quickly using null_23 as a base and the Gear Live system dump. This is not at all ready and definitely not ready to flash. If you do decide to flash it, you risk bricking your device. That being said, I am requesting that a more experienced dev check over my work. If it seems in order, then it will be tested, until such a time, test at your own risk.
Link: http://d-h.st/go2
Click to expand...
Click to collapse
Dude, you are fast!
I will not try it out right away because i just set up Null 23 and cloudnotifier so that to have notifications on the iPhone.
BTW, is there any chance that it will work with an iPhone. Ala Google Glass, that is.
TekGadgt said:
Hello everyone!
This is my first attempt at porting Android Wear to the Galaxy Gear! I am not an experienced dev and this was done fairly quickly using null_23 as a base and the Gear Live system dump. This is not at all ready and definitely not ready to flash. If you do decide to flash it, you risk bricking your device. That being said, I am requesting that a more experienced dev check over my work. If it seems in order, then it will be tested, until such a time, test at your own risk.
Link: http://d-h.st/go2
Click to expand...
Click to collapse
I just tried it out with the installation through TWRP, definitely not working as you said yet, just boot loops. I've been looking around in the zip and I see no problems that were noticeable. Hopefully this port of android wear can happen!
Sent from my SM-N900V using XDA Premium 4 mobile app
sandvich123127 said:
I just tried it out with the installation through TWRP, definitely not working as you said yet, just boot loops. I've been looking around in the zip and I see no problems that were noticeable. Hopefully this port of android wear can happen!
Sent from my SM-N900V using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thank you for testing so quickly! I'm glad it did not cause any serious issues to your device. I will do some talking with some devs I know and see what I can get worked out. Porting to the 1 will actually be easier than to the 2 or Neo, since there is an android base for the 1, unlike the 2 and Neo which are Tizen only.
Do you have a change log? If this is based on Null, it's still 4.2, while the wear launcher, if I remember correctly, requires a newer version of Android, probably 4.4. Just curious what your plans are to deal with that. Seems to me the only real options are either editing the wear app or porting 4.4 aosp and hoping the launcher works. Theoretically, the gear live dump could be ported but the major difference between cpus makes it a much more difficult task than people originally hoped. I think the best chance would be if a dev team (ie CM) were to pick up the protect, but there's the downside to a large bounty: there's a lot of people wanting to go it alone for the cash.
Sent from my VS985 4G using XDA Free mobile app
Trust me, I'm not doing this in an attempt to get the bounty. The money doesn't interest me at all. As far as the change log goes, this is the absolute first attempt, so there hasn't been anything changed yet. So again, this was a quick attempt in an effort to get the ball rolling and get the community involved in the development.
TekGadgt said:
Trust me, I'm not doing this in an attempt to get the bounty. The money doesn't interest me at all. As far as the change log goes, this is the absolute first attempt, so there hasn't been anything changed yet. So again, this was a quick attempt in an effort to get the ball rolling and get the community involved in the development.
Click to expand...
Click to collapse
No worries, I didn't think you were. You didn't have the typical billion "Donate please!" links that they would.
But what does first attempt mean? Just null kernel and modules with gear live system folder? I know a little about these things so I'd like to take a look, mostly out of curiosity, so I'd like to know what you've already done, preliminary as it is.
I agree though, we needed some kind of thread started and I agree that it's too early to put anything in the development forum.
Sent from my VS985 4G using XDA Free mobile app
Sent from my VS985 4G using XDA Free mobile app
JesusFreak316 said:
No worries, I didn't think you were. You didn't have the typical billion "Donate please!" links that they would.
But what does first attempt mean? Just null kernel and modules with gear live system folder? I know a little about these things so I'd like to take a look, mostly out of curiosity, so I'd like to know what you've already done, preliminary as it is.
I agree though, we needed some kind of thread started and I agree that it's too early to put anything in the development forum.
Sent from my VS985 4G using XDA Free mobile app
Sent from my VS985 4G using XDA Free mobile app
Click to expand...
Click to collapse
Not just a swapped out system folder. the base of the null_ system folder is still there. I only migrated the things necessary for a standard port. The only issue is that there is no ROM for the gear live yet, so a proper permissions section is not available for me to port from the updater script of the live to the updater script of the galaxy gear. I'm pretty convinced that if someone with a little more knowledge than myself edited the updater script permissions section to set the proper permissions for the new files, that this would at least boot.
Hi guys, I stumbled across this ebay listing item number 161368138405 . The seller claims he will update your gear to 4.4.2 for £25 + p & p , I have emailed the developer a link to the bounty thread, hopefully he may be able to help.
Sent from my SM-T320 using Tapatalk
Its some fake **** i think.
Would like to se a device info screen screenshot.
In the pictures he wirtes "This is not for the watch"
And later on "(1) Watch will become android 4,4,2"
Does he know what he is selling or not?
When he says "This is not for the watch", I think he means that you are not buying the watch in the picture. That is, you are not buying the physical watch, just the software upgrade.
I think it is high risk when you send your watch to him.
TekGadgt said:
...........
Click to expand...
Click to collapse
But for you rom is started?
4.2.2.
I wouldn't be surprised if he means 4.2.2.
He was pretty sure on his reply to me it was 4.4.2
RevengeDevTeam said:
But for you rom is started?
Click to expand...
Click to collapse
gingerdude said:
He was pretty sure on his reply to me it was 4.4.2
Click to expand...
Click to collapse
RevengeDevTeam: I have not necessarily classified this as a ROM, since it currently doesn't boot. That's why this is listed in the general thread. I am working on it, but there are no guarantees right now.
gingerdude: I'm pretty sure it's a scam. I wouldn't send him my watch if I were you.
gingerdude said:
Hi guys, I stumbled across this ebay listing item number 161368138405 . The seller claims he will update your gear to 4.4.2 for £25 + p & p , I have emailed the developer a link to the bounty thread, hopefully he may be able to help.
Sent from my SM-T320 using Tapatalk
Click to expand...
Click to collapse
Yeah, the listing was ended by the poster because there was an error in the listing. I bet he got scared cause people started to figure him out.
Oh that's a shame. I thought it might give you guys a head start
Will be watching with interest
Sent from my Nexus 5 using Tapatalk
richlum said:
When he says "This is not for the watch", I think he means that you are not buying the watch in the picture. That is, you are not buying the physical watch, just the software upgrade.
Click to expand...
Click to collapse
So I emailed the seller and he said it was Null Rom but it was 4.4...apparently he was mistaken haha
--------------------------------------------------------------------------------
From: shagmeimbj
To: lexirodster81
Subject: Details about item: shagmeimbj sent a message about Samsung gear watch SM- V700 unlocking service to android 4.4.2 #161368138405
Sent Date: Jul-16-14 06:37:52 PDT
Dear lexirodster81,
Can you maybe send a screenshot of the 4.4.2 in the settings menu...not saying I don't believe you haha these pics could be from Null rom though which is 4.2.
- shagmeimbj
This was his response...
"Dear shagmeimbj,
Hello
This service is to install the null rom what is 4.4.2
- lexirodster81
Click "respond" to reply through Messages, or go to your email to reply
Respond
Hello everyone,
As you all know, Hashcode has stopped supporting safestrap (as he mentioned in his last post in the safestrap thread. Good luck to him on his new career and many many thanks for the amazing safestrap). Now it's time for our existing developers to chime in and get the lead and keep the project running for us (at least the AT&T note 3 community. If they can go further, that's even better). I'm asking all of my friends/brothers here on the note 3 community that have the skills for it to jump in and mess with safestrap and see what they can do. I know for sure that we have a very good number of very smart devs here who can definitely make something happen.
Thank you in advance!
K-Alzwayed said:
Hello everyone,
As you all know, Hashcode has stopped supporting safestrap (as he mentioned in his last post in the safestrap thread. Good luck to him on his new career and many many thanks for the amazing safestrap). Now it's time for our existing developers to chime in and get the lead and keep the project running for us (at least the AT&T note 3 community. If they can go further, that's even better). I'm asking all of my friends/brothers here on the note 3 community that have the skills for it to jump in and mess with safestrap and see what they can do. I know for sure that we have a very good number of very smart devs here who can definitely make something happen.
Thank you in advance!
Click to expand...
Click to collapse
Questions! Could we keep them in the correct forum?
Lol. Note 4 is coming out. Safestrap would be wanted more over there as it will arrive completely stock and locked down. SS for Note 3 seems to be working perfectly fine the way it is. However, I don't use it much anymore.
Delakit said:
Questions! Could we keep them in the correct forum?
Lol. Note 4 is coming out. Safestrap would be wanted more over there as it will arrive completely stock and locked down. SS for Note 3 seems to be working perfectly fine the way it is. However, I don't use it much anymore.
Click to expand...
Click to collapse
Well, that's true, but we are also gonna be getting more updates. We are not going to just stay on 4.4.2 forever, right? Lol
Both of you have great point but it's not who needs it more. We all need it for our devices. I hope we can find someone to pick up the torch.
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
The only reason we would need an update is if we were to get Android L, but I'm not holding my breath for that one, specially since the note 4 is supposed to be released with kit kat, and then it will probably update to L. It would be awesome if we would get the android update!
RoloRacer on DynamiKat Note3
I don't understand how come people don't expect high spec flagship devices to get updates.... We will have it.
Sent from my XT907 using XDA Free mobile app
mrkhigh said:
I don't understand how come people don't expect high spec flagship devices to get updates.... We will have it.
Sent from my XT907 using XDA Free mobile app
Click to expand...
Click to collapse
I always wonder the same. Once a new phone comes out, people think their current phone is garbage. Note 3 will still be a flagship kickass phone for at least 4 years from now IMO. Very high specs that can keep up with so many updated to come.
Every phone I've ever had I had the latest os long before it was officially released. I'm not waiting on att for it.
K-Alzwayed said:
Well, that's true, but we are also gonna be getting more updates. We are not going to just stay on 4.4.2 forever, right? Lol
Click to expand...
Click to collapse
None that will be affective enough. Who knows, especially with what I've seen in the past, we could very well stay on 4.4.2 forever.
lildoggs said:
Both of you have great point but it's not who needs it more. We all need it for our devices. I hope we can find someone to pick up the torch.
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Nobody really needs it. It's a desire, correct? Regardless, I'm fairly certain that people will be grabbing the Note 4 and checking for any immediate possibilities. Time will tell.
Delakit said:
None that will be affective enough. Who knows, especially with what I've seen in the past, we could very well stay on 4.4.2 forever.
Nobody really needs it. It's a desire, correct? Regardless, I'm fairly certain that people will be grabbing the Note 4 and checking for any immediate possibilities. Time will tell.
Click to expand...
Click to collapse
I highly doubt that there will be root for the note 4 right away. It will definitely take a very long time if not never.
K-Alzwayed said:
I highly doubt that there will be root for the note 4 right away. It will definitely take a very long time if not never.
Click to expand...
Click to collapse
I can guarantee there won't be root for quite some time. That's why I stated that people will want Safestrap on Note 4, not the Note 3 that already has a fairly stable version. Stable enough, that is. Time will tell.
Why do we guarantee no root. You people make statements without merit
Sent from my XT907 using XDA Free mobile app
Gezzz lots of older phones still get updates. I'm still thinking at some point we will see a bootloader hack
No worries. The Alliance Team is gonna try to pick up SS for everyone.
RErick said:
No worries. The Alliance Team is gonna try to pick up SS for everyone.
Click to expand...
Click to collapse
Hells to the yes. NOW I feel good. Thank you so much.
RErick said:
No worries. The Alliance Team is gonna try to pick up SS for everyone.
Click to expand...
Click to collapse
thanks a lot peopple..... !!!!!
Since we've been talking about this pretty extensively in a different thread I figured I would make a new thread for discussing, troubleshooting and attempting to improve the ram management issue on the S6.
Hopefully some good will come of this
So far this Is what we've got:
Should work on all variants including the edge and possible on other Samsung devices.
Thanks to @mikeyinid for finding these and @s.rapp for answering questions, and making the instructions easier to understand
And anyone else who I may have missed who helped contribute.
Prerequisites:
-A rooted device
-A root file explorer/manager app
-A backup of your original build.prop to be safe
Explanation: (From @mikeyinid )
Here is a quick rundown on how this came about, and what we actually know.
Since I purchased the S6 on release day, I've been messing with certain things, as you can see from the ROM I posted, Looper(shameless plug). Debloating Samsung apps really helped with battery life and I was pretty happy with the results. But like so many other people, I didn't understand why my S6 killed apps so aggressively. Initially I thought it might be the memory leak we all know so much about in 5.0. So, I did a little research and found the patch for that. While it did help keep the device stable over time, apps were still being killed with no prejudice. All this time I noticed really useless services running in the background, often stuff I'd never even opened. I studied LMK and started messing with those settings. After a month of trying everything I could find documented, I was ready to give up. Yesterday I was looking through the services.jar smali for the 37,875th time and realized the DHA referenced in there has to have something to do with memory management. I kept overlooking it because I hadn't seen mention of it anywhere else. I am no smali guru, as some of you know. But it was pretty obvious DHA was influencing memory management to some extent. Samsung, although leaving us in the dark on this, was kind enough to give us props to set the values for DHA. I pulled a few that seemed relevant, added them to my build.prop, and what do you know. For the first time in almost two months of tinkering, I saw an improvement in the way my device was managing memory.
The thing everyone needs to understand; I have no clue what DHA is. It overrides every aspect of Googles LMK and seems to do so in a way that makes more sense. I'm sure someone with more knowledge than myself will be able to tune this to the point the S6 will be the multi-tasking champ. There are several other props in the smali that are probably useful. I will try to get them all with their default values posted today. This has been pretty exciting for me, I spent way to much time trying to figure out the issue to not make some sort of progress. I hope you guys enjoy the tweaks, and I hope it helps sway those of you on the fence about keeping this device to stay. It's only gonna get better
Instructions:
First find your build.prop. This is located in /system. to get to /system you need to go to the root directory using a file explorer and then go to the system folder. The build.prop will be in there. You can also use and app such as build.prop tweaker but its a bit harder (imo)
In your build.prop scroll to the very bottom and paste this in:
Code:
# MultiTasking Tweaks
ro.config.dha_cached_max=15
ro.config.dha_cached_min=4
ro.config.dha_empty_max=36
ro.config.dha_empty_min=9
ro.config.dha_empty_init=36
ro.config.dha_lmk_scale=0.545
ro.config.dha_update_max_count=5
ro.config.dha_step=2
ro.config.dha_th_rate=1.4
ro.config.dha_defend_th_level=0
ro.config.64bit_lmk_enable=true
ro.config.sdha_apps_bg_max=70
ro.config.sdha_apps_bg_min=8
ro.config.dha_ils_enable=true
ro.config.dha_ils_dyna_lmk=true
ro.config.dha_ils_rate=1.5
Now you need to find and remove any duplicate build.prop lines which may cause an issue. So look through the build.prop and remove any lines that look like these(Not the ones you just added at the bottom!):
ro.config.dha_cached_max=
ro.config.dha_empty_max=
ro.config.dha_th_rate=
ro.config.dha_lmk_scale=
Finally reboot your device and report back here!
Video Tutorial (courtesy of @Thin_Bezel )
https://youtu.be/d-vaLXF0OxY
A note from @mrapp :
"The major addendum here seems to be that when using this build.prop apps like Chrome and and those calling webpages via Webview (Tinfoil for Facebook) still suck. The kernels being tested at the moment don't appear to have this issue, so if you're capable of flashing kernels I personally recommend checking out the Vindicator thread if you're on T-Mobile/W8 or UniKernel (universal) if you're on any other device. UniKernel tests may or may not be edge friendly, so always make a backup. Lots of people have gotten in to trouble today. Don't be one of them!"
Please note we are constantly experimenting with different values so these are subject to be updated rather frequently
As I was saying before, Maybe someone can try compare Zenfone 2 services.jar with the one in samsung galaxy s6.
The Asus Zenfone 2 is knowed to had a great multitasking experience, it can keep a loot of apps even in his 2GB version, and remember that Zenfone is in Android 5.0 and don't have any problem with multitasking.
I already downloaded the firmware for Zenfone and decompiled his services.jar if someone like to try something, here is attached:
iFlasher said:
As I was saying before, Maybe someone can try compare Zenfone 2 services.jar with the one in samsung galaxy s6.
The Asus Zenfone 2 is knowed to had a great multitasking experience, it can keep a loot of apps even in his 2GB version, and remember that Zenfone is in Android 5.0 and don't have any problem with multitasking.
I already downloaded the firmware for Zenfone and decompiled his services.jar if someone like to try something, here is attached:
Click to expand...
Click to collapse
I'll take a look at it, but I've already gone through several different services.jar trying to find anything that might make a difference. Everything appears to be exactly how Google intended it to be.
mikeyinid said:
I'll take a look at it, but I've already gone through several different services.jar trying to find anything that might make a difference. Everything appears to be exactly how Google intended it to be.
Click to expand...
Click to collapse
I also noticed that Samsung uses the ramdisk to set VM memory settings and lmk settings rather than actually modifying the source for some reason. I tried removing all of these and letting the settings be stock google but that also made no difference
Sent from my SM-G920T using XDA Free mobile app
Xileforce said:
I also noticed that Samsung uses the ramdisk to set VM memory settings and lmk settings rather than actually modifying the source for some reason. I tried removing all of these and letting the settings be stock google but that also made no difference
Sent from my SM-G920T using XDA Free mobile app
Click to expand...
Click to collapse
Right, all of that can be controlled with init.d scripts. i set the values ridiculously high and can see that that scripts actually work. Then going the other way no matter how low I set them or even disable them, there is no difference. Still can't have more than 5 or so apps open.
mikeyinid said:
Right, all of that can be controlled with init.d scripts. i set the values ridiculously high and can see that that scripts actually work. Then going the other way no matter how low I set them or even disable them, there is no difference. Still can't have more than 5 or so apps open.
Click to expand...
Click to collapse
What's a good test to see if memory management is improved? I've done some mods to lmk in my latest kernel and want to see if it helps any.
Sent from my SM-G920T using XDA Free mobile app
Xileforce said:
What's a good test to see if memory management is improved? I've done some mods to lmk in my latest kernel and want to see if it helps any.
Sent from my SM-G920T using XDA Free mobile app
Click to expand...
Click to collapse
just open apps, never hit the back button, then switch between them using recents.
mikeyinid said:
just open apps, never hit the back button, then switch between them using recents.
Click to expand...
Click to collapse
Hmmm...idk still seems pretty mediocre :/ not sure if better or worse.
Sent from my SM-G920T using XDA Free mobile app
Xileforce said:
Hmmm...idk still seems pretty mediocre :/ not sure if better or worse.
Sent from my SM-G920T using XDA Free mobile app
Click to expand...
Click to collapse
Tried it on your latest kernel and it seems to be the same.
NJGSII said:
Tried it on your latest kernel and it seems to be the same.
Click to expand...
Click to collapse
Yea figured...the issue apparently isn't the lmk then...
Sent from my SM-G920T using XDA Free mobile app
Xileforce said:
Yea figured...the issue apparently isn't the lmk then...
Sent from my SM-G920T using XDA Free mobile app
Click to expand...
Click to collapse
I don't know a whole about kernel stuff. Does there happen to be any oom_adj stuff in there?
I'm losing hope that this will be fixed with any update. I think moving to arm64 may have shot Samsung in the foot. What is the other arm64 lollipop device samsung has released? Note 4?.
---------- Post added at 07:00 PM ---------- Previous post was at 06:57 PM ----------
Xileforce said:
Yea figured...the issue apparently isn't the lmk then...
Sent from my SM-G920T using XDA Free mobile app
Click to expand...
Click to collapse
It's not. It has nothing to do with lmk. I've messed with every possible scenario, pulled in stuff from cm and see no difference. Even changing oom_adj values in services.jar makes zero difference.
mikeyinid said:
I don't know a whole about kernel stuff. Does there happen to be any oom_adj stuff in there?
I'm losing hope that this will be fixed with any update. I think moving to arm64 may have shot Samsung in the foot. What is the other arm64 lollipop device samsung has released? Note 4?.
---------- Post added at 07:00 PM ---------- Previous post was at 06:57 PM ----------
It's not. It has nothing to do with lmk. I've messed with every possible scenario, pulled in stuff from cm and see no difference. Even changing oom_adj values in services.jar makes zero difference.
Click to expand...
Click to collapse
I meant I thought it may help with killing recents so soon. It had some tweaks to preserve favorites among other things
Sent from my SM-G920T using XDA Free mobile app
Xileforce said:
I meant I thought it may help with killing recents so soon. It had some tweaks to preserve favorites among other things
Sent from my SM-G920T using XDA Free mobile app
Click to expand...
Click to collapse
I was agreeing with you lol.
mikeyinid said:
I don't know a whole about kernel stuff. Does there happen to be any oom_adj stuff in there?
I'm losing hope that this will be fixed with any update. I think moving to arm64 may have shot Samsung in the foot. What is the other arm64 lollipop device samsung has released? Note 4?.
---------- Post added at 07:00 PM ---------- Previous post was at 06:57 PM ----------
It's not. It has nothing to do with lmk. I've messed with every possible scenario, pulled in stuff from cm and see no difference. Even changing oom_adj values in services.jar makes zero difference.
Click to expand...
Click to collapse
I have note 4 too and it has same problem with latest lollipop update, i switched to cm12.1 and now all the problem are gone, switching between apps it's really fast and apps stay in ram flawlessly.
CQ7 said:
I have note 4 too and it has same problem with latest lollipop update, i switched to cm12.1 and now all the problem are gone, switching between apps it's really fast and apps stay in ram flawlessly.
Click to expand...
Click to collapse
Interesting. This gives me hope! Ty for sharing. Im pretty sure its an issue on the ROM side rather than kernel.
Sent from my SM-G920T using XDA Free mobile app
Xileforce said:
Interesting. This gives me hope! Ty for sharing. Im pretty sure its an issue on the ROM side rather than kernel.
Sent from my SM-G920T using XDA Free mobile app
Click to expand...
Click to collapse
Right, but what on the ROM side could be causing this kind of behavior? I see myself as quite tech savvy, but I'm woefully uninitiated in the inner workings of Android you guys are unraveling here.
Even after removing just about all of Samsungs proprietary stuff, just leaving the bare basics, we're still seeing app genocide as soon as we're multitasking.
It'd sure be awesome of the community fixes this before Samsung does...
Has Samsung acknowledge this issue and said they will fix it with the 5.1.1 update? Honestly, I feel like for the premium you pay for this phone, this is very ridiculous. Things like these can really make or break a purchase. I myself have not got the S6 solely for this reason, I cannot justify spending 600+ on a device which cannot even keep up with my 3 year old Nexus 4.
I hope they do fix it this month though. What are the chances they will though, the S6 is selling well so Samsung probably does not care about these things.
oxxshadow said:
Has Samsung acknowledge this issue and said they will fix it with the 5.1.1 update? Honestly, I feel like for the premium you pay for this phone, this is very ridiculous. Things like these can really make or break a purchase. I myself have not got the S6 solely for this reason, I cannot justify spending 600+ on a device which cannot even keep up with my 3 year old Nexus 4.
I hope they do fix it this month though. What are the chances they will though, the S6 is selling well so Samsung probably does not care about these things.
Click to expand...
Click to collapse
The S6 isn't selling as well as Samsung had hoped. And the memory issue is probably a large part of it. I have a S4 also, and it doesn't have any issues multi tasking on lollipop. It's shameful that a 3 year old device can managed to run just about everything I throw at it with no problem.
oxxshadow said:
Has Samsung acknowledge this issue and said they will fix it with the 5.1.1 update? Honestly, I feel like for the premium you pay for this phone, this is very ridiculous. Things like these can really make or break a purchase. I myself have not got the S6 solely for this reason, I cannot justify spending 600+ on a device which cannot even keep up with my 3 year old Nexus 4.
I hope they do fix it this month though. What are the chances they will though, the S6 is selling well so Samsung probably does not care about these things.
Click to expand...
Click to collapse
Samsung has acknowledged the ram issue and said they will fix it in an update. That's about as specific as they got. My guess would be 5.1.1 update though.
Sent from my SM-G920T using XDA Free mobile app
Xileforce said:
Samsung has acknowledged the ram issue and said they will fix it in an update. That's about as specific as they got. My guess would be 5.1.1 update though.
Sent from my SM-G920T using XDA Free mobile app
Click to expand...
Click to collapse
Sadly, Samsung has neither acknowledged the specific issue nor promised any updates. All the articles in the blogosphere regarding this (including the one from Forbes) cite a Facebook comment from a random Samsung employee giving an incredibly vague and generic response about future updates when asked a direct question about the memory issue by xda member johanbiff.
I'm baffled by the low level of journalism here.
EDIT: Typo.