• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [ROM] Quattrimus JB (CM10, AOKP41)

XogdroidjbX said:
Just curious, my wife's spectrum is running broken out and she wants aokp 41 like mine has.. would I have to return her phone to stock and take the ICS OTA or .cab followed by using the bootloader tool, or can it be flashed straight from broken out?
Click to expand...


Yes to stock, ICS ota, bootloader.

When you're in ICS ota, get a lock on the GPS before flashing to AOKP
 
XogdroidjbX said:
Just curious, my wife's spectrum is running broken out and she wants aokp 41 like mine has.. would I have to return her phone to stock and take the ICS OTA or .cab followed by using the bootloader tool, or can it be flashed straight from broken out?
Click to expand...

Easiest way is to download the V6 stock no root zip and use the return to root method using CWM. You will also need to return to stock recovery. If you have CWM installed then the ota will fail.

Go here and this will get you straight http://androidforums.com/spectrum-a...re-v4-v6-verizon-stock-only-cwm-recovery.html
 
Well this random thing has really caused a stir. I did a lot of reading and didn't find anything conclusive yet.

One interesting finding is that qrngd on MSM devices (that's us) ensures that the random entropy never falls to zero. It does this by feeding entropy into /dev/random by using /dev/hw_random. It is a proprietary binary but it seems quite simple. I could write a replacement that ensures that the entropy is always full, but that would be rather complicated to do properly due to the kernel APIs.

I'm thinking about trying out a couple kernel patches. One idea is to have the random device fetch entropy from the hw_random device directly to ensure it stays full. This would have the side effect of not needing qrngd at all. Another idea is to just use hw_random and hardcode the entropy value to the max.

The problem, though, is that I don't really see any lag on my phone, so I wouldn't know if any particular solution worked or not. Can someone describe the lag that they are experiencing, and how to see it clearly?
 
XogdroidjbX said:
Thanks guys. Figured it didn't hurt any to ask first. :D Thanks for the reminder about the gps lock also.
Click to expand...
Really? Wouldn't the easiest thing be to .CAB directly to Stock V7, then pwnage, then flash? Assuming you have a PC you can CAB from... That'd be my recommendation.

PS: Don't forget to enable GPS and get a lock while you're on V7 stock before flashing either custom JB ROM.
 
tdm said:
The problem, though, is that I don't really see any lag on my phone, so I wouldn't know if any particular solution worked or not. Can someone describe the lag that they are experiencing, and how to see it clearly?
Click to expand...

Mine has been pretty smooth since CM10, but my husband's still on stock/rooted and it's really bad. I think choppy is really a better term than lag, or even stutter. Sometimes scrolling between home screens, opening the app drawer, keyboard " locks up", scrolling (especially in the app manager, play store, tapatalk, etc.), switching between pictures, almost like there's too much running in the background and it needs a split second to catch up.
Something odd though. Seeder doesn't seem to make any difference on his...?
 
  • Like
Reactions: tdm
In the few minutes I've been running beta 6 it seems to run smoother and more responsive compared to beta 4. It seemed like often times there'd be a slight delay for the keyboard to pop up while entering a text message etc(maybe it was related to swype?)all things considered it was a very very minor annoyance, but after some very unscientific testing lol, it seems like its resolved. I'm running out of compliments tdm lol.
 
  • Like
Reactions: tdm
I have some weird issues with aokp since beta 5. I've been running cm10 for a while but have attempted to go back to aokp41 several times but since beta 5 and also 6 which I just got done testing I have two issues which are super annoying. First issue is anytime I plug my phone into my bose computer speakers (which I use almost everyday while working in my shop) it puts my phone in silent mode. I can turn silent mode off but in a couple minutes it turns itself back on. I don't have this issue in cm10. Also in aokp41 the R is back in the status bar. My internet works normal but for some reason the R is back. Also this problem does not exist in cm10.

Does anyone have any ideas about this? Possible solutions?
 
I just came from aokp beta 4 to 6, I'm getting full 4g but the network is reading "roaming indicator on" on the pull down and lock screen.
 
I'm guessing it's because I dirty flashed Beta 6, but my light sensor is just saying -1. Anyone know what would be causing that and/or how I can kick it into coming back online?

*Edit* Never mind. It just needed to be brought into the light. Lol Started reporting after it actually had light to see.
 
tdm said:
I'll check the eri. Did this happen in beta4?
Click to expand...

actually everything on beta 4 worked for me perfectly. it came up Verizon. now I'm at work and its coming up Sprint. we have a network extender here I guess my GPS ids saying I'm in Detroit. (I'm in Cleveland)
 
Noticed two things this morning:

1. CM's android_hardware_qcom_display has a cm-10.1-caf branch.
2. CM has an android_hardware_qcom_display-caf project.

So between these, it is obvious that progress is being made on getting CM10.1 working on "older" MSM devices like ours (older than the MSM 89xx, which powers the Nexus 4, Optimus G, etc.)

I think I'll try compiling CM10.1 again today or tomorrow....
 
tdm said:
Noticed two things this morning:

1. CM's android_hardware_qcom_display has a cm-10.1-caf branch.
2. CM has an android_hardware_qcom_display-caf project.

So between these, it is obvious that progress is being made on getting CM10.1 working on "older" MSM devices like ours (older than the MSM 89xx, which powers the Nexus 4, Optimus G, etc.)

I think I'll try compiling CM10.1 again today or tomorrow....
Click to expand...


You are the man. Thanks for all your hard work.
 
I just upgraded to Beta 6 this morning and my phone did a soft reset (CM logo) while navigating. WIll there still be a kmsg? If so how do I get to it to upload it for TDM?
 
mediumrarestea said:
Can anyone confirm is SMS is working? Also, any recommended launchers, themes for this? Thanks!
Click to expand...

SMS is fine. I've used the Lucid Cyanogenmod theme for over a year, I love that. That themes the whole ROM. Personally I also use Apex Launcher. Some other great launchers are ADW, Nova, and Holo. Though CM's built-in launcher, Trebuchet, is kick-ass too. There are tons of free and paid themes on the Play store for ADW, Nova, Apex, and others. The dev called david 1171 on the play store made several that I used to almost exclusively use on ADW.
Here's a great app for browsing CM themes: https://play.google.com/store/apps/details?id=com.jrummy.list.tmobile.themes&hl=en
 
I made some kernel changes to test effects of the performance of /dev/random and entropy availability. Anyone who sees tangible improvements with Seeder, please try this and report your findings.

Changes:
* Use hardware rng istead of software rng for all /dev/random and /dev/urandom operations.
* Short circuit all code paths that add entropy (both kernel and userspace), as they are no longer needed.
* Hard code available entropy to the maximum.
* Apply the ELF patch that uses get_random_int().

To test:

1. Remove all traces of Seeder. I suggest a dirty flash.
2. Test performance.
3. Install the new boot image.
4. Verify the kernel version says -cm-hwrng and entropy_avail is 4096.
4. Test performance.

To install the new boot image, download the appropriate image:
CM10b6
AOKP41b6

Push this to the phone as eg. /data/local/tmp/boot.img, then run this as root:

dd if=/data/local/tmp/boot.img of=/dev/block/mmcblk0p8 bs=4096
Make sure you type that correctly! I suggest copy/paste.

Now reboot the phone and verify the kernel version.
 
You must log in or register to reply here.
Back
Top Bottom