Related
I had a few questions that I can't pull up much information on. There looks to be a ton of updates we now have the option of putting on our EVO, what are the differences.
Kernel
--- Alright, I know this one but for anyone who doesn't. This is the heart of the phone. It is what allows software to talk to hardware.
--- Why do some of the kernel changes break the camera/accelerometer? Are these drivers built into the kernel instead of modules? Can they not be rebuilt with different kernels?
NAND
--- What is the NAND and why are we unlocking it?
--- NAND is a type of flash, no? Are all they system files (i.e. the /system folder) on their own chip inside the evo? How can rooting and remounting the system r/w not control the /system folder?
--- While I'm at it, does rooting just me remounting everything but the /system folder as r/w. So a non rooted phone is read only except for the SD card and where ever apps from the market are installed?
Recovery
--- It seems like there are a couple recovery systems out there... clockwork and another. Did the EVO not come with its own recovery system. What have these modded versions added?
ROMS
--- What are these really doing if they are not messing with the /system folder. Are they just a bundle of different programs? Change the rom and you change the programs that are installed? What is the difference between a ROM and a DEV-ROM
RADIO
--- What is the deal with the new radio. Is it updated drivers for the baseband? This kind of gets into my kernel question about how the drivers are handled within the kernel. How can this work across multiple kernels, but we cant get the camera working?
I know this is a lot, but if anyone could fill in some of the holes for me I would appreciate it.
Thanks
bump...
Any thoughts? You don't have to answer them all.
I am NO expert, but can help a bit....
Kernel
--- Alright, I know this one but for anyone who doesn't. This is the heart of the phone. It is what allows software to talk to hardware.
--- Why do some of the kernel changes break the camera/accelerometer? Are these drivers built into the kernel instead of modules? Can they not be rebuilt with different kernels?
From my understanding, the kernles that break the camera, are kernels that are ports of kernels from other phones. So, the drivers for the camera are not the same as for the other phones camera.
Recovery
--- It seems like there are a couple recovery systems out there... clockwork and another. Did the EVO not come with its own recovery system. What have these modded versions added?
My understanding is that the phone's original recovery, is locked to only flash Sprint's Official ROM's. So the custom recovery will allow to flash custom ROM's
ROMS
--- What are these really doing if they are not messing with the /system folder. Are they just a bundle of different programs? Change the rom and you change the programs that are installed? What is the difference between a ROM and a DEV-ROM
Aside from changing apps, ROM's can do different things like optimizing the apps so that they run smoother, move data from one place to another to run more efficiently and allow for a number of customizations that would not be available with only the stock ROM rooted. A ROM is understanded as a usable, stable ROM. A DEV-ROM is one that is not stable, were it has things that still dont work and need to keep improving.
Hope it helps!
Perfect thanks.
The ROM/DEV-ROM thing was really bugging me, and the recovery explanation makes sense.
amw2320 said:
I had a few questions that I can't pull up much information on. There looks to be a ton of updates we now have the option of putting on our EVO, what are the differences.
Kernel
--- Alright, I know this one but for anyone who doesn't. This is the heart of the phone. It is what allows software to talk to hardware.
--- Why do some of the kernel changes break the camera/accelerometer? Are these drivers built into the kernel instead of modules? Can they not be rebuilt with different kernels?
Click to expand...
Click to collapse
So with *.NIX kernels such as linux, unix, and the android kernel there are modules that make up the kernel itself. Any *.NIX kernel is going to be modular and this makes it more efficient and robust. In the case of specific items not working between different kernels, it most likely means the kernel was compiled with specific modules that have specific scripts and drivers in it. This method speeds up the kernel because it takes out stuff not needed. But means it limits the devices the kernel can run on.
In the case of Android ROMs not being able to fully interface with hardware, it likely means the kernel is missing something as another commentator already suggested.
NAND
--- What is the NAND and why are we unlocking it?
--- NAND is a type of flash, no? Are all they system files (i.e. the /system folder) on their own chip inside the evo? How can rooting and remounting the system r/w not control the /system folder?
--- While I'm at it, does rooting just me remounting everything but the /system folder as r/w. So a non rooted phone is read only except for the SD card and where ever apps from the market are installed?
Click to expand...
Click to collapse
We are unlocking NAND and rooting phones to get access to file systems that are locked down by phone manufactures/cell providers. Doing so unleashes the full potential of the device.
If you rooted your phone and you do not have full access to the file system, you only did part 1 of the root process. There are 2 parts because one unlocks NAND and the other unlocks the file system completely with the phone booted. Step 1 just unlocks filesystem for NAND which means you have to be booted into NAND for full access to file system. I think I have that right.
Recovery
--- It seems like there are a couple recovery systems out there... clockwork and another. Did the EVO not come with its own recovery system. What have these modded versions added?
Click to expand...
Click to collapse
Clockwork and the others are just replacing NAND with their own system, if I am correct. I recommend doing this if you are rooted because you get better features and a constantly updated system, where as NAND is only updated when Sprint and HTC have an update with a NAND update in it (which isn't often). The way I recommend updating this is using ROM Manager once you are rooted. It is very safe and easy.
ROMS
--- What are these really doing if they are not messing with the /system folder. Are they just a bundle of different programs? Change the rom and you change the programs that are installed? What is the difference between a ROM and a DEV-ROM
Click to expand...
Click to collapse
When you see ROM, think GUI for the OS, collection of apps and scripts. The ROM what you are going to interact with and use. I highly recommend flashing a custom ROM once rooted because you will have less problems and they are way more efficient than stock. Developers take time and care to test and tweak their ROMs so that they not only perform good, but give us the features we want. Find one you like and install. Make sure you do a NAND backup though once you get everything installed the way you like. Also do a titanium backup (app from marketplace) too.
RADIO
--- What is the deal with the new radio. Is it updated drivers for the baseband? This kind of gets into my kernel question about how the drivers are handled within the kernel. How can this work across multiple kernels, but we cant get the camera working?
Click to expand...
Click to collapse
It is recommended not to mess with the radio unless a ROM you want requires it. I flashed it without any trouble at all and things seem fine on my phone. Some people recommend flashing it because they think it makes the cell radios in the phone perform more efficiently and such. This is all I can say on the radio as I'm no expert.
I see most of the questions have been answered above...I'll attempt as well and perhaps it will help clarify (or just give a different way of looking at it).
amw2320 said:
I had a few questions that I can't pull up much information on. There looks to be a ton of updates we now have the option of putting on our EVO, what are the differences.
Kernel
--- Alright, I know this one but for anyone who doesn't. This is the heart of the phone. It is what allows software to talk to hardware.
--- Why do some of the kernel changes break the camera/accelerometer? Are these drivers built into the kernel instead of modules? Can they not be rebuilt with different kernels?
Click to expand...
Click to collapse
Yes, the kernel is the heart of any OS (Windows has one, Linux has one, etc). The kernel is where everything eventually goes to do anything.
The reason the new kernels do not have camera functionality is because, while we have generic source code, we do not have the drivers/modules for that source code. HTC does some modifications within the source that are proprietary and so we have to attempt to try and reverse engineer it. About the time we do, they release the source code (I have suspicions of conspiracy, but that may just be me) and that's when the kernel's really roll out with some fun stuff.
New kernels will be the source of the most new features...overclocking, efficiency improvements, etc.
NAND
--- What is the NAND and why are we unlocking it?
--- NAND is a type of flash, no? Are all they system files (i.e. the /system folder) on their own chip inside the evo? How can rooting and remounting the system r/w not control the /system folder?
--- While I'm at it, does rooting just me remounting everything but the /system folder as r/w. So a non rooted phone is read only except for the SD card and where ever apps from the market are installed?
Click to expand...
Click to collapse
This is one of the areas I'm most weak in for understanding but I'll still take a stab.
NAND is a type of flash and, to my knowledge, it's own seperate chip. It is usually locked to prevent modifications that could break your phone or prevent it from updating properly...I *think* it's used during boot so the lock would translate straight through to your OS and prevent changes if put in a locked state (think similar to how some SD cards have a "lock" switch on the side to make it read only, except a software version of it).
Recovery
--- It seems like there are a couple recovery systems out there... clockwork and another. Did the EVO not come with its own recovery system. What have these modded versions added?
Click to expand...
Click to collapse
Clockwork and AmonRA's recoveries are replacements that add functionality over the stock recovery. The stock recovery is only meant to be used by the manufacturer to perform certain tasks (like updating, resetting, etc...but no user functions like backup/restores.). Both Clockwork and AmonRA's recoveries add the ability to take a complete image of your phone (so that you can always restore any software changes no matter how severe), reformat and partition your sd card (to add/remote a cache partition or a partition for Apps2SD), reset battery stats, and a host of other things I'm sure I haven't even touched on. Also, I believe they add the functionality to flash unsigned updates done by the community (not just restricting us to HTC's updates).
ROMS
--- What are these really doing if they are not messing with the /system folder. Are they just a bundle of different programs? Change the rom and you change the programs that are installed? What is the difference between a ROM and a DEV-ROM
Click to expand...
Click to collapse
Most of the ROMs you see now require NAND unlocks so that they can mess with the apps in /system. Some ROMs are just a certain package of apps or a set of themes. Others add functionality or make certain things easier to implement. Yet others are tweaked to attempt to change other aspects of the OS to improve performance of battery life through tweaks to when the system performs certain tasks.
Ultimately, each ROM is different and the changelogs *should* tell you what all they've done over the stock (or if they're based on another ROM, you can open that page to see the tweaks they are tweaking, etc). (Sometimes it can get pretty big on the tweaks on another rom's tweaks on another rom's tweaks...check the CDMA hero forums for some combination roms ).
ROMs vs Dev-ROMs - Dev-ROM's are usually a work in progress...they are testing new features and often will be on the bleeding edge (emphasis on bleeding). These will sometimes (even likely) break something while they try and improve or add new functionality in another aspect. You should only flash these if you want to help test and if you have an idea of what's going on so you can help troubleshoot.
Normal ROMs are usually more stable (usually) and will have milder modifications (though once a DEV-ROM has successfully gotten a new feature stable, most other ROMs will incorporate those changes...it's kindof a lifecycle).
RADIO
--- What is the deal with the new radio. Is it updated drivers for the baseband? This kind of gets into my kernel question about how the drivers are handled within the kernel. How can this work across multiple kernels, but we cant get the camera working?
Click to expand...
Click to collapse
Radio images are a bit more like firmware updates to the radio chip. These often help to improve reception or connectivity or fix instabilities or other problems. Not everyone experiences the issues that it attempts to fix and doing a flash on your own does have certain risks. The odds of a problem arising for you isn't high, but the effect is potentially severe if a problem does occur. The main thing to remember is to ensure you have enough battery for the changes to occur (firmware updates in general recommend this on all devices, be it laptop BIOS updates or phone radio updates...I recommend using the wall charger and not unplugging it until 5 minutes after the update has completed), and ensure that you don't try and do anything else on the phone while the update is occuring.
I know this is a lot, but if anyone could fill in some of the holes for me I would appreciate it.
Thanks
Click to expand...
Click to collapse
Hopefully the info given by me and my fellow ex-newbies will help with your desire to learn! There's a lot of cool stuff about our phones and I love that we can get a bit into the guts of the thing (unlike some phones*)
*I can't help but throw a little jab at Apple every so often.
This is great information and helps me to push myself even further towards ROM development.
I enjoy my Evo and this website is amazing
Great thread and information, I was looking for something similar. I'm totally new to Android and want to start the whole rooting process.
I don't mean to hijack the thread or anything, but some terms are thrown around and I don't have a 100% understanding of what they really mean....could someone please define them?
Recovery?
Flashing?
Thanks codemonk and webs, that was awesome.
Onepanda, i'll give your question a shot.
Flashing is really just putting files on you phone. Generally it refers to replacing the andriod system files. You can flash a kernel, a ROM, drivers, or just an update to one of those.
Recovery is a mode you can put your phone into from boot. This is where you flash the files from. You cant just replace system files while they are running, so you boot into recovery mode and flash them from there.
Recovery mode also has a few other features allowing you to reset settings (cache) and make backups.
hi guys,i'm wondering,what is the best and stable Android build that u haved tested? i see alot of builds here but i dont know witch one to choose
All builds are pretty good, it really depends on your personal taste, and what you're looking for.
I'm running Not So Super Froyo Latest RLS, with 2.6.25 kernel by l1q1d, so far pretty good build.
Had several crashes the last 2 weeks, but all kernel related to phone sleeping, but minor data corruption (fixed by reinstalling the corrupted app, unless it's a system file then I just reinstall the build)
Krazy-Killa said:
All builds are pretty good, it really depends on your personal taste, and what you're looking for.
I'm running Not So Super Froyo Latest RLS, with 2.6.25 kernel by l1q1d, so far pretty good build.
Had several crashes the last 2 weeks, but all kernel related to phone sleeping, but minor data corruption (fixed by reinstalling the corrupted app, unless it's a system file then I just reinstall the build)
Click to expand...
Click to collapse
exactly the same on polaris
phone
crashes on phone sleeping?
dany547 said:
crashes on phone sleeping?
Click to expand...
Click to collapse
Probably due to me tinkering so much.. Some people have the issue others don't. lol
Krazy-Killa said:
All builds are pretty good, it really depends on your personal taste, and what you're looking for.
I'm running Not So Super Froyo Latest RLS, with 2.6.25 kernel by l1q1d, so far pretty good build.
Had several crashes the last 2 weeks, but all kernel related to phone sleeping, but minor data corruption (fixed by reinstalling the corrupted app, unless it's a system file then I just reinstall the build)
Click to expand...
Click to collapse
your systems apps should not get corrupted, potentially minor data loss though because of the odexing process the classes.dex files are not kept in the dalvik cache. so the only thing that could have a problem is the launcher.
this is what the reboot protection was moving the dalvik to the sd so that way it wasnt kept on the system, since the sd does unmount when shutting down
for me the best is Fat Free Froyo with lastest 2.6.25 kernel from git.
The stability really comes from the .25 kernel as it is much more older and mature. My barebones build might work with .25? I haven't tested it but I recall someone saying it worked.
I don't think it will work since scooters cyanogen has a different libskia than other builds
aceoyame said:
The stability really comes from the .25 kernel as it is much more older and mature. My barebones build might work with .25? I haven't tested it but I recall someone saying it worked.
Click to expand...
Click to collapse
Sent from my HTC Hero using XDA App
Oh I know, was just saying that someone said they got it to work so just saying it might work lol
thoughtlesskyle said:
your systems apps should not get corrupted, potentially minor data loss though because of the odexing process the classes.dex files are not kept in the dalvik cache. so the only thing that could have a problem is the launcher.
this is what the reboot protection was moving the dalvik to the sd so that way it wasnt kept on the system, since the sd does unmount when shutting down
Click to expand...
Click to collapse
Apparently that doesn't work for me, especially with the 2.6.32 kernel. No matter how I reboot (button, battery, actual menu option), almost all apps get corrupted, and the Framework gets completely shot the **** (no lock screens, unable to silence phone or turn on Airplane mode).
The Dalvik move to SD apparently doesn't work for me either, unless it's only on a certain build? I'm using Not So Super Froyo RLS18.
I must reflash rom every one -two day, its crash, not workink proceses, system its very slow, after restart phone not remember settings and sometimes delete any data. i test very much roms,
Best Android build is Warbyte Donut for me, very stable and all works fine and quickly, but it is Donut and I Need Froyo..
i see
i got instaled a Donut build,but the white screen and the file system coruption made me to switch back to Wm i'll w8 untill a new build will appeare
fat free
I've got the fat free froyo on kaiser with .32 kernel downloaded with atools.
It works fine with an sd system install (class 6). Fast and stable.
You can olso try system on nand and data on sd! I could not do this because my nand is corrupt....but the result was really good.
The problem you were having was caused by your kernel not the build
dany547 said:
i got instaled a Donut build,but the white screen and the file system coruption made me to switch back to Wm i'll w8 untill a new build will appeare
Click to expand...
Click to collapse
Sent from my HTC Hero using XDA App
no
no,the karnel was for my device
dany547 said:
no,the karnel was for my device
Click to expand...
Click to collapse
Yes it was a kernel fault. Listen to people who are more knowledgeable than yourself. Next time install kernel from '25 branch which is stable and doesn,t suffer from white screens and data corruption. The kernel you used was experimental and it still doesnt work as well as we would want it to.
dany547 said:
no,the karnel was for my device
Click to expand...
Click to collapse
people like you the, i know everything because i manage to get android booting on my windows mobile phone even though i looked at maybe 1 tutorial and read it half way. the flash first read 2nd type. are pretty much the entire reason why there hasnt been a new Not so super or fat free froyo.
-Arturo- said:
Yes it was a kernel fault. Listen to people who are more knowledgeable than yourself. Next time install kernel from '25 branch which is stable and doesn,t suffer from white screens and data corruption. The kernel you used was experimental and it still doesnt work as well as we would want it to.
Click to expand...
Click to collapse
is u want to give me that Kernel i'll apreciate! my karnel was from l1q1d's page (2.6.32)
i release this version with this changelog:
- ext2/ext4 support
- adb working on windows (remember to install drivers on windows)
- ipv6 support
- bluetooth modules
- nand stable
*update with ramswap*
you need the android update (new version of modules)
the ext4 support is compiled but i didn't edit the initrd.
Tomorrow i'll release a new version of atools (1.2.0) with ext4 enabler and new initrd.
I'll commit all changes to git after positive comments.
Backup all and reinstall after flash.
just great, I'll test as soon as possible!
l1q1d said:
i release this version with this changelog:
- ext2/ext4 support
- adb working on windows (remember to install drivers on windows)
- ipv6 support
- bluetooth modules
- nand stable
Click to expand...
Click to collapse
Because of this, Kaiser will be my primary phone tomorrow.
Magic is boring anyway, everything is working
Contacts lost after reboot using softreset button.
Goggles working fine!
Sent from my CyanogenMod Kaiser/Kaiser using XDA App
@tiagoclc: did you reinstall all before install new kernel?
You mean after...
Yes. I put new modules directly in androidinstal.tar.
After install system, clearing data, I restored data.
Setting google account again. After sync, ill try to reboot again.
Sent from my CyanogenMod Kaiser/Kaiser using XDA App
yes after...
strange, i reset so many times...
I'm getting ready to flash this on my Kaiser as well, and I'll report if I get any corruption after 1-2 days of use, as that seems to be the timeframe for me whenever the phone starts corrupting badly, especially framework and lost apps.
Will be installing the new Cynogen 7 Alpha by Scoot as well, as I'm really interested in getting Gingerbread on my Kaiser, as it worked really well (besides GPS not working, and facebook.
EDIT: At the moment, so far so good, I'm not transfering my SIM over just yet until I can confirm for myself if the phone will be stable enough... I had a serious issue with Android and the Kernels going on the frits when I needed it the most (was in a car accident, and couldn't make any calls because the phone decided to go into a reboot loop, and didn't have time or the patience to deal with the issue as I had more pressing issues to deal with)
Which brings me to one question, what exactly was done to resolve NAND corruption, and to post "nand stable"? As far as I was seeing, there was speculation that the YAFFS2 driver and the NAND driver were fighting over ECC, and that also the NAND driver hasn't been fully ironed out bug wise.
I do see the checkpointing is now working correctly, as I see the YAFFS2 driver constantly creating checkpoints every couple of minutes, then sitting idle, and doing it again (possibly whenever writing to the NAND occurs).
Also, was wondering if there were any improvements made to Power Management? I know the PM7500 chip is now enabled and working, and power management is now fully working for components like the radio and possibly the WiFi module as well, but still no control over the CPU dynamic clocking, or scaling.
l1q1d said:
i release this version with this changelog:
- ext2/ext4 support
- adb working on windows (remember to install drivers on windows)
- ipv6 support
- bluetooth modules
- nand stable
you need the android update (new version of modules)
the ext4 support is compiled but i didn't edit the initrd.
Tomorrow i'll release a new version of atools (1.2.0) with ext4 enabler and new initrd.
I'll commit all changes to git after positive comments.
Backup all and reinstall after flash.
Click to expand...
Click to collapse
so far pretty smooth on my vogue i have restarted a few times without issues, using a modified cm7 build. what was causing the nand issue?
This is a beta tester kernel, for explanation read the kernel thread and wait for source release.
After a fresh install, without data restore, rebooted 4 times (button) and 1 pulling out sim card and data partition is aparently ok.
Probably my data partition was corrupt when I made the backup.
Ill post more results later.
Sent from my CyanogenMod Kaiser/Kaiser using XDA App
Wow, that IPv6 module is huge!
Bad: I've had five or six freezes since installing this.
Good: no corruption, with data on NAND.
EDIT: It crashes precisely at:
insmod /system/lib/modules/ramzswap.ko disksize_kb=26010
I've turned off compcache until we figure this out.
ramzswap.ko is not compiled for this kernel so i will post it soon.
EDIT:
add ramswap module
Also had about 3 crashes since flashing this kernel, but no data or framework corruption as of yet.
Sent from my AT&T Tilt using XDA App
Check if crash are due to the rom or ril.
l1q1d said:
Check if crash are due to the rom or ril.
Click to expand...
Click to collapse
this is just a guess but i think his might be RIL based, my phone isnt connected to a network actively and i haven't had any crashes or data corruption and i have loaded my contacts and a messaging backup on it. i know your looking for real world beta testers, so i will stop posting on this thread if you so desire
it could be useful a log of crash
l1q1d said:
- nand stable
*update with ramswap*
Click to expand...
Click to collapse
This mean android dont gonna die after 3 days of use when you install on nand? (its called yaffs, or i am wrong) regards!
NAND is the architecture of our phones internal flash memory.
Yaffs is the filesystem applied to this flash memory.
l1qu1d, wich radio version is recommended to use with this kernel?
Sent from my CyanogenMod Kaiser/Kaiser using XDA App
I am testing new Kernel with CM7 too... seems to be quite stable so far...
More results after more days of full use...
CyanogenMod 11 KitKat for Optimus S/V
This is a basic CyanogenMod 11 rom for the Optimus S/V. It has NOT been tested extensively and I take NO responsibility for any bricked phones, data loss or damages that occur as a result of flashing any version of this rom. It requires ClockWorkMod 6.0.4.5 or later, or TWRP 2.6.3 or later, in order to flash.
What works:
Phone calling (ZVH and ZVJ radios require a patch)
Wifi
Mobile data (thanks to thekraven)
USB tethering
Camera
USB mass storage, MTP
What's broken:
Bluetooth
Wifi tethering
SELinux
You tell me
CWM 6.0.4.6 can be found in the rom directory. Flash Skinny_4.4_Gapps.zip after flashing the rom to get Play Store and Google Sync. Other Gapps will probably be too big to fit on /system.
https://www.mediafire.com/folder/nfgfef6qpril7/CM11
Contributors:
skinbark
bigsupersquid
thekraven
Special thanks to the CyanogenMod and androidarmv6 teams, also gu5t3r for GOptimize.
CM11 KitKat os2sd Version:
cm-11-20140116-thunderc-skinbark-sd.zip is a version of CM11 which is designed to run off your sd card.
To use this version:
1) create and format 3 ext4 partitions following the fat32 partition on your sd card (use gparted not a windows partitioning tool)
/data - at least 256 mb (512 mb or more recommended)
/system - at least 256 mb
/cache - at least 256 mb
2) format /boot in cwm
3) install cm-11-20140104-thunderc-sd.zip
4) install Skinny_4.4_Gapps-sd.zip and reboot
Known Issues (in addition to those in post #1):
formatting/backup/restore issues
possible reduced performance (older/slower sd cards)
reduced battery life (?)
Add wipe zips to a folder on your sd card and flash them from recovery to clear external /data, /system, /cache, or all three.
CWM_6.0.4.6-thunderc-sd.zip is a special version of CWM for os2sd that should only be used if you understand how it works.This version of CWM is not necessary to flash the os2sd rom. See this post for more info about recovery issues with this rom.
A Class 10 microSD card is recommended for best performance.
Power off or reboot to recovery before removing sd card.
os2sd mod courtesy of bigsupersquid
https://www.mediafire.com/folder/dj2d4vpp0hzvb/CM11sd
Warning: This is a highly experimental setup and a work-in-progress. You should have adb installed and know how to use it, along with the flash_image command, before attempting this install. If you have trouble installing this and are unsure how to resolve the problem ask for help on this thread. I take no responsibility for bricked devices, data loss or any other damages resulting from the use of this software. USE AT YOUR RISK.
New build with rild fix for ZVD/ZV5. You'll want to upgrade to this for stability and battery life even if you're not activated.
cm-11-20131225-thunderc-skinbark.zip
Link in OP.
Merry Christmas guys!
Sweet! Will flash once o find my ov...
Virgin fix uploaded.
Virgin.fix.CM11.0.zip
Link in OP.
I'll test. I still use this phone a bit. I don't use gapps anymore so I wouldn't be ale to ile any bugs against them. Is thereanything in particular you want tested?
captaincrook said:
I'll test. I still use this phone a bit. I don't use gapps anymore so I wouldn't be ale to ile any bugs against them. Is thereanything in particular you want tested?
Click to expand...
Click to collapse
Well the biggie right now is getting data going which is sort of difficult for me since my phone's not activated (next week I hope). I'm assuming you're not activated? I guess just general stability and performance, battery life, see what you can run on on it, put it through the wringer. All info is welcome since I really haven't had much feedback yet. It seems to be pretty stable. Let me know if you have any problems, thanks.
really works well...nice job. No chance to test 3g data yet, but everything else works very well...I had to install a keyboard manually, and the battery stats are wrong (fully charged, and stayed fully charged all day) but it is def a daily driver for me.
I uploaded a new 'OS2SD' rom with special recovery, gapps and virgin fix:
cm-11-20140101-thunderc-sd.zip
CWM_6.0.4.6-thunderc-sd.zip
Skinny_4.4_Gapps-sd.zip
Virgin-fix-CM11-sd.zip
Link in post #2. Happy New Year!
Got the order of the partitions wrong in post #2, sorry. Fixed now. 3G fix coming soon!
I uploaded new standard and os2sd builds with data fix.
cm-11-20140104-thunderc-skinbark.zip
Link in post #1
cm-11-20140104-thunderc-sd.zip
Link in post #2
After a crash fest with the build at the time of my last post, this newish one is alright so far. Things get choppy fast and the input is a real pain. That is about as good as I have it. Alternate market works, wifi is good, and its chugging along.
captaincrook said:
After a crash fest with the build at the time of my last post, this newish one is alright so far. Things get choppy fast and the input is a real pain. That is about as good as I have it. Alternate market works, wifi is good, and its chugging along.
Click to expand...
Click to collapse
long press home and press the three-bar onscreen button to close running apps.
also fast reboot off market is very handy to manually clear ram. heard about that one from andyopie150, like it.
Ya the main issue is just generally its a bit slow. I'm not trying to be one of those people who dog the ROM cause devs sibt human but this is just what I have experienced. I know our SOC came out when Moses was around so I'm not expecting miracles. I'm not sure if you guys have more planned or not but its really neat how efficient the phone is on 4.4 and if it was to get faster it'd be amazing.
The keyboard, can you guys adjust the size values? Its microscopic! Hacker's Keyboard fits the bill in the meantime.
captaincrook said:
Ya the main issue is just generally its a bit slow. I'm not trying to be one of those people who dog the ROM cause devs sibt human but this is just what I have experienced. I know our SOC came out when Moses was around so I'm not expecting miracles. I'm not sure if you guys have more planned or not but its really neat how efficient the phone is on 4.4 and if it was to get faster it'd be amazing.
The keyboard, can you guys adjust the size values? Its microscopic! Hacker's Keyboard fits the bill in the meantime.
Click to expand...
Click to collapse
For now I can just suggest the usual speed-up stuff - turn off animations, ksm, cpu/governor etc. There may be some build.prop tweaks you could use, and I'm expectiing zram support to be enabled soon. Crossbreeder might be something else to try. If we could get ART going it might help some but I don't know if that's likely. I probably won't try to tweak the stock keyboard, there's plenty of alternatives available.
tried flashing this on my optimus V and i got a error when i was flashing it, error 7 i think it was, i used the CWM you wanted us to use but it made it so that i couldnt boot into recovery.
Trozzul said:
tried flashing this on my optimus V and i got a error when i was flashing it, error 7 i think it was, i used the CWM you wanted us to use but it made it so that i couldnt boot into recovery.
Click to expand...
Click to collapse
regular rom or os2sd?
skinbark said:
regular rom or os2sd?
Click to expand...
Click to collapse
regular i tried a different CWM 6+ and that one gave me the error*
Trozzul said:
regular i tried a different CWM 6+ and that one gave me the error*
Click to expand...
Click to collapse
Here's another recovery you can try.
https://www.mediafire.com/?s8c94941y8kubdd
captaincrook said:
Ya the main issue is just generally its a bit slow. I'm not trying to be one of those people who dog the ROM cause devs sibt human but this is just what I have experienced. I know our SOC came out when Moses was around so I'm not expecting miracles. I'm not sure if you guys have more planned or not but its really neat how efficient the phone is on 4.4 and if it was to get faster it'd be amazing.
The keyboard, can you guys adjust the size values? Its microscopic! Hacker's Keyboard fits the bill in the meantime.
Click to expand...
Click to collapse
Any information is a good thing, positive or negative. Harmonia with the Xionia kernel fairly flies speed-wise, but everything since that seems to choke my phone somewhat. And Mirage is the best Gingerbread available... but I enjoy the extra features more than the speed, which is what keeps me trying for the bleeding edge.
(example: the double-tap-hold-and-slide to zoom is built in all over 4.4, in 4.2 I only saw that in Maps.)
ART may or may not happen. I have to learn more thumb assembly to fix it. My decent class for school this session (the easy one since I did 8088 back in 1991) is x86 assembly. Doesn't apply, but maybe I can get more parallell info from it. There's lots of good info out on the net with minimal searching as well, but not much if any on downconversion of thumb2 to thumb1 code. I found enough to fix a few files but there's still more to go. I'd be impressed with myself if I got that to run.
CrossBreeder seems to work.
How do I fix unable to mount /usbstorage?
Happens whenever I wipe something in recovery or install a ROM...
Also is there a way of fixing "UnregisterIRListener is called()", which is spammed ALL THE TIME in CatLog? It's not ROM related, as a developer told me it also happens in unedited stock?
My battery life sucks after flashing multiple ROMs and kernels, in relative to the STOCK unrooted ROM with same governors and schedulers or better like ondemandx!
EDIT (Jan 31, 2014):
I am brainstorming possible causes of unregisterIRListener / unable to mount usb storage problem / bad battery:
- Unable to mount /usbstorage messed up the ROMs I install or broke root, as I keep getting errors whenever I wipe something -> therefore, maybe I am unable to clean-flash and this is causing all of my problems
- I messed up on rooting therefore some part of root is broken
- SE Linux or internal storage not being write-able is a cause
- Samsung messed up on infrared-red coding including it with Knox and when it broke, causes phone to go ballistics in logcat
- When I went ballistics in late December and early January flashing a bunch of kernels without clean-flashing, I think I broke something
Possible solutions?
- Fix root, SELinux, usbstorage error, and/or internal storage somehow
- Unroot, go back to stock and then re-root using a safer method hoping it fixes it, along with flashing an "ultimate wipe" script for the Note 3
- Find where the code is stemming from and take away the unregisterIRListener call
Mystery? said:
How do I fix unable to mount /usbstorage?
Happens whenever I wipe something in recovery or install a ROM...
Also is there a way of fixing "UnregisterIRListener is called()", which is spammed ALL THE TIME in CatLog? It's not ROM related, as a developer told me it also happens in unedited stock?
Click to expand...
Click to collapse
Fwiw - I'm not a developer
But it's true, they were in a logcat from an odexed (but rooted, otherwise unedited) stock build.
dwitherell said:
Fwiw - I'm not a developer
But it's true, they were in a logcat from an odexed (but rooted, otherwise unedited) stock build.
Click to expand...
Click to collapse
wait aren't those who make ROMs developers?
Anyways is it referring to the infrared thing on the phone?
Mystery? said:
wait aren't those who make ROMs developers?
Anyways is it referring to the infrared thing on the phone?
Click to expand...
Click to collapse
lol yeah that's one definition, I just don't feel like I make anything really, more mess w/ other peoples stuff
And yeah that's what I was thinking when I first saw it.
dwitherell said:
lol yeah that's one definition, I just don't feel like I make anything really, more mess w/ other peoples stuff
And yeah that's what I was thinking when I first saw it.
Click to expand...
Click to collapse
I uninstalled WatchOn and same thing persists... hmm. Could it be that when root broke Knox, it also affected one of the infrared functions?
Also does the same thing happen to you with the function?
Mystery? said:
I uninstalled WatchOn and same thing persists... hmm. Could it be that when root broke Knox, it also affected one of the infrared functions?
Also does the same thing happen to you with the function?
Click to expand...
Click to collapse
Tbh this stuff is a bit above my paygrade - I didn't try to mess w/ it very long though as I wrote it off as "normal" and that was it. I have an app to do the remote thing (not WatchON) and those are still in the logcat, though I never tried to look for differences when using vs. not using if that's what you are asking.
dwitherell said:
Tbh this stuff is a bit above my paygrade - I didn't try to mess w/ it very long though as I wrote it off as "normal" and that was it. I have an app to do the remote thing (not WatchON) and those are still in the logcat, though I never tried to look for differences when using vs. not using if that's what you are asking.
Click to expand...
Click to collapse
hmmm I seriously think the error unregisterIRListener is a problem Samsung screwed up on... I was searching in other threads and someone else mentioned it and idk if its related to the problem but soon afterwards they started talking about SELinux or internal storage not being write-able. Could the error be related the unregisterIRListener? Idk why but my battery life sucks on multiple roms even after flashing different kernels in the past few weeks in relative to the STOCK unrooted ROM with same governors and schedulers or better like ondemandx
I am brainstorming possible causes of unregisterIRListener (I know @dwitherell, you may not know much about this, but this is for others):
- Unable to mount /usbstorage messed up the ROMs I install or broke root, as I keep getting errors whenever I wipe something -> therefore, maybe I am unable to clean-flash and this is causing all of my problems
- I messed up on rooting therefore some part of root is broken
- SE Linux or internal storage not being write-able is a cause
- Samsung messed up on infrared-red coding including it with Knox and when it broke, causes phone to go ballistics in logcat
- When I went ballistics in late December and early January flashing a bunch of kernels without clean-flashing, I think I broke something
Possible solutions?
- Fix root, SELinux, usbstorage error, and/or internal storage somehow
- Unroot, go back to stock and then re-root using a safer method hoping it fixes it, along with flashing an "ultimate wipe" script for the Note 3
- Find where the code is stemming from and take away the unregisterIRListener call
Mystery? said:
...
- Unable to mount /usbstorage messed up the ROMs I install or broke root, as I keep getting errors whenever I wipe something -> therefore, maybe I am unable to clean-flash and this is causing all of my problems
...
Click to expand...
Click to collapse
If this is a message you are seeing while flashing things in twrp - it is completely normal and of no concern. That's all I got