Sorry Villain rom is down at the moment if you are having trouble getting the wonderful FROYD 1.2.1 here are some links
http://villainrom.jeremygohblog.com/...ase-signed.zip
and
http://villainrom.desean.net/release...ase-signed.zip
These are both for Froyd 1.2.1
OTA Update: FroydVillain 1.2.2 "GPS really needs a kick in the nuts"
VillainROM Updater app finally makes a return to the FroydVillain platform.
New in this update:
•Framework fixes for the GPSLocatorService that fix an issue causing a hang/crash when GPS was obtaining initial fix and location update.
•CPUSpeed no longer supports a screen off profile. See below for details.
•Updated lib_htcril.so to improve GSM switching, -should- also fix the people experiencing GPS+GSM not working.
•Kernel updated to fix some regression bugs in the USB stack, ARM code issues and to prevent the camera app clogging the IO bus.
•All the different OC kernels are now in the OTA app, just enable experimental updates to see them.
This OTA update clears the dalvik cache, as there are updates to the framework, so naturally your phone will take longer to boot.
We no longer support the use of a screen off profile with the interactive governor. It's really not needed. While it may make some difference to battery longevity, the benefits far outweigh the downsides. We're talking -maximum- a loss of an hour, over using a screen off profile. However you get the added benefits of:
Being able to use anything with the screen off without losing performance. For example phone calls, listening to music, etc.
Time for a brave new world of thinking, folks. Get used to the idea that it's better for the governor to accomplish a task as quickly as possible, then clock back down.
The other switch in thinking, is this. It's time we stop trying to work around whatever bull**** problem that apps on the market introduce by being buggy, crap or poorly designed. If we find there's an app or a widget that runs your phone at top clock all night, well, start giving the developer ****. We're no longer going to try and work around issues introduced into the OS by bad applications. Developers need to start taking more responsibility or face people not using their apps anymore.
Screen off profiles are a nasty workaround for this problem and it's going to go away, at least in FroydVillain. Your phone's performance should not be at the mercy of whether the screen is on or not. Having many frequencies in the table is a false economy because, and especially with the
EXTRA
For any other details
IF ANY BODY NEED ACCESS TO THIS XDA ACCOUNT TO EDIT
i.e
pulser
ninpo
lenny
email for account details
[email protected]
[email protected]
neither links work....anyone got ANOTHER link we could use?
thanks
Mike, your links is borked:
Use this link instead: http://tinyurl.com/3a6r9u5
thanks for the links
hey jeremy
nice to see someone else from the Elf forums over here
Whoops.... hopefully one of team villain can log in and change top post
Sent from my HTC Desire using Tapatalk
Still down hopefully mcduck will get it sorted soon
anyone that haves the links of the kernels? i need a nice kernel, but can't find a link anywhere
Great work... I was doing fine until I tried one of the kernels... First boot should take longer... but how much longer? Mine's been on the VillainRom Loading screen for maybe 30 mins...
Cheers for the work...
Tom
tom3668 said:
Great work... I was doing fine until I tried one of the kernels... First boot should take longer... but how much longer? Mine's been on the VillainRom Loading screen for maybe 30 mins...
Cheers for the work...
Tom
Click to expand...
Click to collapse
30 mins is too long. Try reboot again, if still failed to boot up. Reflash again.
Sent from my HTC Hero using Tapatalk
Delete this thread
As per OP request, thead buried.
Hi,
I find battery usage a bit high on CM 7(RC1 and nighly).
Batter Montor widget or CurrentWidget shows values from 6-12 mAh.
With same radio i have 3-5 mA when using default HTC Sense ROM.
I did full wipe factory reset, dalvik, cache etc..
I need some tips how to diagnose the problem and eventually file a bug report.
I am using lates radio 32.54.00.32U_5.14.05.17, but the problem is the same with older one 32.49.00.32U_5.11.05.27
I don't think the problem is with the radio itself, because it will be problematic with all ROMs (?)
You do realise that you can post in the CM7 thread. You also realise that RC and nightly builds arn't stable releases?
You also realise that RC and nightly builds arn't stable releases?
Click to expand...
Click to collapse
ofc i know that . I also know that if it is a bug, someone will have to report it. That's the goal of RC after all . May be you should read the whole post after all.
I seem to be having a similar experience with oxygen rom so would be interested in investigating what is causing this. Tried looking at all the usual stuff in QSI to weed out programs that may be causing this problem but nothing jumps out at me. Plus, i'm having the problem with completely clean rom without any apps installed.
j0r01 said:
ofc i know that . I also know that if it is a bug, someone will have to report it. That's the goal of RC after all . May be you should read the whole post after all.
Click to expand...
Click to collapse
Don't think that sort of response if going to help your cause tbh
I also know that if it is a bug, someone will have to report it. That's the goal of RC after all . May be you should read the whole post after all.
p5x said:
I seem to be having a similar experience with oxygen rom so would be interested in investigating what is causing this. Tried looking at all the usual stuff in QSI to weed out programs that may be causing this problem but nothing jumps out at me. Plus, i'm having the problem with completely clean rom without any apps installed.
Don't think that sort of response if going to help your cause tbh
Click to expand...
Click to collapse
same here. battery just runs dry very fast! (after playing a song on youtube, battery goes down for about 6%)
Try a different kernel. I recommend ManU kernel (the CFS-HAVS-AXI-version).
Same comments in spanish forum:
http://www.htcmania.com/showthread.php?t=303281&page=21#402
This guy is recommending aEVViollet (..35) kernell.
I'm thinking about changing into Oxygen.
Best regards
It is getting better, isn't it?
Hi everyone,
I just recently rooted, and flashed CM 7.0.3 to my Telus Desire HD (signature has phone details), and after the first day noticed SIGNIFICANT battery drain; overnight on Standby it would drain 50-70%!
I installed the Current Widget and it showed throughout most of the night it would average 140-360mA of drain! Checked the Battery Info, and it showed ADWLauncher to be the highest source of drain, along with Sensors.
I'm just re-conditioning the battery now, but this has gotten me concerned. The phone is brand-new, along with the battery.
ADWLauncher is key to the ROM, so can't really disable it. I wiped Dalvik, Cache, User, before and after installing CM, so not sure what else I can do...
I didn't want to install any ROM that has HTC Sense components because their app permissions give me goose bumps (Sense UI = asking to be hacked), so that's why I went with CM. Also used it on a Moto Milestone, and it ran beautifully on that phone.
Can anyone help please? I'm at my wits end
I am unable to directly solve your problem, but I have some thoughts that could potentially solve this problem.
Firstly, what is the state of your ADW desktop at the moment? Try clearing all but the Current widget and see what happens. Another thing to try is disabling all of the 3D effects and such in the menu.
On a final note, ADW is not a core part of cyanogen-mod, you can just install Go Launcher, for example, and it will completely replace ADW. That is another thing to try.
Let us know how you get on.
I'd suggest installing a very lite launcher from market..even lighter than Go Launcher or Launcher Pro, setting it as default and uninstalling AWD with Root Uninstaller.
However, that's the not-curious way of dealing with the problem. AWD should not be consuming that much in CM. I remember Kalabdan had done a great job on the Milestone. Try to find out if your AWD can be upgraded. If all else fails try out the CM RC1 which has been out for a while.
I'd recommend wiping data+cache and formatting the system partition before flashing a rom.
KrisDouglas said:
I am unable to directly solve your problem, but I have some thoughts that could potentially solve this problem.
Firstly, what is the state of your ADW desktop at the moment? Try clearing all but the Current widget and see what happens. Another thing to try is disabling all of the 3D effects and such in the menu.
On a final note, ADW is not a core part of cyanogen-mod, you can just install Go Launcher, for example, and it will completely replace ADW. That is another thing to try.
Let us know how you get on.
Click to expand...
Click to collapse
So far I just finished fully re-conditioning the battery, and have wiped the batterystats.conf file via ClockworkMod Recovery, and also wiped out the cache just to let it re-build just in case.
I checked out reviews on Go Launcher for Desire HD users, and a lot of people report seeing a higher battery drain with that one, than others like ADW. I think I'll wait to see how it behaves after re-conditioning first, and see if there is any improvement. If that fails, I'll give Go Launcher a try.
Do you think I should install one of the new CM7.1.0 nightly builds to see if it helps? I've read a lot of forum postings claiming to see marked improvement in performance and battery life after upgrading to it...
Cheers!
Well, after doing everything in my last post, battery life has improved, but it's still draining faster than what I think it should be...
I've attached my currentwidget.log file to this post so you can see for yourself the drain I'm experiencing.
hi, just wondering if there are any roms available that are completely stable and finished for this phone?
if not, (as i have not found any), is the original stock rom (rojers) available to download anymore?
thanks guys..
jmpcrx said:
hi, just wondering if there are any roms available that are completely stable and finished for this phone?
if not, (as i have not found any), is the original stock rom (rojers) available to download anymore?
thanks guys..
Click to expand...
Click to collapse
After reading a lot, I believe I can confirm that only GB, and stock ICS are stable, as with no issues, some little glitches but no deal breakers. As for Rogers, there's only Osimod GB ROM based of Rogers. The rest are based of UCLJ3
lasuazo said:
After reading a lot, I believe I can confirm that only GB, and stock ICS are stable, as with no issues, some little glitches but no deal breakers. As for Rogers, there's only Osimod GB ROM based of Rogers. The rest are based of UCLJ3
Click to expand...
Click to collapse
ok thanks lasuazo ;--)
I guess omni and cm11
jmpcrx said:
hi, just wondering if there are any roms available that are completely stable and finished for this phone?
if not, (as i have not found any), is the original stock rom (rojers) available to download anymore?
thanks guys..
Click to expand...
Click to collapse
I may be off base here but I guess the [4.4] cyanogenmod 11 and omni ROM are pretty much stable ...
Though the pretty much is still a while away from complete the following are the general bugs with bubor's amazing Roms:
There is an audio bug when making VoIP calls which gives audio latency ..
There is fixed camera rotation which means all the pictures are in landscape
There is no Wi-Fi direct
Google experience launcher is not that Good looking (I know I am complaining)
Google maps 7 has issues but can be dual loaded with maps 6 so they work
Backlight,PPI, lag all have fixes though
Battery drain is a bit more
But as far as performance goes... They are pretty smooth..
So I guess make your choice
thefusor said:
I may be off base here but I guess the [4.4] cyanogenmod 11 and omni ROM are pretty much stable ...
Though the pretty much is still a while away from complete the following are the general bugs with bubor's amazing Roms:
There is an audio bug when making VoIP calls which gives audio latency ..
There is fixed camera rotation which means all the pictures are in landscape
There is no Wi-Fi direct
Google experience launcher is not that Good looking (I know I am complaining)
Google maps 7 has issues but can be dual loaded with maps 6 so they work
Backlight,PPI, lag all have fixes though
Battery drain is a bit more
But as far as performance goes... They are pretty smooth..
So I guess make your choice
Click to expand...
Click to collapse
i wish i could agree with you.. im running kitkat crdroid, and like every rom i have flashed over the years, has plenty of bugs that make it very annoying as a daily rom. phone switching off twice a day, icons/widgets dissapearing after rebooting, becomes laggy after a week or so of usig the rom, laggy browsing on all browsers, trebucket crashing regurly etc etc, thats on top of the bugs you list.. the only roms that are stable are completely finished official cm or miui roms (which there are none for this fone..). the stock rom is the only one that has not given me trouble. with the greatest respect to those that put their time i to make these roms, im sure people who flash them make them out to be more stable than they really are unfortunatelly.
Maybe we have developer aura or something like that? I'm sure I just used 4.4 PAC ROM for a week without reboot or any crashes. Bluetooth, fixed camera rotation and VoIP - yes, these are issues we can't fix, the same is with google maps v.7 (we just have no hardware NEON support that uses v.7 of maps). There is also issue with wi-fi: if you turn it off, it sometimes don't turns on until reboot. As for myself, I just never turn it off.
Besides of these issues, everything is smooth and stable. Really is. But I got sometimes trebuchet crashes - this was a time when I flashed dirty and didn't make a factory reset - the new trebuchet version sometimes conflicts with the data from old version. I just went to Settings - Apps, found Trebuchet (or Launcher3 if old version) and tapped Erase Data. And the issue was gone! But I recommend to always make a factory reset with new ROM. That's really important.
And even if you have those constant trebuchet bugs whatever you do (icons disappearing is also a trebuchet bug, I never encountered it though), just install a different launcher. Google now launcher is the basic, and is like trebuchet in many ways, miui one is also good, and others, they are many!
I had problems with some icons disappearing when the system reboots. I found that the icons that disappeared were for applications which were installed on the SD card. When I moved them to the system, they stopped disappearing.
Makshow said:
Maybe we have developer aura or something like that? I'm sure I just used 4.4 PAC ROM for a week without reboot or any crashes. Bluetooth, fixed camera rotation and VoIP - yes, these are issues we can't fix, the same is with google maps v.7 (we just have no hardware NEON support that uses v.7 of maps). There is also issue with wi-fi: if you turn it off, it sometimes don't turns on until reboot. As for myself, I just never turn it off.
Besides of these issues, everything is smooth and stable. Really is. But I got sometimes trebuchet crashes - this was a time when I flashed dirty and didn't make a factory reset - the new trebuchet version sometimes conflicts with the data from old version. I just went to Settings - Apps, found Trebuchet (or Launcher3 if old version) and tapped Erase Data. And the issue was gone! But I recommend to always make a factory reset with new ROM. That's really important.
And even if you have those constant trebuchet bugs whatever you do (icons disappearing is also a trebuchet bug, I never encountered it though), just install a different launcher. Google now launcher is the basic, and is like trebuchet in many ways, miui one is also good, and others, they are many!
Click to expand...
Click to collapse
like i said in my first post, i do really appriciate the fact that people spend Alot of time cooking theese roms, and it easy for me to come along and moan about them, but i have found over the years that after using a custom rom for a couple of weeks or so, its like the ram seems to gradually get eaten away, the device gradually slows down, becomes laggy and ultimately unuseable (not just this fone, and not just me that says this). im not saying all are like this, just many i have used, mainly because they never get finished.
i am very open though to people suggesting that i am doing something wrong, and maybe you have picked up on that something.. you say you do a factory reset, can i ask, do you mean a factory reset in the fone settings, or are you referring to a full wipe using cwm/twrp? as when i flash, i wipe everything accept what i dont want wiped on the external sd.. i dont factory reset, is this after you have flashed the new rom? or before you flash a new rom?
also thank you for the erase data tip for trebucket, i will try that.. i have not used the google now launcher yet, but i tried using miui launcher but when i went back to trebucket the lockscreen stayed as the miui lockscreen, which has happened on past cm roms, so i just deleted it.
just gets a bit frustrating when you spend hours getting everything working/setting up personalisation, then the phone just seems to start getting worse day by day, but maybe like you say, its cos i "dirty flashed"?
linuxguy42 said:
I had problems with some icons disappearing when the system reboots. I found that the icons that disappeared were for applications which were installed on the SD card. When I moved them to the system, they stopped disappearing.
Click to expand...
Click to collapse
i did think that, and im sure you are right, but i have had every app/folder/widget dissappear twice now, then, randomly over several restarts, some widgets/apps will replace themselves over the top of the new ones i have just newly placed there.. strange, but i have came across this before on cm roms, so im sure there is a bug there somewhere, even if it is not too common..
jmpcrx said:
you say you do a factory reset, can i ask, do you mean a factory reset in the fone settings, or are you referring to a full wipe using cwm/twrp? as when i flash, i wipe everything accept what i dont want wiped on the external sd.. i dont factory reset, is this after you have flashed the new rom? or before you flash a new rom?
Click to expand...
Click to collapse
Yes, what you do should suffice. I meant cwm/twrp wipe (boot, system, data, cache, android.secure). SD card is not touched. So you are doing fine with that, but anyway, there has to be something make those issues... Can you look at /system/addon.d folder? There is stored info about files that will be preserved even if you install a new ROM with a wipe. If there are many leftovers from ROMs or programs you tried earlier, then you should try to manually clear this folder before new ROM install.
the device gradually slows down, becomes laggy and ultimately unuseable
Click to expand...
Click to collapse
That was the point with pre-4.2 ROMs, and even with 4.2 there was a bug with gallery thumbnails which made it to eat gigabyte and more of storage after some time. That was fixed in CM 10.1.3. Also a Lite-Kernel used by earlier ROMs is very great, but has its issues, for example, systemui crashes when camera launch after some phone use and sleep of death.
I used CM 10.1.3 for a a three months and still keeping a backup of it for a some case. There was no slowing or lagging, it was almost perfect (if you don't use VoIP or BT handset) even after those months of use. Strangely, but I didn't have even "settings -> about crash" issue bubor listed!
Welll here are some tip which have helped me
jmpcrx said:
i wish i could agree with you.. im running kitkat crdroid, and like every rom i have flashed over the years, has plenty of bugs that make it very annoying as a daily rom. phone switching off twice a day, icons/widgets dissapearing after rebooting, becomes laggy after a week or so of usig the rom, laggy browsing on all browsers, trebucket crashing regurly etc etc, thats on top of the bugs you list.. the only roms that are stable are completely finished official cm or miui roms (which there are none for this fone..). the stock rom is the only one that has not given me trouble. with the greatest respect to those that put their time i to make these roms, im sure people who flash them make them out to be more stable than they really are unfortunatelly.
Click to expand...
Click to collapse
i .. umm.. well i agree that as of now they have issues but they will get better .. ours is an old device... so i guess we should tread slowly . which is exactly what the developers are doing .. .
and i agree on the ram hungry part but there are ways for that too . .
funny i have been messaging people to help me post this stuff through them . . but well thats the prob with being a junior member .
My personal tested suggestions for omni rom which have really incremented to the performace some of which are :
- using one of the lightest launchers as i find trebuchet and even google launcher RAM hungry is 'Lightning Launcher' the bloody app itself is in BYTES!!
-also i use link2sd with ext4 that helps in storage and also use sd maid for regular clean up.
-also i have been testing memory swapping using linux swap partition on sd card (class 10 ) and yeah i know it degrades sd card but oh well like Glados testing testing testing
-i have also switch off startup at boot for certain apps
and i apologize for posting what maybe well known tricks or improvs but i really dont know where else to post these (still have the ten post ban from posting )
and if these dont help then sorry to waste your time . .
PS anyone think an F2FS file system like for the nexus7 would\might help ?
tl;dr use the given tips maybe they might help . . and with custom roms i guess you have to spend time to keep them running well .
Makshow said:
Yes, what you do should suffice. I meant cwm/twrp wipe (boot, system, data, cache, android.secure). SD card is not touched. So you are doing fine with that, but anyway, there has to be something make those issues... Can you look at /system/addon.d folder? There is stored info about files that will be preserved even if you install a new ROM with a wipe. If there are many leftovers from ROMs or programs you tried earlier, then you should try to manually clear this folder before new ROM install.
That was the point with pre-4.2 ROMs, and even with 4.2 there was a bug with gallery thumbnails which made it to eat gigabyte and more of storage after some time. That was fixed in CM 10.1.3. Also a Lite-Kernel used by earlier ROMs is very great, but has its issues, for example, systemui crashes when camera launch after some phone use and sleep of death.
I used CM 10.1.3 for a a three months and still keeping a backup of it for a some case. There was no slowing or lagging, it was almost perfect (if you don't use VoIP or BT handset) even after those months of use. Strangely, but I didn't have even "settings -> about crash" issue bubor listed!
Click to expand...
Click to collapse
ok thanks, i cleared the data in trebucket, and started again with placing apps/widgets on home screen, and i also have deleted the hacked version of adobe flash that you install with dolphin browser, and, supprisingly after a couple of days of testing, my apps/widgets are not deleting themselves, the phone is significantly less laggy, and i have had no switch offs, so, im very pleased with that! so id suggest against downloading that version of flash player with this rom..
thefusor said:
i .. umm.. well i agree that as of now they have issues but they will get better .. ours is an old device... so i guess we should tread slowly . which is exactly what the developers are doing .. .
and i agree on the ram hungry part but there are ways for that too . .
funny i have been messaging people to help me post this stuff through them . . but well thats the prob with being a junior member .
My personal tested suggestions for omni rom which have really incremented to the performace some of which are :
- using one of the lightest launchers as i find trebuchet and even google launcher RAM hungry is 'Lightning Launcher' the bloody app itself is in BYTES!!
-also i use link2sd with ext4 that helps in storage and also use sd maid for regular clean up.
-also i have been testing memory swapping using linux swap partition on sd card (class 10 ) and yeah i know it degrades sd card but oh well like Glados testing testing testing
-i have also switch off startup at boot for certain apps
and i apologize for posting what maybe well known tricks or improvs but i really dont know where else to post these (still have the ten post ban from posting )
and if these dont help then sorry to waste your time . .
PS anyone think an F2FS file system like for the nexus7 would\might help ?
tl;dr use the given tips maybe they might help . . and with custom roms i guess you have to spend time to keep them running well .
Click to expand...
Click to collapse
some good tips there, thankyou, i havent tried any of them yet, but i will have a go at some of them and see what happens.. thanks thfusor..
jmpcrx said:
hi, just wondering if there are any roms available that are completely stable and finished for this phone?
if not, (as i have not found any), is the original stock rom (rojers) available to download anymore?
thanks guys..
Click to expand...
Click to collapse
For what it's worth, I recently had to reflash and decided to use dman325's stock UCLJ3. (He has two versions, stock and one with the aosp lockscreen. If you decide to use either, use the stock one. dman325 had to resign the aosp one with a test signing key that, recently, got invalidated or declined and it prevents Google Play from updating past 3.7.15 and Google Play Services wont install at all because of a shared_uid fault due to certificate conflict, etc.)
I got frustrated with the amount of bloat in an otherwise vendor fun-packed rom, so I went in and hacked out lots of crap. Largely relying on either "what is safe to get rid of" lists for similar samsung phones and my own poking around/guestimation using dex2jar and jd-gui. I really, honestly don't understand what InputEventApp.apk was meant to do. Seriously. But, getting rid of it reduced the logcat spam tremendously. Also, the wsslcm* apks are somewhat frightening in appearance.
I've gone a few steps further, I modified android.policy.jar smali to prevent the emergency dial option from showing up on the lock screen - I accidentally pocket dialed 911 a year ago and am not about to do that again. I also modified the kernel ramdisk image to set ro.debuggable=1 and ro.secure=0. I tried, while I was at it, to replace /dev/random with /dev/urandom, but I'll have to do some experimenting.
I've added a few static binaries for proper gnu utilities. bash, ls, grep, sort, du, etc. It surprises me that a functional shell environment doesn't get more attention on phones with keyboards.
So, that's my $0.02. Try the stock UCLJ3 and fiddle with it a bit. Good luck.
etherfish said:
For what it's worth, I recently had to reflash and decided to use dman325's stock UCLJ3. (He has two versions, stock and one with the aosp lockscreen. If you decide to use either, use the stock one. dman325 had to resign the aosp one with a test signing key that, recently, got invalidated or declined and it prevents Google Play from updating past 3.7.15 and Google Play Services wont install at all because of a shared_uid fault due to certificate conflict, etc.)
I got frustrated with the amount of bloat in an otherwise vendor fun-packed rom, so I went in and hacked out lots of crap. Largely relying on either "what is safe to get rid of" lists for similar samsung phones and my own poking around/guestimation using dex2jar and jd-gui. I really, honestly don't understand what InputEventApp.apk was meant to do. Seriously. But, getting rid of it reduced the logcat spam tremendously. Also, the wsslcm* apks are somewhat frightening in appearance.
I've gone a few steps further, I modified android.policy.jar smali to prevent the emergency dial option from showing up on the lock screen - I accidentally pocket dialed 911 a year ago and am not about to do that again. I also modified the kernel ramdisk image to set ro.debuggable=1 and ro.secure=0. I tried, while I was at it, to replace /dev/random with /dev/urandom, but I'll have to do some experimenting.
I've added a few static binaries for proper gnu utilities. bash, ls, grep, sort, du, etc. It surprises me that a functional shell environment doesn't get more attention on phones with keyboards.
So, that's my $0.02. Try the stock UCLJ3 and fiddle with it a bit. Good luck.
Click to expand...
Click to collapse
thanks etherfish, if i continue to have probs i may well do that, i was thinking about going back to stock. dont think i have the confidence to fiddle like you have though as im more of a windows man than linux, but thanks for the great advice
jmpcrx said:
thanks etherfish, if i continue to have probs i may well do that, i was thinking about going back to stock. dont think i have the confidence to fiddle like you have though as im more of a windows man than linux, but thanks for the great advice
Click to expand...
Click to collapse
Well, you learn by doing, I believe. Also, I have a classy - for a flip phone - Motorola Razr2 v8 kicking around I can always put my SIM into if I've managed to hose my captivate glide. Also, I'm replying because I can't post in the rom development forum until I have 10 posts. Hurray for well founded, but nonetheless arbitrary restrictions. So, a number of things have piqued my curiosity.
So, first of all, this surprised me in the logs:
Code:
I/Launcher( 2263): onCreate(): product model family:U1 product model : GT-I9221
I'd always wondered why I had an SGH-I927 when other phones, like the remarkably similar Galaxy R, are GT-I9103. Is/was GT-I9221 an internal reference?
Also, there are other inconsistencies, for example:
Code:
D/RILJ ( 426): [1718]> REQUEST_GET_NEIGHBORING_CELL_IDS
D/RILJ ( 426): [1718]< REQUEST_GET_NEIGHBORING_CELL_IDS error: com.android.internal.telephony.CommandException: REQUEST_NOT_SUPPORTED
If you jump into the debug/field test menu system, (dial *#*#197328640#*#* ) you can bring up the list of neighboring cells in both GSM and WCDMA modes... So, why is the request marked not supported? Furthermore, why didn't samsung disable the request in the first place if they went to the trouble of disabling it from working. I imagine this has a reason, but I doubt it's a terribly great one.
And the FM receiver? I do believe our broadcom BCM4329 is a bluetooth+wifi_in_an_sdcard (well, SDIO really, but still, not pci-e and not usb.) and has an FM receiver built in, but it's omitted and hidden?
Code:
W/AudioPolicyManager( 112): FM radio recording off
Oh, the conspiracy theories. And then there's the weird lines you discover if you dump the string identifiers from /system/bin/drexe!
For example, these lines are all sequential:
Code:
broadcast -a android.provider.Telephony.SECRET_CODE android_secret_code://767*3855
InvokeOemRequestHookRaw broadcast factorst OK
InvokeOemRequestHookRaw factorst fail %d
/system/.configure.txt
(what's with /system/.configure.txt???)
Do not type 767*3855 into your phone. It's the factory wipe code or possibly part of it. I do believe drexe is the DataRouter you often see spamming the logs with:
Code:
E/DataRouter( 107): usb connection is true
E/DataRouter( 107): DSR is ON. Don't send DTR ON.
And we find these strings in drexe:
Code:
__initialize_usb_ipc
/data/.usb_stream
usb connection is true
InvokeOemRequestHookRaw usbstatus true is success
oh, and:
Code:
pipe failed (%s)
fork failed (%s)
child pid = %d.
execute sh.
system/bin/sh
execl fail %d
What do you think? Why does drexe seem to have code to support and start a shell? Well, if nothing else, thank you for reading.
P.S. I don't suspect anything the least bit conspiracy like, malicious, or devious. I've worked for some huge companies; i don't think it'd be likely.
etherfish said:
Also, I'm replying because I can't post in the rom development forum until I have 10 posts. Hurray for well founded, but nonetheless arbitrary restrictions.
Click to expand...
Click to collapse
Technically, you can post in cappy dev forums started from 3 posts. I saw someone posting there his fourth post.
As for other things you listed... Well, I'll be glad to have an FM receiver in our glide. But I really think that reason for all this staff can be as simply as hands growing from wrong place or restricted development time...
Makshow said:
Technically, you can post in cappy dev forums started from 3 posts. I saw someone posting there his fourth post.
As for other things you listed... Well, I'll be glad to have an FM receiver in our glide. But I really think that reason for all this staff can be as simply as hands growing from wrong place or restricted development time...
Click to expand...
Click to collapse
I recently, after some research, also installed dans stock (i decided to go complete stock since i didnt know what the lock screen thing meant).
I havent had any trouble with being outdated. Only thing i noticed (unless im doing it wrong, im new to this phone) was that screencaps dont work. its power button and volume down, right?
Other things id like to customize are data being in the top drawer instead of bluetooth (since i never use it), and id like to be able to see who texted me on the lock screen, but while still using the stock messaging app, and without an app having to constantly run.
Other than those couple of things its been great!
im HOPING down the road for an un-buggy or at least minimally buggy version of 4.4. well see what happens with that i guess.
Some help
Pawprints1986 said:
I recently, after some research, also installed dans stock (i decided to go complete stock since i didnt know what the lock screen thing meant).
I havent had any trouble with being outdated. Only thing i noticed (unless im doing it wrong, im new to this phone) was that screencaps dont work. its power button and volume down, right?
Other things id like to customize are data being in the top drawer instead of bluetooth (since i never use it), and id like to be able to see who texted me on the lock screen, but while still using the stock messaging app, and without an app having to constantly run.
.
Click to expand...
Click to collapse
well i always say stock is best cause it IS optimized however there are things like keep and total Google integration that i like so i updated to kit kat
for screen caps if they dont work i could maybe suggest an application called super manager its pretty loaded it has screen cap and may even give you prox sense wake up for device.
also customizing the drawer hmm.. i guess you could try xposed framework but please be careful and make a backup before
as for who texts you and the content of the text you could try dash clock its able to do a lot
hello guys I was just wondering if I could get some help since I returned back to fully Ice Cream Sandwich Stock. I completely removed all the system bloat with link2sd, uninstalled all att crap. Can anyone recommend me something since I feel the ram consuption still to high... battery so far is doing kind of good almost as in crdroid
But i believe it can be improved. Any recommended settings or something else i can do? Already tried lite kernel but it gave me some issues. Rather keep stock. Any recommendations please guys. Also if you know a "ok google" like app or something as a swifty assistant would be nice. Please recommend. Thanks in advance
jmpcrx said:
hi, just wondering if there are any roms available that are completely stable and finished for this phone?
if not, (as i have not found any), is the original stock rom (rojers) available to download anymore?
thanks guys..
Click to expand...
Click to collapse
Hi,
well that depends.. on what you mean with "finished"
I have tested all (3 months ago) available ROMs for the Glide. IMO the best available ROM is PACman but as said it depends. I used pac_i927-milestone.1.RC1.4.zip for a long time (months) without having any issues besides Bluetooth Headset which is a general problem in JB and higher version). I have tried other PACMan ROM versions as well but the above one was the best of stability and battery life (in my case).
So it depends what features you really need or are a must-have for you. If you do not have bluetooth headsets I would recommend the above otherwise .. well I would recommend sediROM
Regards
xdajog
---------- Post added at 02:39 PM ---------- Previous post was at 02:33 PM ----------
lasuazo said:
hello guys I was just wondering if I could get some help since I returned back to fully Ice Cream Sandwich Stock.
Click to expand...
Click to collapse
Haven't done that before but would be rooted ICS stock also ok for you?
If so:
--> search for thread ID 1994902 or search for: [ROM] Stock UCLJ3 Rooted, Deodexed, Zipaligned
(sorry not allowed to post links..)
Regards
xdajog
Q&A for [rom] stock p8000
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [rom] stock p8000. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Should the 15th of August ROM update happen through the phones update thing?
I have a data network issue and I'm not sure that update fixes the problem but I just dont want to reflash my phone.
Hi, everyone.
How many P8000 users have flashed recent 0815 stock? Have you noticed any issues?
It is a bit suspicious that Elephone removed the download link to this ROM from Elephone BBS, replaced with Update soon notice.
I guess they fixed the camera, but probably broken something else, so hesitating to flash this one.
taka111san said:
Hi, everyone.
How many P8000 users have flashed recent 0815 stock? Have you noticed any issues?
It is a bit suspicious that Elephone removed the download link to this ROM from Elephone BBS, replaced with Update soon notice.
I guess they fixed the camera, but probably broken something else, so hesitating to flash this one.
Click to expand...
Click to collapse
I have it flashed, the downside seems to be battery now my phone idle has consumed 26% so far total of 12hours
rockycocky said:
I have it flashed, the downside seems to be battery now my phone idle has consumed 26% so far total of 12hours
Click to expand...
Click to collapse
Hi, thanks for feedback. Well, it doesn't seem like a drawback for me. I myself have an average of 48 hours on full charge (using 25/07 stock ROM, tuned with L-Speed), so 26% in 12 hours seems quite reasonable. ) Of course, it heavily depends on your system config/apps.
Any other obvious bugs/crashes may be?
taka111san said:
Hi, thanks for feedback. Well, it doesn't seem like a drawback for me. I myself have an average of 48 hours on full charge (using 25/07 stock ROM, tuned with L-Speed), so 26% in 12 hours seems quite reasonable. ) Of course, it heavily depends on your system config/apps.
Any other obvious bugs/crashes may be?
Click to expand...
Click to collapse
I have flashed it since a couple of days. Cant find any downsides at all...
For me (after clean flashing) my battery time got BETTER, specially noticed
that i got rid of some wakelocks i was wondering about...
Fingerprint seems more accurate, camera works with 3rd part apps..
sharkware said:
I have flashed it since a couple of days. Cant find any downsides at all...
For me (after clean flashing) my battery time got BETTER, specially noticed
that i got rid of some wakelocks i was wondering about...
Fingerprint seems more accurate, camera works with 3rd part apps..
Click to expand...
Click to collapse
Hi, thanks for the feedback.
I guess Ele guys did only fix the cam and some other fixes like description says, and left anything else at least untouched, did not bring any new bugs in the ROM ).
I think I'll wait until the end of the week may be for the update on Ele BBS (still wondering why they removed the download link), and then give it a try on my P8K.
0815 rom seems alright though I still have the non-working wifi issue at times where you have to off/on it to get it running again(though it shows as connected in the notif. bar
problems with the stock rom
I flashed my Elephone p8000 today with the P8000_20150815 rom and 3rd party camera apps are working now. I got a few problems with the drivers, but finally made it. But the problem is that when the phone is locked, i cant pull down the notification menu. Otherwise the notification menu works, but not on the lockscreen.
Edit: auto shutdown works,but after it restart automatically, phone is hanging. Manual restart and i can use my phone again.
Pls fix
[rom] stock p8000
P8000_20150815 new update
I did not find the front of the camera?
erm not seeing to update, you guys forcing it manually?
I've flashed to the latest ROM. Didn't lose any data either, if you untick user data, then no data is lost
Sent from my Elephone P8000
I am on 15/08 stock rom..the phone turn off its own when it is standbye..has anyone had experience this??
Hi, I'm using the stock ROM and I noticed that, if I change the notifications sound, after a while (maybe a day maybe 2) the elephone "decides" to reset to the default notifications sound. Same problem with the incoming call sound.
Is there somebody else experiencing this problem?