Related
I started using Google ION ROM rev1 last week and I have been very happy. Question is, why is it so much faster and lag free than the standard G1 ROM? I was on JF 1.51 before this and it was very laggy. Also, I first tried Google ION ROM rev2 and I didn’t see any speed improvement.
Is Google ION ROM missing anything? If not, why wouldn’t Google optimize the G1 ROM to be this fast?
The first person to say something about a different version of DalvikVM is getting punched in the face
It's because it's a nice, clean build of AOSP 1.5r2 with no extra bull**** installed, thats all.
whats a DalvikVM?
j/k! "Ducks as cyanogen swings:
P.S. Luvin your work cyanogen, thank you sincerely.
and its not because it has pre-generated odex files either.
Its all kernel optimization I believe.
dwang said:
and its not because it has pre-generated odex files either.
Its all kernel optimization I believe.
Click to expand...
Click to collapse
Nope, the kernel is msm_defconfig (you can pull /proc/config.gz and compare for yourself), right from AOSP with zero changes.
cyanogen said:
Nope, the kernel is msm_defconfig, right from AOSP with zero changes.
Click to expand...
Click to collapse
Ok, it must be "magic" then.
dwang said:
Ok, it must be "magic" then.
Click to expand...
Click to collapse
I installed ion, I dont think its any faster than any of cyanogen's roms
defconoi said:
I installed ion, I dont think its any faster than any of cyanogen's roms
Click to expand...
Click to collapse
same here
salamandar said:
whats a DalvikVM?
j/k! "Ducks as cyanogen swings:
P.S. Luvin your work cyanogen, thank you sincerely.
Click to expand...
Click to collapse
DalikVM is a virtual machine created by some guy at Google.
http://en.wikipedia.org/wiki/Dalvik_virtual_machine
defconoi said:
I installed ion, I dont think its any faster than any of cyanogen's roms
Click to expand...
Click to collapse
I havent tried any cyanogens ROMs yet. I may have to give one a try, its based on JF 1.51, right?
defconoi said:
I installed ion, I dont think its any faster than any of cyanogen's roms
Click to expand...
Click to collapse
alapapa said:
same here
Click to expand...
Click to collapse
Did you install rev1 or rev2?
It's the dalvikvm combined with the .odex optimizations.
afflaq said:
It's the dalvikvm combined with the .odex optimizations.
Click to expand...
Click to collapse
did u even read the entire thread. Not its not.
dalvikvm in ion is exactly the same as j1.5.
android already does dexopt automatically on the dex files in the dalvik-cache. You can see it in the logcat whenever you change kernels.
All the stuff that people are doing to their ROMs are basically all placebo effect. The additional speeds that people are getting is from using cyan's boot.img.
I used ION for a few weeks, actually just started using Cyanogen's newest. I don't really notice much, if any, speed difference between the two. Same with Dude's latest ROM.
I do believe ION is all about the optimization (default CPU is 384mhz, not 528 on G1 port). ION was just optimized as much as possible to run the same speed on a slower processor. At least that's my take on it.
androidmonkey said:
Did you install rev1 or rev2?
Click to expand...
Click to collapse
both
(10 char minimum)
afflaq said:
It's the dalvikvm combined with the .odex optimizations.
Click to expand...
Click to collapse
See here about DalvikVM: http://forum.xda-developers.com/showpost.php?p=4021692&postcount=3791
It's snake oil. I don't know how or why people (and ROM developers) are spreading this idea. It's just plain wrong.
Then read this about dexopt (particularly the "preparation" section): http://android.git.kernel.org/?p=platform/dalvik.git;a=blob_plain;f=docs/dexopt.html;hb=HEAD
Those .odex files are the exact same thing that is generated by the runtime in dalvik-cache. Now, it *is* possible that accessing resources inside of an apk where the original classes.dex has been removed could be slightly faster due to smaller size, but the zip format is designed to be seeked on so I don't really buy this either.
cyanogen said:
See here about DalvikVM: http://forum.xda-developers.com/showpost.php?p=4021692&postcount=3791
It's snake oil. I don't know how or why people (and ROM developers) are spreading this idea. It's just plain wrong.
Then read this about dexopt (particularly the "preparation" section): http://android.git.kernel.org/?p=platform/dalvik.git;a=blob_plain;f=docs/dexopt.html;hb=HEAD
Those .odex files are the exact same thing that is generated by the runtime in dalvik-cache. Now, it *is* possible that accessing resources inside of an apk where the original classes.dex has been removed could be slightly faster due to smaller size, but the zip format is designed to be seeked on so I don't really buy this either.
Click to expand...
Click to collapse
Had the forums let me enter that in all caps to show my sarcasm I would have... /bonk
afflaq said:
Had the forums let me enter that in all caps to show my sarcasm I would have... /bonk
Click to expand...
Click to collapse
I realized that after I posted, but the points made are still true.
aFLACK!!!!
Again, it's not the dalkvik vm, or the odex files, or the smaller rom (not much actually, only a few files smaller than an adp google rom), it's the combination of the three plus a few other factors.
Dwang, you keep waving that flag that the dalvik vm does dexopt at the dalvik-chache, yet you're still failing to realize that IT IS DOING DEXOPT AT THE DALVIK CACHE... if the files are pre-odexed, the VM doesn't even do that. The dex at dalvik cache are not optimized, they're still dalvik bytecode, dalvik does this to prevent parsing the whole apk at app runtime and wasting time with both storing the dex to phone memory (which is already limited), and then running dexop at the extracted bytecode (because, as you correctly pointed out the other day, dalvik doesn't do jit, so .dex is quite useless to it),
with odexed files, you're saving both of those steps, the device just executes the .odex as needed without having to load to phone memory (thus linux's memory management doesn't kick in and dump, for example, home screen memory, explaining why you can return to home so quick). On T-Mobile's and google's roms, it goes an extra step by removing the .dex file from the apk, that way, when the machine still has to decompress the .apk file, it doesn't have to load such a big file to memory or check it all.
I don't think there's any sort of device specific modifications, since those would have been meant for the Ion and would break once running in Dream, unless it was haykuro that put them there, in that case, we're barking up the wrong tree and have to ask him what he did, but as I remember, it was actually him who broke ion with r2, so i guess that's not it either.
Nobody really knows why it works the way it does (and in some cases, doesn't work), but the combination of those three things i mentioned DO have an effect on how much work the phone has to do and how fast it can do it. Come on guys, it's all basic stuff...
What? Can people please read the entire thread before posting. Geez.
Its been established that the dalvik vm in ION is EXACTLY the same as in JF 1.5.
And, the dex files in dalvik-cache are optimized. Every time I load a new kernel, the dex files in dalvik-cache get re-generated.
Plus, cyan pointed to this link that says that it is:
http://android.git.kernel.org/?p=platform/dalvik.git;a=blob_plain;f=docs/dexopt.html;hb=HEAD
So its neither dalvik vm nor odex files that is contributing to the speed.
jubeh said:
Again, it's not the dalkvik vm, or the odex files, or the smaller rom (not much actually, only a few files smaller than an adp google rom), it's the combination of the three plus a few other factors.
Dwang, you keep waving that flag that the dalvik vm does dexopt at the dalvik-chache, yet you're still failing to realize that IT IS DOING DEXOPT AT THE DALVIK CACHE... if the files are pre-odexed, the VM doesn't even do that. The dex at dalvik cache are not optimized, they're still dalvik bytecode, dalvik does this to prevent parsing the whole apk at app runtime and wasting time with both storing the dex to phone memory (which is already limited), and then running dexop at the extracted bytecode (because, as you correctly pointed out the other day, dalvik doesn't do jit, so .dex is quite useless to it),
with odexed files, you're saving both of those steps, the device just executes the .odex as needed without having to load to phone memory (thus linux's memory management doesn't kick in and dump, for example, home screen memory, explaining why you can return to home so quick). On T-Mobile's and google's roms, it goes an extra step by removing the .dex file from the apk, that way, when the machine still has to decompress the .apk file, it doesn't have to load such a big file to memory or check it all.
I don't think there's any sort of device specific modifications, since those would have been meant for the Ion and would break once running in Dream, unless it was haykuro that put them there, in that case, we're barking up the wrong tree and have to ask him what he did, but as I remember, it was actually him who broke ion with r2, so i guess that's not it either.
Nobody really knows why it works the way it does (and in some cases, doesn't work), but the combination of those three things i mentioned DO have an effect on how much work the phone has to do and how fast it can do it. Come on guys, it's all basic stuff...
Click to expand...
Click to collapse
Okay, I finally cleaned up what I've been working on the past few weeks
New sqsh with tattoo senseui!
so this is senseui from the tattoo, so it runs at native resolution 240x320. I have not tested it at *any* other resolution.
I haven't done a lot of testing so I can't guarantee everything works... ie I think that bluetooth might be broken? who knows... other folks please post your experiences!
Please note: I *have* seen the whole thing crash due to WifiService dying on my vogue once... and I've also seen a hard lockup on the polaris once... not sure why or workaround, but it doesn't seem to be commonplace.
I use the tattoo.user.conf and I *don't* use rosie, and it runs nice and speedy... YMMV.
New rootfs that cleans up a *lot* of little things... you can now use the volume-down installer to *update* your nand partitions and back up your nand data! (you first have to have a the nand flash complete before this will work, and you need to use the rootfstonand with the updated rootfs)
Maybe I'll post some screenshots? who knows...
Everything is HERE
EDIT: Forgot the most important part... Credits!
This build is almost entirely from the Belgian HTC Click image posted somewhere out there. Lots of time was spent getting the RIL to talk to the phone application without crashes, but it seems somewhat stable now.
At my disposal I had donut and tattoo builds from enatefox, zenulator, plemen, and maybe a couple others.
Some bits needed to be swapped out to work, and that took the bulk of my time... oh well
I'll also give some creds to the folks over in kaiserland, but I'm not sure who (sorry).
Thanks muchly! Been beating my brains out trying to dyi a port of Tattoo and you've done all the hard work. Made my day, now I can go to sleep....
Trying this out tomorrow. I'll write about anything I see. Nice job.
Thanks Vilord
I'm a big fan of tattoo native resolution senseui.
testing.
lauyanyameric said:
it says:
No sys found on SD, booting Part/NAND
(e2fsck 1.41.4 (27-Jan-2009)
ext2fs_check_if_mount: No such file or directory while determining whether /dev/block/mmcblk0p3 is mounted.
/dev/block/mmcblk0p3: clean, 11/130560 files, 18794/522112 blocks
Using partitioned system
e2fsck 1.41.4 (27-Jan-2009)
/dev/block/mmcblk0p2 is mounted.
e2fsck: Cannot continue, aborting.
mount: Device or resource busy
Failed
Failed to mount /system
_
Click to expand...
Click to collapse
that is likely due to my new partition/nand management code...
What is your partition setup?
I'll poke at it in a few minutes
vilord said:
that is likely due to my new partition/nand management code...
What is your partition setup?
I'll poke at it in a few minutes
Click to expand...
Click to collapse
I don't know what could be causing the bootup issue
I dropped in some debugs and catchalls that might help
The faster!
This is the fastest version ever.
i'm using haret and no paritions, works perfect!
i wish i could put it on nand, but i'm using a NIKE and the NBH is for vogue...
NICE JOB VILORD!
Hi,.
Thanks vilord, this is the best build with sense that i have tried.
I have the mount system error the first time i try to boot it, the second time it boot without problem.
Im wrting this from this build
arleybarros: what is the state of android on NIKE at this point? Do you still have no vibrate?
all: I'm still not 100% sure why the installer's choking, but I'll poke it when I get home (I still need to partition the SD on my POLA200, so I should be able to see exactly what you see when I do it)
Sigh, more user freindly
I really don't mean to sound a negative note, your hard work , along with the other devs is sooo appreciated and admired. But for the many newbies that are out here, drooling other the new toys you guys are providing, I would really like to see complete bundles, which are updated as needed, with maybe a version number assigned to each updated build. Because of the modular nature of the OS, it is far to easy to to mismatch components resulting is a royal mess, and a real bad taste for potential users.
Or am I just full of it?
no you're completely right.
Once I get things ironed out with the installer, and after I've gotten some more feedback, I'll put it together with two zip downloads, one for NAND installation and one for haret/SD installation.
vilord said:
arleybarros: what is the state of android on NIKE at this point? Do you still have no vibrate?
Click to expand...
Click to collapse
Since the vibration was disabled (2009-09-22) all the builds works almost like vogue, except for:
Camera: never worked, maybe because the drivers are diferent or because nike camera max resolutuion is 2MP (force close)
Bluetooth: never worked, maybe drivers
Vibration: disabled
everythig else works perfect.
gjbnh said:
I really don't mean to sound a negative note, your hard work , along with the other devs is sooo appreciated and admired. But for the many newbies that are out here, drooling other the new toys you guys are providing, I would really like to see complete bundles, which are updated as needed, with maybe a version number assigned to each updated build. Because of the modular nature of the OS, it is far to easy to to mismatch components resulting is a royal mess, and a real bad taste for potential users.
Or am I just full of it?
Click to expand...
Click to collapse
I think this is a good idea too..thanks.
Im having trouble with data connection. it was one for a moment then stopped. Any suggestions?
Never mind I got it working. It was turned off in the settings. great build!
I'll make this nandable and post soon.
got it booted - without ext partitions
lauyanyameric said:
it says:
No sys found on SD, booting Part/NAND
(e2fsck 1.41.4 (27-Jan-2009)
ext2fs_check_if_mount: No such file or directory while determining whether /dev/block/mmcblk0p3 is mounted.
/dev/block/mmcblk0p3: clean, 11/130560 files, 18794/522112 blocks
Using partitioned system
e2fsck 1.41.4 (27-Jan-2009)
/dev/block/mmcblk0p2 is mounted.
e2fsck: Cannot continue, aborting.
mount: Device or resource busy
Failed
Failed to mount /system
_
Click to expand...
Click to collapse
I am really looking forward to this, but get the same result as lauyanyameric on my Kaiser, afterwards I am dropped to shell .... Anything I can do to help debug?
Tried it without partition, and I get data error and it created a 34 mb data.img.
Tried with a blank data.img (no partitions) and I was able to boot!
Grateful for your work! Thanks.
try formating your sd card again...
So far, so great.
Running via Haret and this is working superbly. Everything that should be working, is working.
So far have tested audio, data, GPS, camera (via Camera Pro), and apps such as Voice Search, Exchange Sync, Market and they all work and are quite responsive.
Noticed a few rosie reloads after using memory intensive apps, so I added a 32mb swap in the conf file. So far no more rosie reloads.
Also, the USB to PC app doesn't appear to like my work machine. Not sure if this is an issue with the desktop or the app.
Will be flashing to NAND after a bit more testing.
Thanks again Jesse!
Cheers
Nick
First off thanks for all the hard work you and others have done bringing android to the vogue. I have donut running off of nand right now and love it but am wanting to try this build but have no idea how to reflash it on there. i have tried searching and searching but i havent found a good answer on how to do it.
nabicat said:
So far, so great.
Running via Haret and this is working superbly. Everything that should be working, is working.
So far have tested audio, data, GPS, camera (via Camera Pro), and apps such as Voice Search, Exchange Sync, Market and they all work and are quite responsive.
Noticed a few rosie reloads after using memory intensive apps, so I added a 32mb swap in the conf file. So far no more rosie reloads.
Also, the USB to PC app doesn't appear to like my work machine. Not sure if this is an issue with the desktop or the app.
Will be flashing to NAND after a bit more testing.
Thanks again Jesse!
Cheers
Nick
Click to expand...
Click to collapse
Im getting the Rosie reloads too... how do you add the 32mb swap or better yet can you just upload your conf file? Thanks
vilord said:
no you're completely right.
Once I get things ironed out with the installer, and after I've gotten some more feedback, I'll put it together with two zip downloads, one for NAND installation and one for haret/SD installation.
Click to expand...
Click to collapse
Thank you I think doing this will add a layer of usability to the releases, and gain a greater community of users as a result. Personally I would rather have releases further apart in time with this kind of thing rather than a rush to try the newest toy.
This is a quick walkthrough of how to apply my variant of "Mimicans speedfix" using my kernels on the Captivate. The speedfix essentially consists of making an ext3 or ext4 filesystem on an sdcard, and using that as our /data directory. This method is different from the original method in many of the details, but the underlying basis is that the stock /data partition is slow as molasses so we replace it.
This method should be pretty safe. As you will notice we dont copy around stuff and create a symlink mess. We just mount a partition over the current one. Yes we still mount the old one as well, even though it wont be used unless you take your card out. If that happens the phone will mount your old /data (that will probably be very out of date at the time) but itll get you up and running right away.
Right now there are two kernels, these mount the default partition, ext3 or ext4 on the second sdcard partition, the two options are:
Stock clock speed and Overclocked.
The overclocked kernel will clock from 100 to 800 Mhz as stock, then skippinig 1Ghz going to 1.2 Ghz.
Also, before we begin make sure you have this version of Odin. I used Samsung windows drivers that I found here.
You'll also want to read this thread about download mode. here you'll learn that you will have to try real hard to actually brick these phones, and even then it may still boot.
Ofcourse you also want to have root on your captivate.
You'll also need the android sdk.
If you are on Windows or Mac you will need some software to partition and format the sdcard, this live cd will work. You could also just get an ubuntu live cd or similar.
So, now we have the necessary tools and our new kernels and can get started.
Partition the disk:
There were reports from the modaco forums when mimocan first released his fix that ext3/4 partitions larger than 2gb were a problem, so keep your 2nd partition 2gb or smaller.
Use your favorite partitioning sofware to create 2 partitions on your sdcard. the first one will be formated FAT32 (vfat), and the second one ext3 or ext4. Make sure both are 'primary partitions'. You may want to make the second partition have partition type 83 (linux native).
Copy data files to sdcard:
If you are coming from stock, (eg without an existing a2sd /data partition on your sdcard) boot the phone without your formatted card and hotplug it before starting this process.
Using the sdk you need to connect the phone and use 'adb shell' to get a prompt on the phone.
Then follow these steps:
Code:
$
$ su -
# mkdir /sdcard/mnt
# mount -t ext4 /dev/block/mmcblk1p2 /sdcard/mnt
# busybox cp -a /data/* /sdcard/mnt
# umount /sdcard/mnt
# exit
$ exit
Flashing the kernel
1) Disconnect USB cable.
2) Open up odin.
3) Put your phone into download mode.
4) Connect USB cable, wait a second Odin should detect your phone, if not fiddle about with your drivers and reboot windows or something. This can be a real PITA.
5) In Odin load the kernel tarfile as "CSC"
6) Click "Start" in Odin, flashing should only take a few seconds.
You may run into issues here randomly and have a phone with the phone-!-computer image (I did!). Just go read up on the 'download mode' thread linked above it tells you how to proceed.
7) When you have booted your new kernel and /data partition you may have some issues with a few widgets/apps. Reinstalling or waiting/fiddeling with them seems to solve the issue. Maps was slow to open the first time after a new /data partition was mounted for me a few times, but subsequent launches were snappy.
If you want you may donate to my beer fund. It is not necessary but much appreciated
Didn't work for me. I partitioned my external SD card, flashed the speedup2 kernel, then ran the commands you posted, replacing 'ext3' with 'ext4'. My quadrant score is still in the low 900's.
Can you explain exactly what those commands do? The mimocan fix makes a lot more sense to me. Why did you decide to take a different approach?
Thanks for your help and effort!
I get 1716 scores in quadrant, but with real world running tests Touchdown and Dolphin HD browser still lag like holy hell.
I originally had the "method 2" hack (moving apps to the NAND) and that worked wonders, especially with these apps.
Can anyone test these two applications and see if there is lag for you?
Dolphin - try opening a new tab, closing it, and goto a large page and scroll with the volume buttons - it should all be smooth and quick
Touchdown - It should be very quick going between emails, I get a 5+ second delay before showing the email
Also in Quadrant, even though I get 1700 scores, do you guys get stuck at I/O Database writes for a good 3+ minutes?
The captivate speedup kernel link is dead. Can soneone please post a mirror? Thanks
Worked great for me using ext4 partition/kernel. It brought my quadrant to 1817! Thats with a poor little 4gig, class 2 micro sd card. Im also running the i9000 JM2 firmware with Samset 1.6.
Thank you for all your hard work!!!! My phone is now complete (for now lol).
andy2na said:
I get 1716 scores in quadrant, but with real world running tests Touchdown and Dolphin HD browser still lag like holy hell.
I originally had the "method 2" hack (moving apps to the NAND) and that worked wonders, especially with these apps.
Can anyone test these two applications and see if there is lag for you?
Dolphin - try opening a new tab, closing it, and goto a large page and scroll with the volume buttons - it should all be smooth and quick
Touchdown - It should be very quick going between emails, I get a 5+ second delay before showing the email
Also in Quadrant, even though I get 1700 scores, do you guys get stuck at I/O Database writes for a good 3+ minutes?
Click to expand...
Click to collapse
Might be tome for you to pick up a new SD card. I have used both fix's and find this fix to be way better. I get no lag in Dolphin HD.
_Opiate_ said:
Might be tome for you to pick up a new SD card. I have used both fix's and find this fix to be way better. I get no lag in Dolphin HD.
Click to expand...
Click to collapse
Its a brand new Kingston 8gb class 4 card, havent used it before applying this hack
Postal76 said:
Didn't work for me. I partitioned my external SD card, flashed the speedup2 kernel, then ran the commands you posted, replacing 'ext3' with 'ext4'. My quadrant score is still in the low 900's.
Can you explain exactly what those commands do? The mimocan fix makes a lot more sense to me. Why did you decide to take a different approach?
Thanks for your help and effort!
Click to expand...
Click to collapse
All you do is copy the files from your original /data partition onto the root of your ext{3|4} partition on the sdcard. Then that is mounted on reboot ontop of /data so you can use the new data partition from your card.
I feel this is a MUCH cleaner method than the original Mimocan fix, that copis a full copy of data into the root of the device (unnecessary backup since you still have your original /data partition as well), then it mounts your sdcard on /disk and symlinks that to /data.
I just don't see the need for the symlinks and stuff and honestly I thought this was a simpler method, no symlinks or anything.
If you arent seeing any speedups I'm betting something didn't go right, you are probably still running of the old /data partition. Are you sure you are running the speedup2 kernel and not the ext4 only kernel?
spyz88 said:
The captivate speedup kernel link is dead. Can soneone please post a mirror? Thanks
Click to expand...
Click to collapse
It seems to work from here...
_Opiate_ said:
Might be tome for you to pick up a new SD card. I have used both fix's and find this fix to be way better. I get no lag in Dolphin HD.
Click to expand...
Click to collapse
Except the Quadrant scores do you notice any real speed boost?
andy2na said:
.....
Also in Quadrant, even though I get 1700 scores, do you guys get stuck at I/O Database writes for a good 3+ minutes?
Click to expand...
Click to collapse
yeah database I/O takes forever still.
Like I said in the other thread, try to reinstall the apps, Dolphin is very very fast here (thanks for getting me a new browser btw.)
I'm still a complete failure and now i get stuck at the galaxy s boot screen
Nuke, after doing the ext4 only method, I only get quadrant scores of 900.
Am I doing something wrong? I go through all the steps fine and everything seems like it went well but it seems like I'm doing something wrong down the line.
one thing I do notice is that I have A LOT MORE AVAILABLE MEMORY in advanced task killer. I use to only have 100 now I have 180MB.
Is it crucial to have to flash the Speedfix2?
after i put in
busybox cp -a /data/*
nothing happens it just sits there
igm503 said:
after i put in
busybox cp -a /data/*
nothing happens it just sits there
Click to expand...
Click to collapse
that part took like 15 min for me since I have a lot of application and app data
but there is no trailing dot it just repeats what i typed and then leaves a blank space
same thing it just repeats it
igm503 said:
but there is no trailing dot it just repeats what i typed and then leaves a blank space
Click to expand...
Click to collapse
What do you mean by "there is no trailing dot" ? Did you type it in? You need to include the trailing dot in your command; based on what you posted it appears you did not do that.
WOW! Okay... So now I'm getting 1756...
You just have to leave Quadrant on for like 15 minutes sometimes! This is very strange!
Notice the period after the asterisk. In the old forum, someone had a problem with that.
I did this fix last night after countless times of my messing up and figuring out how to partition with my phone still being able to read the card, flash problems with Odin, etc etc. I'm using an 8gb Classic 6 and just got an 1805 in Quadrant, and the phone is incredibly, noticeably faster. Did have some weird app problems when it was first applied, but some reinstalls fixed it. Thanks again Nuka!
Sent from my SAMSUNG-SGH-I897 using XDA App
Don't wanna post other peoples work... so go get it yourself through ROM Manager.
Anyone tried this yet?
I have. Great ROM. But the Bluetooth is still choppy. Is there a fix for this. This is the one and only reason I can't use this ROM. I need Bluetooth.
Sent from my Incredible using XDA App
Downloading it now. I've never used Rom Manager before and noticed there was CM 6.0.1, 6, and 6 RC3. Was CM 6 stable release newer than RC3? I've been on RC3 since it came out and it's been rock solid other than random reboots with wifi on.
where?? dont see.. cleared download cache
This is awesome, download now. Koush will update his thread soon, but for those who don't use clockwork app here is the download site
http://koush.tandtgaming.com/htc/inc/
ACD168 said:
This is awesome, download now. Koush will update his thread soon, but for those who don't use clockwork app here is the download site
http://koush.tandtgaming.com/htc/inc/
Click to expand...
Click to collapse
Thanks for the link, my phone was cutting off the download. Will try and post results later.
unreal2k said:
Thanks for the link, my phone was cutting off the download. Will try and post results later.
Click to expand...
Click to collapse
No problem man, you're welcome.
Is there a changelog for these?
rulevoid said:
Is there a changelog for these?
Click to expand...
Click to collapse
+1 [10 chars)
Unlike 6.0.0, 6.0.1 does not appear to be overclocked, and it is much more stable on my Inc. No reboots yet.
http://github.com/CyanogenMod/android_device_htc_inc
write /sys/module/lowmemorykiller/parameters/minfile 0,0,0,5120,5632,6144
write /sys/module/lowmemorykiller/parameters/check_filepages 1
+ # Power Management
+ write /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq 245000
+ write /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq 998400
+ write /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor ondemand
+ write /sys/devices/system/cpu/cpufreq/ondemand/sampling_rate 40000
+
service wpa_supplicant /system/bin/logwrapper /system/bin/wpa_supplicant \
-Dwext -ieth0 -c/data/misc/wifi/wpa_supplicant.conf
# we will start as root and wpa_supplicant will switch to user wifi
...still only seeing ~700MB of internal storage.
Update
I did S-off, upgraded the radio to 2.15 and installed CM 6.0.1.
I overclocked to 1.152 and i got 1450 in quadrant. So far so good.
I connected it to my computer and it asked me to format the internal memory, only 760mb shows up as total space to format though. Any thoughts?
Edit: Now under phone settings it shows 0.00B for internal memory and i get notifications for low disk space.
Edit2: Restarted the phone and now i'm in a boot loop. Back to SR 2.5 for now.
I am still unable to get facebook to sync with my contacts on this? 6.0.1, Any help please, I can get anything else working no problem. Works perfect with the Facebook for Sense...
Amin Sabet said:
Unlike 6.0.0, 6.0.1 does not appear to be overclocked, and it is much more stable on my Inc. No reboots yet.
Click to expand...
Click to collapse
That's great news! The instability / reboots made the previous versions nearly unusable for me. I look forward to trying this.
Does sling player work yet?
Could someone package an update.zip with the changes? I hate wiping for only a dozen lines of code when I JUST restored all my apps before 6.0.1 was released
Can anyone post the kernel version? I've heard that the kernel that comes with 6.0.1 isn't overclocked, however I'm still able to oc to 1.15
I did an install with no wipe, if the kernel and / or build number differs then I'll do a full wipe.
AaronBBrown said:
...still only seeing ~700MB of internal storage.
Click to expand...
Click to collapse
That's not the same as your 8gb of onboard storage. That's your app storage you really can't get to normally. If you installed the 6.0 final or 6.01 you will see your onboard 8gb storage in Astro File Manager. Main problem still exists though, the OS isn't scanning it for music and photos like it should. That's going to be fixed eventually.
This version is MUCH more stable for those who had reboots and black screen issues. It's only been about 12 hours but I haven't had an FC or any reboots yet. Just look forward to the fix mentioned above and Bluetooth getting finalized.
EDIT - an hour after posting this my phone was stuck with a black screen, no response for several minutes until it finally rebooted... oh well
Hi!
trying to fix my imei I accidentally wiped my "persist" partition
A2017 Chinese model convert to A2017u
twrp 3.2.3.0 bootloader unlocked
persist partition is missing in my twrp backup
error:failed to mount '/persist' (invalid argument)
realy need help
Regards!
@netphone: You can format the persist partition from TWRP, with mke2fs or mkfs.ext4, as ext4 filesystem. But then your device's auto-rotate, sensors, etc probably won't be working. This is because some of the persist partition's contents aren't automatically regenerated even after it is formatted.
Quite some time ago I made a backup of this partition in case of issues listed above, and then subsequently wiped it by accident. Luckily I had a backup I could restore. You can find it at:
https://forum.xda-developers.com/showpost.php?p=75981746&postcount=1844
Several members tried it and said it works fine. Just flash the zip in TWRP.
I have an A2017U, and since you are converting to A2017U from A2017, then it should work. It's not like you have anything to lose, your partition is already wrecked anyway, the most that happens is it doesn't work out. In the future, I would advise making your own backup. It (the partition) is only 32MB in size.
AnonVendetta said:
@netphone: You can format the persist partition from TWRP, with mke2fs or mkfs.ext4, as ext4 filesystem. But then your device's auto-rotate, sensors, etc probably won't be working. This is because some of the persist partition's contents aren't automatically regenerated even after it is formatted.
Quite some time ago I made a backup of this partition in case of issues listed above, and then subsequently wiped it by accident. Luckily I had a backup I could restore. You can find it at:
https://forum.xda-developers.com/showpost.php?p=75981746&postcount=1844
Several members tried it and said it works fine. Just flash the zip in TWRP.
I have an A2017U, and since you are converting to A2017U from A2017, then it should work. It's not like you have anything to lose, your partition is already wrecked anyway, the most that happens is it doesn't work out. In the future, I would advise making your own backup. It (the partition) is only 32MB in size.
Click to expand...
Click to collapse
can i also use it on G version? i think something messed up in my persist partition.
i have read this on xda:
PERSIST - contains data which shouldn't be changed after the device is shipped, e.g. DRM related files, sensor reg file (sns.reg) and calibration data of chips; wifi, bluetooth, camera etc.
Some package installers such as OpenGapps also make use of this partition to read configuration file.
also contains calibration data etc.I like to try this as i counter calibration issues.
If yes,any recommend on what OS i should flash this? And should i wipe my persist partition before flashing yours?
I try to backup my own persist partition in TWRP,but in backup it shows my perist partition is 0mb.On diskinfo it says my partition is 27,5mb in size,but others report theirs are 32mb in size.
EDIT; i still did a backup in twrp even though it says the size is 0mb.The backup map is like 300kb.
how did you wiped persist partition? In twrp wipe section persist is not showed
@Predatorhaze: My zip may work on G, or not, you can try and let me know.
You can "wipe" persist with the command:
dd if=/dev/zero of=/dev/block/bootdevice/by-name/persist
And back it up with:
dd if=/dev/block/bootdevice/by-name/persist of=/sdcard/persist.img
Run these commands from TWRP terminal. dd is a famous Linux command line utility.
The partition is exactly 32MB in size.
AnonVendetta said:
@Predatorhaze: My zip may work on G, or not, you can try and let me know.
You can "wipe" persist with the command:
dd if=/dev/zero of=/dev/block/bootdevice/by-name/persist
And back it up with:
dd if=/dev/block/bootdevice/by-name/persist of=/sdcard/persist.img
Run these commands from TWRP terminal. dd is a famous Linux command line utility.
The partition is exactly 32MB in size.
Click to expand...
Click to collapse
and after the command,i mount persist and flash the zip?
thanks!
@Predatorhaze: If you wipe persist with my command, then it will be unmountable prior to flashing the zip. This is because dd destroys persist's ext4 filesystem by zeroing it out. After the zip is mounted TWRP should mount persist automatically, but if not you can do it manually.
You should Google the difference between partition, volume, and filesystem.
AnonVendetta said:
@Predatorhaze: If you wipe persist with my command, then it will be unmountable prior to flashing the zip. This is because dd destroys persist's ext4 filesystem by zeroing it out. After the zip is mounted TWRP should mount persist automatically, but if not you can do it manually.
You should Google the difference between partition, volume, and filesystem.
Click to expand...
Click to collapse
When i used your command it says no more space left,32mb copied,0mb.Then i flashed your persist zip and rebooted twrp.
Now i flashed ROM and gapps magisk etc.I see playstore mounts persist (dont know why),after flashing all files i manually wiped all folders and files from persist folder and flashed your persist zip again,then ive powered off my phone,turned on and booted.Thanks
I already noticed the size is different,my persist folder was smaller in size,and also the thermal kicked in when booted on os.Phone was warm and CPU limited to 1036mhz.I noticed this thermal kick in was gone since i complained about battery.
My battery was sitting on 12%,i run geekbench cpu bench...half way of the bench my phone shut down (shows 0% battery,but half way in bench it was still 12%).I decided to just power on my phone and boot.My phone booted the os and shows 10% battery.Dont know if this is a bug in geekbench or something else..
I reached 4+ hours sot with 2 hour of gaming (from 100% to 10%).
Also i charged my phone at night ( i do this rarely).when i woked up my battery was 100% and unplugged the charger,when i unplugged it droppped direct to 99%.Is this normal? I can remember with my previous devices when i charged at night,and unplugged in the morning,it sits on 100% for a while
@Predatorhaze: It is possible for a computer (which a phone is) to shut down while running stress testing software, if this happens then it means your setup is unstable and couldn't handle the tests. Sometimes the OS will intentionally crash itself (BSOD) to prevent damage to itself or hardware. I like to overclock PCs as a hobby, and while there's a lot I don't know, I've been at it long enough to master the basics. I regularly do benchmarking and stress testing to see if my setups are rock solid, or need more tuning.
AnonVendetta said:
@Predatorhaze: It is possible for a computer (which a phone is) to shut down while running stress testing software, if this happens then it means your setup is unstable and couldn't handle the tests. Sometimes the OS will intentionally crash itself (BSOD) to prevent damage to itself or hardware. I like to overclock PCs as a hobby, and while there's a lot I don't know, I've been at it long enough to master the basics. I regularly do benchmarking and stress testing to see if my setups are rock solid, or need more tuning.
Click to expand...
Click to collapse
Thanks.
Can you maybe share your stock /sys folder also?
@Predatorhaze: Why do you need my sys directory? I'm not running a stock ROM, BTW.
AnonVendetta said:
@Predatorhaze: Why do you need my sys directory? I'm not running a stock ROM, BTW.
Click to expand...
Click to collapse
To compare with mine and maybe replace it
@Predatorhaze: Umm...no. That directory contains thousands of subdirectories and quite a few files. As well as a bunch of symbolic links that point to other places. It wouldnt be quick or convenient to make a zip. Do you even know what Android/Linux use /sys for? I do, and I'm pretty sure you don't even understand what you're really asking for. In any case, sys won't hold the answer to your questions. It seems to me that you are off on a wild goose chase.
AnonVendetta said:
@Predatorhaze: Umm...no. That directory contains thousands of subdirectories and quite a few files. As well as a bunch of symbolic links that point to other places. It wouldnt be quick or convenient to make a zip. Do you even know what Android/Linux use /sys for? I do, and I'm pretty sure you don't even understand what you're really asking for. In any case, sys won't hold the answer to your questions. It seems to me that you are off on a wild goose chase.
Click to expand...
Click to collapse
No,i dont really know,and you are right.Im still trying to find out my battery % problems (And no,its not because my battery is degraded)
i used in terminal cat /sys/class/power_supply/bms/charge_full and it showed something with 29xxxxxx,where i think my battery cap is around 2900mah and i believe this,as i reach more than 4 hours sot with gaming included.
Thank anyway for all your help!
AnonVendetta said:
@Predatorhaze: It is possible for a computer (which a phone is) to shut down while running stress testing software, if this happens then it means your setup is unstable and couldn't handle the tests. Sometimes the OS will intentionally crash itself (BSOD) to prevent damage to itself or hardware. I like to overclock PCs as a hobby, and while there's a lot I don't know, I've been at it long enough to master the basics. I regularly do benchmarking and stress testing to see if my setups are rock solid, or need more tuning.
Click to expand...
Click to collapse
this shutdown only happens when its less than 20% or something.I also noticed when its less than 20%,geekbench shows 3 clusters where one of them is at 0.0ghz.
maybe some problem with fuel gauge.
i tried to reset the gauge at 100%,but sot is just worse now
@Predatorhaze: I recently received a private message from @Choose an username..., his unedited PM is below:
heads-up about ter
Just some info, do what you want with it:
This Predatorhaze guy is the most toxic user in our side of xda, he thinks his battery is pristine, asks for help, then refuses it and tries to find a culprit anywhere
A couple months ago he claimed that Oki's "Deep Wipe" function made his battery go bad (which he claimed beforehand too) and his explanation was that it made the system believe he had two batteries...
His shutdown problem when he ran a benchmark is not because of system instability or whatever, that's rather overclock/volt specific as we don't really have any oc kernel. The problem he has is that BCL acts when voltage goes below the safe threshold, because his battery is so wrecked that it can't withstand high current usage (i.e. high internal resistance and other stuff). I'm not going to tell this to him because he'll branch out as he usually does.
He's blaming the persist partition because his lockscreen says 5V charging speed, that's what he said in Telegram ? i mean we appreciate you keeping him busy, but you're just wasting your time. if anything just try to convince him that his battery is K.O., maybe he can change it and stop destroying whatever's left of this...
My response:
Re: heads-up about ter
I don't really need a heads up about anyone, although he is a waste of time. He doesn't know much of anything, but he is looking for any excuse at all that will explain his battery issues. If you ask me his battery is bad, I already tried telling him this. I only continue to try to help him because I figure he might listen at some point, but he's wearing my patience thin.
You dont need to tell him anything directly, I've decided I'm going to forward him a verbatim copy of your PM, and maybe my response as well. I really don't feel that it's OK to trash talk someone behind their back, especially when you wouldn't say the same things to them directly. If I have an issue with someone, then I take it to them direct, I'm not known for mincing words. Maybe he will just "lose it" on the forum and get himself permabanned. But then it will be his fault.
Mind if I ask what Telegram group you are a member of? Is it related to LOS?
His response:
Re: heads-up about ter
Who says I wouldn't say it to him directly? All of us did, he eventually got banned on the Schwifty group, made a different account, got banned again. It's borderline bullying on the GSI testing group. Now he's going around every old ROM thread commenting how they don't work
Also attach a verbatim copy of your comment, of course ?
Which has led up to now...honestly, your battery is going bad, you are just unwilling to accept it. Please stop wasting people's time, being antagonistic in general, and being more stubborn than a pack mule. Your request for my /sys directory is asinine, up until this point I've just been trying to help you, but you are deluding yourself. The sooner you replace your battery, the sooner your issues will be resolved. I will no longer continue to post in threads where you complain about your battery and post about weird off the wall **** that you think are supposedly causing your problems. Enough is enough.....
ok enough said.
i already told 100 times,these problem occurs on different setups,what they say is wrong.
that thing about geekbench,doesnt happen always.
and i have changed my battery...it sits on 50%.Doesnt chharge up,doesnt go down,just sits on 50%.
also sometimes when i change bootstack+vendor partition,my battery shows different % after.