Database Info

[ROM] [G1/MAGIC] 14/OCT/09 Android 1.6 AKIRAH "Phoenix" 3.1 - BFS303 memory patch

[ROM] [G1/MAGIC] 14/OCT/09 Android 1.6 AKIRAH "Phoenix" 3.1 - BFS303 memory patch
Back from ashes...
This is official android 1.6 release for ADP1 + some AOSP, rooted and modified.
Current version
HTML:
3.1
* Fixed data synchronization
* Better terminal instead of terminal.apk
* WIFI Tether 1.6pre3
* More languages
* Camera should be fixed
* IM is back
* comes with ROM Updater
Suggest to wipe ext, and wipe data. You know the rules, might not be really required, but expect some FC's and problems.
Known issues
HTML:
[I]No T-Mobile IM[/I]
Past versions
HTML:
3.0.2a Comes with BFS-303 + memory patch kernel (107 Mb RAM)
* most of problems should be fixed now
* Terminal, Wifi-Tether 1.6pre3
[ problems: no data synchronization, gmail push broken ]
3.0.1
kernel 2.6.29-mkk5 BFS 303
Japanese keyboard fixed
New cyanogen init.d
Cyanogen phone.apk and mms.apk
3.0
- updated frameworks and apks from official framework and SDK.
- Supported languages: Czech, German, English, Spanish, French, Italian, Japanese, Korean, Dutch, Polish, Russian
- added some parts of text to speech and accessibility
- Full package update (no wipe required)
I suggest to cleanup /system/sd/dalvik-cache (might work without, but it's better to do that).
2.1 - upgraded kernel to 2.6.29.6-bfs300-mkk2
see 2.0
2.0 - apps2sd
cm kernel 2.6.29 from 4.1.11.1
all donut goodies
compcache enabled by default
terminal, pdfreader, htc ime, and few things that I've forget to mention
What it requires:
HTML:
root
Radio 2.22.19_26I
Sdcard with FAT32/EXT2 or EXT3 or EXT4/
Recovery image that can flash ROMS not signed with release-keys
DangerSPL / HaykuroSPL
Installation
HTML:
Backup
Wipe
* You might need to format your linux partition
Flash
Downloads
Akirah 3.1
ANDROID1.6 Akirah.3.0
Upgrade from 2.0 to 2.1
ANDROID1.6 Akirah.2.1
ANDROID1.6 Akirah.2.0
Click to expand...
Click to collapse
Themes
Blackened by jonnybueno
Chimera by d750
Minus theme by david1171 for v.2x
Blur theme by Brandenk - for v2.x
Click to expand...
Click to collapse
Theme template by david1171
Click to expand...
Click to collapse

Thank you for reposting, it was locked to me too! flashing later today...

I might try this later, seems okay

akirah said:
What it requires:
root
Radio 2.22.19_26I
Sdcard with FAT32/EXT2 or EXT3 or EXT4/
Recovery image that can flash ROMS not signed with release-keys
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Is the sdcard partition really required or is it only required if one wishes to use the A2SD?
And does the Cyanogenized 1.4 Recovery image count here?

I have a feeling they are going to lock this one too, probably because the Google Apps are included.

So they should close all HERO and Rogers and almost all others.

If they lock this one, then someone high up at xda needs to write a clear policy about what is and isn't allowed on this site, Rom-wise. At the moment I'm sure its individal mods acting alone, each with differing interpretations of what the current site policy is.
If this Rom gets grief, I assume the same standards will apply to Hero roms? Have they closed down the theme boards yet? The problem is (in my view) is that there are far too many mods with itchy trigger fingers (see the raspberry link at the bottom of the first post in my BetterBrowser thread in my sig for a prime example)
Cyanogen is the subject of a cease and desist. Akirah isn't, neither is xda as a site. As long as the files are offsite thus ensuring xda isn't liable, why are different standards being applied here versus the WinMo boards?

have flashed and have no complaints, it zoom zoom super fast!!, everything seems to work have just installed advanced launcher.

Coming from Cyanogens latest experimental build, the install blackscreened me. Wiped, cleared cache, and installed. Reflashed with the same result. I would love to watch what is happening with the adb tools, but that hasn't worked since I installed win7/

akirah said:
Installation
HTML:
Backup
Wipe
erase dalvik-cache
You might need to format your linux partition
Click to expand...
Click to collapse
Where is the step in which you actually flash?

Downloaded before google SHUTS YOU DOWN SON

pinetreehater said:
Coming from Cyanogens latest experimental build, the install blackscreened me. Wiped, cleared cache, and installed. Reflashed with the same result. I would love to watch what is happening with the adb tools, but that hasn't worked since I installed win7/
Click to expand...
Click to collapse
same exact results here..

sstang2006 said:
same exact results here..
Click to expand...
Click to collapse
Try moving app app-private to some folder on /system/sd
and see if it helps

also blankscreen after trying update from 4.1.1.1

can i see some screen shot of this? D;
tnx!

pinetreehater said:
Coming from Cyanogens latest experimental build, the install blackscreened me. Wiped, cleared cache, and installed. Reflashed with the same result. I would love to watch what is happening with the adb tools, but that hasn't worked since I installed win7/
Click to expand...
Click to collapse
Use the latest drivers from the 1.6 SDK, works fine for me on win7.

makethetick said:
Use the latest drivers from the 1.6 SDK, works fine for me on win7.
Click to expand...
Click to collapse
Same results here. Using Win7 x64 and it's worked perfect from day 1, but I started with the updated drivers.

Don't hate Google just yet
kreat1ve said:
Downloaded before Google SHUTS YOU DOWN SON
Click to expand...
Click to collapse
I'm not sure, but I think, the reason Cyanogen received a C&D is because he has an application on the android market that is open to the public that distributes Google copyright applications exclusive to those only on Google experience phones such as the G1. This website is for developers, and it sucks that this website has become more of a popularity contest than what it is meant to do, which Google promotes, the developing part of it. Being that Android is for everyone and can be accessed from non-Google experience phones, that is why he was ordered to stop before legal action is taken. If they were smart, they would have waited until Cyanogen became rich and then sued him for millions for copyright infringement, HOWEVER, they do believe in open-source projects such as Android. Google sells there brand in different packages, if you want the Google brand it will cost you more. They want to take down Microsoft down as much as all of us do. So I wouldn't hate them just yet, they still believe in something good.
Yes this is off-topic, felt i should actually post on an off topic post already. thnx

I adb pulled system/sd/*
then formatted ext, wiped and flashed rom no problems.
I then used adb file explorer to bulk install app-private and app back to phone.
from previous thread it seemd people had the black screen when trying to update straight from 4.1.11.1 so decided formatting ext is best bet

+1 for black screen. Wipe and delete dalvik-cache.
D/dalvikvm( 2520): GC freed 8907 objects / 492664 bytes in 142ms
E/System ( 2520): Failure starting core service
E/System ( 2520): java.lang.NullPointerException
E/System ( 2520): at com.android.server.PackageManagerService.scanPackageL
I(PackageManagerService.java:1875)
E/System ( 2520): at com.android.server.PackageManagerService.scanDirLI(Pa
ckageManagerService.java:1771)
E/System ( 2520): at com.android.server.PackageManagerService.<init>(Packa
geManagerService.java:497)
E/System ( 2520): at com.android.server.PackageManagerService.main(Package
ManagerService.java:266)
E/System ( 2520): at com.android.server.ServerThread.run(SystemServer.java
:112)
E/AndroidRuntime( 2520): Crash logging skipped, no checkin service
I/SystemServer( 2520): Starting Status Bar Service.
E/SystemServer( 2520): Failure starting StatusBarService
E/SystemServer( 2520): java.lang.NullPointerException
E/SystemServer( 2520): at com.android.server.status.StatusBarIcon.getIcon(Statu
sBarIcon.java:143)
E/SystemServer( 2520): at com.android.server.status.StatusBarIcon.<init>(Status
BarIcon.java:65)
E/SystemServer( 2520): at com.android.server.status.StatusBarService.makeStatus
BarView(StatusBarService.java:306)
E/SystemServer( 2520): at com.android.server.status.StatusBarService.<init>(Sta
tusBarService.java:237)
E/SystemServer( 2520): at com.android.server.ServerThread.run(SystemServer.java
:194)
E/AndroidRuntime( 2520): Crash logging skipped, no checkin service
I/SystemServer( 2520): Starting Clipboard Service.
I/SystemServer( 2520): Starting Input Method Service.
E/SystemServer( 2520): Failure starting Input Manager Service
E/SystemServer( 2520): java.lang.NullPointerException
E/SystemServer( 2520): at android.app.ApplicationContext.registerReceiverIntern
al(ApplicationContext.java:782)
E/SystemServer( 2520): at android.app.ApplicationContext.registerReceiver(Appli
cationContext.java:757)
E/SystemServer( 2520): at android.app.ApplicationContext.registerReceiver(Appli
cationContext.java:751)
E/SystemServer( 2520): at com.android.server.InputMethodManagerService.<init>(I
nputMethodManagerService.java:437)
E/SystemServer( 2520): at com.android.server.ServerThread.run(SystemServer.java
:209)
E/AndroidRuntime( 2520): Crash logging skipped, no checkin service
I/SystemServer( 2520): Starting NetStat Service.
I/SystemServer( 2520): Starting Connectivity Service.
W/dalvikvm( 2520): threadid=25: thread exiting with uncaught exception (group=0x
4001da68)
E/AndroidRuntime( 2520): Uncaught handler: thread ConnectivityThread exiting due
to uncaught exception
E/AndroidRuntime( 2520): *** EXCEPTION IN SYSTEM PROCESS. System will crash.
E/AndroidRuntime( 2520): java.lang.NullPointerException
E/AndroidRuntime( 2520): at android.app.ActivityThread.getProvider(Activi
tyThread.java:3938)
E/AndroidRuntime( 2520): at android.app.ActivityThread.acquireProvider(Ac
tivityThread.java:3967)
E/AndroidRuntime( 2520): at android.app.ApplicationContext$ApplicationCon
tentResolver.acquireProvider(ApplicationContext.java:1514)
E/AndroidRuntime( 2520): at android.content.ContentResolver.acquireProvid
er(ContentResolver.java:579)
E/AndroidRuntime( 2520): at android.content.ContentResolver.query(Content
Resolver.java:147)
E/AndroidRuntime( 2520): at android.provider.Settings$NameValueCache.getS
tring(Settings.java:472)
E/AndroidRuntime( 2520): at android.provider.Settings$Secure.getString(Se
ttings.java:1649)
E/AndroidRuntime( 2520): at android.provider.Settings$Secure.getInt(Setti
ngs.java:1689)
E/AndroidRuntime( 2520): at com.android.server.ConnectivityService.getPer
sistedNetworkPreference(ConnectivityService.java:182)
E/AndroidRuntime( 2520): at com.android.server.ConnectivityService.<init>
(ConnectivityService.java:123)
E/AndroidRuntime( 2520): at com.android.server.ConnectivityService.<init>
(ConnectivityService.java:47)
E/AndroidRuntime( 2520): at com.android.server.ConnectivityService$Connec
tivityThread.run(ConnectivityService.java:87)
E/AndroidRuntime( 2520): Crash logging skipped, no checkin service
I/Process ( 2520): Sending signal. PID: 2520 SIG: 9
I/Zygote ( 2519): Exit zygote because system server (2520) has terminated
E/installd( 2361): eof
E/installd( 2361): failed to read size
I/installd( 2361): closing connection
I/ServiceManager( 2354): service 'batteryinfo' died
I/ServiceManager( 2354): service 'usagestats' died
I/ServiceManager( 2354): service 'telephony.registry' died
I/ServiceManager( 2354): service 'SurfaceFlinger' died
I/ServiceManager( 2354): service 'entropy' died
I/ServiceManager( 2354): service 'power' died
I/ServiceManager( 2354): service 'clipboard' died
I/ServiceManager( 2354): service 'netstat' died
D/AndroidRuntime( 2534):
D/AndroidRuntime( 2534): >>>>>>>>>>>>>> AndroidRuntime START <<<<<<<<<<<<<<
D/AndroidRuntime( 2534): CheckJNI is OFF
D/AndroidRuntime( 2534): --- registering native functions ---
I/Zygote ( 2534): Preloading classes...
D/dalvikvm( 2534): GC freed 800 objects / 44048 bytes in 7ms
D/dalvikvm( 2534): GC freed 240 objects / 13920 bytes in 6ms
D/dalvikvm( 2534): GC freed 228 objects / 14392 bytes in 7ms
Click to expand...
Click to collapse
Thanks.
BR.

[Q] Force close on ALL applications when keyboard input is requested

This one is fun - I'm getting an FC every time an application requests keyboard input. If I hit the Google search icon on the top left of the home screen, it immediately FCs - that's what I'm using to test.
I downloaded aLogCat to the device via Google Play on my desktop, and ran it. Here is what I believe to be the relevant log section , from tapping the search icon, to re-entering aLogCat.
I believe the ClipboardEx service is causing the issue, possibly as an interference with another app I have installed - but I don't know what, or how to give you guys a list of apps installed without just typing each one.
This issue happened once to me, and a factory restore fixed it - two weeks later, and it's back. I'm not an experience Android guy, though I am a nerd and a developer. Surely this is something fixable. Does anyone have any thoughts on what could be causing this?
Code:
I/InputReader( 184): Touch event's action is 0x1 (deviceType=0) [pCnt=1, pending(waiting finished signal)=1, s=]
I/InputDispatcher( 184): Delivering touch to current input target: action: 0x1
I/InputDispatcher( 184): Delivering touch to current input target: action: 0x1
I/InputDispatcher( 184): Delivering touch to current input target: action: 0x1
I/ActivityManager( 184): START {intent.toShortString} from pid 383
D/PowerManagerService( 184): acquireDVFSLockLocked : type : DVFS_MIN_LIMIT frequency : 1008000 uid : 1000 pid : 184 tag : ActivityManager
W/ActivityManager( 184): mDVFSLock.acquire()
D/Launcher.HomeFragment( 383): onPause
D/Launcher( 383): onPause
V/TaskCloserActivity( 3234): TaskCloserActivity onReceive()
D/KeyguardViewMediator( 184): setHidden false
D/ActivityManager( 184): Trying to launch applicationName
D/ControlPanelRemoteService( 3246): onDestroy()
D/OpenGLRenderer( 383): Flushing caches (mode 1)
D/dalvikvm( 3157): GC_CONCURRENT freed 259K, 5% free 6784K/7111K, paused 2ms+3ms
D/KeyguardViewMediator( 184): setHidden false
D/STATUSBAR-StatusBarManagerService( 184): setSystemUiVisibility(0x0)
D/STATUSBAR-StatusBarManagerService( 184): manageDisableList what=0x0 pkg=WindowManager.LayoutParams
D/libEGL ( 3157): loaded /vendor/lib/egl/libEGL_POWERVR_SGX540_120.so
D/libEGL ( 3157): loaded /vendor/lib/egl/libGLESv1_CM_POWERVR_SGX540_120.so
D/libEGL ( 3157): loaded /vendor/lib/egl/libGLESv2_POWERVR_SGX540_120.so
D/OpenGLRenderer( 3157): Enabling debug mode 0
E/ClipboardServiceEx( 3157): Had failed to obtaining clipboardEx service.
D/AndroidRuntime( 3157): Shutting down VM
W/dalvikvm( 3157): threadid=1: thread exiting with uncaught exception (group=0x40bb01f8)
E/AndroidRuntime( 3157): FATAL EXCEPTION: main
E/AndroidRuntime( 3157): java.lang.NullPointerException
E/AndroidRuntime( 3157): at android.sec.clipboard.ClipboardExManager.updateData(ClipboardExManager.java:241)
E/AndroidRuntime( 3157): at android.widget.EditText.onFocusChanged(EditText.java:134)
E/AndroidRuntime( 3157): at android.view.View.handleFocusGainInternal(View.java:3727)
E/AndroidRuntime( 3157): at android.view.View.requestFocus(View.java:5420)
E/AndroidRuntime( 3157): at android.view.ViewGroup.onRequestFocusInDescendants(ViewGroup.java:2154)
E/AndroidRuntime( 3157): at android.view.ViewGroup.requestFocus(ViewGroup.java:2110)
E/AndroidRuntime( 3157): at android.view.ViewGroup.onRequestFocusInDescendants(ViewGroup.java:2154)
E/AndroidRuntime( 3157): at android.view.ViewGroup.requestFocus(ViewGroup.java:2110)
E/AndroidRuntime( 3157): at android.view.ViewGroup.onRequestFocusInDescendants(ViewGroup.java:2154)
E/AndroidRuntime( 3157): at android.view.ViewGroup.requestFocus(ViewGroup.java:2110)
E/AndroidRuntime( 3157): at android.view.ViewGroup.onRequestFocusInDescendants(ViewGroup.java:2154)
E/AndroidRuntime( 3157): at android.view.ViewGroup.requestFocus(ViewGroup.java:2110)
E/AndroidRuntime( 3157): at android.view.ViewGroup.onRequestFocusInDescendants(ViewGroup.java:2154)
E/AndroidRuntime( 3157): at android.view.ViewGroup.requestFocus(ViewGroup.java:2110)
E/AndroidRuntime( 3157): at android.view.ViewGroup.onRequestFocusInDescendants(ViewGroup.java:2154)
E/AndroidRuntime( 3157): at android.view.ViewGroup.requestFocus(ViewGroup.java:2113)
E/AndroidRuntime( 3157): at android.view.View.requestFocus(View.java:5370)
E/AndroidRuntime( 3157): at android.view.ViewRootImpl.performTraversals(ViewRootImpl.java:1598)
E/AndroidRuntime( 3157): at android.view.ViewRootImpl.handleMessage(ViewRootImpl.java:2459)
E/AndroidRuntime( 3157): at android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime( 3157): at android.os.Looper.loop(Looper.java:137)
E/AndroidRuntime( 3157): at android.app.ActivityThread.main(ActivityThread.java:4514)
E/AndroidRuntime( 3157): at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime( 3157): at java.lang.reflect.Method.invoke(Method.java:511)
E/AndroidRuntime( 3157): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:790)
E/AndroidRuntime( 3157): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:557)
E/AndroidRuntime( 3157): at dalvik.system.NativeStart.main(Native Method)
W/ActivityManager( 184): Force finishing activity com.google.android.googlequicksearchbox/.SearchActivity
E/android.os.Debug( 184): [email protected] > dumpstate -k -t -n -z -d -o /data/log/dumpstate_app_error
I/dumpstate( 3272): begin
W/ActivityManager( 184): Activity pause timeout for ActivityRecord{423f3fe0 com.google.android.googlequicksearchbox/.SearchActivity}
W/PowerManagerService( 184): Timer 0x7->0x3|0x0
I/PowerManagerService( 184): Ulight 7->3|0
D/PowerManagerService( 184): setLightBrightness : mButtonLight : 0
E/lights ( 184): write_int failed to open /sys/class/sec/sec_touchkey/brightness
I/InputReader( 184): Touch event's action is 0x0 (deviceType=0) [pCnt=1, pending(waiting finished signal)=0, s=0.70 ]
E/lights ( 184): write_int failed to open /sys/class/sec/sec_touchkey/brightness
I/PowerManagerService( 184): Ulight 3->7|0
D/PowerManagerService( 184): setLightBrightness : mButtonLight : 140
I/InputReader( 184): Touch event's action is 0x1 (deviceType=0) [pCnt=1, pending(waiting finished signal)=0, s=]
D/VoldCmdListener( 89): asec list
D/VoldCmdListener( 89): CommandListener::AsecCmd::runCommand -> --
I/dumpstate( 3272): done
D/KeyguardViewMediator( 184): setHidden false
D/Launcher( 383): onResume
D/STATUSBAR-StatusBarManagerService( 184): setSystemUiVisibility(0x0)
D/STATUSBAR-StatusBarManagerService( 184): manageDisableList what=0x0 pkg=WindowManager.LayoutParams
D/myTest ( 383): [MonthTheme] onResume!!
D/KeyguardViewMediator( 184): setHidden false
D/myTest ( 383): firstDayOfWeek = -1
I/power ( 184): *** release_dvfs_lock : lockType : 1
D/myTest ( 383): [MonthView] updateView.mStartDay: 1
D/DEFERED_APP_VISIBILITY( 184): tweaking closing app
D/PowerManagerService( 184): releaseDVFSLockLocked : all DVFS_MIN_LIMIT are released
W/ActivityManager( 184): mDVFSLock.release()
D/Launcher.HomeFragment( 383): onResume

I've now removed all downloaded applications from my Tab. No dice.
I'm going to see if I can dig up any more logs, then reset it I guess.

I've discovered that copying something to the clipboard also causes the FC. This is definitely an issue with TouchWiz's clipboard as far as I can figure out.

Weird because I know I've copy pasted from the tab before
Sent from my SAMSUNG-SGH-I727 using xda premium

jamesd86 said:
Weird because I know I've copy pasted from the tab before
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
It works for me, too, until the whole thing starts crashing, lol.
I reset to factory and re-installed all my stuff; it seems to be working now. I guess it's Samsung's way of reminding me to keep regular backups...

My tab crashed and then this same exact thing started happening. The logs mentioned ClipboardServiceEx.
I am rooted, so I started an adb shell and found that /data/clipboard has all the persistent clipboard entries (I love that feature by the way).
I did this:
su
mv /data/clipboard /data/oldclipboard
mkdir /data/clipboard
chmod 775 /data/clipboard
chown system.system /data/clipboard
reboot
This fixed it, although it cleared all my "held" info in the clipboard. A small price to pay. If you really had to, you could probably fish in /data/oldclipboard for it. Of course, now I will go delete oldclipboard.
Hope that helps someone.

Thanks for that info, you never know!
Pp.
Transmitted from another galaxy with an Infected P-5113.

same thing happening to me. but i was prompted to update my device so i clicked yes thinking it would fix the problem now im stuck on the "use google location" page of the setup forms because when i click next i guess theres a keyboard involved so it crashes. only other button is a back arrow which does nothing.
i havent ever messed with this stuff but i guess ill have to find out how to factory reset through the usb cable.
unwanted pain in the butt

dorkmo said:
same thing happening to me. but i was prompted to update my device so i clicked yes thinking it would fix the problem now im stuck on the "use google location" page of the setup forms because when i click next i guess theres a keyboard involved so it crashes. only other button is a back arrow which does nothing.
i havent ever messed with this stuff but i guess ill have to find out how to factory reset through the usb cable.
unwanted pain in the butt
Click to expand...
Click to collapse
If you plan to root, just do that, boot into recovery, do an adb shell and clear the clipboard directory.
If you aren't going to install a custom recovery then yeah, wipe it out.

wd5gnr said:
If you plan to root, just do that, boot into recovery, do an adb shell and clear the clipboard directory.
If you aren't going to install a custom recovery then yeah, wipe it out.
Click to expand...
Click to collapse
ok newbie here with samsung tabs having same problem, how do you boot into recovery and do an adb shell ? can see above how to clear the clipboard directory and i dont want to factory reset too hard to reload all the crap on ....
thanks

I had the same problem, I do not want to root my device, but I like to use the standard key board from Sumsung. I send a a-mail to a lot of dutch companies (resellers) to tell them about the problem. I think that Sansung must make a firware update to solve this problem. I what to ask all people who have problems with the keyboard to e-mail Samsung and there reseller to put preasure on Samsung to make a firmware.
I use a work a round, I use a 3e party keyboard untill Samsung makes a firmware update.

wd5gnr said:
I did this:
su
mv /data/clipboard /data/oldclipboard
mkdir /data/clipboard
chmod 775 /data/clipboard
chown system.system /data/clipboard
reboot
Hope that helps someone.
Click to expand...
Click to collapse
YEZZZZZ THANK YOU VERY MUCH!!!:good::laugh:
This worked perfectly on my Samsung Galaxy Tab 2 10.1 (P5110)

Thanks wd5gnr for the solution, worked very well!
Regards.

Glad it helped. I noticed someone asked earlier for more details.
There are plenty of root tutorials here. As for installing ADB there are a few ways to go and it depends on your PC's OS and if you want to get someone's simplified package or not. Read: http://www.howtogeek.com/125769/how-to-install-and-use-abd-the-android-debug-bridge-utility/ and the comments on that page too. If you google something like "installing ADB" you should find lots of help.
Once you have adb installed and can get to a shell, you should be good with my earlier instructions.

[ROM][m7]Android 4.4.3 KTU84L Google Play Edition - Rooted/Busybox/Odexed (6/4/14)

Stock Android 4.4.3 KTU84L for HTC One M7
-Made from full system/boot dump of Google Play Edition HTC One 4.4 KTU84L.H4
-Rooted with SuperSU 1.94 by Chainfire
-Busybox installed
-Odexed (for ART compatibility and possible minor OTA support)
Requirements
-GSM HTC One (m7ul/m7tmo/m7att)
-Latest Custom Recovery with 4.4 support (TWRP 2.6.3.3+, CWR 6.0.4.3+)
-S-OFF (SuperSID or GoogleSID)
Features
-Stock Android 4.4.3 w/ Google Apps
-ART capability
-Tap to Pay (Google Wallet)
-Beats Audio toggle in sound settings
Credits
-Chainfire, for SuperSU 1.94 (working on 4.4.3)
Changelog
-Android 4.4 features can be found (here)
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"
}
Instructions
-Do a factory reset (unless coming from previous GPe ROM, then just wipe cache/dalvik)
-Install with TWRP or CWR
Downloads
MD5 (bigxie_m7_GPe_KTU84L_odexed-unsigned.zip) = 128abf3d8906b20cd03c374dbc7e1d25
http://www.androidfilehost.com/?fid=23501681358542399 - AFH
https://mega.co.nz/#!DMkD3QIZ!O8CJXzRACE5_QVAh6sUSywkaJHrqizQHSEYnjOm2f7g - Mega
Older Version Downloads
MD5 (bigxie_m7_GPe_KRT16S_odexed-signed.zip) = 5c9f5c46921e0824dcd75db3927f92a0
http://goo.im/devs/bigxie/m7/bigxie_m7_GPe_KRT16S_odexed-signed.zip - Goo.im
https://mega.co.nz/#!3BtCBD6T!ViZfS1MwhR4ttcPEkB3XrDVv9Asardy4e01UJO-5ZB0 - Mega
Radio
http://www.mediafire.com/download/hl9lphiibp51i1w/RadioUpdate_4T.21.3218.21_10.16.1718.01L.zip
MD5 (bigxie_m7_GPe_JWR66V_odexed-signed.zip) = bac188e3b7df88cac7285e2b5e1950e7
https://mega.co.nz/#!DBNGCRRT!fPOi00s-e47XkpODR6uhHCVo7hRyuKVM-iRWIUfWldw
http://goo.im/devs/bigxie/m7/bigxie_m7_GPe_JWR66V_odexed-signed.zip
Deodexed version - provided by Whitehawkx
http://goo.im/devs/Whitehawkx/m7/m7_GPe_JWR66V_deodexed-signed.zip
Radio - GE_Radio_4A.18.3263.15_10.38h.1157.04L.zip
https://mega.co.nz/#!HdwxkQqC!TgSeIFmErtLL8iJkpzdR5ThAPn8S0U5BmoEZKrJ_87w
faux123 Google Edition Kernel - Use this if you want additional features such as logo2menu, sweep2wake, etc.
http://forum.xda-developers.com/showthread.php?t=2255900
MD5 (bigxie_m7_GPe_odexed_stock-7-7-13.zip) = 1d36d5a70703018b4fa4ed4f97cbeba4
http://goo.im/devs/bigxie/m7/bigxie_m7_GPe_odexed_stock-7-7-13.zip
https://mega.co.nz/#!HJ8jlBJB!OJd7Sl7LrAJC2d6VT4SpJhoxGRpGbn1bE-Dl9TB7lfI
Deodexer - Requires flashing ROM first!
http://goo.im/devs/bigxie/m7/bigxie_m7_GPe_deodexer.zip
Radio
http://goo.im/devs/bigxie/m7/Radio_4A.17.3250.14_10.39.1150.04L.zip
Tbalden Google Edition Kernel - Use this if you want additional features such as logo2menu, sweep2wake, etc.
http://forum.xda-developers.com/showthread.php?t=2307371
MD5 (bigxie_m7_GPe_odexed_tbalden.zip) = 42bb792149e08188030271c745223a61
http://goo.im/devs/bigxie/m7/bigxie_m7_GPe_odexed_tbalden.zip
ROM Mirrors - Mirrors are appreciated and I will try to update the OP with them as promptly as I can
http://www.4shared.com/zip/4MTwPwsZ/bigxie_m7_GPe_odexed_tbalden.html
https://mega.co.nz/#!F5FWSDyI!SZjiLxEn2QZ_5iciXc9EQUaiKDBYClohVkId-jRxqBo
http://www.uploadmagnet.com/b9vw9c8xa5kv/bigxie_m7_GPe_odexed_tbalden.zip
http://d-h.st/knJ
https://mega.co.nz/#!tJFQFIab!PcsmZHK8HszM9E9jzXAZyw6jNgYLWE6M6cj3lLmwSYw
http://www.uploadmagnet.com/zbwqv5zjoz1s/bigxie_m7_GPe_odexed_tbalden.zip
http://mirror.lag.re/bigxie_m7_GPe_odexed_tbalden.zip
http://htcfanboys.com/download/theDroidfanatic/?action=list&file=5474

Frequently Asked Questions + Other Resources
Frequently Asked Questions
Q: Where's my lock screen?
A: For some reason, HTC chose to disable it by default. Go into security settings and enabled slide, pin, whatever. While you're in there, you may want to enable lock screen widgets as well.
Q: How do I get that sweet launcher from the Nexus 5? I thought that came with KitKat?
A: It's currently only for Nexus 5, however it will install just fine on this ROM. Get it here.
The following questions are quite outdated and will be hidden:
Q: Can so and so feature from Sense be ported to this ROM?
A: Most likely no, you'll have to find a third party solution in the Play Store, or if none exists, live without the feature or return to Sense.
Q: Does the IR blaster work?
A: Yes, it is working as of the 4.3 update!
Q: How do I remove the 3-dot legacy menu?
A1: Download TricksterMod Kernel app from the Play Store, scroll to Specifics, 'Screen Wake Control', switch on 'Disable 3Dot Menu', hit the check mark at the top right, and reboot your phone.
A2: Alternatively, if you know how to edit your build.prop with Root Explorer or something comparable, add "qemu.hw.mainkeys = 1" to the bottom of the file, save and reboot.
Q: Is the included kernel the official GPe ROM kernel?
A: Yes, it is the stock kernel with the ramdisk edited to be debuggable and insecure.
Q: Is the camera quality better or worse than Sense?
A: The OS gets the exact same raw data from the sensor in this ROM as it does in Sense, so the difference is in post processing. It is generally agreed that the photos are comparable to Sense except in really low light, where Sense's post processing is a little bit better.
Q: I don't have an English keyboard? How do I proceed?
A1: As a workaround, you can use the Korean keyboard to type English to get far enough into the Play Store and download an alternative keyboard.
A2: Alternatively, if you know how, you can switch your CID to GOOGL001 and the keyboard should show up now.
Q: How do I take a screenshot?
A: Press and hold power + volume down (at the same time) and don't let go until the screenshot animation and sound play (it will be obvious, takes perhaps a little over 1 second of holding down the buttons).
Q: Has anyone made such and such theme/mod/feature?
A: It would be prudent to check the correct respective forum first (i.e 'Themes and Apps' for themes, 'Original Development' for kernels, etc.)
Q: Can this get OTA updates directly?
A: No.
Q: Is Google Wallet compatible?
A: Not at the moment, and most likely it won't ever be as the HTC One is missing the hardware secure element required by Wallet.
Videos - These are outdated as of 8/5/13 (for the 4.2.2 build only, but may still have pertinent info!)
Installation by Devicecustomizer
Review by Devicecustomizer
Review by krazygreen

When will we be able to FULLY convert to a Google Edition and receive OTA updates etc.?

barkmarkin said:
When will we be able to FULLY convert to a Google Edition and receive OTA updates etc.?
Click to expand...
Click to collapse
Probably when devs start receiving the device from Google Play

Link is up, please mirror, thx!

barkmarkin said:
When will we be able to FULLY convert to a Google Edition and receive OTA updates etc.?
Click to expand...
Click to collapse
Really? The device itself isn't even in the hands of people who ordered it, and we only just got a hold of a system dump today. Slow down and calm down.

mine will complete soon. OP can I mirror it?

ultimatepichu said:
mine will complete soon. OP can I mirror it?
Click to expand...
Click to collapse
Yes, please.
Make sure the md5 checks out before you reup.
MD5 (bigxie_m7_GPe_odexed_tbalden.zip) = 42bb792149e08188030271c745223a61

bigxie said:
Yes, please.
Click to expand...
Click to collapse
I'll just make a torrent lol, if you're okay with that. Seems like the only way to manage the demand currently.

Did you manage to fix the data usage bigxie? I'm looking into but won't if you found the cause

Nice to see this happening so fast! HTC is going the easiest way, Sense and Google Edition can use the same kernel

tischn said:
Thank you soo much. I will flash it as soon as i'm at home.
and p.s. You have written the wrong date in the Title.
Click to expand...
Click to collapse
It's definitely June 28th in China
bbedward said:
Did you manage to fix the data usage bigxie? I'm looking into but won't if you found the cause
Click to expand...
Click to collapse
Nope, seems like the entire entry is just missing from Settings. Not sure, but it may be a bug with the GPe ROM? I mean IR isn't working yet either, they might have rushed this (as the One GPe was announced later than the GS4).

Here's the exception, when launching data usage, for reference.
Code:
W/dalvikvm( 4350): threadid=1: thread exiting with uncaught exception (group=0x41e1eba0)
E/EmbeddedLogger( 728): App crashed! Process: com.android.settings
E/EmbeddedLogger( 728): App crashed! Package: com.android.settings v17 (4.2.2-eng..20130622.034104)
E/EmbeddedLogger( 728): Application Label: Settings
D/InputManager( 728): setFocusedApplication Exception: java.lang.NullPointerException
E/AndroidRuntime( 4350): FATAL EXCEPTION: main
E/AndroidRuntime( 4350): java.lang.RuntimeException: Unable to start activity ComponentInfo{com.android.settings/com.android.settings.Settings$DataUsageSummaryA
ctivity}: java.lang.IllegalStateException: Bandwidth module disabledE/AndroidRuntime( 4350): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2463)
E/AndroidRuntime( 4350): at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2520)
E/AndroidRuntime( 4350): at android.app.ActivityThread.access$600(ActivityThread.java:162)
E/AndroidRuntime( 4350): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1366)
E/AndroidRuntime( 4350): at android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime( 4350): at android.os.Looper.loop(Looper.java:158)
E/AndroidRuntime( 4350): at android.app.ActivityThread.main(ActivityThread.java:5751)
E/AndroidRuntime( 4350): at java.lang.reflect.Method.invokeNative(NativeMethod)
E/AndroidRuntime( 4350): at java.lang.reflect.Method.invoke(Method.java:511)
E/AndroidRuntime( 4350): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1083)
E/AndroidRuntime( 4350): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:850)
E/AndroidRuntime( 4350): at dalvik.system.NativeStart.main(Native Method)
E/AndroidRuntime( 4350): Caused by: java.lang.IllegalStateException: Bandwidth module disabled
E/AndroidRuntime( 4350): at android.os.Parcel.readException(Parcel.java:1442)
E/AndroidRuntime( 4350): at android.os.Parcel.readException(Parcel.java:1388)
E/AndroidRuntime( 4350): at android.net.INetworkStatsService$Stub$Proxy.openSession(INetworkStatsService.java:180)
E/AndroidRuntime( 4350): at com.android.settings.DataUsageSummary.onCreateView(DataUsageSummary.java:302)
E/AndroidRuntime( 4350): at android.app.Fragment.performCreateView(Fragment.java:1785)
E/AndroidRuntime( 4350): at android.app.FragmentManagerImpl.moveToState(FragmentManager.java:887)
E/AndroidRuntime( 4350): at android.app.FragmentManagerImpl.moveToState(FragmentManager.java:1059)
E/AndroidRuntime( 4350): at android.app.BackStackRecord.run(BackStackRecord.java:682)
E/AndroidRuntime( 4350): at android.app.FragmentManagerImpl.execPendingActions(FragmentManager.java:1437)
E/AndroidRuntime( 4350): at android.app.Activity.performStart(Activity.java:5174)
E/AndroidRuntime( 4350): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2436)
E/AndroidRuntime( 4350): ... 11 more
W/ActivityManager( 728): Force finishing activity com.android.settings/.Settings$DataUsageSummaryActivity

I cant help it but asking for someone please report battery life with BetterBatteryStat once done downloading & testing.
thanks for your time guys.

I hope they included flash to focus this time.

This is using a custom kernel and not the stock HTC kernel. Does that mean we don't have a boot.img dump from the GE?
Since this is using a compiled kernel does it still have the same glitches as the existing AOSP roms? My understanding was most of the bugs were in the kernel at this point.
Specifically I'm referring to:
- A2DP packet loss and disconnects
- poor bluetooth connectivity (long time to switch devices and having to toggle bluetooth on/off to reconnect)
- Call audio not working over bluetooth
- poor GPU performance compared to Sense

bbedward said:
Here's the exception, when launching data usage, for reference.
Click to expand...
Click to collapse
Code:
java.lang.IllegalStateException: Bandwidth module disabled
?????????? Well there's your problem.

where should i upload to? I'm doing 4shared and dev-host now...

bbedward said:
Here's the exception, when launching data usage, for reference.
Code:
W/dalvikvm( 4350): threadid=1: thread exiting with uncaught exception (group=0x41e1eba0)
E/EmbeddedLogger( 728): App crashed! Process: com.android.settings
E/EmbeddedLogger( 728): App crashed! Package: com.android.settings v17 (4.2.2-eng..20130622.034104)
E/EmbeddedLogger( 728): Application Label: Settings
D/InputManager( 728): setFocusedApplication Exception: java.lang.NullPointerException
E/AndroidRuntime( 4350): FATAL EXCEPTION: main
E/AndroidRuntime( 4350): java.lang.RuntimeException: Unable to start activity ComponentInfo{com.android.settings/com.android.settings.Settings$DataUsageSummaryA
ctivity}: java.lang.IllegalStateException: Bandwidth module disabledE/AndroidRuntime( 4350): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2463)
E/AndroidRuntime( 4350): at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2520)
E/AndroidRuntime( 4350): at android.app.ActivityThread.access$600(ActivityThread.java:162)
E/AndroidRuntime( 4350): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1366)
E/AndroidRuntime( 4350): at android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime( 4350): at android.os.Looper.loop(Looper.java:158)
E/AndroidRuntime( 4350): at android.app.ActivityThread.main(ActivityThread.java:5751)
E/AndroidRuntime( 4350): at java.lang.reflect.Method.invokeNative(NativeMethod)
E/AndroidRuntime( 4350): at java.lang.reflect.Method.invoke(Method.java:511)
E/AndroidRuntime( 4350): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1083)
E/AndroidRuntime( 4350): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:850)
E/AndroidRuntime( 4350): at dalvik.system.NativeStart.main(Native Method)
E/AndroidRuntime( 4350): Caused by: java.lang.IllegalStateException: Bandwidth module disabled
E/AndroidRuntime( 4350): at android.os.Parcel.readException(Parcel.java:1442)
E/AndroidRuntime( 4350): at android.os.Parcel.readException(Parcel.java:1388)
E/AndroidRuntime( 4350): at android.net.INetworkStatsService$Stub$Proxy.openSession(INetworkStatsService.java:180)
E/AndroidRuntime( 4350): at com.android.settings.DataUsageSummary.onCreateView(DataUsageSummary.java:302)
E/AndroidRuntime( 4350): at android.app.Fragment.performCreateView(Fragment.java:1785)
E/AndroidRuntime( 4350): at android.app.FragmentManagerImpl.moveToState(FragmentManager.java:887)
E/AndroidRuntime( 4350): at android.app.FragmentManagerImpl.moveToState(FragmentManager.java:1059)
E/AndroidRuntime( 4350): at android.app.BackStackRecord.run(BackStackRecord.java:682)
E/AndroidRuntime( 4350): at android.app.FragmentManagerImpl.execPendingActions(FragmentManager.java:1437)
E/AndroidRuntime( 4350): at android.app.Activity.performStart(Activity.java:5174)
E/AndroidRuntime( 4350): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2436)
E/AndroidRuntime( 4350): ... 11 more
W/ActivityManager( 728): Force finishing activity com.android.settings/.Settings$DataUsageSummaryActivity
Click to expand...
Click to collapse
Wait, so you already have it? Would you make a mirror for us please ?

ultimatepichu said:
where should i upload to? I'm doing 4shared and dev-host now...
Click to expand...
Click to collapse
MEGA.CO.NZ plzzzzz

[APP][DEV][4.0+][V1.3]ROM Mart Customizable HUB for ROM Developers

ROM Mart is an app that let you provide add-ons to custom ROM users, such as wallpapers, apps and mods.
The app is really flexible and the developer can set categories, sub-categories and some layout parameters.
The only thing developer needs to do is create a simple XML file and upload it on his server, then add some strings to the build.prop file
Special Thanks to @maximo76 for the app icon
Features:
Flexible UI : App UI can be customized by modifying xml parameters
Categorized: All the content can be categorized in categories and sub-categories
Notifications: When developer add/remove content from the remote file a notification will be prompted to the user
Updates check frequency: set when the app must check for updates
Set/Download wallpapers
Install apps
Install mods
updates checker service will automatically start/stop based on connection status! (WiFi, mobile data)
Should work with any device running Android 4.0+
No need to subscribe to any site, just put the link to the remote xml file and you are done!
Will always be free!
More will come in future based also on devs requests
Permissions explanation:
android.permission.WRITE_EXTERNAL_STORAGE" ==> Save content to SD-card
android.permission.SET_WALLPAPER" ==> permission to set device wallpaper
android.permission.INTERNET" ==> Download manifest and content
android.permission.ACCESS_NETWORK_STATE" ==> get network state to start/stop updates service
How To :
Add these lines to the build prop:
Code:
hub.pub.url= public url to the xml file
hub.ab.name=App ActionBar title
hub.dl.folder=complete path to your download folder (ex: /sdcard/hub-downloads). Folder will be automatically created by the app
hub.sched.time= Time in minutes for udates check
XML Syntax:
HTML:
<?xml version="1.0" encoding="utf-8"?>
<items>
<category name="your category name">
<sub-category name="your sub-category name"
images ="true | false"
apps="true | false "
mods="true | false"
use-grid="true | false"
use-cards="true | false">
<item url="URL to the content (images, apps, zips)"
thumbUrl="optional for images, required for apps and mods"
name="App/image/mod name"
author="author"
description="required for Apps and Mods, not used for images"
preview-images="Images Link separated by a semicolon (;). Required only for apps and mods"/>
</sub-category>
</category>
</items>
Tags explanation:
<category> :
This tag inside inside the app will be a ViewPager Tab
Attributes:
name="" ==> this will be the Tab name
Click to expand...
Click to collapse
Click to expand...
Click to collapse
<sub-category>
Every Sub-Category will be a list item inside the menu.
Attributes:
name="" ==> The sub-category name user will display inside the app
images="true|false" ==> needed to tell to the app if this sub-category contains images on not
apps="true|false" ==> Same as for images attribute.
mods="true|false" ==> Same as images and apps.
use-grid="true|false" ==> This will tell the app to use a ListView instead of GridView. default is false so it will use a listview.
use-cards="true|false" ==> This one will tell to the app if you want to use google cards look or not. Default is false.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
<item>
This is one of the downloadable contents you want provide to your users (an image, and app or a mod).
Attributes:
url="" ==> URL of the content
thumbUrl="" ==> unused for images, used by apps and mods to provide the image you'll see inside the list or gridview
name="" ==> image, app or mod name
author="" => image, app or mod author
description="" ==> Content description used only by apps and mods. Not required for images.
preview-images="" ==> Link or links to preview images separated by a semicolon ;. These images will be displayed on the detailed view when user clicks on a list/gridView item. Used for apps and mods, unused for images.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Note that Not required fields can be omitted in XML!
thumbUrl and name for images can be omitted! The app will generate a name automatically ("Item #xxyy")
A simple XML example, can be found here: manifest.xml
(It's based on DirtyUnicorns wallpapers xml)
Put the app in /data/app or in /system/app, as you wish
:::In case of Force Close:::
- Read this post and check Build.prop permissions ==> http://forum.xda-developers.com/showpost.php?p=52404174&postcount=13
- if it's not file's permissions related take a logcat and post the log
Click to expand...
Click to collapse
Warnings:
- all links must be publicly accessible and must be direct links to the content (check the example xml!!)
- of course, also the xml link must be publicly accessible!
- use an editor that provides also code highlighting and errors check (i use Komodo Edit)
Sharing policy:
- Let me know if you include it in your rom!
- Add credits to your thread! (me and DSHT, my team)
- Add a link to this thread in yours!
- You are not allowed to change app icon or any other resource inside the package.
- You are not allowed to change the app code
- Any violation will be reported to xda moderators!
Changelog:
V1.0:
- initial release
V1.1:
- fixed zip flash (SU required)
- new App icon by maximo76
V1.2:
- fixed API level issue
V1.3
- fixed NumberFormatException
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"
}
XDA:DevDB Information
ROM Mart, App for all devices (see above for details)
Contributors
xcesco89
Version Information
Status: Stable
Current Stable Version: 1.3
Stable Release Date: 2014-05-04
Created 2014-05-03
Last Updated 2014-05-09

Great cesco my rom will have this
Inviato dal mio unknown utilizzando Tapatalk

What an awesome app
Good job cescuz

Great work. My rom will have that too
Sent from my HTC One using XDA Premium 4 mobile app

Ehehe,another Great work thanks Cesco

hmm. crashes on my Nexus 5 running CM11 when you open it.

This looks very promising
Sent from my Nexus 5 using Tapatalk

This looks very nice. Any free reliable servers that would be compatible with this that u can recommend?
Sent from my SM-G900T using Tapatalk

This looks great for start up ROM devs
You can either find a good or a free. Almost impossible to find both. Let alone one that will handle that kind of traffic reliably.
Bat cave One

zelendel said:
This looks great for start up ROM devs
You can either find a good or a free. Almost impossible to find both. Let alone one that will handle that kind of traffic reliably.
Bat cave One
Click to expand...
Click to collapse
I was afraid of that. Thanks for your response
Sent from my SM-G900T using Tapatalk

That's strange, on my N5 and G2 all works without issue, anyway I'll change some lines of code and upload a new version. As I see, seems there are problems with build.prop file permissions. (Usually these are rwxr-xr-x and all works)
Thanks for these reports
Inviato dal mio Nexus 5 utilizzando Tapatalk

FC on open.
Code:
E/AndroidRuntime(18968): FATAL EXCEPTION: main
E/AndroidRuntime(18968): Process: com.dsht.center, PID: 18968
E/AndroidRuntime(18968): java.lang.RuntimeException: Unable to start activity ComponentInfo{com.dsht.center/com.dsht.center.MainActivity}: java.lang.NumberFormatException: [B]Invalid int: "disable"[/B]
E/AndroidRuntime(18968): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2195)
E/AndroidRuntime(18968): at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2245)
E/AndroidRuntime(18968): at android.app.ActivityThread.access$800(ActivityThread.java:135)
E/AndroidRuntime(18968): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1196)
E/AndroidRuntime(18968): at android.os.Handler.dispatchMessage(Handler.java:102)
E/AndroidRuntime(18968): at android.os.Looper.loop(Looper.java:136)
E/AndroidRuntime(18968): at android.app.ActivityThread.main(ActivityThread.java:5017)
E/AndroidRuntime(18968): at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime(18968): at java.lang.reflect.Method.invoke(Method.java:515)
E/AndroidRuntime(18968): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:779)
E/AndroidRuntime(18968): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:595)
E/AndroidRuntime(18968): at dalvik.system.NativeStart.main(Native Method)
E/AndroidRuntime(18968): Caused by: java.lang.NumberFormatException: Invalid int: "disable"
E/AndroidRuntime(18968): at java.lang.Integer.invalidInt(Integer.java:137)
E/AndroidRuntime(18968): at java.lang.Integer.parse(Integer.java:374)
E/AndroidRuntime(18968): at java.lang.Integer.parseInt(Integer.java:365)
E/AndroidRuntime(18968): at java.lang.Integer.parseInt(Integer.java:331)
E/AndroidRuntime(18968): at com.dsht.center.MainActivity.onCreate(MainActivity.java:92)
E/AndroidRuntime(18968): at android.app.Activity.performCreate(Activity.java:5231)
E/AndroidRuntime(18968): at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1087)
E/AndroidRuntime(18968): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2159)
E/AndroidRuntime(18968): ... 11 more
W/ActivityManager( 3398): Force finishing activity com.dsht.center/.MainActivity
xcesco89 said:
That's strange, on my N5 and G2 all works without issue, anyway I'll change some lines of code and upload a new version. As I see, seems there are problems with build.prop file permissions. (Usually these are rwxr-xr-x and all works)
Thanks for these reports
Inviato dal mio Nexus 5 utilizzando Tapatalk
Click to expand...
Click to collapse
build.prop should never be any other mode then 644. on legacy roms setting build.prop to 755 may cause bootloop (because of primitive system), I have had this on my old phone (i9001)

broodplank1337 said:
FC on open.
Code:
E/AndroidRuntime(18968): FATAL EXCEPTION: main
E/AndroidRuntime(18968): Process: com.dsht.center, PID: 18968
E/AndroidRuntime(18968): java.lang.RuntimeException: Unable to start activity ComponentInfo{com.dsht.center/com.dsht.center.MainActivity}: java.lang.NumberFormatException: [B]Invalid int: "disable"[/B]
E/AndroidRuntime(18968): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2195)
E/AndroidRuntime(18968): at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2245)
E/AndroidRuntime(18968): at android.app.ActivityThread.access$800(ActivityThread.java:135)
E/AndroidRuntime(18968): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1196)
E/AndroidRuntime(18968): at android.os.Handler.dispatchMessage(Handler.java:102)
E/AndroidRuntime(18968): at android.os.Looper.loop(Looper.java:136)
E/AndroidRuntime(18968): at android.app.ActivityThread.main(ActivityThread.java:5017)
E/AndroidRuntime(18968): at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime(18968): at java.lang.reflect.Method.invoke(Method.java:515)
E/AndroidRuntime(18968): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:779)
E/AndroidRuntime(18968): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:595)
E/AndroidRuntime(18968): at dalvik.system.NativeStart.main(Native Method)
E/AndroidRuntime(18968): Caused by: java.lang.NumberFormatException: Invalid int: "disable"
E/AndroidRuntime(18968): at java.lang.Integer.invalidInt(Integer.java:137)
E/AndroidRuntime(18968): at java.lang.Integer.parse(Integer.java:374)
E/AndroidRuntime(18968): at java.lang.Integer.parseInt(Integer.java:365)
E/AndroidRuntime(18968): at java.lang.Integer.parseInt(Integer.java:331)
E/AndroidRuntime(18968): at com.dsht.center.MainActivity.onCreate(MainActivity.java:92)
E/AndroidRuntime(18968): at android.app.Activity.performCreate(Activity.java:5231)
E/AndroidRuntime(18968): at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1087)
E/AndroidRuntime(18968): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2159)
E/AndroidRuntime(18968): ... 11 more
W/ActivityManager( 3398): Force finishing activity com.dsht.center/.MainActivity
build.prop should never be any other mode then 644. on legacy roms setting build.prop to 755 may cause bootloop (because of primitive system), I have had this on my old phone (i9001)
Click to expand...
Click to collapse
i know. You'll probably get error when the file is 700 (rwx------). With 644 (rw-r--r--) | 744 (rwxr--r--) and 755(rwxr-xr-x) App works without issues (already tested).
I prefer avoid the use of su to read build.prop file because will cause the prompt of annoying toasts telling you "garanted superuser permissions". I can also copy the build.prop to the app files dir, but in case you change something in the prop the app will not recognize it.
I don't have devices with internal and external SDcard, so, try to use /mnt/extsd or whatever the path is instead of /data/media
EDIT:
You can also make a simple init.d script that changes permissions, or check your updater-script and change the permissions setting here
EDIT2:
Version 1.1 ready. Fixed some stuff related to zip flashing and new app icon by @maximo76

xcesco89 said:
ROM Mart is an app that let you provide add-ons to custom ROM users, such as wallpapers, apps and mods.
The app is really flexible and the developer can set categories, sub-categories and some layout parameters............
Click to expand...
Click to collapse
isnt it possible to make this a stand alone app ?

TheHaso said:
isnt it possible to make this a stand alone app ?
Click to expand...
Click to collapse
You mean by hardcoding build.prop strings inside the app?
Inviato dal mio Nexus 5 utilizzando Tapatalk

great work confirm that
v1.1 works now with SUpermissions when you try to flash a zip via recovery.
only thing left is that it dont read the build.prop and FC's
rwx---- permission :silly: all others like rw-r-r work fine
edit: question: why not use a manifest.xml in /system/ folder? its similar to the build.prop lines but then it dont matter what permission the build.prop has...
just an idea

skeleton1911 said:
great work confirm that
v1.1 works now with SUpermissions when you try to flash a zip via recovery.
only thing left is that it dont read the build.prop and FC's
rwx---- permission :silly: all others like rw-r-r work fine
edit: question: why not use a manifest.xml in /system/ folder? its similar to the build.prop lines but then it dont matter what permission the build.prop has...
just an idea
Click to expand...
Click to collapse
Rwx------ equals 700 and only root can read write and execute. So it's normal that app FC's when it tries to read the file: it doesn't have permissions
Just change file permissions to rwxr--r-- (744) or rw-r--r-- (644) and the app will not Force close. Check other files in /system, I doubt they all have 700 permission.
You can also try to make a simple init.d script that changes build.prop permissions (busybox chmod 644 /system/build.prop)
Inviato dal mio Nexus 5 utilizzando Tapatalk

xcesco89 said:
Rwx------ equals 700 and only root can read write and execute. So it's normal that app FC's when it tries to read the file: it doesn't have permissions
Just change file permissions to rwxr--r-- (744) or rw-r--r-- (644) and the app will not Force close. Check other files in /system, I doubt they all have 700 permission.
You can also try to make a simple init.d script that changes build.prop permissions (busybox chmod 644 /system/build.prop)
Inviato dal mio Nexus 5 utilizzando Tapatalk
Click to expand...
Click to collapse
Yep. Thank you mate. I Already did it with an init.d script thanks
Sent from my HTC One using XDA Premium 4 mobile app

Is there a way to get this app working without editing the build.prop?

FC when opening, using LG Optimus L9 (p760) with CM9:
Code:
D/TAG ( 1785): Helpers:findBuildPropValueOf found {hub.pub.url} with the value (https://dl.dropboxusercontent.com/u/13475549/wallpaper_manifest.xml)
D/TAG ( 1785): Helpers:findBuildPropValueOf found {hub.ab.name} with the value (Pollos)
D/TAG ( 1785): Helpers:findBuildPropValueOf found {hub.dl.folder} with the value (/mnt/sdcard/)
D/TAG ( 1785): Helpers:findBuildPropValueOf found {hub.sched.time} with the value (60)
D/dalvikvm( 286): GC_CONCURRENT freed 2794K, 41% free 7998K/13379K, paused 1ms+6ms
D/OpenGLRenderer( 527): Flushing caches (mode 1)
D/OpenGLRenderer( 1785): Enabling debug mode 0
I/ActivityManager( 286): Displayed com.dsht.center/.MainActivity: +677ms
D/OpenGLRenderer( 527): Flushing caches (mode 0)
D/AndroidRuntime( 1785): Shutting down VM
W/dalvikvm( 1785): threadid=1: thread exiting with uncaught exception (group=0x40a451f8)
E/AndroidRuntime( 1785): FATAL EXCEPTION: main
E/AndroidRuntime( 1785): java.lang.NoSuchMethodError: com.astuetz.viewpager.extensions.PagerSlidingTabStrip.setBackground
E/AndroidRuntime( 1785): at com.dsht.center.MainActivity.loadPreviewFragment(MainActivity.java:229)
E/AndroidRuntime( 1785): at com.dsht.center.MainActivity$LoadManifest.onPostExecute(MainActivity.java:206)
E/AndroidRuntime( 1785): at com.dsht.center.MainActivity$LoadManifest.onPostExecute(MainActivity.java:1)
E/AndroidRuntime( 1785): at android.os.AsyncTask.finish(AsyncTask.java:602)
E/AndroidRuntime( 1785): at android.os.AsyncTask.access$600(AsyncTask.java:156)
E/AndroidRuntime( 1785): at android.os.AsyncTask$InternalHandler.handleMessage(AsyncTask.java:615)
E/AndroidRuntime( 1785): at android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime( 1785): at android.os.Looper.loop(Looper.java:137)
E/AndroidRuntime( 1785): at android.app.ActivityThread.main(ActivityThread.java:4575)
E/AndroidRuntime( 1785): at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime( 1785): at java.lang.reflect.Method.invoke(Method.java:511)
E/AndroidRuntime( 1785): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:789)
E/AndroidRuntime( 1785): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:556)
E/AndroidRuntime( 1785): at dalvik.system.NativeStart.main(Native Method)
W/ActivityManager( 286): Force finishing activity com.dsht.center/.MainActivity

[ROM][EOL][CARBON][KK 4.4.4] CarbonROM (MT4GS)

hLe Storm ROM 4.4.4
Looks like I graduated from ArchiKitchen, now compiling from source and I may be on to something here. But first...
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and
* YOU acknowledge you are doing so at your own risk.
*/
Now that that's out of the way, hLe Storm (pronounced "hailstorm") 4.4.4 is a build of CarbonROM, using the kernel from @Emmanuel U (among advice), and device identity and other projects from Team KitKatDS. As CarbonROM is EOL (end-of-life) as of April 5th (or earlier), some commits have been taken/"cherry picked" from CyanogenMod 11 source.
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"
}
WHAT WORKS:
Powers on
Phone calls
SMS and (after using the busybox trick) MMS
Mobile Data (HSPA detected with my carrier)
Wifi
Google Play
GPS, based on GPS Status & Toolbox
Camera via UCam app, also now stock and Google Camera
Torch
Needs further testing
WHAT DOES NOT WORK:
Camcorder in stock app records nothing
Probably the same for any replacement Camcorder app (encountered this problem earlier this month)
No detail in the Google Search bar with the default launcher (search and voice search still work, just need to tap blindly)
You tell me...
TODO:
Continue to extensively test current functionality.
Suggestions?
DOWNLOAD:
AndroidFileHost Mirror
CARBON-KK-UNOFFICIAL-20151213-2320-doubleshot.zip (MD5: 023864307a38b61d154e5679b229809b)
GAPPS:
OpenGapps Mini
OpenGapps Micro
OpenGapps Nano
INSTRUCTIONS:
Download ROM above, and your favourite GApps package
Save/push files to your External SD card (preferably in the root folder where you can find it later)
Reboot into recovery ("adb reboot recovery")
Nandroid/Back up device (optional)
Wipe cache and data/factory reset
Install ROM and GApps
Wipe Dalvik cache
Reboot
Enjoy!
CREDITS:
Emmanuel U for the Ion Kernel and other repo fun
Team KitKatDS for the Device Tree and Vendor Info plus other goodies
TeamSXL
TeamHydra
SilverL
TBalden
thewisenerd
streambinder
galaxyfreak
CyanogenMod
CarbonDev
Did I miss anything? I appreciate the feedback, and any thanks as well!
XDA:DevDB Information
[ROM][EOL][CARBON][KK 4.4.4] CarbonROM (MT4GS), ROM for the T-Mobile myTouch 4G Slide
Contributors
joel.maxuel
Source Code: https://github.com/carbon-mt4gs
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.0.x
Version Information
Status: No Longer Updated
Beta Release Date: 2015-12-13
Created 2015-05-27
Last Updated 2016-08-28

Other Info...
Anyone looking to develop KitKat ROM's for the Doubleshot? This Local Manifest will give you a good start:
If looking to compile updated CarbonROM 4.4.4 for this device, you can start your build environment with:
Code:
mkdir carbon
cd carbon
repo init -u https://github.com/carbon-mt4gs/android.git -b kk && repo sync -f
Then continue all the build steps as normal.

What looks to be the first problem I encountered...camera:
/proc/kmsg
logcat
Essentially (via logcat):
Code:
D/[UCAM]CameraHolder( 9650): Open camera 0
E/CameraService( 170): CameraService::connect X (pid 9650) rejected (invalid cameraId 0).
W/CameraBase( 9650): An error occurred while connecting to camera: 0
E/[UCAM]CameraHolder( 9650): Fail to connect Camera
E/[UCAM]CameraHolder( 9650): java.lang.RuntimeException: Fail to connect to camera service
...and kmsg:
Code:
<4>[ 2831.616455] ------------[ cut here ]------------
<4>[ 2831.616546] WARNING: at /home/joel/carbon/kernel/htc/doubleshot/fs/sysfs/dir.c:455 0xc02879d8()
<4>[ 2831.616668] sysfs: cannot create duplicate filename '/devices/virtual/kgsl/kgsl/proc/9650'
<4>[ 2831.616821] Modules linked in:
<4>[ 2831.616943] Function entered at [<c010cc1c>] from [<c01940e0>]
<4>[ 2831.617034] Function entered at [<c01940e0>] from [<c0194218>]
<4>[ 2831.617156] Function entered at [<c0194218>] from [<c02879d8>]
<4>[ 2831.617218] Function entered at [<c02879d8>] from [<c0287ba0>]
<4>[ 2831.617370] Function entered at [<c0287ba0>] from [<c03c49c4>]
<4>[ 2831.617431] Function entered at [<c03c49c4>] from [<c03c51c0>]
<4>[ 2831.617553] Function entered at [<c03c51c0>] from [<c045c5f8>]
<4>[ 2831.617675] Function entered at [<c045c5f8>] from [<c0457cf4>]
<4>[ 2831.617767] Function entered at [<c0457cf4>] from [<c022c3c4>]
<4>[ 2831.617767] Function entered at [<c022c3c4>] from [<c02252d4>]
<4>[ 2831.617767] Function entered at [<c02252d4>] from [<c02265e0>]
<4>[ 2831.617767] Function entered at [<c02265e0>] from [<c0236c6c>]
<4>[ 2831.617767] Function entered at [<c0236c6c>] from [<c0238630>]
<4>[ 2831.617767] Function entered at [<c0238630>] from [<c0238d28>]
<4>[ 2831.617797] Function entered at [<c0238d28>] from [<c02266e4>]
<4>[ 2831.617797] Function entered at [<c02266e4>] from [<c0106c40>]
<4>[ 2831.617797] ---[ end trace debad88b1f20abd4 ]---
<3>[ 2831.617797] kobject_add_internal failed for 9650 with -EEXIST, don't try to register things with the same name in the same directory.
Well well well, I guess we cannot be perfect, and my work is far from done. Drat.
Guess I may have to commit this? EDIT: I did, and it made no difference.
Just for fun, I also have a logcat from bootup time. Namely of interest:
Code:
E/HAL ( 170): load: module=/system/lib/hw/camera.vendor.msm8660.so
E/HAL ( 170): dlopen failed: cannot locate symbol "_ZN7android16CameraParameters15setPostviewSizeEii" referenced by "camera.vendor.msm8660.so"...
E/CameraWrapper( 170): failed to open vendor camera module

you might need some legacy build parameters for htc camera callbackd, and maybe some patch in the camera header hw part so that the proprietary camera module could fit with the os. I think Emmanuel's repos will contain what you may need.

tbalden said:
you might need some legacy build parameters for htc camera callbackd, and maybe some patch in the camera header hw part so that the proprietary camera module could fit with the os. I think Emmanuel's repos will contain what you may need.
Click to expand...
Click to collapse
Have merged KitKatDS/android_frameworks_av with CarbonDev/android_frameworks_av into my github, hopefully that will work. I figured out the missing parameter, and see in CameraParameters.cpp that it's just a dummy function. But it turns out I needed more than just the function and the call to it. Luckily I could do an automatic merge (because I am not up for the manual way - yet).
Going to be a few more hours compiling before I can figure out if that worked (my poor dual-core PC is working hard ).
Eventually I want to get the CarbonDev commits into android_frameworks_native, but that will be a manual process (3 files to edit by hand) when I looked at the compare.
EDIT: Finished earlier than I thought. And a healthy camera init:
Code:
I/CameraService( 169): CameraService started (pid=169)
I/CameraService( 169): Loaded "MSM8660 Camera Wrapper" camera module
D/libEGL ( 252): loaded /system/lib/egl/libEGL_adreno200.so
D/libEGL ( 252): loaded /system/lib/egl/libGLESv1_CM_adreno200.so
D/libEGL ( 252): loaded /system/lib/egl/libGLESv2_adreno200.so
I/Adreno200-EGL( 252): <qeglDrvAPI_eglInitialize:269>: EGL 1.4 QUALCOMM build: AU_LINUX_ANDROID_JB_VANILLA.04.02.02.60.051_msm8960_JB_VANILLA_CL2997615_release_AU (CL2997615)
I/Adreno200-EGL( 252): Build Date: 04/11/13 Thu
I/Adreno200-EGL( 252): Local Branch:
I/Adreno200-EGL( 252): Remote Branch: quic/mako_jb_mr1
I/Adreno200-EGL( 252): Local Patches: NONE
I/Adreno200-EGL( 252): Reconstruct Branch: AU_LINUX_ANDROID_JB_VANILLA.04.02.02.60.051 + NOTHING
E/cutils-trace( 252): Error opening trace file: No such file or directory (2)
D/QualcommCameraHardwareZSL( 169): int android::HAL_getNumberOfCameras(),return how many camera 2
Torch now works as well, but when I open the stock Camera app (which is now there), I get "Unfortunately, Camera has stopped." Strangely, works fine in UCam. IP Webcam works as well, but I tried a few camcorder apps out there and neither worked.
CLEANUP of old thoughts:
Bootup Logcat
Camera Logcat
Camera Kmsg
Camera Logcat is probably the most interesting here now:
Code:
E/AndroidRuntime( 2454): FATAL EXCEPTION: Camera Handler Thread
E/AndroidRuntime( 2454): Process: com.android.camera2, PID: 2454
E/AndroidRuntime( 2454): java.lang.RuntimeException: setParameters failed
E/AndroidRuntime( 2454): at android.hardware.Camera.native_setParameters(Native Method)
E/AndroidRuntime( 2454): at android.hardware.Camera.setParameters(Camera.java:1696)
E/AndroidRuntime( 2454): at com.android.camera.AndroidCameraManagerImpl$CameraHandler.handleMessage(AndroidCameraManagerImpl.java:298)
E/AndroidRuntime( 2454): at android.os.Handler.dispatchMessage(Handler.java:102)
E/AndroidRuntime( 2454): at android.os.Looper.loop(Looper.java:136)
E/AndroidRuntime( 2454): at android.os.HandlerThread.run(HandlerThread.java:61)
W/ActivityManager( 481): Force finishing activity com.android.camera2/com.android.camera.CameraLauncher
Not sure what to try here except use the android_frameworks_av off KitKatDS, not CarbonDev's (that had the KitKatDS commits applied to it). I will work on that...compiling has started.
UPDATE: Still broken, logcat is showing the same error. Tried other cameras on this build (Google Camera), and close to the same result.
Camera logcat (Stock, Google ... *:E)
MORE: Realized an important flag was being set twice in the BoardConfigCommon.mk:
Code:
# Camera
BOARD_USES_QCOM_LEGACY_CAM_PARAMS := true
COMMON_GLOBAL_CFLAGS += -DICS_CAMERA_BLOB -DNO_UPDATE_PREVIEW -DQCOM_BSP_CAMERA_ABI_HACK -DQCOM_LEGACY_CAM_PARAMS
BOARD_HAVE_HTC_FFC := true
TARGET_DISABLE_ARM_PIE := true
BOARD_NEEDS_MEMORYHEAPPMEM := true
USE_DEVICE_SPECIFIC_CAMERA := true
BOARD_USES_PMEM_CAMERA := true
I thought maybe LEGACY_CAM_PARAMS were cancelling each other out. Recompiled (without -DQCOM_LEGACY_CAM_PARAMS), No dice.
Latest Camera Logcat. Fatal exception at line 696.
Tried some commits against frameworks/native, still no go:
Code:
E/AndroidRuntime( 2725): FATAL EXCEPTION: Camera Handler Thread
E/AndroidRuntime( 2725): Process: com.android.camera2, PID: 2725
E/AndroidRuntime( 2725): java.lang.RuntimeException: setParameters failed
E/AndroidRuntime( 2725): at android.hardware.Camera.native_setParameters(Native Method)
E/AndroidRuntime( 2725): at android.hardware.Camera.setParameters(Camera.java:1696)
E/AndroidRuntime( 2725): at com.android.camera.AndroidCameraManagerImpl$CameraHandler.handleMessage(AndroidCameraManagerImpl.java:298)
E/AndroidRuntime( 2725): at android.os.Handler.dispatchMessage(Handler.java:102)
E/AndroidRuntime( 2725): at android.os.Looper.loop(Looper.java:136)
E/AndroidRuntime( 2725): at android.os.HandlerThread.run(HandlerThread.java:61)
I forgot which camera I used for the logcat on my thread post, but if it was the Carbon one, here is what is at line 298 of src/com/android/camera/AndroidCameraManagerImpl.java:
Code:
case SET_FACE_DETECTION_LISTENER:
setFaceDetectionListener((FaceDetectionListener) msg.obj);
return;
So this may be the key. I tried a commit last night, but it didn;t do anything, trying a change to the Gallery2 app that disables the Face Detection on both cameras. We shall see how that goes...
So the latest change involving turning down face detection didn't work. Still getting the same error. A user on StackOverflow pointed out that what I was featuring from the logcat was secondary to the actual problem. That this is a more complete picture:
Code:
E/QualcommCameraHardwareZSL( 170): Invalid focus mode value: continuous-picture
E/QualcommCameraHardwareZSL( 170): virtual android::status_t android::QualcommCameraHardware::setParameters(const android::CameraParameters&): 6487, rc = -22
...
E/AndroidRuntime( 2700): FATAL EXCEPTION: Camera Handler Thread
E/AndroidRuntime( 2700): Process: com.android.camera2, PID: 2700
E/AndroidRuntime( 2700): java.lang.RuntimeException: setParameters failed
E/AndroidRuntime( 2700): at android.hardware.Camera.native_setParameters(Native Method)
E/AndroidRuntime( 2700): at android.hardware.Camera.setParameters(Camera.java:1696)
E/AndroidRuntime( 2700): at com.android.camera.AndroidCameraManagerImpl$CameraHandler.handleMessage(AndroidCameraManagerImpl.java:298)
E/AndroidRuntime( 2700): at android.os.Handler.dispatchMessage(Handler.java:102)
E/AndroidRuntime( 2700): at android.os.Looper.loop(Looper.java:136)
E/AndroidRuntime( 2700): at android.os.HandlerThread.run(HandlerThread.java:61)
So it was a parameters problem after all! I looked up continuous-picture in (my copy and KitKatDS's) frameworks_av and it is listed, and not hidden behind any #ifdef's. So it should pick up. I just don't know how to tackle this one at this point (if I ever had a clue).
Any further suggestions @Emmanuel U, @thewisenerd, @streambinder, @galaxyfreak, @tbalden? Thanks for all the help so far.

joel.maxuel said:
Have merged KitKatDS/android_frameworks_av with CarbonDev/android_frameworks_av into my github, hopefully that will work. I figured out the missing parameter, and see in CameraParameters.cpp that it's just a dummy function. But it turns out I needed more than just the function and the call to it. Luckily I could do an automatic merge (because I am not up for the manual way - yet).
Going to be a few more hours compiling before I can figure out if that worked (my poor dual-core PC is working hard ).
Eventually I want to get the CarbonDev commits into android_frameworks_native, but that will be a manual process (3 files to edit by hand) when I looked at the compare.
EDIT: Finished earlier than I thought. And a healthy camera init:
Code:
I/CameraService( 169): CameraService started (pid=169)
I/CameraService( 169): Loaded "MSM8660 Camera Wrapper" camera module
D/libEGL ( 252): loaded /system/lib/egl/libEGL_adreno200.so
D/libEGL ( 252): loaded /system/lib/egl/libGLESv1_CM_adreno200.so
D/libEGL ( 252): loaded /system/lib/egl/libGLESv2_adreno200.so
I/Adreno200-EGL( 252): <qeglDrvAPI_eglInitialize:269>: EGL 1.4 QUALCOMM build: AU_LINUX_ANDROID_JB_VANILLA.04.02.02.60.051_msm8960_JB_VANILLA_CL2997615_release_AU (CL2997615)
I/Adreno200-EGL( 252): Build Date: 04/11/13 Thu
I/Adreno200-EGL( 252): Local Branch:
I/Adreno200-EGL( 252): Remote Branch: quic/mako_jb_mr1
I/Adreno200-EGL( 252): Local Patches: NONE
I/Adreno200-EGL( 252): Reconstruct Branch: AU_LINUX_ANDROID_JB_VANILLA.04.02.02.60.051 + NOTHING
E/cutils-trace( 252): Error opening trace file: No such file or directory (2)
D/QualcommCameraHardwareZSL( 169): int android::HAL_getNumberOfCameras(),return how many camera 2
Torch now works as well, but when I open the stock Camera app (which is now there), I get "Unfortunately, Camera has stopped." Strangely, works fine in UCam. IP Webcam works as well, but I tried a few camcorder apps out there and neither worked.
CLEANUP of old thoughts:
Bootup Logcat
Camera Logcat
Camera Kmsg
Camera Logcat is probably the most interesting here now:
Code:
E/AndroidRuntime( 2454): FATAL EXCEPTION: Camera Handler Thread
E/AndroidRuntime( 2454): Process: com.android.camera2, PID: 2454
E/AndroidRuntime( 2454): java.lang.RuntimeException: setParameters failed
E/AndroidRuntime( 2454): at android.hardware.Camera.native_setParameters(Native Method)
E/AndroidRuntime( 2454): at android.hardware.Camera.setParameters(Camera.java:1696)
E/AndroidRuntime( 2454): at com.android.camera.AndroidCameraManagerImpl$CameraHandler.handleMessage(AndroidCameraManagerImpl.java:298)
E/AndroidRuntime( 2454): at android.os.Handler.dispatchMessage(Handler.java:102)
E/AndroidRuntime( 2454): at android.os.Looper.loop(Looper.java:136)
E/AndroidRuntime( 2454): at android.os.HandlerThread.run(HandlerThread.java:61)
W/ActivityManager( 481): Force finishing activity com.android.camera2/com.android.camera.CameraLauncher
Not sure what to try here except use the android_frameworks_av off KitKatDS, not CarbonDev's (that had the KitKatDS commits applied to it). I will work on that...compiling has started.
UPDATE: Still broken, logcat is showing the same error. Tried other cameras on this build (Google Camera), and close to the same result.
Camera logcat (Stock, Google ... *:E)
MORE: Realized an important flag was being set twice in the BoardConfigCommon.mk:
Code:
# Camera
BOARD_USES_QCOM_LEGACY_CAM_PARAMS := true
COMMON_GLOBAL_CFLAGS += -DICS_CAMERA_BLOB -DNO_UPDATE_PREVIEW -DQCOM_BSP_CAMERA_ABI_HACK -DQCOM_LEGACY_CAM_PARAMS
BOARD_HAVE_HTC_FFC := true
TARGET_DISABLE_ARM_PIE := true
BOARD_NEEDS_MEMORYHEAPPMEM := true
USE_DEVICE_SPECIFIC_CAMERA := true
BOARD_USES_PMEM_CAMERA := true
I thought maybe LEGACY_CAM_PARAMS were cancelling each other out. Recompiled (without -DQCOM_LEGACY_CAM_PARAMS), No dice.
Latest Camera Logcat. Fatal exception at line 696.
Tried some commits against frameworks/native, still no go:
Code:
E/AndroidRuntime( 2725): FATAL EXCEPTION: Camera Handler Thread
E/AndroidRuntime( 2725): Process: com.android.camera2, PID: 2725
E/AndroidRuntime( 2725): java.lang.RuntimeException: setParameters failed
E/AndroidRuntime( 2725): at android.hardware.Camera.native_setParameters(Native Method)
E/AndroidRuntime( 2725): at android.hardware.Camera.setParameters(Camera.java:1696)
E/AndroidRuntime( 2725): at com.android.camera.AndroidCameraManagerImpl$CameraHandler.handleMessage(AndroidCameraManagerImpl.java:298)
E/AndroidRuntime( 2725): at android.os.Handler.dispatchMessage(Handler.java:102)
E/AndroidRuntime( 2725): at android.os.Looper.loop(Looper.java:136)
E/AndroidRuntime( 2725): at android.os.HandlerThread.run(HandlerThread.java:61)
I forgot which camera I used for the logcat on my thread post, but if it was the Carbon one, here is what is at line 298 of src/com/android/camera/AndroidCameraManagerImpl.java:
Code:
case SET_FACE_DETECTION_LISTENER:
setFaceDetectionListener((FaceDetectionListener) msg.obj);
return;
So this may be the key. I tried a commit last night, but it didn;t do anything, trying a change to the Gallery2 app that disables the Face Detection on both cameras. We shall see how that goes...
So the latest change involving turning down face detection didn't work. Still getting the same error. A user on StackOverflow pointed out that what I was featuring from the logcat was secondary to the actual problem. That this is a more complete picture:
Code:
E/QualcommCameraHardwareZSL( 170): Invalid focus mode value: continuous-picture
E/QualcommCameraHardwareZSL( 170): virtual android::status_t android::QualcommCameraHardware::setParameters(const android::CameraParameters&): 6487, rc = -22
...
E/AndroidRuntime( 2700): FATAL EXCEPTION: Camera Handler Thread
E/AndroidRuntime( 2700): Process: com.android.camera2, PID: 2700
E/AndroidRuntime( 2700): java.lang.RuntimeException: setParameters failed
E/AndroidRuntime( 2700): at android.hardware.Camera.native_setParameters(Native Method)
E/AndroidRuntime( 2700): at android.hardware.Camera.setParameters(Camera.java:1696)
E/AndroidRuntime( 2700): at com.android.camera.AndroidCameraManagerImpl$CameraHandler.handleMessage(AndroidCameraManagerImpl.java:298)
E/AndroidRuntime( 2700): at android.os.Handler.dispatchMessage(Handler.java:102)
E/AndroidRuntime( 2700): at android.os.Looper.loop(Looper.java:136)
E/AndroidRuntime( 2700): at android.os.HandlerThread.run(HandlerThread.java:61)
So it was a parameters problem after all! I looked up continuous-picture in (my copy and KitKatDS's) frameworks_av and it is listed, and not hidden behind any #ifdef's. So it should pick up. I just don't know how to tackle this one at this point (if I ever had a clue).
Any further suggestions @Emmanuel U, @thewisenerd, @streambinder, @galaxyfreak, @tbalden? Thanks for all the help so far.
Click to expand...
Click to collapse
Lemme compile my own build later today and back to you, I think my github is missing something I have locally

So I just reproduced the error build on my side, I'll be playing around with it later today when I have time.
Edit: so fixed the error with the focus modes, so the camera functions. But now the camcorder isnt working properly. It records but something fails when it stops recording and it doesn't save the video. I'll keep you posted.

Emmanuel U said:
So I just reproduced the error build on my side, I'll be playing around with it later today when I have time.
Edit: so fixed the error with the focus modes, so the camera functions. But now the camcorder isnt working properly. It records but something fails when it stops recording and it doesn't save the video. I'll keep you posted.
Click to expand...
Click to collapse
That was quick! Must be only recompiling the Camera2 apk (never figured out how to do that - although never really looked - except maybe drag the project into Eclipse).
So what is the focus mode fix? I can compile with that and see if my camcorder crashes as well.

joel.maxuel said:
That was quick! Must be only recompiling the Camera2 apk (never figured out how to do that - although never really looked - except maybe drag the project into Eclipse).
So what is the focus mode fix? I can compile with that and see if my camcorder crashes as well.
Click to expand...
Click to collapse
You should always steer away from hacking ROMs to fix an error, as the issue is usually on your side. https://github.com/KitKatDS/android...mmit/6ec8fea20ce4ef854f634b4ad0389986b9e4eb2e

A new rom for my old MyTouch 4G slide?

Dukenukemx said:
A new rom for my old MyTouch 4G slide?
Click to expand...
Click to collapse
That's right.
I wanted to see what compiling from source is like, and since my daily driver (Fx3Q) has a few bits needed before development can be fruitful (need device tree), I figured I would build for the Doubleshot.
As Emman has pointed out, there are so many competing priorities with the newer ROM's thanks to newer devices that older devices can barely keep up and maintain their mark in the existing code.
I don't have the skill set to change that problem, but I will go along and debug away.
This ROM doesn't make any promises, it's just a change in perspective (presenting CarbonROM instead of having CM as the only KitKat ROM). And if I get bored enough in a months time (assuming the major bugs are squashed - I sure hope so), I just might try out another perspective.

So this is my current logcat.
I'm concerned about this line
Code:
E/OMXCodec( 170): [OMX.google.h264.encoder] ERROR(0x80001001, 0)
E/MPEG4Writer( 170): The number of recorded samples is 0
That hex error code points to OMX_ErrorUndefined. I'm thinking I'm overlooking something because the road can't end here haha. I call it quits for tonight because I got a paper due in a few hours, but I'll hop back on it soon.
Edit: btw this is where the camcorder records but when trying to end the recording, it fails and it's like you never recorded a video. I have some local changes, but no point in uploading them yet because they haven't shown any signs of being beneficial. However, my change from before should fix your native_set_parms error. Later, I'm gonna remove a decent amount of unneeded lines from the camerawrapper.

I see this is now your new enemy. How are those wrinkles coming?
Possibly related (further up):
Code:
E/SoftAVCEncoder( 170): Failed to initialize the encoder: -8
E/AudioHardwareMSM8660( 170): cur_rx for pcm playback = 2
So from my view, the crash has to do with checking the video content, but finding a null file.
Makes sense, in my earlier post about finding no camcorder app that actually worked, well, I did find one that didn't crash at the outset (or ever), but it didn't record anything.
Too bad any search for "E/SoftAVCEncoder Failed to initialize the encoder: -8" comes up with four results, all unrelated to our situation.

I'll certainly keep an eye out for this rom. I'd like to bring back the MyTouch4G Slide with a working fast rom.

joel.maxuel said:
I see this is now your new enemy. How are those wrinkles coming?
Possibly related (further up):
Code:
E/SoftAVCEncoder( 170): Failed to initialize the encoder: -8
E/AudioHardwareMSM8660( 170): cur_rx for pcm playback = 2
So from my view, the crash has to do with checking the video content, but finding a null file.
Makes sense, in my earlier post about finding no camcorder app that actually worked, well, I did find one that didn't crash at the outset (or ever), but it didn't record anything.
Too bad any search for "E/SoftAVCEncoder Failed to initialize the encoder: -8" comes up with four results, all unrelated to our situation.
Click to expand...
Click to collapse
Well those errors seem to be inherent from the OMX error, earlier in the logs.

From my question in Stackoverflow:
There are several lists of capabilities that the camera HAL needs to report correctly, including the supported focus modes. The correct list depends on your camera hardware, and the HAL then also needs to accept whatever it advertises as supported. Several keys are mandatory, so just commenting them out may cause other crashes - instead, you should figure out what's actually supported, and include only those values. (Generally, anything that's KEY_SUPPORTED_* you need to set valid values to in the camera HAL)
Click to expand...
Click to collapse
Looks like we cannot just comment out/remove that line, more like remove the offending focus mode (or modes if we find more) from it.

joel.maxuel said:
From my question in Stackoverflow:
Looks like we cannot just comment out/remove that line, more like remove the offending focus mode (or modes if we find more) from it.
Click to expand...
Click to collapse
Yea we can, the problem isn't with the wrapper. That line was never supposed to be there anyway because we don't need to override the detected focus values. It's something in the framework....or else my KitKatDS wouldn't work either. I'm still on a busy streak but I'll dive into it soon I promise lol.

Update later today...
As many may know, Kitkat is end-of-life, or near EOL, depending on the ROM you use. For CarbonROM, it have been EOL for several months now (when the commits stopped occurring), but for CyanogenMod, they are still maintaining critical patches all the way down to CM10.1 (which will probably cease soon).
Because of Stagefright issues, I wanted to re-do CM10.1 at the very least. But I was plagued with build errors. I got a build, but the robbing and stealing I did in the build phase made sure it didn't boot. So it seems CM10.1 is un-buildable at this point.
I then turned to CarbonROM. Because Carbon is close to that of CM in the code, I was able to cherry-pick any new android_frameworks_av commits (where the stagefright problem(s) are found), and get a successful build.
I am pleased to say, unlike out-of-the-box (EOL) CarbonROM 4.4.4, this build is not vulnerable - at least until the next round comes out...D'Oh!
I will be uploading the build tonight. Uploaded - see 1st post.

November 14th build...
...is on AndroidFileHost at the moment, will add to DevDB later today.
In short, this fixes the SF2.0 problems. Will be updating the OP shortly.
Enjoy!

This rom is still being worked on? Does it fully work? Can I finally go back to a QWERTY phone?