Related
I wonder if everybody runs RevolutionHD 4.1.x with Bricked kernel 1.5 having this same problem:
- Launch Camera App
- Take a picture (optional)
- Hit Gallery icon on the top left
50% of the times, my phone will freeze. I have to reinstall the battery.
I can not replicate the same problem with faux123 kernel came with the ROM.
Thank.
I love Bricked Kernel because it gives the best battery life.
xixoxix said:
I wonder if everybody runs RevolutionHD 4.1.x with Bricked kernel 1.5 having this same problem:
- Launch Camera App
- Take a picture (optional)
- Hit Gallery icon on the top left
50% of the times, my phone will freeze. I have to reinstall the battery.
I can not replicate the same problem with faux123 kernel came with the ROM.
Thank.
I love Bricked Kernel because it gives the best battery life.
Click to expand...
Click to collapse
this is what i did and i had no problem at all
After installing the ROM keep in the recovery, be sure to do the following:
- install Bricked kernel (Bricked-v1.5r1-beta1-528-ondmnd-1536-192.show-p1984.zip) version from bricked thread by finding the ALL DOWNLOADS
DO NOT TRY (Bricked-v1.5r1-beta2-535-ondmnd-1536-192.show-p1984.zip) yet Because i still got hang problems when using Beta 2 535
- install the camfix 1.4 from bricked thread
- after booting to the main. don't begin with the camera, go to setting> applications> ALL tab> scroll down and tap on Camera> Clear Data
do this only if you flashed ROM with 2.3.5 sense 3.5
i hope this problem will solve all your matters, give intensive use of the camera so to make sure it's working fine.
Thanks, I'll try and report later.
just forgot to note that I'm using HTC Sensation XE with Beats Audio.
i don't have any idea here if will work on any normal sensation with the newer beta 2.
from experiencing sensation XE, i still recommend the beta 1, any suggestions from the normal sensation or sensation 4G users would be helpful and very welcomed.
I did what you suggested, so far no problem hope that would fix it.
Will test and report after few days.
Great to hear that, keep going.
about the incoming call black screen it happens once or twice when the phone is on sleep mode.
then the phone will go all normal.
so to avoid the 1st times, use any other phone to call your phone multiple times so to confirm that the screen will wakes up at 2nd or 3rd time when the incoming call occurs.
There are a bunch of AOSP rom's for our phone, most of them share the same issues since it's the same code, with slight differences based on which commits they've added. I'm hoping we can list the common issues in one thread as a reference.
1. Data handoffs between 3g/4g - I believe this is now fixed in most of them after the RIL patches, right?
2. Call volume - This CM10 commit (http://review.cyanogenmod.com/#/c/24564/) should fix this. Not in most rom's yet
3. Bluetooth pairing, call connect, streaming - does this work fully in any AOSP rom?
4. Sleep of death
5. Wakelock caused after playing media (DirectTrack)
6. Camera issues, like save to sd. The JB mod camera hasn't been updated yet.
7. Misc battery life issues - are most of these due to #5?
8. Activation issues after a flash
9. Low video recording volume
10. Notification light problems
11. 160 char sms limit, MMS doesn't work
12. Problems waking up with home button
13. Screen redraw issues (these can be fixed by turning off hardware overlays, but that increases cpu consumption)
I think it would be very helpful if we could track which rom's had which fixes merged, since otherwise it's hard to tell without asking in each thread, doing a lot of searches, and trying out.
Slimbean:
-Wake lock issue still seams to be an issue, battery life is bad
-notification light not working when call/text/email etc come in. Will be patched on next release
-data seams stable enough (ril patch is active on most recent build)
-horrible battery life
-call volume will be patched on next release
-home button to wake up phone is hit or miss
-odd screen glitches every now and then (fully live withable)
-mms sending takes forever, needed several reboots to even get it to work
-if usb fast charge is available in your kernel, it has a toggle for it in the notification tray (awesome)
-did I mention the battery life is bad?
-soft key light options do not work
I'll report more as I find them. I like these threads, good call.
Sent from my VZW GS3 running Synergy/Trinity/Dark Horse Rises
Great idea for a thread!
Add low video recording in all AOSP Roms. As far as I know this has not been fixed yet.
Sticky?
Sent from my SCH-I535 using xda app-developers app
- continuous WiFi connectivity issues (none of the AOSP roms worked reliable for me)
annoyingduck said:
Slimbean:
-Wake lock issue still seams to be an issue, battery life is bad
-notification light not working when call/text/email etc come in. Will be patched on next release
-data seams stable enough (ril patch is active on most recent build)
-horrible battery life
-call volume will be patched on next release
-home button to wake up phone is hit or miss
-odd screen glitches every now and then (fully live withable)
-mms sending takes forever, needed several reboots to even get it to work
-if usb fast charge is available in your kernel, it has a toggle for it in the notification tray (awesome)
-did I mention the battery life is bad?
-soft key light options do not work
I'll report more as I find them. I like these threads, good call.
Sent from my VZW GS3 running Synergy/Trinity/Dark Horse Rises
Click to expand...
Click to collapse
I am using slimbean 2.5 and I am getting anywhere from 16 to 24 hours of battery life on a single charge (3-4 hours of screen) which is about normal for any AOSP/AOKP based rom.
I actually made a similar list, but deals with comparing TW quirks to AOSP quirks:
Touchwiz VS. AOSP
Touchwiz:
- No Bluetooth and Aux input simultaneously
- Wallpaper Cropping forced to non-scrolling
- No way to disable auto volume reduction upon headset plug-in
- God awful front end interface design (this is more of an opinion)
- Google Music will randomly stop working, requires screen to be turned on for it to start playing the next track
AOSP:
- Volume Quirks (upon reboot, media volume will play quiet regardless of where the slider is, if maxxed you must turn it down and then up again similar to the call volume issue)
- Call Volume at Max every call (wasn't this fixed recently?)
- Wrongly uses noise reduction mic for recording (thus quieter)
- Inferior Camera (features mainly)
- Worse battery life
- Sometimes drops data
- Not as buttery as ICS for some reason (recents excluded)
- Will frequently kill background apps, making 2GB of ram somewhat pointless
- Bluetooth streaming issues (This doesn't personally affect me but I thought I'd throw it in anyway)
Basically, the one with the shorter list wins. So, I'm on TW for now but I yearn for the AOSP list of quirks to shrink.
Div033 said:
- Wrongly uses noise reduction mic for recording (thus quieter)
Click to expand...
Click to collapse
I've been told this has been fixed, but I still experience it. Is there a workaround for this currently?
I believe that there is a big tracker which is linked to on the irc chat. I would link to it but I'm not at my pc.perhaps someone could do so?
#verizons3 on freenode
Sent from my Galaxy Nexus using Tapatalk 2
bobloblaw1 said:
I believe that there is a big tracker which is linked to on the irc chat. I would link to it but I'm not at my pc.perhaps someone could do so?
#verizons3 on freenode
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
This 1? http://tinyw.in/25QW
Number 6 is not really a problem. It's all based on personal preference.
Number 1 was fixed. Sleep of death could be kernel and/or clock speed settings. Mms works fine. There is a fix somewhere for direct track. Battery issues? Umm mines been perfect. That could be contributed to people not knowing what's causing wake locks and not fixing it. Not sure how anybody is getting screen redraws I haven't disabled hardware overlay and mine is fine, using apex if that makes a difference.
Most if not all of those issues are non existent in liquid smooth.
Hope this is the right spot to post this question. I tried flashing 2 separate roms today (Slim Rom and Liquid Smooth) which I believe are both AOSP, but I could be wrong. On both occasions, it starts to boot and gets to the google account login screen and the screen on the phone just keeps flickering and goes black.
I am unlocked, obviously rooted, with CWM 6.0.1.1 and have flashed JB TW rom in the past with no problems but went back to TW ICS, which I am currently running now.
Anyone know or direct me to the right thread as to why the screen flickering happens after flashing these AOSP roms? I haven't tried CM10 yet because these other roms actually sound more stable than CM10 right now.
Any suggestions? Thanks in advance.
bales3795 said:
Hope this is the right spot to post this question. I tried flashing 2 separate roms today (Slim Rom and Liquid Smooth) which I believe are both AOSP, but I could be wrong. On both occasions, it starts to boot and gets to the google account login screen and the screen on the phone just keeps flickering and goes black.
I am unlocked, obviously rooted, with CWM 6.0.1.1 and have flashed JB TW rom in the past with no problems but went back to TW ICS, which I am currently running now.
Anyone know or direct me to the right thread as to why the screen flickering happens after flashing these AOSP roms? I haven't tried CM10 yet because these other roms actually sound more stable than CM10 right now.
Any suggestions? Thanks in advance.
Click to expand...
Click to collapse
Disable hardware overlay in developer options
Neverendingxsin said:
Disable hardware overlay in developer options
Click to expand...
Click to collapse
That might work, but I cannot even get into the OS to disable anything. It is completely unusable when I flash any of these roms.
Would there be something out there that I could flash in CWM to disable this in the rom pre-boot?
bales3795 said:
That might work, but I cannot even get into the OS to disable anything. It is completely unusable when I flash any of these roms.
Would there be something out there that I could flash in CWM to disable this in the rom pre-boot?
Click to expand...
Click to collapse
Nothing that I know of sorry.
One of the main reasons I don't use any AOSP roms is because of the bluetooth sync issue. In two of my cars, it will sync for the first time, but any other time I get in the car it won't pair up. I have to manually connect it every single time.
wifi errors, i get out of range and or wps failed on any aosp rom.
I find that signal is just not as strong as compared to Touchwiz roms.
Sent from my SCH-I535 using xda app-developers app
ROM: CM10 M2
Using Android Pro Widgets (the APW People widget in particular), it lags (the widget, not the ROM). Anyone run into this issue? Not a big problem, just curious.
Any word on when the call volume is going to be merged into the CM10 build for d2vzw
So,
I've gotten use to CM10. For months after EOS4 came around, it was ungodly slow. Even after switching off the media scanner, using a custom kernel, etc... the UI FR and general responsiveness was extremely lacking. It seems that it's been the Go-To ROM of choice for many, many months now, and the performance situation may have changed, but i'm hesitant to flash it, even if the only reason is that everything works great, other than a bit of bitrot here and there with CM10-- which brings me to my issue:
KAT kernel (version 69, of course (haha! seriously outdated)) seems to blow out my YouTube DPI, which can be fixed simply by setting the DPI to 150 or so n XPosed, and a quick dirty flash/ update kills the bitrot i run into every couple months...this time, however, i was clearing space, and organizing my .zips, when i decided it would be a brilliant idea to put all my AOSP ROMs together, all my mods & themes/addns together, and all my kernels together. The issue is, I cant for the life of me remember which kernel, and kernel version i was using! Besides the funky DPI behavior, KAT also introduces an extreme degree of video ghosting and stuttering.
I've tried a couple older kernels, but often, I'd find out the kernel was for ICS, and I'd be stuck at the boot screen.
Can someone please point me in the direction of 1-2 CM10 Kernels?
Bonus round: have the EOS issues been fixed definitively. Or do you still have to bang yuor head against the wall, look t your tablet upside down, and do some voodoo on it to get it workng?
I have never had issues like they with EOS4, so I cannot say if your issues are still around. Most users who have issues with EOS I believe did not do a factory reset, or restored system settings with Titanium Backup.
But, I would try the KatKernel 103 lidpatch CM10.1 version:
http://downloads.timduru.org/android/tf101/K.A.T/kernel/Tim_KatKernel_103_JB4.2_Lidpatch_CM10.1.zip
Edit - this is a cm10.1. If you are still on CM10, 69/70 are the most recent compatible ones.
CyanogenMod is a free, community built distribution of Android 4.2 (Jelly Bean) which greatly extends the capabilities of your phone.
! Remember: ROM in alpha stage. Not ask for ETA or for date of new build. Try to minimize spam on DEV thead
What working:
-Boot
-Display and touch screen (with multi touch)
-Wi-Fi
-Bluetooth
-HW
-RIL
-GPS & Network Location
-ADB
-Camera
-USB Mass Storage
-SD Card
-Sound
-Wi-fi tethering
-USB tethering
-Video playback.
What not working (for now, maybe fix soon):
REPLY ME ON THIS THEAD FOR CHANGE WORKIN\NOT LIST!
Thanks to this people (only they makes this build happen)
- dhiru1602
- rodero95
- sconosciuto
DOWNLOAD:
Download last build there:
Gapps for Rom
This Rom are builded for making alternative with some differents.
THIS IS NO TOTALY NEW ROM !
Any kernel changes?
always welcome and yes build build and build
good job !
A Perfect Sweet ROM
Dear AntiBillOS,
Thank you for your rom.
After using Carbon A3 over a week with satisfaction I did a dirty flash with your rom.
Everything is functioning well and good. AV playing and recording is nice and smooth.
Wifi, network, file transfer is also smooth. Overall no lag, fast and very responsive, a good battery life with a well organized settings giving a perfect sweet test.
I uninstalled the default launcher Trebuchet and installed Launcher8 for its simplicity. Uninstalled few google things that are not for me. I went to recovery and clear cache and delvik.and reboot. After showing Samsung logo, a blank screen appeared and it hung there. Pulling battery out and in and power on few times managed to boot. Again in a planned reboot it hung after showing Samsung logo.
Hope you will share your ROM with us in the coming future and make us happy.
Regards.
Cannot reboot the phone. Is it only a problem of mine?
Power button is working fine here. Try Rebooter app to reboot. Probably you need to reflash. If stuck after Samsung logo, pull the battery out. Press power button. Insert battery and power on.
Sent from my GT-I9003 using xda app-developers app
guys, does the video recording work very fine in this build?
(I have serious issues with vrecording in cm10.2 by dhiru, not just in playback, but also the recorded video looks kinda buggy))
Even after a clean flash the problem's still there: to reboot the phone I have to shut down and then power on. If I try to reboot it gives me a black screen.
But this is a minor issue.
What about the 3g net? I noticed that in dhiru's cm 10.2 a3 it often disconnects, but the 3g icon is still there even with phone not reaching the 3g signal. Is this problem solved here?
Video rec/ply 480-720 is fine here.
Sent from my GT-I9003 using xda app-developers app
Yo, dev! Are you even alive?
Good rom.
3rd time I install it from fresh ddlf2.
3g problem seems solved, with the other kernel it showed 3g icon even if not connected.
Reboot problem still persists, I have to pull-off battery to get the reboot.
wow good news for our sl
go dev go:thumbup:
Sent from my GT-I9003 using xda premium
Antutu 3D Testing problem
Dear AntiBillOS,
Your rom is doing a NON STOP FLIGHT. Good performer.
Antutu benchmark sometimes cashes when doing 3D tests. It crashes in the middle or at the end of the 3D test.
Providing Alogcat logs - don't know it will help you or not.
Will be pleased if you provide only the kernel.
Thanks a ton.
I cannot use this rom. I'm very sad because the 3g issue is fixed here, BUT after a 1st reboot made taking off battery, I'm not capable of rebooting the phone again, even after wiping cache and dalvik. I always get a black illuminated screen after Samsung logo.
In cwm format system and flash again. After flashing, select power off. Take out-in battery. Now use power button to start. After samsung logo wait for 15 sec if the circle is not shown do the battery thing again. Keep trying...
This kernel can boot into recovery but hang into reboot.
Sent from my GT-I9003 using xda app-developers app
im kinda confused, so im sorry for this noob question.
but this is another alternative rom right of cm 10.2? would i be still beable to flash other roms on top of it like the normal one?
Yes. Same as other cm 10.2. As the dev says - not a new ROM.
Sent from my GT-I9003 using xda app-developers app
after the samsung logo it shows the most unresponsive black screen i've ever seen.
I just want to let you know I finally made the ROM jump from MaximusHD to CyanogenMod 12.1 and it went superb!
Before starting this I thought I would be busy the whole evening (or more than one) so I prepared for the worst. I still use this phone on a daily basis. I got another HTC oldy as a backup just in case. My HTC One S isn't recognized on my PCs anymore since jumping in the swimming pool with it last summer so I had an extra handicap not being able to upload from PC to device.
I updated TWRP to the latest. Cleared storage. Rebooted in MaximusHD again ignoring the setup wizard as much as possible. Once booted I opened the web browser and downloaded the CM12.1 05DEC Unofficial ROM and TK GApps mini directly to my device. (All links available in the specific thread here on XDA) Booted in recovery again and flashed CM12.1 and TK GApps. All my apps and settings were uploaded/installed when the device booted CM12.1.
After boot all I had to do is change my Mobile 3G APN setting.
After one hour of work I couldn't believe it went so quick! And easy! The experience of CM12.1 on this 3 year old phone is unbelievable. I thought I would experience more lag and slow responses but... none of that. I can't notice any difference in speed comparing with the MaximusHD ROM.
I hope this stimulates others to make the update.
bakmanhans said:
I just want to let you know I finally made the ROM jump from MaximusHD to CyanogenMod 12.1 and it went superb!
Before starting this I thought I would be busy the whole evening (or more than one) so I prepared for the worst. I still use this phone on a daily basis. I got another HTC oldy as a backup just in case. My HTC One S isn't recognized on my PCs anymore since jumping in the swimming pool with it last summer so I had an extra handicap not being able to upload from PC to device.
I updated TWRP to the latest. Cleared storage. Rebooted in MaximusHD again ignoring the setup wizard as much as possible. Once booted I opened the web browser and downloaded the CM12.1 05DEC Unofficial ROM and TK GApps mini directly to my device. (All links available in the specific thread here on XDA) Booted in recovery again and flashed CM12.1 and TK GApps. All my apps and settings were uploaded/installed when the device booted CM12.2.
After boot all I had to do is change my Mobile 3G APN setting.
After one hour of work I couldn't believe it went so quick! And easy! The experience of CM12.1 on this 3 year old phone is unbelievable. I thought I would experience more lag and slow responses but... none of that. I can't notice any difference in speed comparing with the MaximusHD ROM.
I hope this stimulates others to make the update.
Click to expand...
Click to collapse
I've been tempted by the idea of jumping the MaximusHD rom ship for a while too. Are you happy with the camera performance? One of the reasons I'm reluctant to go the non-Sense rom way is the lack of the full hardware access to the camera on those roms.
I just jumped the ship three days ago. I didn't use the camera besides taking 3 pictures for test purposes. I'm a long time Camera ZOOM FX user so the app installed itself again. I replaced the CM12 camera app in the drawer with it.
I need more user experience time with the camera to tell you it lacks in any way.
What, besides performance (speed) issues, will affect the camera not being able to have full hardware access?
bakmanhans said:
What, besides performance (speed) issues, will affect the camera not being able to have full hardware access?
Click to expand...
Click to collapse
A couple of things I remember were missing from non-Sense camera apps are the ability to shoot slow motion video (lower res but higher fps) and the HDR mode for photos.
Not that these two produced any usable results though .
I believe the other parameters like photo/video resolution are adjustable with the stock CM camera and ZOOM FX apps, right?
twotimer said:
A couple of things I remember were missing from non-Sense camera apps are the ability to shoot slow motion video (lower res but higher fps) and the HDR mode for photos.
Not that these two produced any usable results though .
Click to expand...
Click to collapse
I can't find slow motion video. I never saw it in the MaximusHD ROM either. ZOOM FX cam does have the HDR option, just like with MaximusHD. But seriously, it's nothing more than a gimmick. Do you ever use it?
twotimer said:
I believe the other parameters like photo/video resolution are adjustable with the stock CM camera and ZOOM FX apps, right?
Click to expand...
Click to collapse
With stock CM camera I don't see these options. This cam app is really minimal. Some say you need to set resolution by entering the hamburger menu upper-left but I don't have the menu. App version is 2.0.002.
With ZOOM FX Premium all resolutions settings are there.
When booting my phone this morning I noticed that there is still one MaximusHD ROM leftover. I guess it's not really part of the ROM. It's the boot screen. The first screen you see when cold booting your phone. It's a screen with HTC logo and the development warning text in red underneath it. Can I easily get rid of it?
bakmanhans said:
When booting my phone this morning I noticed that there is still one MaximusHD ROM leftover. I guess it's not really part of the ROM. It's the boot screen. The first screen you see when cold booting your phone. It's a screen with HTC logo and the development warning text in red underneath it. Can I easily get rid of it?
Click to expand...
Click to collapse
It's not part of the ROM, it's rather a part of the bootloader itself. You can change it by flashing a modified bootloader version:
http://forum.xda-developers.com/showthread.php?p=38387544#post38387544
Just read the thread on how to do that and find the one that fits your HBOOT version.
Coming from MaximusHD my hboot is at version 2.16... I don't see any download for that.
I've been using 20151223 UNOFFICIAL for some time now without the camera/flashlight issue. I've been using the camera more than once during the holidays.
Only trouble I have is getting cellular (3G) back online after flight modus. It's not possible. I have to restart the device every time. Anybody else experiencing this?
No, working great here on 2015-12-23 Unofficial HBOOT 2.16 from Flyer. When going out of plane mode, it takes around 15 seconds to get H icon (for HSDPA, 3G if you prefer). It may be a problem with the SIM card or advanced operator settings.