Related
Ive been hearing about a RAM hack for the Nexus, and ive been searching everywhere in nexus development for instructions, but i cant seem to find any. Can anyone either point me in the direction or tell me how to apply the Ram hack, and what needs to be done?
thanks for any help!
heroskyy said:
Ive been hearing about a RAM hack for the Nexus, and ive been searching everywhere in nexus development for instructions, but i cant seem to find any. Can anyone either point me in the direction or tell me how to apply the Ram hack, and what needs to be done?
thanks for any help!
Click to expand...
Click to collapse
right now things are down due to people have major battery problems....you will have to wait until cyanogen gets things cleared up
icon57 said:
right now things are down due to people have major battery problems....you will have to wait until cyanogen gets things cleared up
Click to expand...
Click to collapse
"Everything's down due to battery problems"
I'm curious,
What exactly does this mean? Will you elaborate?
DMaverick50 said:
"Everything's down due to battery problems"
I'm curious,
What exactly does this mean? Will you elaborate?
Click to expand...
Click to collapse
Basically the "RAM Hack" was enabling the EBI1 memory bank to be addressed in the kernel source (modifications to arch/arm/mach-msm/board-mahimahi.h and arch/arm/mach-msm/board-mahimahi.c I believe).
These changes were checked in for the 2.6.32 kernel - they were ported back to the 2.6.29 kernel and a compiled kernel with these changes was posted.
Some people who have flashed this kernel are experiencing issues where their battery will no longer charge regardless of what they do (reflashing back to stock for example).
So, it looks like the updated kernel has been pulled until it gets sorted what is causing the issue.
what he said ^^^ lol
not just the kernel but the CM ROM as well has been pulled until the issue is found and fixed.
Interesting, if you had the issue though how would you go about fixing it?
There's a kernel compiled with the default config from the repo (2.6.32) that seems to resolve the issue for those that had it. Found here: http://www.cyanogenmod.com/downloads/rom
http://n0rp.chemlab.org/android/nexus/testing/zImage-2.6.32-defconfig
I keep on hearing this EU bug here and there .....I have some questions regarding this .....
1,why does this happen?
2,will it affect only vibrant running ics or even jellybean?
3.how can I bring back my vibrant to normal? (don't post me regarding those guide I need breif steps).........thanks for helping
Answers (sort of):
akarshfrevr said:
1,why does this happen?
Click to expand...
Click to collapse
1. No one knows why it happens yet. Seems the earliest case had been around February for the Vibrant (before it got a real name like EUbug. Happened to Jasonhunterx)
akarshfrevr said:
2,will it affect only vibrant running ics or even jellybean?
Click to expand...
Click to collapse
2. There has been a crap-ton (this isn't metric or imperial but is a valid form of volume in my realm) amount of speculation, attempts, theories, support, more speculation all in the [Guide] Encryption Unsuccessful - Reset Android thread in the Captivate side of things. Me, Yosup, Mr_Psycho, DerT, Silvercrown, Swehes,...have all contributed to it over time but no one can get to the *root* of the problem. Even Adam Outler and Cyanogen themselves don't know why. There is also a Reference thread going too and is located here ---> [REF][ICS] Encryption Unsuccessful Reference
Here is a recent post I had over there with a brief synopsis of devices effected and ROMs/Kernel.
Bottom line, is there is no solution yet, although some users have reported getting their /data back but have no idea why or how. Further bottom line would be, if you don't want to get hit or roll the dice with the EU bug, STAY ON FROYO OR GB builds. **Sorry for the Bold CAPs but that is an important part that many should read. So far I haven't heard anyone on JB get hit with it, but that doesn't mean it isn't out there. Was Months before ICS users realized what was happening and then it was too late.
akarshfrevr said:
how can I bring back my vibrant to normal?
Click to expand...
Click to collapse
Short answer: You can't (yet). Some really bright minds are working on it but many users on both sides have left the Vibrants and Cappy's behind in pursuit of newer and shiny models. I fear that we might not find a solution and if we do, this device will be close to 3 years old and while it still rocks hard, is considered a dinosaur in mobile phone tech. And that to me is too bad.
agreed @ WOOD im yet to upgrade /update or renew my contract with Tmobile i dont know what i want to do anymore ever since the Vibrant it was like now all i think of is ..is there DEVing going on with this and that phone lol i wanted the Blaze 4g because the dual core SNAP Dragon s3 but i saw little to no dev on there still trooping out the Vibrant hardcore lol with great deal of DEV's was so sad to c FISH leave my heart SANK lol
Woodrube said:
Short answer: You can't (yet). Some really bright minds are working on it but many users on both sides have left the Vibrants and Cappy's behind in pursuit of newer and shiny models. I fear that we might not find a solution and if we do, this device will be close to 3 years old and while it still rocks hard, is considered a dinosaur in mobile phone tech. And that to me is too bad.
Click to expand...
Click to collapse
Since it happened to me also (read my testimony here), I could say this bug is somehow reversible UNLESS ONE HITS THE "RESET PHONE" BUTTON. Do not press it! Pull the battery out and boot to recovery through button combo and restore a nandroid. If you are a flasher and not a noob, always keep a working nandroid backup (it saved me). I'm not sure if I could flash anything else, perhaps it's the same flashing process somehow getting corrupted?
ioancr said:
... I could say this bug is somehow reversible UNLESS ONE HITS THE "RESET PHONE" BUTTON. Do not press it! ...
Click to expand...
Click to collapse
I never pressed Reset (and knew beforehand not to thanks to advice from Woodrube, et al) ... yet I still succumbed to EU.
No one knows a sure fire way to make this "reversible" unfortunately. Those who have had their internal sd's restored seem to have been more lucky than anything else - ie. there's no common thread to link nor duplicate their results.
Maybe one day, this thing gets figured out.
yosup said:
I never pressed Reset (and knew beforehand not to thanks to advice from Woodrube, et al) ... yet I still succumbed to EU.
No one knows a sure fire way to make this "reversible" unfortunately. Those who have had their internal sd's restored seem to have been more lucky than anything else - ie. there's no common thread to link nor duplicate their results.
Maybe one day, this thing gets figured out.
Click to expand...
Click to collapse
Wow, I didn't know that, it seems really worse than I thought of. Sorry if I ask it, but you still were able to get to recovery weren't you? Also, did you have a nandroid backup to try a restore?
Then I was yes very lucky, sorry for you guys and hope someday someone will save your phones too...
ioancr said:
... Sorry if I ask it, but you still were able to get to recovery weren't you? Also, did you have a nandroid backup to try a restore? ...
Click to expand...
Click to collapse
Yes, I could get to recovery, but I couldn't mount the internal sd anymore (and haven't been able to yet to date). So, I couldn't restore a nandroid backup or flash any of the roms I had downloaded on the int sd.
The vold.fstab emmc swap method at least let's me use the phone normally (albeit without the int sd), but I'm keeping my fingers crossed Woodrube & The Gang figure out how to restore access to the int sd ... some day.
I got scared by this bug i left ics itself and now I'm running helly bean ...........I don't have an ext memory card and should I get one? you know just in case if something goes wrong I can use the roms from ext memory card or nandroid backup and come back to normal ...........
This bug appears to be similar to the emmc bug on the note. Essentially, the eprom (programmable chip) on the motherboard of your phone.... for some reason it writes additional bits of code (like 2 bits or 8 bits) on the chip which then basically changes how the cpu sees the index... which then Bricks the phones.
Like Woodrube said...... The Vibe is 3 years old and it Totally Amazes me how great this phone really is.......... it is one of the few that could get ICS or JB ....... think about it this thing was released with Eclair (2.1)...... and still running like that lil bunny......
Oh and BTW CONGRATS TO WOODRUBE..... He is now the latest addition to the Moderator's group here at XDA Congrats to Woodrube.
:victory::victory::victory::victory::victory: ~~~~~ oka1
Woodrube said:
Answers (sort of):
Short answer: You can't (yet). Some really bright minds are working on it but many users on both sides have left the Vibrants and Cappy's behind in pursuit of newer and shiny models. I fear that we might not find a solution and if we do, this device will be close to 3 years old and while it still rocks hard, is considered a dinosaur in mobile phone tech. And that to me is too bad.
Click to expand...
Click to collapse
oka1 said:
... Oh and BTW CONGRATS TO WOODRUBE..... He is now the latest addition to the Moderator's group here at XDA Congrats to Woodrube.
:victory::victory::victory::victory::victory: ~~~~~ oka1
Click to expand...
Click to collapse
:thumbup::thumbup: Congrats, Woodman!! :thumbup::thumbup:
Very worthy bump-in-pay-grade for one of the all-time "counselors" that roam these halls. Great to see that good guys do win.
Note: I'm not sure if the following information is 100% valid for our device, but I've been digging into the problem and how others have gotten it.
How to reproduce:
- After bootup perform sudden power removal
- boot-up interup and reboot.
Click to expand...
Click to collapse
Yup, with encryption support in ICS, Android has become a lot more
picky about having all the filesystems initialized with valid data,
and mistakenly assumes that anything that's not zero or valid is
encrypted, refusing to go any further.
In Gingerbread and before, anything that wasn't valid was expected to
be invalid, and Android would just re-initialize it, regardless of
whether it was zero or not.
Click to expand...
Click to collapse
theexel said:
Note: I'm not sure if the following information is 100% valid for our device, but I've been digging into the problem and how others have gotten it.
Click to expand...
Click to collapse
Interesting stuff. I wonder what would cause part of the file system to become invalid though, seemingly during normal usage.
Not trying to thread jack but I read this quote on team-passion by the dev:
The encryption bug is due to a partition going bad. If it happens to the internal SD then you're done. It's not an ICS bug. It happens on all ROMs and all phones. ICS makes an effort at fixing it. Previous versions don't, or don't make themselves apparent. Bricks have been happening for ever. The Vibrant is 2 years old. Hardware fails. Just like in your PC. This kind of error come up on stock OTA updates, on other devices, as well. Not for SD, as far as I could find. But OTA updates of ICS are for new devices. If there are any corruptions the phone gets returned
Click to expand...
Click to collapse
Is there any truth to this? Can the EU bug happen on any rom? Is ICS as safe as any other rom?
crazexr7 said:
Not trying to thread jack but I read this quote on team-passion by the dev:
Is there any truth to this? Can the EU bug happen on any rom? Is ICS as safe as any other rom?
Click to expand...
Click to collapse
till date it has only occurred on ics roms ......jb roms not even a single case reported .....I'm hoping it won't come to jb .....I got scared by this bug and I moved from ics to jb .......2.2 and 2.3 are safe to escape from this bug
crazexr7 said:
Not trying to thread jack but I read this quote on team-passion by the dev:
Is there any truth to this? Can the EU bug happen on any rom? Is ICS as safe as any other rom?
Click to expand...
Click to collapse
No, there is no truth to this (see my earlier post in this thread for more info).
Not 1 single Froyo or Gingerbread build hsa ever gotten the bug (fact).
The EU bug occurred in early ICS builds for the first time (fact).
It occurred more frequently in Passion versions b1-v13 more than any other ROM out for the Vibrant (fact).
Sounds like there is some spin doctor action going on over there (speculation based on fact).
No one has yet to figure out why,how or when this happens. BUT, it is not from hardware degradation, except for the very small chance that overclocking puts extra heat and strain on the Nand chip (fact and speculation).
Ok so OKA1 said something about the EMMC chip corruption on the Note (which he owns). I was allocated my new forums and lo and behold, one was the Galaxy Tab 8.9 and guess what? They are having a major problem with....CWR and kernels that are making the machines nearly un-usable. Here is a link to the General section that might have some more info with it's multiple threads about the same thing (for now. Muhahaha!)
Woodrube said:
No, there is no truth to this (see my earlier post in this thread for more info).
Not 1 single Froyo or Gingerbread build hsa ever gotten the bug (fact).
The EU bug occurred in early ICS builds for the first time (fact).
It occurred more frequently in Passion versions b1-v13 more than any other ROM out for the Vibrant (fact).
Sounds like there is some spin doctor action going on over there (speculation based on fact).
No one has yet to figure out why,how or when this happens. BUT, it is not from hardware degradation, except for the very small chance that overclocking puts extra heat and strain on the Nand chip (fact and speculation).
Ok so OKA1 said something about the EMMC chip corruption on the Note (which he owns). I was allocated my new forums and lo and behold, one was the Galaxy Tab 8.9 and guess what? They are having a major problem with....CWR and kernels that are making the machines nearly un-usable. Here is a link to the General section that might have some more info with it's multiple threads about the same thing (for now. Muhahaha!)
Click to expand...
Click to collapse
ok so I'm running chimera v1.1 if I want to flash froyo again can I just flash a froyo rom from ics and be ok? or do I have to odin back to stock and go from there?
Gingerbread/Ice Cream Sandwich/Jellybean to Froyo with just a ROM flash = Brick waiting to happen.
ODIN back to stock, bud.
You can go from:
Froyo <-> Froyo:good:
Froyo -> Gingerbread :good:
Gingerbread <-> Gingerbread/MIUI:good:
Froyo/Gingerbread -> ICS/JB:good:
ICS <-> ICS:good:
ICS ->JB:good:
JB <-> JB:good:
ICS/JB -> Froyo/Eclair:bad:
Gingerbread -> Froyo/Eclair:bad:
Do NOT restore cross-OS Nandroids either. Meaning that you cannot restore a Froyo while you are on GB/ICS/JB.
Woodrube said:
You can go from:
Froyo <-> Froyo:good:
Froyo -> Gingerbread :good:
Gingerbread <-> Gingerbread/MIUI:good:
Froyo/Gingerbread -> ICS/JB:good:
ICS <-> ICS:good:
ICS ->JB:good:
JB <-> JB:good:
ICS/JB -> Froyo/Eclair:bad:
Gingerbread -> Froyo/Eclair:bad:
Do NOT restore cross-OS Nandroids either. Meaning that you cannot restore a Froyo while you are on GB/ICS/JB.
Click to expand...
Click to collapse
Thanks guys I'm going to miss ICS but it's just not worth keeping. I would love to flash to JB but GPS and 911 issues are scaring me away.
Did you find it cleared multi-touch issues or improved it at all? Some people say Cyanogenmod fixed things, but I'd just like more confirmation that it'd make a difference
fedreta said:
Did you find it cleared multi-touch issues or improved it at all? Some people say Cyanogenmod fixed things, but I'd just like more confirmation that it'd make a difference
Click to expand...
Click to collapse
I also have this problem. Tomorrow planning to flash on ParanoidAndroid or Cyanogenmod. Tomorrow otpishus the results.
**Menos** said:
I also have this problem. Tomorrow planning to flash on ParanoidAndroid or Cyanogenmod. Tomorrow otpishus the results.
Click to expand...
Click to collapse
I've never tried flashing a ROM before, my device is already unlocked/rooted. What do you do exactly to flash Cyanogenmod?
Just installed Cyanogenmod and saw that the problem is not solved. I fear starting to appear that the problem is hardware. Now have to wait for an update from Google.
IIRC, the screen issue is due to a firmware config that cannot be addressed by flashing a new ROM. An updated firmware package will have to be pushed via Google.
Tony_YYZ said:
IIRC, the screen issue is due to a firmware config that cannot be addressed by flashing a new ROM. An updated firmware package will have to be pushed via Google.
Click to expand...
Click to collapse
Did Google confirm this was the problem? I just need to make sure it is their problem before I go and swap it out since I have 1 more week to decide
fedreta said:
Did Google confirm this was the problem? I just need to make sure it is their problem before I go and swap it out since I have 1 more week to decide
Click to expand...
Click to collapse
From what I have seen, google is aware of all the big bugs and is working on a big update. Looks like screen flicker, multitouch, overheating, corrupted images on startup, gps, wifi performance etc are going to be fixed in a bugfix update. All the nexus devices start their lives like this, one of the few annoying things about being a nexus fanboy, you get to enjoy the bugs before anyone else gets to.
http://www.engadget.com/2013/08/13/2013-nexus-7-multitouch-bug/
fedreta said:
Did Google confirm this was the problem? I just need to make sure it is their problem before I go and swap it out since I have 1 more week to decide
Click to expand...
Click to collapse
I'm trying to remember the source of my information. But it was stated a few times that the second OTA is what causes the screen issues after powering your device up for the first time.
Tony_YYZ said:
I'm trying to remember the source of my information. But it was stated a few times that the second OTA is what causes the screen issues after powering your device up for the first time.
Click to expand...
Click to collapse
Yeah I remember this too, something about the kernel supplying not enough voltage to the touchscreen in an attempt to improve battery life. This has to be a kernel bug.
Try flashing a different kernel as that is what bridges hardware and software.
Aren't all kernels based on stock?
Sent from my Nexus 7 using xda premium
uprightbass360 said:
From what I have seen, google is aware of all the big bugs and is working on a big update. Looks like screen flicker, multitouch, overheating, corrupted images on startup, gps, wifi performance etc are going to be fixed in a bugfix update.
Click to expand...
Click to collapse
I would love to see that happen, but where do you see Google acknowledged and commited to fix all those problems?
If it is just speculation, that doesn't help folks who are within their return period and can get out instead of playing guinea pig.
sfhub said:
I would love to see that happen, but where do you see Google acknowledged and commited to fix all those problems?
If it is just speculation, that doesn't help folks who are within their return period and can get out instead of playing guinea pig.
Click to expand...
Click to collapse
According to the minions on their google+ "they are working on these issues". I by no means know that google is in fact going to be able to fix all of these issues, nor am I able to guarantee what they do, but I don't see that by repeating what their reps are saying is pure speculation. I think that judging by past examples anyone who has bought a nexus device at launch has either knowingly or unknowingly already agreed to be a guinea pig. In the end I am one of the last people to say that someone shouldn't return a defective piece of hardware, but it seems a lot of the issues people are having are being misdiagnosed as hardware issues when in fact they can (and most likely will) be fixed by an OTA.
I can dare to say that the issue is present in Android 4.3 affecting any device running it even Custom Roms I'm on CyanogenMod 10.2 on my d2spr (S3 Sprint) and the issue is present there too. Also that causes reboots too. I could be wrong too.
Sent from my SPH-L710 using Tapatalk 4
Team SXTP
Also the jss build is giving problems in the nexus 4 thread
Sent 4rm my Nexus 7 FLO... Only thing missing is O.G. N7's development...
uprightbass360 said:
Looks like screen flicker, multitouch, overheating, corrupted images on startup, gps, wifi performance etc are going to be fixed in a bugfix update.
Click to expand...
Click to collapse
uprightbass360 said:
According to the minions on their google+ "they are working on these issues". I by no means know that google is in fact going to be able to fix all of these issues, nor am I able to guarantee what they do, but I don't see that by repeating what their reps are saying is pure speculation.
Click to expand...
Click to collapse
No problem with repeating what they are saying, but you seem to have commited them to more than they are saying in their personal comments, not those as official reps.
IMO everyone should get accurate information so they can evaluate for themselves whether it is worth the risk to keep it or just to return the unit.
Personally I think the random reboots and GPS can be addressed in software and the multi-touch is probably 50/50 something that can be worked around in software, but everyone has their own tolerance levels for these kind of issues and "are looking into it or are working on it" and "going to be fixed" are quite different levels of commitment.
I'm sorry but what issues are you having because I exchanged my first n7 because I was having multitouch stuttering and issues with unresponsiveness which made the device unusable. The new device is okay.
Hi everyone,
as the LG G2 is produced by the same manufacturer (LG) as the Nexus 5 and has the same chipset (despite some minor differences e.g. Battery, Display,...), I have been wondering if there is a way to port the Kali-Linux Android ROM (Nethunter) to work with the LG G2.
LINK: http://http://www.kali.org/kali-linux-nethunter/
LINK:http://http://www.offensive-security.com/kali-linux-nethunter-download/
The mere existence of a MAHDI ROM port from N5 to G2 makes me think, that it should be possible.
I would also be quite keen on getting involved in such an effort but I am not very fluent in porting Android ROMS.
I have basic coding skills and am not afraid of learning new stuff so I'd really appreciate if one of the Android-Gurus would kind of orchestrate the whole thing.
Thanks for your attention and good bye.
mick
That would be really awesome!
Yeah, but it seems it will remain a dream, as the members to whom this is addressed to, obviously do not read the Q&A Forums. Why should they anyway?
The problem is, if I open a development-thread it's not unlikely, that someone will be playing the wrong-forum-double-post-card.
mickmattes said:
Yeah, but it seems it will remain a dream, as the members to whom this is addressed to, obviously do not read the Q&A Forums. Why should they anyway?
The problem is, if I open a development-thread it's not unlikely, that someone will be playing the wrong-forum-double-post-card.
Click to expand...
Click to collapse
To be honest, I'd say look at Dr87's github. He ported Mahdi over... Though really I don't think that the rom itself is "ported" so much as the drivers/kernel/ramdisk need to be modified to work with the code on this device.
I would suggest starting by getting the rom source you want. Then setting up the device in the source using the devices/kernel/vendor files he made. You'll likely get errors during the build, but it would give you a starting point.
There are many, many guides out there on porting roms to new devices. Read through some of those if you haven't and it might help to steer you in the right direction.
Yoinx said:
To be honest, I'd say look at Dr87's github. He ported Mahdi over... Though really I don't think that the rom itself is "ported" so much as the drivers/kernel/ramdisk need to be modified to work with the code on this device.
Click to expand...
Click to collapse
Do you mean, that it is not "ported" due to the fact that the chipsets of both devices are the same?
I would suggest starting by getting the rom source you want. Then setting up the device in the source using the devices/kernel/vendor files he made. You'll likely get errors during the build, but it would give you a starting point.
Click to expand...
Click to collapse
Yeah, I'm going to try that. Sounds promising.
There are many, many guides out there on porting roms to new devices. Read through some of those if you haven't and it might help to steer you in the right direction.
Click to expand...
Click to collapse
I don't want to look lazy, but as you pointed out, there are many guides out there. Some are old, most are really old. Can you name one or two particularly good ones?
Anyway, thanks for your suggestions...it's going to be a long night.
No, I mean the rom source doesn't seem to need heavy changing typically. Usually the changes to the rom code at large is pretty minimal. Most of the time you need to tweak the device files to work with the rom (caf changes and such).
To be honest, I'd point you toward the Cyanogenmod guides... they have some custom commands but their guide would probably be the most up to date of any.
That should be correct. They have a FAQ at the Nethunter site where they say, that one could use the rom by building a rootfs. This would imply, however, that one could not use the features that come with a dedicated kernel.
So, yes, the rom part should not be the problem. The kernel part will be problematic. I think I'll send a message to dr87, perhaps he has some advice,too.
Just to make it clear, I bought this device some days ago and I want to be quite sure that my messing around with it will not brick or damage it somehow.
Ok. So I'll have a look at the CM-Guides.
I just read about this for the nexus 5 and googled for the lg g2 and came across this thread. I would love to get this working on my g2, gonna do some more googling and see if I can find anything else going on.
twist said:
I just read about this for the nexus 5 and googled for the lg g2 and came across this thread. I would love to get this working on my g2, gonna do some more googling and see if I can find anything else going on.
Click to expand...
Click to collapse
Hello
Is it possible to install NetHunter a device is jailbroken.
My phone Is LG G2 ....
.........0x0........
Would be freaking awesome!!
I am learning how to port Ubuntu, at the moment. Once I learn that, I can attempt to do it with Kali. Sound good? It may a take a bit, but better than no one trying at all.
SamsungIsBetterThanApple said:
I am learning how to port Ubuntu, at the moment. Once I learn that, I can attempt to do it with Kali. Sound good? It may a take a bit, but better than no one trying at all.
Click to expand...
Click to collapse
so, its been 6 years... Did u do it?
Hey there XDA! I need a little help with something. I'm trying to test some new optimizations, and there's one change that could make a huge difference or no difference at all, and I need more people than just me to help test it. The rom used for testing is my build of PureNexus, due to its closeness to stock aosp and assortment of features. Please make sure the rom fits our needs if you are unfamiliar. No user-end features have been changed. Both of the roms are compiled with a custom SaberMod 4.9 toolchain and DragonTC 3.9.
Obligatory "im not responsible if you brick your device"
The Experiment:
There are 2 builds that will be in the link downloads folder, Test A and Test B. There is one change between the two, in fact, it's just one Boolean value. Please help by downloading and flashing them, and reporting your experience.
The Rules:
Run each build for at least 1 day
Use your normal kernel with your normal settings
Please don't use xposed
Include your favorite benchmark and examples of differences (ex. app opening is slower/faster)
The experiment will end April 15th, please submit your results by then
The Downloads:
https://basketbuild.com/devs/frap129/Nexus%206%28shamu%29/Test
Thanks in advanced! The changes I made and the difference between the two will be released after the experiment ends!
Reserved for results and such
I'd love to flash this and test it out, but I'm going to need a bit more info. What are the changes you made? Also, if I do flash, is a full wipe necessary before I try the first as well as in-between the two?
It seems that a lot of what you are trying to test (benchmark, lag, possibly battery life) is a strong function of the kernel and not the ROM. So if your are asking the people to use their own kernel I'm not sure the feedback you get is comparable from person to person.
Also, as mentioned in the past above, it helps if you explain what these roms are, what they are based on, if you have complied them yourself or not, do they have any built in features different from stock, etc.
mrjiggywiggy said:
I'd love to flash this and test it out, but I'm going to need a bit more info. What are the changes you made? Also, if I do flash, is a full wipe necessary before I try the first as well as in-between the two?
Click to expand...
Click to collapse
The point of the experiment is to be a double blind test, therefore I would prefer not to say what change has been made. I have compiled both of these from source using SaberMod 4.9 and DragonTC 3.9, if that helps you at all. Thanks for your interest.
najoor said:
It seems that a lot of what you are trying to test (benchmark, lag, possibly battery life) is a strong function of the kernel and boot the ROM. So if your are asking the people to use their own kernel I'm not sure the feedback you get is comparable from person to person.
Also, as mentioned in the past above, it helps if you explain what these roms are, what they are based on, if you have complied them yourself or not, do they have any built in features different from stock, etc.
Click to expand...
Click to collapse
Your first statement is part of why I want to do this. Because the change was not to the kernel, any increase in performance should be maintained regardless of the kernel, though it may vary. In regards to your second statement, I stated in the OP that they are my builds of PureNexus. Obviously, no features were changed to remain consistent for the sake of the test. Nonetheless, thank you for your input. I will add more info to the OP
frap129 said:
.... I would prefer not to say what change has been made.
Click to expand...
Click to collapse
You should tell !
Will flash A tomorrow and B the day after tomorrow in a MultiROM (need Android N this week)
Also, any interest in a revival of G Watch developing?
NLBeev said:
You should tell !
Click to expand...
Click to collapse
I will once the experiment is over!
konradit said:
Will flash A tomorrow and B the day after tomorrow in a MultiROM (need Android N this week)
Also, any interest in a revival of G Watch developing?
Click to expand...
Click to collapse
Thanks for the help! and not at the moment. I had started working on a new rom, but then 6.0 came out and I had to scrap most of my work. Maybe when I get a little more free time.
frap129 said:
I will once the experiment is over.
Click to expand...
Click to collapse
OK. You are using the 'placebo effect'.
The user/patient may think it works. But in practice more that 50% may become unsatisfied.
Good luck with the experiment!
NLBeev said:
OK. You are using the 'placebo effect'.
The user/patient may think it works. But in practice more that 50% may become unsatisfied.
Good luck with the experiment!
Click to expand...
Click to collapse
Nope, for this to be placebo I would have to say which one should work better for the user to believe that it actually works better. There is a legitimate difference between the two, but one is not necessarily "better"
You are gonna be hard pressed for people to test this out with the vague way you put it. Let alone using those 2 useless tool chains. Many wont look twice just because of those.
Also one boolean change is not gonna make any real diff.
zelendel said:
You are gonna be hard pressed for people to test this out with the vague way you put it. Let alone using those 2 useless tool chains. Many wont look twice just because of those.
Also one boolean change is not gonna make any real diff.
Click to expand...
Click to collapse
Neither of them are useless, and this one boolean actually caused a major difference by changing the way that ART is compiled and targeted for a device. Please don't spread ignorant garbage without a little thought. It only hurts the community.
frap129 said:
Neither of them are useless, and this one boolean actually caused a major difference by changing the way that ART is compiled and targeted for a device. Please don't spread ignorant garbage without a little thought. It only hurts the community.
Click to expand...
Click to collapse
I'm not. Many developers have already called out the so called tool chains making a big diff. Why do you think none of the temp use them?
Either way good luck to you
to avoid all the arguing would it be possible for you to make 2 builds one pure untouched aosp with pure untouched aosp kernel and the other with just your one change based off the first? Seems that would simplify things greatly
adm1jtg said:
to avoid all the arguing would it be possible for you to make 2 builds one pure untouched aosp with pure untouched aosp kernel and the other with just your one change based off the first? Seems that would simplify things greatly
Click to expand...
Click to collapse
Well then I would have to download AOSP source code, which would take about a day with my internet speeds (and im not that patient lol). I honestly don't understand why using PureNexus is a problem.
frap129 said:
Well then I would have to download AOSP source code, which would take about a day with my internet speeds (and im not that patient lol). I honestly don't understand why using PureNexus is a problem.
Click to expand...
Click to collapse
You have to understand that people will not run a rom just to test something that most devs say are placebo.
A few months ago tool chains were all the talk and people found out for themselves.
zelendel said:
You have to understand that people will not run a rom just to test something that most devs say are placebo.
A few months ago tool chains were all the talk and people found out for themselves.
Click to expand...
Click to collapse
As I stated before, the difference between the two builds is not a toolchain, both use the same ones.
I imagine self reporting will be .... Anecdotal and skewed. Unless a person does exactly the same things in the same amount, error will ensue. Also use will likely vary moreso between a typical weekday and a Friday. If he dataset is big and diverse enough, these can be considered nominal but that means many hundreds of instances at the least. How do u plan to normalize the data, will there be measures of dispersion published?.... Don't mean to be that guy but unless u control the controls the results will not be robust and conclusive. I want to see this work and not have people's impressions be skewed by systemic flaws! I'm all about empirical evidence and ROM development and promotion are laden with unverifiable claims about performance and battery life. "Benchmarks don't matter" is all I hear. I would love to see standardized testing with repeatable data producing unbiased comparisons so the mystery is removed and claims are verifiable.
Sent from my Nexus 6 using Tapatalk
Guess the test is over with few to no takers.
Sent from my Nexus 6 using XDA Free mobile app
Nothing