Develop Bugs

[Q] Trackwake trick not working

Hi everyone!
I'm new in this forum, I've searched but didn't find nothing about my problem. I rooted my telephone using the new Revolutionary method and now I have CWM4 recovery. I tried to apply this trick to unlock the desire with the trackball instead of power button. It seems to go fine but when I reboot the device it won't start. It stays in the splash screen until I take the battery out and restore a previous backup. I tried changing the recovery, used CWM3, CWM 2.5, Amon RA 2, but nothing worked.
Am I doing anything wrong?
Thanks in advance.

What rom have you got? The CyanogenMod and (all) roms that are based on it can activate it in the settings.
Settings - CyanogenMod settings - Lockscreen - Unlock options - Trackball unlock

I haven't installed any rom, just rooted the oficial one, so.. I guess I have Froyo.. could this be the problem?
Sent from my HTC Desire using XDA App

Yes I think maybe it doesn't with on stock rom
Sent from my CM7.1 Desire using XDA Premium App

I think that is for Oxygen Rom..
If you like stock rom flash (install) this rom >> http://forum.xda-developers.com/showthread.php?t=1200261 this is stock Gingerbread sense rom based on official HTC Desire Gingerbread ROM with additional mods to install whichever you like. Make sure you make backup before installing use titanium backup or nandroid backup in recovery.
For trackpad to unlock on above rom go to this >> http://forum.xda-developers.com/showpost.php?p=7515638&postcount=3 and flash SNQ Kernel v6 first and then Trackball Wake..
If you decide to install any other rom just search in that thread for its trackpad unlock.

Thanks very much for the tip! I've seen the ROM and seems nice, but I need to ask.. If I go to Gingerbread, will I be able to go back to what I have now? I read that after you upgraded to 2.3, you couldn't come back to Froyo...
-----------------------------------------------------------------
EDIT:
I've been searching and I found this pre-rooted Froyo ROM. I must understand that it's the stock ROM with root access, so these are my questions:
Can I use those optional mods there with my already rooted Froyo rom? I see the only difference between that one and mine is that "init.d" thing (which I still have to read about), so I'd like to know wether "installing" it or "flashing" it or whatever I must do to have it will be enough to apply those mods.
In case this is not possible, could anyone explain to me what's the main difference between a stock ROM and the other ones? What lets you apply or not some certain tricks in a ROM? Is it the Radio? The kernel? The HBOOT? The Recovery?
Thanx!
Sent from my HTC Desire using XDA App

Please understand that TRACKPAD to UNLOCK function is HACK!
Hacks are usually ROM-specific. This means that you MUST use the hack made for your specific ROM. Please search for such patch from the same thread where you found your ROM.
Or let us know which ROM you are using, so that others can point you the exact zip file you need (if such exists, of course).

Thanks, Laizy-jumper, I had Froyo stock rom, I thought I had said it a few posts before.
I've finally decided to flash my device with NeoPhyte Reflex S rom, so I now have the trick working in my Desire. I would have loved I could make the hack work in my stock rom, but I was told that it was unadvisable to do that (furthermore, I didn't get to find how to do it).
So now I'm testing my new rom, although I keep thinking I prefer stock one. If you know how I could make trackwake trick work in Froyo stock, I'd love to read it.
Thanks for your answer and your time

falbala84 said:
If you know how I could make trackwake trick work in Froyo stock, I'd love to read it.
Click to expand...
Click to collapse
You can have trackpad wake only on a ROOTED phone.
I suggest following ROM with a "tweaks-12" patch for such combination.
http://forum.xda-developers.com/showthread.php?t=773997
This is very close to the actual stock Froyo. I have been using it myself before Gingerbread ROMs came out.
If you want ONLY trackpad wake function (not any other functions from the patch) then you need only one file to be updated in the ROM. It's the keyboad layout file you can find in the tweaks-12 patch, /system/usr/keylayouts/ folder.
If you move this file to the original ROM zip file (the same location in it) then you don't need to patch the ROM separately. You need to switch off the verification option in recovery when you are flashing zip files modified by yourself!
But I must admit I am not a fan of trackpad wake/unlock function myself. It may activate the screen when you have a phone in the pocket, means a lot of extra battery drain.
Why don't you use Gingerbread rooted ROM? It's much more advanced imho.
This one is the closest for stock:
http://forum.xda-developers.com/showthread.php?t=1196327
With TP-W patch from there:
http://forum.xda-developers.com/showpost.php?p=16484585&postcount=3

You can have trackpad wake only on a ROOTED phone.
Click to expand...
Click to collapse
I know that, actually I had already rooted my phone, that was the point, precisely, I couldn't make the trick work although I was root.
If you want ONLY trackpad wake function (not any other functions from the patch) then you need only one file to be updated in the ROM. It's the keyboad layout file you can find in the tweaks-12 patch, /system/usr/keylayouts/ folder.
If you move this file to the original ROM zip file (the same location in it) then you don't need to patch the ROM separately. You need to switch off the verification option in recovery when you are flashing zip files modified by yourself!
Click to expand...
Click to collapse
That's an interesting thing to hear, I'd only need to know how to get my original ROM in order to modify it...
Why don't you use Gingerbread rooted ROM? It's much more advanced imho.
Click to expand...
Click to collapse
I have installed a GB based ROM, but I've read it has problems with wifi connection, so I'm testing it for a while and after that I'll decide what to do.
But I must admit I am not a fan of trackpad wake/unlock function myself. It may activate the screen when you have a phone in the pocket, means a lot of extra battery drain.
Click to expand...
Click to collapse
Well, I don't usually keep the phone in my pocket, I use to bring it in my bag, I also have a leather case that protects it, and I have an unlock pattern set to unlock, so I don't think it's easy the phone gets unlocked by accident However, I've read Desire has a very fragile power button, so I prefer not to use it.
Thank you!

falbala84 said:
That's an interesting thing to hear, I'd only need to know how to get my original ROM in order to modify it...
Click to expand...
Click to collapse
I think you should be able to modify your existing ROM on the phone as well.
But you need to know something about adb tools and such, to be able to read and write files to phone /system folder. You need to do that while in recovery. Mount /system in recovery, use QtAdb on your pc, to transfer files between phone and pc. I am not going to give you a full lesson here. I am running Linux on my pc, so it is very easy with that. But it might be a bit more complicated on Windows because you need to install some extra drivers, I suppose. On Linux, just download QtAdb with binaries and run it.
falbala84 said:
I have installed a GB based ROM, but I've read it has problems with wifi connection, so I'm testing it for a while and after that I'll decide what to do.
Click to expand...
Click to collapse
That's not really true. I have not had a single problem with WiFi. But I am not trying early beta versions either. ;-) First let others to try and read the opinions. I am flashing once I see there are no significant problems left with a ROM. I don't care about the very latest and fanciest features, rather using a bit older but stable version.

Well, I think I made a mistake using the verb "test", I should have said "try", since I'm not using a beta version, either. Actually, I'm using a popular rom which I was recommended by several people in a Spanish forum (that's why my English is not very good).
That's the kind of answer I was really looking for at the first time, the way I could modify my ROM with those tools you mention. I did some searching but din't find the way to do it, so I had to flash this new ROM.
May I ask you what rom you are using at the moment? I think I'll end up installing pre-rooted stock Froyo unless I find a rom that I really like.. Or do some researching and start working with adbtools (I'm a programmer in Java, I think I'd be able to do it )
Thanks!!

falbala84 said:
May I ask you what rom you are using at the moment? I think I'll end up installing pre-rooted stock Froyo unless I find a rom that I really like..
Click to expand...
Click to collapse
I was using Cool VisionS v8 port http://forum.xda-developers.com/showthread.php?t=1018843 for some time. And I must admit it was really stable and reliable. Finally I got a little tired of Rosie rotation, so I changed to a different ROM.
Currently I am using AceModS007 v32. No big troubles either. Just a little more laggy because of Sense 3 components. Sense 3 lockscreen is the most annoying part of this ROM and it does not seem to be possible to switch to Sense 2.1 version of it.
I actually consider moving back to VisionS or ordinary AceS (without Sense 3 mods). There are several improvements done for those. I was missing quality video recording earlier, now it is probably better (current AceModS007 is also quite usable on that).
I have not tried any rooted GB "Stock" ROMs. I find Sense 2.1 to be much nicer than old 1.x, so I really don't want to go back ;-)
Sense 3 looks pretty nice. But it's not really good for everyday use by my opinion. It might be good for "gamers" but not as a phone solution.
I have also tried Oxygen 2.1.6. Nice and clean but I was really missing Sense goodies.

Finally I got a little tired of Rosie rotation, so I changed to a different ROM.
Click to expand...
Click to collapse
If that means desktop rotates, I definitely won't install that rom
I'm pretty sure I want Sense in my phone, but I have some questions: Which are the differences between Sense 2.1 and Sense 1.x? And which one is Sense 3? I now have the lockscreen where you pull a ring and I, personally, hate it, as much as the answering method or the alarm discarding one. I believe I have a mix between 2.1 and 3.0, so... which sense should I have to get old unlock method? (where you slid a bar down).
I have not tried any rooted GB "Stock" ROMs. I find Sense 2.1 to be much nicer than old 1.x, so I really don't want to go back ;-)
Click to expand...
Click to collapse
So, Froyo stock rom has Sense 1.x? Or 2.1?
I never thought it was this difficult to choose! And I thank you, furthermore, because I can practise English while I try to decide!

falbala84 said:
If that means desktop rotates, I definitely won't install that rom
Click to expand...
Click to collapse
It's only VisionS ROM that has such option. AceS and SagaS don't have that.
falbala84 said:
I'm pretty sure I want Sense in my phone, but I have some questions: Which are the differences between Sense 2.1 and Sense 1.x? And which one is Sense 3? I now have the lockscreen where you pull a ring and I, personally, hate it, as much as the answering method or the alarm discarding one. I believe I have a mix between 2.1 and 3.0, so... which sense should I have to get old unlock method? (where you slid a bar down).
Click to expand...
Click to collapse
Unfortunately I am not able to list the differences between 1.x and 2.1. Just can't remember the "old one" . But I am sure that I would immediately miss the new one if I should go back to the old 1.9.
Most of stable/reliable ports are 2.1. Some of them have Sense 3 parts included. A kind of a mix of different pieces.
Sense 3 has few nice pieces. For example Messaging application, music (missing in many ports), Weather (just the app and widget, the nice weather lockscreen used to be a battery eater), USB PC connection screen.
falbala84 said:
So, Froyo stock rom has Sense 1.x? Or 2.1?
Click to expand...
Click to collapse
Stock ROMs are all Sense 1.x.
BTW. There is a solution to remove Sense 3 lockscreen. See the solution from there:
http://forum.xda-developers.com/showpost.php?p=17069636&postcount=8991
Basically, you need to replace 3 files: HTCLockscreen.apk, Dialer.apk and Phone.apk. Take the files from the base 2.1 ROM. It's a detective work to find the original ROM, sometimes. But I think it's worth of trying.
The given zip may not work for all versions, I think. But there is always a chance to try it
EDIT: Sense 2.1 lockscreen requires also /system/framework/com.htc.framework.jar replacement. Tried and works!

I'm going to try that I guess...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So, is this Sense 1.x? This is the lockscreen I want, then... Is it possible to install files from 1.x in a GB based rom?

I do not know which ROM you are pointing at... I've read that MIUI ROMs are iP**** styled. Perhaps the first two screens are from there. Lower resolution screens might be from different (non-bravo) port.
Personally, I do not like such approach
I really like Android on Desire. Standard Sense is practical for a phone. Any major change in it adds suspicions about some "hidden features" that I may not like.
As a programmer, you probably understand what I mean.
I also use Droidwall due to the same reason
Sense 2.1 lockscreen is similar to 1.9. The bar to drag up'n'down. Sense 3 lockscreen has the ring with 4 icons. That's the difference.

Standard Sense is practical for a phone. Any major change in it adds suspicions about some "hidden features" that I may not like.
As a programmer, you probably understand what I mean.
Click to expand...
Click to collapse
I agree, that's precisely why I didn't want to change something that I mostly liked.
I'm now trying the solution you showed me to remove sense 3 lockscreen, but I need to know.. What is IC?
Attached is the version for IC 1.1.2 A2SD
Click to expand...
Click to collapse

falbala84 said:
I'm now trying the solution you showed me to remove sense 3 lockscreen, but I need to know.. What is IC?
Click to expand...
Click to collapse
IC means InsertCoin. This is the name of the modded ROM by baadnewz
As I already mentioned, you need 4 files. Those must be taken from the same base as original 2.1 ROM. For example Cool AceS Sense 2.1 ROM. This one contains the latest updated versions, usually.
In addition, you need to clear dalvik-cache after replacing those files.
Which ROM are you using? Maybe I can give you some more detailed answers.
I made a flashable zip for AcesMod007.

I read about the 4 files, but the thing I don't know is: do I need to extract my ROM, modify, save and flash again? Or can I put files into my phone some way? I guess it must be with adb, but I haven't got any time to learn how to use it.
My Rom is called Reflex S 2.1.7, do you think I could use the file you uploaded?

11/04/11 Tmobile USA lite 4.0 Rooted Fast Stable No HTC Sense

11/04/2011
Version 4.0 of the ultimate ROM for Tmobile USA wildfire s users!!!
Whats new in 4.0:
Fixed picture messaging for Tmobile USA users
Removed a few more HTC sense components
Tweaked for improved performance
Prerequisites: Must have s-off, clockwork mod installed, back up your current data.
Based on RUU_Marvel_TMOUS_1.62.531.3_Radio_47.10f.35.3032_7.48.36.17M_release_202047_signed
Features:
ADW Launcher
Permanent Root
Super User
Busy Box
data2sd
HTC IME mod keyboard by jonasl
Email app from cm7
Tmobile wifi calling
working MMS for tmobile USA
Removed:
HTC Sense
Tmobile Boot Jingle
Tmobile Boot Animation
Gmail
Google Talk
Voice Dialer
Voice Search
Most media files (ringtones, notifications)
A majority of the HTC sense stuff
Works: Everything works daily used on my Tmobile USA wildfire S
Not Work: none
DOWNLOAD:
TMOlite4.0.zip
Installation Instructions:
1. Partition sdcard with fat32 primary and EXT3 primary partitions.. I used 0 swap size. You can partition within CWM.
2. Install TMOlite4.0.zip from within CWM
3. Enjoy your phone without HTC Sense and large internal memory!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Install at your own risk!
Special Thanks:
Alquez: CWM and cyanogen mod port for htc marvel
jinkataru: help getting data2sd to work
thehumble1: TMO USA support
tera tike: partial list and testing what apps can be erased
carrie: for MMS testing

this spot reserved....

Looks good. I didn't see this when I went about making almost the same ROM, including Tara Tike's removals.
I think we both have the same problem with Asian and European ROMs that our accelerometer (and maybe something else too) doesn't work, which means we won't get to run CM7 or other fun ROMs without porting it to the TMOUS kernel.
What I'd like to do now is get Melethron's data2Whatever working, which would give us unlimited system storage (well up to 2GB). Even with 120mb free I still think there is a lot that could be gained with D2WE.
Other than that, I'd really like to figure out how to port the CM7 version to our state-side phones.
Anyway, let me know if you're interested.

Thanks for your insight. I'm interested but I'm actually not good at programming. If anything I can do to help I can try or test for you but as far as porting kernels I have no idea.
Sent from my HTC Wildfire S using Tapatalk

thehumble1 said:
Looks good. I didn't see this when I went about making almost the same ROM, including Tara Tike's removals.
I think we both have the same problem with Asian and European ROMs that our accelerometer (and maybe something else too) doesn't work, which means we won't get to run CM7 or other fun ROMs without porting it to the TMOUS kernel.
What I'd like to do now is get Melethron's data2Whatever working, which would give us unlimited system storage (well up to 2GB). Even with 120mb free I still think there is a lot that could be gained with D2WE.
Other than that, I'd really like to figure out how to port the CM7 version to our state-side phones.
Anyway, let me know if you're interested.
Click to expand...
Click to collapse
I got a couple of questions for you humble1, did you downgrade to any official rom(Asian or European) after s-off and is your phone still simlocked?

It's easy to remove HTC Sense, could you make a rom that comes from SDK? Which is based on google and without twice development....

meanmug said:
I got a couple of questions for you humble1, did you downgrade to any official rom(Asian or European) after s-off and is your phone still simlocked?
Click to expand...
Click to collapse
yes phone will be s-off and simunlocked....

ZXYannis said:
It's easy to remove HTC Sense, could you make a rom that comes from SDK? Which is based on google and without twice development....
Click to expand...
Click to collapse
Someone is already doing that.. its called Cyanogen mod.... it being done right now by Alquez

Looks great! I'm scrapping my ROM and trying this. Looks like exactly what I was trying to do. Nice work.
@Tyrone1 did you lock the old market app or is this likely to update to the new market? I hate the new market app.
Also, I found this with my ROM as well. Something we removed was the HTC Quick Lookup, which is what the search button is mapped to at the home screen. I've tried Zeem and ADW and it doesn't work. I know the button is working because in applications with mapped search button (ie. Market, browser) it works fine. Also at the home screen a long press will activate Voice search just fine. I don't know if we need to replace the HTC apk or find a way to map google search to the search button.
---------- Post added at 03:30 PM ---------- Previous post was at 03:09 PM ----------
meanmug said:
I got a couple of questions for you humble1, did you downgrade to any official rom(Asian or European) after s-off and is your phone still simlocked?
Click to expand...
Click to collapse
I haven't tried a completely stock rom for Asia or Europe, but I can use custom roms for TMOUS without problems (1.62-based) and all 1.33 based roms give me problems with accelerometer (and maybe things I haven't found yet).
I'm S-Off and no simlock (I have an AT&T SIM that I use for testing, even though it's not activated).
---------- Post added at 04:01 PM ---------- Previous post was at 03:30 PM ----------
ZXYannis said:
It's easy to remove HTC Sense, could you make a rom that comes from SDK? Which is based on google and without twice development....
Click to expand...
Click to collapse
If you know how to use the SDK distro and combine it with a working kernel, go for it. I don't, but if you (or someone else) tell me how, I'll do it. Actually I'd rather port alquez's CM7 because CM is better than HTC or stock Google distro.

never flashed any ROMS except my own ROMS also flashed some of goapk.com and xda.cn ROMS, it's where I learn a lot also XDA I visit everyday. My phone needs to rest including me. When I have energy including my phone I will flash this ROM including alquez CM7 and other rom made for wildfire s.

It works fine for my needs and I will wait until alquez's Cyanogenmod is ported and working for Tmobile USA users.
Anyone who wants to use or modify this ROM feel free to do so!! Thanks all who have helped wildfire S users... jinkataru, alquez, thehumble1, tera tike and all others... thanks

wow from 2 to 3 in a day. Nice.
Search button isn't working and when I try to change the Ringtone or Notification tone Settings.apk FCs.
I'm on 2.0 though. Didn't see change log to show that 3.0 had these fixed.

thehumble1 said:
wow from 2 to 3 in a day. Nice.
Search button isn't working and when I try to change the Ringtone or Notification tone Settings.apk FCs.
I'm on 2.0 though. Didn't see change log to show that 3.0 had these fixed.
Click to expand...
Click to collapse
LOL i just arbitrarily assign those numbers.. i could've gone to 10.0 just to make it sound like the ROM is highly developed
u should be able to change ringtone and notification with the last version of the rom. However not sure about the search button.. i never really used it before and dont really plan to use it either...
OH yeah PS i came from HD2 hyperdroid prior to this phone too LOL

It's quite amazing how easy this is compared to using a phone that was built for Windows 6.5
Sent from my HTC Wildfire S using xda premium

Any euro htc marvel users willing to test this ROM and see if autorotate and accelerometer work and report in here. Thanks
Sent from my HTC Wildfire S using Tapatalk

Updated to 4.0!!!!! Enjoy!

I see that you are no good at laying off the rom development. Nice work. Now I just have to backup and install the new one.
Also, the search button still doesn't work from the home screen. To fix this put GoogleQuickSearchBox.apk in the system/app directory, change permissions to match the other apps (rwx r-x r-x I think) and reboot.
the apk has to be the newer one. I messed with this for ages till I realized that I didn't have the right, working apk.

thehumble1 said:
I see that you are no good at laying off the rom development. Nice work. Now I just have to backup and install the new one.
Also, the search button still doesn't work from the home screen. To fix this put GoogleQuickSearchBox.apk in the system/app directory, change permissions to match the other apps (rwx r-x r-x I think) and reboot.
the apk has to be the newer one. I messed with this for ages till I realized that I didn't have the right, working apk.
Click to expand...
Click to collapse
thanks for the update!!! I'm still using my lite 4.0 rom working well...
cheerz. hope you get your xtc clip back.. thats why i dont want to mail mine out..

[26.OCT.11] [MAGLDR] Android 2.2.1 Sense 2.0 [DHD 1.84][EU][RAF1.9 AUO]

This ROM is based on Orange Desire HD 1.84.61.2
Intrudution:
This ROM was made for HD2 EU and is meant to be as much "stock" ROM as possible. Most used tweaks are here just to overcome HD2 EU version lack of NAND space. Desire HD base was used as a most stable and feature rich ATM. I hope 2.6.35 kernel will bring us the new possibilities.
Features:
- Orange branding removed.
- Fully stock (only AdobeReader, YouTube, QuickOffice, Gmail and Twitter removed, you may get new versions from Market).
- TTS, voice recognition, themes, ringtones, wallpapers are all still here.
- aGPS lib v2.1 from tytung (US as default).
- Framework cache in RAM (modified imilka's method).
- Dalvik cache on NAND.
- All applications are on SD-EXT partition.
- SU application added.
- andrev_oc daemon added with Daemon Controller application.
- Rafigna's 1.9 kernel with AUO panels patch.
A word of advice:
- Do not use and third party Apps2SD solutions on this ROM. Results are unpredictable. The same applies to dalvik-cache movements. And, it is a really bad idea to put dalvik-cache on SD-EXT, really.
- ROM must be rebooted at least once for RAM method to work.
Installation:
- MAGLDR only for now, sorry. Maybe later.
- 160 mb partition should be enough (or even 150 mb, I just didn't test). 1 Gb or so EXT partition.
Screenshots:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Download:
http://www.multiupload.com/6DEOU4LL71

I think i am first here i am downloading now . Thank you very much for your work
What about flash player 11 ?
And free ram mb ?
Thank you again

First off : Thank you for providing us a 2.2.1 Sense ! 3.0/3.5 are overrated on this device !
Quick question : is the remark about the "not a good idea to move the dalvik to ext" only good for this rom or is it a general remark ? I'm interested in knowing why if it's the second answer...
Thanks !

DannyBiker said:
First off : Thank you for providing us a 2.2.1 Sense ! 3.0/3.5 are overrated on this device !
Quick question : is the remark about the "not a good idea to move the dalvik to ext" only good for this rom or is it a general remark ? I'm interested in knowing why if it's the second answer...
Thanks !
Click to expand...
Click to collapse
probably because an sd card is slower than nand

mmmm10 said:
I think i am first here i am downloading now . Thank you very much for your work
What about flash player 11 ?
And free ram mb ?
Thank you again
Click to expand...
Click to collapse
1. Currently I have FP 11 installed and see no problems. But I rarely use browser, so you better see it for youself.
2. Hell if I know, but framework in RAM makes it 35 mb less.

Well, some people say that the sd cards are faster than nand but more easily corrupted.

DannyBiker said:
First off : Thank you for providing us a 2.2.1 Sense ! 3.0/3.5 are overrated on this device !
Quick question : is the remark about the "not a good idea to move the dalvik to ext" only good for this rom or is it a general remark ? I'm interested in knowing why if it's the second answer...
Thanks !
Click to expand...
Click to collapse
1. It's 2.0 sense. Unfortunately.
2. The first reason was already given. NAND is faster on read than SD. At least it should be. And it is most certanly faster on random access reads. And the second one is much more funny and complicated. Then you move your applications and dalvik-cache to SD-EXT you have about 180 mb NAND free (or so). But they are most certanly not used. Apps are on SD, cache is on SD.

WARP ItSelf said:
1. It's 2.0 sense. Unfortunately.
2. The first reason was already given. NAND is faster on read than SD. At least it should be. And it is most certanly faster on random access reads. And the second one is much more funny and complicated. Then you move your applications and dalvik-cache to SD-EXT you have about 180 mb NAND free (or so). But they are most certanly not used. Apps are on SD, cache is on SD.
Click to expand...
Click to collapse
im ok with sense 2.0 except unlock and answer slider. can you make ring work for answer in this version ?

So I put the rom is the same turns out to be very fast and stable, 2 possible bugs found then the browser crashes by default is also not automatically update the date and time ...... possible solutions?
P.S. I tried putting Dolphin HD Broswer same crash when opening
The pass-through mode, or better Internet does not work out, but the icon does not use the internet PC

Is this froyo or gingerbread? i put this rom thru the kitchen to make a cLK version and im using gingerbread kernels but the rom is saying 2.2.1

[email protected] said:
Is this froyo or gingerbread? i put this rom thru the kitchen to make a cLK version and im using gingerbread kernels but the rom is saying 2.2.1
Click to expand...
Click to collapse
Well obviously its going to say that, because it is!
It clealy states that its Froyo (2.2) in title, and you can also tell from the sense screens.

TheATHEiST said:
Well obviously its going to say that, because it is!
It clealy states that its Froyo (2.2) in title, and you can also tell from the sense screens.
Click to expand...
Click to collapse
First off : Thank you for providing us a 2.2.1 Sense ! 3.0/3.5 are overrated on this device !
from your statement i thought it was GB and the 2.2.1 was a typo because froyo sense is 2.0! There is sense 2.1 GB and 3.0 sense GB and 3.5 sense GB. Just to answer your question.

Hi WARP ItSelf, I like to know in your opinion why I should test your rom if I have Mikhei777 one http://forum.xda-developers.com/showthread.php?t=1259110 and for me works very fine.
Perhaps yours obtain more available free space for apps?
Thanks for your reply.

Authi said:
Hi WARP ItSelf, I like to know in your opinion why I should test your rom if I have Mikhei777 one http://forum.xda-developers.com/showthread.php?t=1259110 and for me works very fine.
Perhaps yours obtain more available free space for apps?
Thanks for your reply.
Click to expand...
Click to collapse
Its entirely upto you to test the ROM. to be more precise there are two types of HD2 users out here. Either EU or T-Mobile.
So if you go to Mikhei777 rom, you can see he did not restrict his ROM to EU version, meaning if you installed his rom on EU version, then you gotta do all the basics to avoid memory errors and also move almost all apps to SD
Coming to this rom, the way i see from the topic label also this ROM is more suited towards EU users who have less space after installing Sense based roms.
Apart from these things, there are wonderful chefs out there. Sometimes there own personal tweaks make the rom for US end users so smooth and a better choice then the predecessor roms we tried.
So you gotta try it to know it. Thats my policy.
Just thought i would share my personal thought with you as well.

incubonero said:
So I put the rom is the same turns out to be very fast and stable, 2 possible bugs found then the browser crashes by default is also not automatically update the date and time ...... possible solutions?
P.S. I tried putting Dolphin HD Broswer same crash when opening
The pass-through mode, or better Internet does not work out, but the icon does not use the internet PC
Click to expand...
Click to collapse
Sorry, if I understand it right:
1. Browser crashes.
2. Time is not automatically updated from operator.
If so - I currently don't have such problems. We need a third independent opinion. Please check partition size.

Authi said:
Hi WARP ItSelf, I like to know in your opinion why I should test your rom if I have Mikhei777 one http://forum.xda-developers.com/showthread.php?t=1259110 and for me works very fine.
Perhaps yours obtain more available free space for apps?
Thanks for your reply.
Click to expand...
Click to collapse
Mikhei777's ROMs are quite good. For me his Froyo ROM was "no go", because I need Voice Recognition working and I had some FCs (but it's probably my fault). The "stock" feeling is very meaningful to me. Moving all applications to NAND will eat EU HD2 space rather quickly (especially if you prefer heavy ones as navigation and games) and using Apps2SD you will have almost the same experience as you will have using my ROM (depends on moving preinstalled apps and dalvik-cache to SD). So you are free to try but do not expect a miracle.

criszz said:
im ok with sense 2.0 except unlock and answer slider. can you make ring work for answer in this version ?
Click to expand...
Click to collapse
I don't think Sense 3 ring will work with Sense 2 as it does with 2.1. But I will try if I have time.

since GB was so buggy, froyo was my 1st priority, especially if it's stock, what a great. Thank You Sir, i'm having EU HD2 so sure I will download and try this ROM.

erwinpiero said:
since GB was so buggy, froyo was my 1st priority, especially if it's stock, what a great. Thank You Sir, i'm having EU HD2 so sure I will download and try this ROM.
Click to expand...
Click to collapse
Please post your experience, I have only one HD2 to try.

WARP ItSelf said:
Please post your experience, I have only one HD2 to try.
Click to expand...
Click to collapse
Sory Sir it's great to try your rom, but i had experience 2 sleep of death, this i've been face when i use rafdroid rom with auo patch, dunno whether it's my HD2 problem.
Thank You
Sent from my Desire HD2 using xda premium

GB or ICS ROM ?

I see that many of you are complaining that ICS ROMs aren't good enough and you mention some camera issues. I got my Desire Z two days ago from an android app competition and now have to root it and find a good ROM to flash. Rooting is much more complicated than on my previous device but there are a lot of guides.
My Question is should I choose a stable gingerbread (like Cynogen 7.1 ) or ICS (Andromadus Mimicry) could be used as a daily driver ?
I am concerned about camera, will it work good enough cause I use it pretty much.

Rooting isn't that complicated, it only took me an hour or so and the Desire Z is my first Android device. Just follow the guide in Wiki here and you'll be fine.
What's stopping you from trying both GB and ICS once you root the phone?
Anyway, Sense 4 ROMs have problems with non-working camera, on AOSP ROMs it works fine except for 720p video, though I think someone mentioned an ICS ROM which has 720p recording fixed, but I don't know which one was it. I don't use camera much so I can't really tell you much more about it.
I've been using Mimicry as a daily driver for a couple of weeks now and it works great for me. Before that, I spent a month or so on unofficial CM9 betas. You will probably get corrupted text every couple of days or so, but it's not a big deal, a simple app restart fixes it.
That said, I didn't even try any AOSP GB ROM, I wanted to see how ICS works and it turned out to be so good that I don't even have a need to try GB.

Thank you for the answer. Can you tell me result of Antutu benchmark app and how much free RAM do you usually have ?
On stock 2.3.3 Desire Z has a score of 2410 and just 100 MB of free RAM which I think isn't enough cause my older android phone has around 200 and is much cheaper than HTC even they have same amount of RAM.
Also on which cpu frequency works your phone ? I mean up to how much is stable to overclock without draining battery to fast.

Most ROMs for the Desire Z have them clocked on 1GHz or sometimes 1.2GHz. They are usually combined with a clever OC daemon, which underclocks it (to 350MHz or so) as soon as the screen's off.
And with a ROM like Mimicry by the way, you get around 180 MB of free RAM on average. Short after boot that can be 200MB, but that fills up quite quickly.
Having stock Sense on the phone is a serious drain; it's big, not really efficient anymore and simply old. ICS consumes less then any older Android.

try a few roms for yourself, this is the only way to know what you find best. for me I've tried six or seven sense roms and have been mostly disappointed with all of them, but others find them ok and even good. there are loads of great gingerbread builds for these phones, mostly cm7 based. of these I prefere elitemod and ilwt. the ics roms were not daily drivers up until a few months ago. the best of these I found have been elitemod and mimicry. of course I haven't used any of the others in some time but mimicry is a tweeked version of audacity so I'm sure that one is usable as well. the sense 4 roms I can't use yet, maybe someday ill try again, there are a few good miui builds but again for me these are only fun for a short time even though they are highly customizable they're just not for me
in the developer threads you will find a sticky a few threads down containing a list of most roms gingerbread and up for these phones, try a few and have fun!
Sent from my HTC Vision using xda premium

stevyhacker said:
Thank you for the answer. Can you tell me result of Antutu benchmark app and how much free RAM do you usually have ?
On stock 2.3.3 Desire Z has a score of 2410 and just 100 MB of free RAM which I think isn't enough cause my older android phone has around 200 and is much cheaper than HTC even they have same amount of RAM.
Also on which cpu frequency works your phone ? I mean up to how much is stable to overclock without draining battery to fast.
Click to expand...
Click to collapse
Here are Antutu results at 1.4 and 1.8 GHz. Normally, I have it clocked at 1.4 GHz max / 384 MHz min with SmartassV2 governor. I wouldn't go to over 1.4 for day to day use, it heats up quite fast at higher clocks. But you will have to experiment yourself and see what works for you, I don't think there's much to be afraid of regarding overclock. If you set the clock too high, your phone will probably just freeze and nothing else bad will happen. Just MAKE SURE you don't set it to apply settings at boot before you're absolutely sure it's stable, otherwise you could end up in a bootloop and you'll have to restore from a backup in Recovery. And of course, as safe as overclock is, don't do it if you're unsure about anything, and don't blame me if something goes wrong, you do it at your own risk. One more thing, for me Mimicry freezes at over 1.6 while it works normally at those clocks with other ROMs I tried, it probably has voltages set lower than the others, but I don't really have a need to check into it, so be careful if you decide to try setting the clock that high.
I get around 200 MB free on boot. If your question was regarding free memory in normal use, read this and just don't worry about it: http://www.androidcentral.com/ram-what-it-how-its-used-and-why-you-shouldnt-care
Sorry if you already know these things, I have no way of telling how much you know, so I wanted to try and cover as much as I could regarding your questions.
edit: Btw, I agree with demkantor, just take some time and try a couple of ROMs, that's the only way you'll find what you like best.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

@mirko935, just a quick tip, if you ever did overclock to high and forget and check the set on boot finding yourself stuck in a boot loop you can just flash the kernel on top of your current rom and it will reset the defaults, just an fyi

I say, have fun on Cyanogenmod 7.2 for a little bit. It's fast, stable, and super customizable. Then, in a couple months if you start to get bored, flash over to an ICS (or Jelly Bean!) ROM.
ICS is acceptable right now, but there are still issues. A little bit longer and the devs should have things running perfect.

Thanks all of you for info and tips, now I am going to root this thing
EDIT:Rooted succesfully

HELP ?
I just flashed Andromadus Mimicry and after choosing options in Aroma installer and flashing gapps i rebooted but after showing HTC logo there is the animation which repeats and phone doesn't boot into OS. Help please, I have deleted cache before flashing ROM.

stevyhacker said:
I just flashed Andromadus Mimicry and after choosing options in Aroma installer and flashing gapps i rebooted but after showing HTC logo there is the animation which repeats and phone doesn't boot into OS. Help please, I have deleted cache before flashing ROM.
Click to expand...
Click to collapse
If your Radio is .19 and you want to try ICS give the Rom in my sig a try (if your radio is not *.19 like in my sig then that could be the problem with the Andromadus rom as well... )
Edit:
Based on the To-Do list of the Andromadus thread : "Add EdKeys' RIL/lib matcher for .19 radio" which was struck out as done, I'm going to assume that you perhaps do not have the 'new' .19 radio flashed and as a result are unable to start that Rom, much like how EliteMod was giving me the same issue until I upgraded my radio.

How to know which my radio is ?

stevyhacker said:
How to know which my radio is ?
Click to expand...
Click to collapse
Would show on the HBoot screen (i.e.: the screen with the 3 androids on the skateboard at the bottom).
If you've never updated yours, you're probably still on the old .26_M radio.
(Power + Down Volume should get you into the bootloader screen to get that info)
EDIT: If you do need to upgrade the radio, click on the radio link in my sig for the thread involving the update. If you've got an unlocked boot loader (i.e.: True S-OFF) you can actually upgrade the radio via the recovery using the zip file from that thread.

You are right my radio is .26_M
EDIT: How to get into recovery directly without HBOOT ?

stevyhacker said:
You are right my radio is .26_M
EDIT: How to get into recovery directly without HBOOT ?
Click to expand...
Click to collapse
I have that same radio and I never had those problems. Did you do a full wipe and are your partitions ext4? It could have something to do with those things.

Mirko935 said:
I have that same radio and I never had those problems. Did you do a full wipe and are your partitions ext4? It could have something to do with those things.
Click to expand...
Click to collapse
You using an ICS rom as well? Both the ones he mentioned and one I mentioned are made for the "new" radio. If you're not using the exact same rom (ICS specifically) then it's not really a relevant statement.
I can't speak for the Adromadus ROM, but The EliteMod one worked just fine with either EXT3 or EXT4 partitions (I later converted system/data/etc over to ext4)
(It's one of the many reasons why having your current phone/rom/etc in the signature is useful).
---------- Post added at 10:50 AM ---------- Previous post was at 10:49 AM ----------
stevyhacker said:
You are right my radio is .26_M
EDIT: How to get into recovery directly without HBOOT ?
Click to expand...
Click to collapse
Without HBoot? I actually never tried it via the buttons, but via HBoot you would just volume down to 'recovery' then hit the power button, but I've always either 'rebooted into recovery' from the power menu, or I waited til my device was showing in ADB and typed adb reboot recovery in the console.

I've solved the problem First time I just deleted cache partition but didn't wipe data and that's where the problem was. If it was an AOSP ROM that wouldn't cause this mess but I had downgraded stock froyo before flashing andromadus.
Thank you once more for helping me to get the ICS godness to my phone

kbeezie said:
You using an ICS rom as well? Both the ones he mentioned and one I mentioned are made for the "new" radio. If you're not using the exact same rom (ICS specifically) then it's not really a relevant statement.
I can't speak for the Adromadus ROM, but The EliteMod one worked just fine with either EXT3 or EXT4 partitions (I later converted system/data/etc over to ext4)
(It's one of the many reasons why having your current phone/rom/etc in the signature is useful).
---------- Post added at 10:50 AM ---------- Previous post was at 10:49 AM ----------
Without HBoot? I actually never tried it via the buttons, but via HBoot you would just volume down to 'recovery' then hit the power button, but I've always either 'rebooted into recovery' from the power menu, or I waited til my device was showing in ADB and typed adb reboot recovery in the console.
Click to expand...
Click to collapse
I wrote in my first post in this topic that I'm using Mimicry, but you're right, I will make a signature asap. Other than that, I used CM9 betas by jerl92 and Ice Cream Sensewich of ICS ROMs, and they all worked fine with that radio. I see that he only mentioned that he wiped cache, that's why I think it could be related to wiping.

Mirko935 said:
I wrote in my first post in this topic that I'm using Mimicry, but you're right, I will make a signature asap. Other than that, I used CM9 betas by jerl92 and Ice Cream Sensewich of ICS ROMs, and they all worked fine with that radio. I see that he only mentioned that he wiped cache, that's why I think it could be related to wiping.
Click to expand...
Click to collapse
I was using CM9 Beta13 before moving to EliteMod, and I was on the old Radio with CM9b13, I didn't need to upgrade to .19 until it came to EliteMod which seemed to be configured for the new radio, hence why I thought of that.
(If nothing else the process for upgrading the radio will certainly wipe most of that other stuff, but yes generally with a brand new rom you want to wipe everything including the system, data, sd-ext, cache, dalvik, etc).

So you have a bootloop? (The boot animation keeps repeating?)
I assume you are on Clockwork Mod Recovery or 4EXT Recovery? First you want to make sure you didn't get a bad ROM download, check the MD5 checksum of the file if you can. Then you want to wipe using the "superwipe+EXT4" zip that is floating around here. (Someone please link it!) Then try flashing it again.
Don't worry about the radio right now, you can update it after you get the rom to boot. Let me know if it works.

[ROM] JB 4.1.2 -Slim Bean GSM Re-Boots from Original

Original thread port thread here:
http://forum.xda-developers.com/showthread.php?t=2446166
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
SlimBean PrimoU HTC One V
Now with added SlimKat goodness
ScreenShots below:
Downloads:
SlimReboot-20140212.zip - 150.05 MB <- mega.co.nz
SlimReboot-201402120.zip - 150.05 MB <- Dev Host
Please note there is no GAPPs to download, so download your Google Apps from the PlayStore or other sources. Flashing GAPPS will mean overwriting Slim & customised GAPPs already incorporated and will probably cause you problems.
Installation Guide(Step by step)
Install ADB and Fastboot tools
sudo apt-get install Android-tools-adb apt-get install Android-tools-fastboot
Download and push SlimRom-20140202-PrimoU.zip file to root of your SD card
Reboot phone into recovery adb reboot recovery
Do a backup(Highly Recommended)
Install ROM(Do factory reset or full wipe before install)
If you're S-OFF Reboot your almost done.
If your S-On Reboot into bootloader adb reboot bootloader
Plug phone to PC(Make sure you have installed fastboot drivers!!!)
Push boot.img (in zip) to place where you have fastboot drivers
Flash the boot.img using fastboot fastboot flash boot boot.img
S-OFF: The boot.img is in the zip, and already flashed :victory:
Reboot to system and enjoy flashed ROM!
Reboot again and let the ROM settle.... This Rom has a long boot time, don't be concerned if it takes 5 minutes the first time.
Features:
Phone.apk added (Thanks for pointing this rookie error guys!)
Holo HD v2.1.1 or Nova Launcher 2.3
Latest play store added
Change in Dexorpt flags and other build.conf tweaks
UI is adjusted closer to AOSP and dark
Unused and extinct libraries and bloat removed
Added sysnotify
Added ES-Explorer & Catlog
Host file updated with latest add blocks etc - http://forum.xda-developers.com/show....php?t=1916098
Added Google 5 black keyboard, and JB4.1.2 Lightweight Black Keyboard (love it, props @Shaftamlee
Calendar Camera, Gallery, Mail, all updated to 4.4.2
4.4.2 Quick Office added
Working:
Everything so far in the SlimRebootv10 version
Bugs:
No One Time Initialising on my phone, you can just add the accounts after boot
Please let me know...
Change Log
20140212: Changed MMS apk
20140210: Rebuilt from LLoirs orginal source
20140208:Fixed Dialer issues
20140207: Added Nova Launcher, and New lightweight Keyboard, fixed sync and torch issues.
20140204: Updated Mail, sync adaptors, camera, gallery, calendar and others to 4.2.2 SlimKat Sources. Added QuickOffice to allow reading of work stuff ! (I've left the old dl link as I think the 4.4.2 apks may reduce stability, will test for the rest of the week)
20140202: Added Adreno drivers and updated UI within a variety of apks
20140130:Change log starts
Contributors Mcgi5sr2, Curtis1973, Lloir
ROM OS Version: 4.1.2 Jelly Bean
ROM Kernel: Linux 3.0.x
ROM Firmware Required: Unlocked Bootloader, Custom recovery(TWRP or CWM)
Based On: SlimBean 3.15
Version Information
Status: Stable
Current Stable Version: 20140212
Created 2014-01-25
Last Updated 2014-02-12
What next:/ Opitimisation, ODEX, incorporation of CM Performance X.
​
This has been learning exercise for me, and I am currently working on a more complete reboot of the the original PrimoU version to see if I can squeeze more speed out of the phone, while keeping it stable.
Forgot to add that I recommend using this to help keep the phone snappy:
http://forum.xda-developers.com/showthread.php?t=2360670
and this ODEXing tool http://forum.xda-developers.com/showthread.php?t=2390162 I ODEXed -all and noticed a significant improvement
Also if you have nay GPS issues still this thread super useful http://forum.xda-developers.com/showthread.php?p=11342772
Massive thanks to @Shaftamle @Lloir @Ticklefish @Curtis1973 @zsoltz @maxwen and also the wider XDA community for it tolerance of newbs
​

First, congratulation for your new ROM!
Second, UI changed closer to AOSP? So, some screenshot would be great.

Ringford said:
First, congratulation for your new ROM!
Second, UI changed closer to AOSP? So, some screenshot would be great.
Click to expand...
Click to collapse
I want screens too. I'm not going to install sth like CMSense crashes on welcome.

Minto107 said:
I want screens too. I'm not going to install sth like CMSense crashes on welcome.
Click to expand...
Click to collapse
Rom install and loaded perfectly!!
screens here - http://forum.xda-developers.com/showthread.php?t=2335776

Is it different in terms of performance? Stability?
Please give a review coz i m out for now and dont have stable net connection to download..
Thanx in advance
Sent from my HTC One V using xda app-developers app

yashkothari911 said:
Is it different in terms of performance? Stability?
Please give a review coz i m out for now and dont have stable net connection to download..
Thanx in advance
Sent from my HTC One V using xda app-developers app
Click to expand...
Click to collapse
well I find it 100% stable and with the added performance mod I have on average 100 MB free RAM. I am yet to experience and FCing, but if anyone has any problems please let me know. Like I said I am going to use this to find my way around roms, before starting on a newer version of Android.
Thanks for the screenshots @ihor2284, and Minto107 the closer to AOSP look comes from editing the images in .apk s in this version. I am currently working on changing a few of these back to CM or AOSP source packages, chosen mostly on size. The aim is to be functional and with a small footprint.

About the only thing you will find that tends to freeze up and force close is the stock browser..happens with many of our roms. ive been trying to decompile the rom and bookmarks sync adapter to allow moving to the data partition vs system and see if i can optimize it more but i keep getting decompile errors.

Curtis1973 said:
About the only thing you will find that tends to freeze up and force close is the stock browser..happens with many of our roms. ive been trying to decompile the rom and bookmarks sync adapter to allow moving to the data partition vs system and see if i can optimize it more but i keep getting decompile errors.
Click to expand...
Click to collapse
Hi Curtis,
what are you using to decopile, I'm running linux on everything and can't get my hands on an easy tool. Going to look into apktool and aapt and see if I can use them without any gui...
Any advice on this would be great, as so far I can only edit the .pngs, even the .9.pngs are beyond my short reach!
regards

im using apktool..in fact ive used about every tool around for windows with no luck.
edit: oh and the force close usually experienced with the browser is due to ram issues..bot anything else. the app works as it is supposed to..just uses more ram than our device can handle at times depending upon web site use. i think my decompile errors are largely due to my pc set up. to lazy to leave xp behind lol..

Hey @mcgi5sr2 sorry i never replied to your pm i've been afkish lately. do you still need help or?

Lloir said:
Hey @mcgi5sr2 sorry i never replied to your pm i've been afkish lately. do you still need help or?
Click to expand...
Click to collapse
Hi Lloir,
no problems, sometimes its better if you learn the longer and harder way . I think I've pretty much finished with this version, but may ask for some tips if I move into building it or a 4.2 from source. Thanks again for the original, totally awesome.

Very nice! Well done!

flashlight does not work, camera dont work also good, quality of speaker is terrible :/

Ganjax said:
flashlight does not work, camera dont work also good, quality of speaker is terrible :/
Click to expand...
Click to collapse
Hi sorry to hear you at having difficulty with this. I've just tested what you said, not been able to repeat the issues on my phone. Could you take a log cat,(the app is on the phone already) Also it eouldnhelp to knownwhat other appsnyou may have been running, like turbo boost etc, and what spec your phone hboot drivers erc are at if you can provide. I do have another faster and lighter version which i will upload tomorrow.

This ROM looks really promising. Nice work!
However I can confirm that the camera and the torch (LED flashlight) do not work. Besides battery drains too fast I guess. It has been discharged completely during the night when doing nothing. No, I have no problems with the battery on other ROMs.
And sorry for not providing any logs either, I'm just not so experienced enough.
Sent from my One V using xda app-developers app

kvestas said:
This ROM looks really promising. Nice work!
However I can confirm that the camera and the torch (LED flashlight) do not work. Besides battery drains too fast I guess. It has been discharged completely during the night when doing nothing. No, I have no problems with the battery on other ROMs.
And sorry for not providing any logs either, I'm just not so experienced enough.
Sent from my One V using xda app-developers app
Click to expand...
Click to collapse
Thanks for the feedback, I think I've sorted all of this out, the ROM still needs a reboot after initial installation, but everything seems pretty gravy from there on in!

mcgi5sr2 said:
Thanks for the feedback, I think I've sorted all of this out, the ROM still needs a reboot after initial installation, but everything seems pretty gravy from there on in!
Click to expand...
Click to collapse
Battery usage looks fine now, sorry for my quick reaction. However the camera is still unstable. I was already surprised when took the first picture, but the camera stopped responding during the second shot. So I guess it still needs improvements. Thank you.
Sent from my One V using xda app-developers app

I see you used my installation guide. That's good you mustn't delete that. And question any other bugs than that 2. If yes that great. I'm looking for something stable and smooth so your port will be great for that?
Wysłane z mojego HTC One V przy użyciu Tapatalka

Minto107 said:
I see you used my installation guide. That's good you mustn't delete that. And question any other bugs than that 2. If yes that great. I'm looking for something stable and smooth so your port will be great for that?
Wysłane z mojego HTC One V przy użyciu Tapatalka
Click to expand...
Click to collapse
Hi Min to,
Thanks for then installation guide, saved me writing out a much less coherent one. Only bus was the camera, with the new adreno drivers this has been smoothed out. I've also now cleaned up the contacts and phone.apk and added holohd2.1.2 for a smoother run. If you odex the romnusing the link in 1st post it is super smooth. But do let me know if you find any problems.
I'll get some more testing done on the camera as well, and should have the update out byntomorrow

kvestas said:
Battery usage looks fine now, sorry for my quick reaction. However the camera is still unstable. I was already surprised when took the first picture, but the camera stopped responding during the second shot. So I guess it still needs improvements. Thank you.
Sent from my One V using xda app-developers app
Click to expand...
Click to collapse
Hi @kvestas,
the new update should improve the rom some more, your right about the camera, and I will be looking into that some more of the next week or so. Let me know if the new drivers etc are any help with it. Thanks again for the feedback.
regards